WeBuilder Features/Ideas

[raymond]

Hello,

I know this is not the way to go but when I sent this list to support they responded that they could not handle the .zip attachment so I will post via the forum. Please understand.

I really like WeBuilder and do hope you continue to improve on it's quality and functionality. Looking forward to version 2008 or whatever other goodies that you have planned for the rest of this year.

What do you think about this list for features/Ideas?

Features / Ideas
--------------------------------

* Task List - A section within a project where users can write notes, comments and add tasks
* crtl + arrow keys does not navigate to the correct word or character. It should navigate to the first character of the next word in the line.
* When a a php variable is used with a quote (") the variable should be highlight. eg. $msg = "Hello $name"
* Need Code hint support for custom classes, objects and functions. The project should have a property where the user add code-hint paths to the project. The system could then search these paths for classes, objects and functions hints to be used inside the code.
* Autocomplete does not look for objects in other files. Add code-hint support should fix this
* Add feature that allows a user to navigate (or open the file) to where a variable, class or function is defined.
* Add auto complete for ASP/VB script
* Show vbscript in object explorer
* Add inline help for php, vbscript, javascript, css and html. When F1 is press the help file could be loaded in a separate tab.
* Add inline php and javascript syntax checking. something similar to inline spell checking This would make it so much easier to spot php errors.
* Add a feature that allows the user to create Project Templates - These template could then be used to create similar projects with common files and layout. For example. A user can create an html project that uses the MooTools javascript library, create folders and upload images and other files to the project folders. the user then saves the project as a template. the next time he/she wants to create a similar project they could just click on the option "Create project from Templates." The system would then create a new project containing all the files folder and project settings from the template. The project template files and folders can be stored as zipped files in the WeBuilder directory

* In addition to the Tools menu add feature to enable Word Wrap, Automatic Spell check and Block Select Mode on a per document basis.
* Slip screen feature - Ability to split the current document code view into horizontal split or vertical split sections.
* Bug: After disabling Word Wrap from the tools menu the wrapping was not disabled for open documents
* Ability to add Virtual or linked files/folder to project. This way a user can include a file/folder that's not inside the projects current directory.
* Add "Rename" menu to document tab context menu. This will allow a user to right click on a tab and rename the document
* Add support for PHPDoc tags in comment. Also add support for autocompleting a comment block. So after typing /** and pressing the enter key. the system shoul display something like this:

/**
*
*/

* Add feature to do word count and character count, selected word count. In other words this would be a feature to view the stats of the document
* Ability to preview library codes
* Shared Library - Add an option that allows developers to share there library code with others on a network or via FTP. This could be something as simple as setting the (local/network) path to where the library files are stored.
* Bug: Renaming a file in the File Explorer does not change the name of the file if it's already open. In other words the name of the file remains the same on the tab.
* Add "Back" button to preview window or screen. This can be very useful when testing a script or web app. Current only the refresh button is available
* Add feature to find matching html tags
* Remove PHP menu since it's already part of the Script menu
* Merge ASP, PHP and SSI toolbars into one toolbar called scripts which will load the appropriate buttons depending on the current document being viewed or edited
* Save state - used to save the current state of the editor including open files. It's more or less like adding a hibernate feature to the program. When reopening Webuilder the system will resume to the last saved state
* Add Cross-Hair feature to preview so that we can see were the mouse is on the ruler
* Bug: At times when saving or previewing a .htm file the system would add a file to the current folder called prev~20.htm, where the ~20 can change to any number. This sometimes a window alert to occur:

[see attached file]


* Add Auto complete to HTML tags. It appears that I sometimes have to press the ctrl+space buttons to see a popup window.
* Add Convert Script Block feature to JavaScript menu. Similar to the Convert script block used on CSS
* Add support for multiple CSS class names inside the class attribute of the Inspector. Same for auto complete.
* Add built in photo/media organizer. Maybe something like a photo library or photo gallery
* Bug: The find window not displaying a message if the wrap end option is checked and the text was not found
* The " > < Select tag content" context menu option does not work. It's selecting the content that either above or below the tags
* Integrate automatic Save/Load Open file list into project so when a project is open it will also load the list of open files.
* Add a button on the tab bar to pop out and show a list open files. This makes it easier to navigate to a file rather than to scroll left/right buttons on the tab bar
* Syntax highlight error when using '' inside the .sql files. For example 'SELECT * FROM users where name=''mary'' and age<25' ORDER BY name
* Add feature that allows a user to navigate to file were the php function or variable was defined or created. Something like a Go to Definition option
* Add support to compile an html app into an Adobe Air executable file.
* Make it easier for used to download and install additional complements such as xdebug, php mozilla preview. It would be great it these could be integrated installations.
* Add feature that allows a user to add FireBug and Web Developer extensions to the FireFox preview screen.
* Add Inspector feature to the preview screen. This would allow you to select an element inside the preview screen which would then navigate to the section of the code where that tag was generated.

* Add feature to allow developers to edit external style sheets by expanding the tag as shown below:

[see attached file]

* This same feature can be applied to <scripts> tag
* It would be nice if Auto complete could show browser compatibility tags like the way Aptana does for JavaScripts
* A WYSIWYG editor for html would also be a cool

[bandrej]

Tried to give my honest opinion to some of your suggestions (mine are bold):

Features / Ideas
--------------------------------

* Task List - A section within a project where users can write notes, comments and add tasks
Agree.

* crtl + arrow keys does not navigate to the correct word or character. It should navigate to the first character of the next word in the line.
It navigates as it is intended for a programmer's editor

* When a a php variable is used with a quote (") the variable should be highlight. eg. $msg = "Hello $name"
I never ever mix variables with double quotes. In my opinion it's bad practice. And if the behaviour of variable highlighting should be changed, I think it could screw up other programming styles. I feel strongly against any change in this direction.

* Need Code hint support for custom classes, objects and functions. The project should have a property where the user add code-hint paths to the project. The system could then search these paths for classes, objects and functions hints to be used inside the code.
Autocomplete works just fine since version 8.1. It works also with included files.

* Autocomplete does not look for objects in other files. Add code-hint support should fix this
See my previous answer.

* Add feature that allows a user to navigate (or open the file) to where a variable, class or function is defined.
Agree, e.g. a ctrl+click on var/class/func would take you directly to it.

* Add inline help for php, vbscript, javascript, css and html. When F1 is press the help file could be loaded in a separate tab.
IMHO not really needed

* Add inline php and javascript syntax checking. something similar to inline spell checking This would make it so much easier to spot php errors.
This would also mean a significant increase in application size + much longer load times. I'm having second thoughts about this. I mean - it would be cool, but at what cost?

* Add a feature that allows the user to create Project Templates - These template could then be used to create similar projects with common files and layout. For example. A user can create an html project that uses the MooTools javascript library, create folders and upload images and other files to the project folders. the user then saves the project as a template. the next time he/she wants to create a similar project they could just click on the option "Create project from Templates." The system would then create a new project containing all the files folder and project settings from the template. The project template files and folders can be stored as zipped files in the WeBuilder directory
That would be cool, but I think WB needs some other features more. I would postpone this one for a later time.

* In addition to the Tools menu add feature to enable Word Wrap, Automatic Spell check and Block Select Mode on a per document basis.
IMHO - that would make things really really complicated. Against that!

* Ability to add Virtual or linked files/folder to project. This way a user can include a file/folder that's not inside the projects current directory.
Again - my previous answer.

* Add "Rename" menu to document tab context menu. This will allow a user to right click on a tab and rename the document
You have to enable the File explorer for this one (view->File Explorer). Right click on the file in File Explorer -> Rename.

* Add support for PHPDoc tags in comment. Also add support for autocompleting a comment block. So after typing /** and pressing the enter key. the system shoul display something like this:
Click on PHP -> PHP Comment Block OR you could define your own snippet. Yes, WB is full of surprises...

* Ability to preview library codes
Not really sure what you mean mate...

* Shared Library - Add an option that allows developers to share there library code with others on a network or via FTP. This could be something as simple as setting the (local/network) path to where the library files are stored.
....OR you could simply have the ability to just export and import library files in eg. XML form...

* Add feature to find matching html tags
Agree, this would be helpful, although in my opinion is really not critical.

* Remove PHP menu since it's already part of the Script menu
Try right clicking on the menu, then click customize. Have fun!

* Merge ASP, PHP and SSI toolbars into one toolbar called scripts which will load the appropriate buttons depending on the current document being viewed or edited
Again - previous answer.

* Save state - used to save the current state of the editor including open files. It's more or less like adding a hibernate feature to the program. When reopening Webuilder the system will resume to the last saved state
I think configuration is not saved on exit, but rather on any change you make, which makes the "save state" function really unnecessary.


* Add Auto complete to HTML tags. It appears that I sometimes have to press the ctrl+space buttons to see a popup window.
Not sometimes... every time. It's not a bug. It's a feature.

* Add built in photo/media organizer. Maybe something like a photo library or photo gallery
Awww, c'mon. I would really like a 120mm howitzer built into my car. But then it wouldn't be a car anymore, would it?

* Integrate automatic Save/Load Open file list into project so when a project is open it will also load the list of open files.
For that you have possibility to create Projects. You're just trying to make a mess of things. Explore the possibilities first.

* Add a button on the tab bar to pop out and show a list open files. This makes it easier to navigate to a file rather than to scroll left/right buttons on the tab bar
Try clicking on Windows menu. It will show you a list of opened files.

* Syntax highlight error when using '' inside the .sql files. For example 'SELECT * FROM users where name=''mary'' and age<25' ORDER BY name
WB DOES NOT support SQL yet! It does have some highlighting abilities, but yes - they are limited.

* Add feature that allows a user to navigate to file were the php function or variable was defined or created. Something like a Go to Definition option
Yes well, you already mentioned that.

... just skipped some internal preview suggestions here, which i don't use...

* A WYSIWYG editor for html would also be a cool
Yes, must agree with this one, but that's a really really long shot

[syrupcore]

quite a list. quite a response. I'll try a few.

wysiwyg html. what a can of worms. that's what dreamweaver is for and that's why dreamweaver costs so much and has a massive support team. this is a nerd's editor!

"* Add inline php and javascript syntax checking. something similar to inline spell checking This would make it so much easier to spot php errors."

Agree that the overhead isn't worth it but integrating with existing tools is inline with the direction the blumentals teams is already headed. Including convenient links to online or offline syntax checkers (like JSLint) seems reasonable.

I've heard karlis mention the possibility of an online Snippets repository in the past. I get the feeling it's something they'd like to do but are having trouble finding the time. It would be very cool.

you can sorta find matching html tags now by choosing 'select tag block'. Also, keep your html simple and it's a lot easier!

ctrl+arrow has come up a few times on the forum. It seems that everyone has a different idea about it. It was mentioned at one point that they may make it a configuration option to change the default behavior. No idea of the status.

Agree 100% on $msg = "Hello $name" being a really bad idea. If anything, the editor should encourage good coding practices, not lazy ones.

I love this request:

* Add feature that allows a user to navigate (or open the file) to where a variable, class or function is defined.

for heavily MVC based apps, it would save some time.

Honestly, the project templates request just seems a little lazy. I use project templates everyday. I have a template and when I need to a new project, I copy the template folder in Explorer and rename it. Then I make a new project in WB and point it to my new folder. done.

" * Add support for PHPDoc tags in comment. Also add support for autocompleting a comment block. So after typing /** and pressing the enter key. "

I agree that snippets are the answer here but also would love to see autocomplete connected to multiline snippets. so you could in fact just type /** and have it render a snippet from there. This is me sneaking in my own request. sneaky sneaky man.

Adobe air? c'mon. Again, a third party compliler seems like a reasonable possibility.

"* Add feature that allows a user to add FireBug and Web Developer extensions to the FireFox preview screen. "

I've suggested it a few times. I think it would be the single greatest enhancement from your list. It would allow so much code introspection and wouldn't cost the blumentals team a dime beyond integration development. Blumentals team, if you haven't yet tried firebug, please do: http://www.getfirebug.com/ I can't really remember life before firebug.

Will

[bandrej]

I can't really remember life before firebug.

... but seriously: there WAS a life before firebug?

[raymond]

Many thanks for the feedback guys.

I hope the dev team will be able to implement a few if not all the "needed" features

[raymond]

On other thing...

I think it would be nice if WeBuilder supported plugins so develoeprs can extend the platform just like how it's possible with Aptana

[raymond]

Hello,

I also think it would be great to add RegEx support inside the Replace With field when doing a Find & Replace search.

[chrisjlocke]

Plug ins would be a neat 'solution' to the bloat issue. For every "Hey, can WeBuilder do this?" there are 10 people who don't want that feature, and don't want the 'bloat' of unnecessary bits. I guess its the philosophy behind Firefox - give 'em the basics, and let 'em bloat it out if they want!

Some nice feature requests though.

[syrupcore]

totally agree on the plugins part. Particularly the anti-bloat aspect.

[raymond]

Thanks for the feedback guys.

IMO I think WeBuilder as is now is just great! I mean, I use almost every feature available. Maybe not on a requalr basis but every now and again.

Anything that might be considered bloated then it can be made into a plugin (e.g. An Adobe AIR app compiler plugin)

[raymond]

Will Webuilder 2008 support the Adobe AIR runtime? It would be great if it offered the ability to compile or run html files in AIR. Maybe a nice UI for configuring the application.xml file could be great!

[fuzzylogic]

Agree 100% on $msg = "Hello $name" being a really bad idea. If anything, the editor should encourage good coding practices, not lazy ones.

Well, I totally disagree 100%

Different languages take different approaches to things. String handling happens to be something that php is good at, there is nothing bad about it. if you are used to other languages then I suppose it would seem strange and inefficient. but this is a legitimate part of the php way of doing things which is different from how you do it in other languages.

But consider the following:

$txtOut = "$First, $Last: $Code.$Title. $Other\n";

versus

$txtOut = $First .', '. $Last . ': '. $Code .'.'.$Title.'.'.$Other."\n";

now you tell me which one is more readable, and also did you notice that there is an error in the second version? can you spot it? I think not easily. The second version is much longer and the result is much harder to comprehend. The mistake was unintentional, but I decided to leave it in as an example of how much harder it is to format a zillion pieces. If this is the wrong approach to creating a formatted string, then why would designers bother with constructs like sprintf ?

From some docs I have read, my understanding is that there is no speed penalty for php to parse the first example, in fact it might even be faster then dealing with all those transitions/appending of the separate quoted strings..

Yes, parsing inside of the strings for syntax highlighting, would be a challenge because you would have to replicate a certain amount of php syntax for dealing with escaped $ and brackets, but it's not any more complex that any of the other parsing that is being done.

[belgar]

Well, whether you believe mixing variables in double or single quotes is bad coding or not, give us a choice to use that feature (variable highlighting) or not. Not have a customer tell those that want it you can't have it. The feature has been built into many lesser IDE's, why not Blumental products? I want this feature in what is otherwise an excellent work environment.