Update: 2015 Beta1 (free for everybody)

[Karlis]

Today we are silently releasing WeBuilder 2015 Beta. Beta will be only available for the WeBuilder; Rapid CSS, HTMLPad or Rapid PHP will come as later betas or production releases only.

WeBuilder 2015 Beta is free for everybody, it expires in January, 2015.
Get it from http://download2.blumentals.net/webuild2015.exe

What's new + Roadmap?
Read - http://www.webuilderapp.com/whatsnew2015.php

Installing WeBuilder 2015 beta
Version 2015 can co-exist with WeBuilder 2014 and it is installed in a separate folder by default. Most settings are shared between versions and you can use both versions. Version 2015, should not alter your old version 2014 settings. Be careful with uninstalling any version (new or old) of WeBuilder. Make sure you choose to keep your settings when prompted by installer.

How can I contribute when using Beta version?


* It is important that you report any bugs via our new support website (http://www.webuilderapp.com/support-contact.php) mentioning that you are using Beta version.

* Beta most likely will contain bugs and every bug you find is a success if you report it to us.

* Please contact support ONLY regarding bugs, errors and obvious misbehaviour. (Do not send us e-mails with content like "I do not like the splash-screen" or "why did you not add the features I requested?")

* If you have some comments or thoughts that are not bug reports, please DO share them, but only in this forum or over the Twitter.

* We have very limited resources and support staff is overloaded already. We will appreciate if you give precise and detailed step-by-step problem reports to maximize the efficiency of the communication.

Thank you!

[Aivars]

Additional note: when reporting bugs it would be helpful if you mentioned if it's a new bug or one that also existed in the 2014 version. Thanks.

[Alextocode]

Yeha. Finally :)
Will download right NOW! Very curious what it will be looking and working now.
btw, I'm user of WeBuilder 2014, how much will be an update to 2015 after beta?

Hope I can give some contribution feedbacks, but knowing me, I'll find something to nag about :)

[user753]

Looking awesome!

Really would like the "X" on top of tabs to close the file. ;)

[Aivars]

We considered this carefully but there's a problem and it's a biggie. The component that we use for tabs is not easily customizable and while it does support X for closing the active tab, there are gotchas. Let me demonstrate so you know what I'm talking about.

This is without X:

tabswithoutx.png (4.54 KiB) Viewed 23869 times

This is with X:

tabswithx.png (4.11 KiB) Viewed 23869 times

As you see, the tabs are wider when close button is used and that makes less tabs visible in the same space. Also, that's probably not what you wanted anyways, I suppose you wanted X on all tabs. So it is what it is, we'll return to this for the next big version and try some other ideas.

[drexbg]

Hi, very happy for the FTP tree, thanks.
I think that the regular expression is not working as expected in the custom highlighter script. Especially, when I try to match the upper case letters.
I wanted to highlight the constants usage with different color in the php code but it not worked as expected or I didn't made the regular expression as it should be?

I added a new token:
Token=tphpconst

then the rule:
// constants
shtmlPHP [A-Z][A-Z_]* shtmlPHP tphpconst

Since the constant usage is similar to idents, I edited the rule fro idents and removed upper case patterns and it is as below:
// idents
shtmlPHP [a-z][a-z_0-9]* shtmlPHP tphpident

I added the rules for the constants after the idents declaration, e.g:

// idents
shtmlPHP [a-z][a-z_0-9]* shtmlPHP tphpident

// constants
shtmlPHP [A-Z][A-Z_]* shtmlPHP tphpconst


And here is a sample code to test

<?php

define( 'MY_CONSTANT', 'some value' );

function example_function() {
// Nothing to do here
}

// the below usage of the constant should be highlighted different that example_function() used above
$my_var = MY_CONSTANT . ' more text here';
?>

[Aivars]

You can somewhat fix it by changing
State=shtmlPHP
to
State=shtmlPHP,CaseSensitive

but the result won't be great either, see screen:

consthighlight.png (15.49 KiB) Viewed 23852 times

And I don't think there's a lookforward built into the parser to remedy this unfortunately.

[drexbg]

Aivars, thank you very much for State=shtmlPHP,CaseSensitive info.

But I was able to fix some of the issues you mentioned by editing the rules. Here are my current rules, in case someone else need them:

// idents
shtmlPHP [a-z_A-Z][a-z_A-Z0-9]* shtmlPHP tphpident

// constants
shtmlPHP [^a-z][A-Z][A-Z_]* shtmlPHP tphpconst

Only the "ALL UPPERCASE" class and function names are not working correctly. But it is OK for my since I never use all uppercase functions or class names + standards are to use CamelCases
This issue can be resolved too since we know that characters { and ( are used after class and functions declarations and if we can somehow ignore the matches if the mentioned characters come after.
Anyway, my solution is OK for me. Looking forward for the final release.

[user753]

[quote="Aivars"]We considered this carefully but there's a problem and it's a biggie. The component that we use for tabs is not easily customizable and while it does support X for closing the active tab, there are gotchas. Let me demonstrate so you know what I'm talking about.[/quote]

Prob 2 ways you can do this. Give the option to turn on/off in Options > Preferences > Other

Or do multiple rows like Notepadd++ does:

http://i.imgur.com/SBXygEF.png

[quote="Aivars"]
As you see, the tabs are wider when close button is used and that makes less tabs visible in the same space. Also, that's probably not what you wanted anyways, I suppose you wanted X on all tabs. So it is what it is, we'll return to this for the next big version and try some other ideas.[/quote]


I, for one & a lot of other programmers I know, like to have my IDE clean of files and keep 3-4 tabs open at maxed so I don't get overwhelmed and can focus on the few files I'm working on... so that space issue probably wouldn't matter.

All in all, the 2014/2015 updates with the FTP/File explorer, Plugins, & Framework additions have made me drop all my other IDE's including PHP Storm for WeBuilder. Keep up the great work guys!

[MikeyB]

Is it just me, or on two posts by Aivars does anyone else see the message:
"You do not have the required permissions to view the files attached to this post."

Looks like Aivars has attached some screenshots but I cannot see them!

[Aivars]

These forum permissions are quite confusing but I think I got it now.

[MikeyB]

These forum permissions are quite confusing but I think I got it now.

Permissions are always but looking good now, can see your attachments.