Quote: In 2.0 the test button turns red while the code is being checked - turning back to its original color when finished.
That'll work for me!
Quote:The editor in 2.0 is a complete rewrite and does include scrollbars (in both directions).
Cool!
Quote:Quote:
* It would be nice if there was a way to highlight or colorize or otherwise mark up programming code. Having a way to make some portions stand out would be very useful.
I am not entirely sure what you are asking for here: syntax highlighting, or some way for the programmer to arbitarily highlight specific section (without regard to synax)?
Yes. Either, or both.
Quote: If that latter, could they then highlight multiple sections simultaneously?
Yes.
Quote:How long would the highlighting persist - would it go away when the editor was closed, or be retained between runs, etc...?
Retained. I am thinking that the text could be colorized/bolded/highlighted in much the same way formatting is done in other text editors. This would help distinguish specific sections of code which perform certain actions, as a way for the programmer to "jump to" the area he is concerned with, for whatever reason.
Advanced programmers read code easily because of long practice, and can quickly see what a specific section of code does by quickly scanning it. For beginners such as myself all the text "runs together" and I have to pick it apart piece by piece. However, if I could highlight all my XLookups, for example, I could ignore all the unmarked (or differently colored) concatenation code that uses the XLookup results. Just an example. I think programmers could find numerous uses for formatted code.
Quote:There has been a lot of discussion about what should be on button versus menus, versus command trees here at Lantica. We are all in agreement that the button bar is extremely valuable real estate and that decisions about what should go there should be made with great care.
I would like to see user defined commands there in SDesigner. That way the commands you use most frequently would be at your fingertips. And it would be entirely up to you to decide what command those would be. In 2.0, event macros extend into SDesigner, and could be used for this.
Perhaps a set of commands could be offered in a "customize" right-click menu, which could contain all the user-defined commands as well as the built-in, much as Microsoft Word allows the user to build his toolbar structure.
Quote:In any case, it is unlikely that icons (pictures/images) etc..., would be used on the buttons. A picture is worth a thousand words and entirely unclear as to which - nevermind the tedium of hovering over a set of button one by one to cause the tooltip to appear, in order to find out what any of them do...
I only have to hover over a new button a couple of times before I learn what they do. After that, use of them becomes automatic. I have not experienced the tedium you speak of. Words seem better suited to drop-down menus than toolbars, IMO, and the time difference between selecting a menu item and scrolling down the list as opposed to just clicking on a button (however small that time is) justifies the use of a button. Again, in my opinion. Your mileage may vary.
Thanks again for listening to my ideas.