World: r3wp

Yes - probably IDE starts with better editor.

yes, basic screen designer. Sometimes properly laying-out your screen 
takes you more time than to code support stuff :-)

Although, with the bug fixes in View, I use that editor a lot more 
than I used too. :)

Yes, GUI work for apps often takes me 75% of my time -- so anything 
to reduce that helps.

Agreed, that agg does good things to refrsh-speed :)

CArl franckly I use all the day long Crimson Editor and it's suffisant 
... but sure an IDE that allow people to manage code / AGG graphics 
animation (a little bit like flash studio ) would be top ...

(In other words, 75% of the app development time.)

I use CE as well, but often switch to use View editor to edit ftp 
files

But would need better support for "macros". such that the gui-designer 
can directly interact with the code.

What I like about view editor is:  editor system/options, editor 
http://www.rebol.net, etc. ;)

CArl it depend how shaped you want the UI ...  people in general 
want to pass the less time possible over the UI ...

Carl, please exlain the 75% app development time.

I think the internal editor has some potential: Multiple docs for 
example could that be easily implemented?

yes, thats cool :)

ie. how exactly is that 75% app time being spent?

do oyu think it is possible to add source-position to values? for 
the ide-version?

Graham: getting GUIs to work perfectly, when they include a lot of 
special features and scrolling, etc, takes too much time.

yes but other things like word colorisation could be very tricky 
 but it's ver usefull ;)

Can any of that work be generalised to be used again?

ah, richt text? :-)

Rich text is on the list to be provided soon.

yes? As proposed - TMD?

I can see that Gateway demo took time ...

maybe with concept like min-face, we could have derived face, which 
could use multiple text and font subobjects, not just one, like current 
face?

Yes, TMD.

Gatewa demo is really nice - always liked it ...

Actually, Gateway demo GUI took no time at all.

I wrote an authoring system and gave it to the artist.

http://shadwolf.free.fr/crimson.jpgis what I use to write rebol 
code and manage it ;)

i once tried such a source-thing. was cool, browsing with kind of 
anamonitor and jumping right to the source from there. but without 
native support needed ugly hacky markup. if native, one could jump 
from a face straight to its sourcecode.

it's very good we can configure hot links to run the script while 
you are working on it

I hope it doesn't print in black!

Carl, do you intend to release a roadmap on what is planned for the 
immediate future?

It would be good to experiment around with editor and see if it can 
deal with scripts as collections of functions, objects, data blocks, 
etc.

If you used Smalltalk editor, you know a bit more about what I mean.

a programmable editor?

Or, also... think about Mac resedit -- sort of.

More than just programmable.

no apsolutly not but a black back grounf makes the source code colored 
to be more shiny and it's less painfull than a white background ;)

I don't think it should be a priority :)

yes, too much of stuff which was promissed, so what actually goes 
first? I expect - SDK, other ports, IOS to 1.3, - what then? View 
1.4 (styles?), rebservices?, rebin?, rif?, language plug-ins? VM? 
:-)

Most people have their own favourite editors .. not going to change 
for anything.

I've seen so many editors over the years... but so few that really 
help me more than just typing of text.

thats what i mean. the trick is, don't try to be clever. load the 
library and just browse contexts.

Actually, I've given up on using just one editor.

I used to be totally emacs only.

and if you change something, load library new. then you have always 
in the browser what rebol really sees (what is in which context)

Carl Well mine I type texte manage files and run script and anamonitor 
using hot keys

only that you need somehow to go back to the source. was nice for 
error-handling too, btw :)

/me hopes Carl gets enough inspiration for next blog article here 
:-)