DNC wrote:Pointless form over function. As for making GDL more like C, I would think that would be much more development intensive than colored text, but be my guest. In the meantime it will continue to look like BASIC because it is like BASIC.
Frankly this seems to be a case of something that ain't broke and doesnt need fixing.
Vitruvius wrote:All the more reason for color-coded code, with keywords one color, variables another, and comments yet another. It makes it MUCH easier to tell what a certain word might be, and helps you notice typos more easily.
we're a community of designers grappling with programming, we're not C programmers!
david wrote:It would be great if GS added colour-coding to GDL scripts, but their text editor needs help in many other ways too. I find it very frustrating to use. One alternative is to use an external text editor and copy/paste scripts across as needed. Many text editors can be 'trained' to recognise keywords from other languages like GDL too.
Since Graphisoft have not seen fit to provide smart colourtext (as in Dreamweaver etc and Visual GDL of 1995-6, and Codewarrior) whereby colour is used to distinguish keywords, comments, parameters, strings, the poor human working with the script needs some way of distinguishing words in the script. Good java and C++ editors like Codewarrior used coloured text.
david wrote:I would personally prefer to type commands in lower case because it makes it much easier to switch between GDL and other languages. There is a strong trend to certain conventions across many languages and I think this is one reason why GS might contemplate this change.
The proposal from GS is that ALL script should be in lower case - keywords, commands, parameters etc. The justification appears to be that this is how things are in java, C etc. and its good to shake off the heritage from BASIC.
david wrote:XML is case sensitive, so "EDITOR" is not the same as "editor" or "Editor". The choice to use upper/lower case is left open, but you have to be absolutely consistent.
The new languages on the block like HTML and XML can use Upper case for keywords (FONT, STYLE etc) and lower case for strings etc, and this is a perfectly good precedent for arguing that GDL should stay with a mixture of upper and lower case.
Jay wrote:no! lets go the dreamweaver route: combined 'code' and 'design' views. a 3D 'design' window for editing your object with 3D tools (possibly the addition of 'mere' surface/polygon tools. NURBS and the like: remember we don't necessarily need object-based 3D tools in GDL as we are
The more I thought about it, the more I realized that the editor I would like to see is essentially Microsoft's Visual Basic 6 editor.
I don't think @Ed Brown is involved with this any longer - 17 years later (!) - if he is even still at Graphisoft. But, it does seem long past time to get an automatic color-coding / indenting / smarter editor for GDL - potentially a perfect project for a new Graphisoft programmer to cut his/her/their teeth on. 🙂
@DGSketcher I agree a new thread might be noticed more... sort of.. other than in the past 20 years, I think there are a few dozen threads on this very issue now. I just happened to see this 17 year old one and thought that re-activating it would drive home how nothing has changed in 17 years and that it is long past time for improvements in this area. It seems that in this forum, posting here has bumped this old thread. We'll see 🙂