Frederick,

<< I would like to see a lot of improvements in the code editor:- >>

I have your original post on this, so I think I've got all of these, but I will double-check, thanks.

Tim Young
Elevate Software
www.elevatesoft.com

Matthew,

<< Type full file in project manager to select it (or type part of it). Not just the current single letter which is not too handy >>

Whatever is in the Project Manager at this time is just the default treeview functionality, so it's not surprising that it's not very useful.

<< Ctrl-Click to go to class definition (looks like that is in!) >>

Actually, right-click/Find Declaration is, but not Ctrl-Click with the underlining.  I'll be adding that when I make the UI modifications to the IDE and we re-do the manuals/screen shots.

<< Keep the layout and other items open in the object inspector when I move from component to component. Perhaps optional, but too much time is spent digging into the multi-level properties. Layout, font, margins, forever opening them. Particularly when editing themes, and you want to change the borders, and you click on something and it closes, so now you have to click a hundred times to open them up again (I exaggerate only slightly). Leave them how I left them. Perhaps a button to close all or something. Big productivity gain! >>

This is partly there right now.  The IDE will attempt to keep the current property open if the component that you're switching to is an instance of the same class type.  But, it won't work for disparate components.

<< But I also agree that theme colouring would be good. Some way to either pre-process or define a set of colours for borders, primary text, secondary text, and perhaps border effects too but less important than colours. Most of my theme changes are applying a colour to the borders and panel headers for consistency. If we could use clThemeText and clThemeBorder and clThemeBackground that would be very nice.>>

Yes, that is the basic idea.  In general, it would allow you to inject custom color names into the IDE for usage with your projects/control interfaces.

Tim Young
Elevate Software
www.elevatesoft.com

Matthew,

<< I'd really like bookmarks like Delphi has, but even if only one that would be good. Ctrl-K + Number to set, Ctrl-Number to jump. I use Ctrl-0 a lot in Delphi to mark where I am in something, and then jump back. Could be within a file or whole IDE (probably better option). I often am doing something when I need to go look it up. Drop bookmark, go find, then return. Right now my "drop bookmark" is the letter 'd'. Put one of those in the code, and go find what I want, then Ctrl-F9 to return to where I was (compiler error, thanks!). >>

Noted, but as an addition: you *can* use Ctrl-Z to go back to where you were after a Find operation in the code editor.  However, it only works within the current code editor window.

Tim Young
Elevate Software
www.elevatesoft.com

Matthew,

<< Just had a thought - string obfuscation. It might be nice to have a mode where all plain text strings are obfuscated too, not just functions. >>

Hmm, I'll have to think about this one...

Eventually, the idea is to have client debugging in the IDE via Chrome.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> Eventually, the idea is to have client debugging in the IDE via Chrome.

That would be nice, though perhaps less essential than it might appear. It is already easy to use the debugging to work out what is going wrong (nil values etc).

--

Matthew Jones

Tim Young [Elevate Software] wrote:

> << Keep the layout and other items open in the object inspector when I move from component to component. Perhaps optional, but too much time is spent digging into the multi-level properties. Layout, font, margins, forever opening them. Particularly when editing themes, and you want to change the borders, and you click on something and it closes, so now you have to click a hundred times to open them up again (I exaggerate only slightly). Leave them how I left them. Perhaps a button to close all or something. Big productivity gain! >>
>
> This is partly there right now.  The IDE will attempt to keep the current property open if the component that you're switching to is an instance of the same class type.  But, it won't work for disparate components.

Indeed, but partly is not what I want. I usually have to click on another component or something first, and that closes the tree. Just leave it open, or rather, just re-open things as I left them. Always! It really is a time eater, and fiddly one at that.

--

Matthew Jones

Teeny issue that sometimes annoys - Ctrl-Left in the editor to move words often jumps two words at the start of a line or something. So I often have to go Ctrl-Left, Ctrl-Right to get to where I want. Ctrl-Right is always good.


--

Matthew Jones

Matthew,

<< Indeed, but partly is not what I want. >>

Yes, I got that.

It is not a particularly simple issue to solve, though, which is why it hasn't been done yet.

Tim Young
Elevate Software
www.elevatesoft.com

Matthew,

<< Teeny issue that sometimes annoys - Ctrl-Left in the editor to move words often jumps two words at the start of a line or something. So I often have to go Ctrl-Left, Ctrl-Right to get to where I want. Ctrl-Right is always good. >>

This is actually a bug report.  If you come up with the circumstances under which you can get it to occur, just email me and I'll make sure that it's fixed.

Tim Young
Elevate Software
www.elevatesoft.com

Matthew:
Yes. Its in the EWB book and isn't that hard to do. However, I left them in there as I know Tim would like to have an integrated solution out of the box.

I would suggest things like this can be part of the EWB ecosystem where users can share components easily so Tim can spend his time more innovatively.



"Matthew Jones" wrote:

Trinione wrote:

> 6 - HTML Editor
>
> 7 - Charting

These are easily applied already with external modules FWIW. I've used both HTML editor and charting using the method in the EWB book.

--

Matthew Jones