---------
*** for the record, this was written on Sep. 18, a day before the announcement was made in this forum; but never got around to post it***
---------
Hi everyone.
Sorry if you feel this is kind of a rant.... but bear with me a little...
I just recently found the GDL help center: gdl.graphisoft.com , but didn't have time to post (and I didn't find any announcement or something related)
On one hand...
I think it is great that a help resource like this comes directly from GS. Many of us know that there are a few sites with great knowledge about GDL, but the effort from GS wasn't that good in that matter. Articles seem to be well written and the code is structured.
On the other hand...
I really don't know what to think about this.
First, it shows in plain sight what many users -new or veteran- complain about: the GDL complexity. I only see four articles right now. All related to text. And three are for: set the units, create a frame and make it readable. In a way, GS is confirming what new users fear when getting into AC, be it basic or advanced:
-"I need an object to display text... with certain units, a frame and an option to rotate it or make it readable"
-"Sure thing... you just need a few lines of GDL code and a bunch of parameters."
-"Great! How many are we talking about?"
-"Oh... just a few hundred lines"
-
Look at the code in the examples from a different point of view. It is kind of ridiculous. Sometimes you need to write two hundred lines of code before a TEXT2 or RICHTEXT to tell AC what and how you want text in an object.
By this date and age, I would have thought that this should have evolved. Something like, instead of having to define and redefine in writing every single bit of options available for a text element, it should behave like an object itself, with certain properties that can be tied to whatever parameters are needed. I mean... you create parameters if you want to define the style that the text will have before you put the text because the style and the text are different things. Why?!? The user creating an object should be able to place a text element -be it from a special palette in a GDL IDE inside AC or whatever- and have every property it can have available to the user to link to a certain parameter. Because that is what you do with all those two hundred lines of code before you call TEXT2.
Want it bold? Link that property to a parameter. Want it centered? Give to user the option to link justification to a parameter. Want it with a frame? Link it to an boolean parameter instead of needing to ask AC to give you the length in meters of the current text and then moving the origin to the correct position set the pen and line type for the following commands and then call another statement so that it can draw a rectangle around the text, all this instead of having a text with its integrated frame.
It is nothing new. I know.
And second... I feel it is a dream crusher. It somehow means that GS is still thinking to keep GDL in its current form: write everything in notepad style windows, save and check outside its development environment, and reopen and look for the errors if it doesn't work and rewrite. I don't think or know if GS would spend the effort in creating a GDL helpcenter -no matter how simple it was to create- and post more structured GDL examples for users if it was thinking of evolving the GDL core of AC.
Thanks.
I feel better now.
Best regards.