Questioning about manuals ?

[Nader Belal]

Where is the place that I can propose the editing for manuals ?

For instance, right now, when revising COOR, COOR{2}, COOR{3} GDL commands, there was no mentioning that the these take effect after defining a specific body.

[Barry Kelly · Accepted solution]

Moonlight wrote:
Where is the place that I can propose the editing for manuals ?

For instance, right now, when revising COOR, COOR{2}, COOR{3} GDL commands, there was no mentioning that the these take effect after defining a specific body.

Well you have mentioned it here - someone from GS may pick up on it.

Or you could try the GDLCenter Forum ... http://gdl.graphisoft.com/forums
That is monitored more by the GDL guys from Graphisoft - at least they reply more there than they do here (for GDL problems).

Or send a support ticket to your local Archicad support people.

Barry.

[Nader Belal]

Thank you @Barrey

[Nader Belal]

@Barry

here it is

http://gdl.graphisoft.com/forums/topic/proposition-about-gdl-reference-manual

[Laszlo Nagy]

You can also make your further suggestion in this thread and I will report them to GRAPHISOFT for their consideration.

[Nader Belal]

@LaszloNagy

Here are they:

http://gdl.graphisoft.com/forums/topic/proposition-about-gdl-reference-manual

[Laszlo Nagy]

Yes, I have seen that and I will forward that to GRAPHISOFT.
I was talking about further/additional suggestions beyond the one you already wrote in that post.

[Nader Belal]

Ok, I will take this advantage to write down few things:

Manual:
1. Style: for Variable names, insert "bmat" for building materials (page 494)
2. Connection with Grasshopper, I think it's time that Graphisoft include snippets examples for GDL that is controled by Grasshopper, instead of mentioning it in Grasshopper manual only.
3. Nurbs, the examples that are mentioned in the manual is quiet obscure, better & clearer examples should be set.
4.Radial graphical hotspot, type 7 is not clear where it's place, beside, the example that is drawn should be shown in 3D, and not in 2D only.
5. Object Migration, snippets must not only mention what they do but how, may be as comment in the examples that comes in the manual.
6. GDL debugger, must be included in the manual with careful instructions of how to use it with examples.

[Laszlo Nagy]

Thanks, I will forward also these to GRAPHISOFT.

[Nader Belal]

@LazloNagy

7. Examples for cutplane{2} is deficient

[Nader Belal]

@LazloNagy

8. PROJECT2{3} needs examples

[Lingwisyer]

Moonlight wrote:
8. PROJECT2{3} needs examples

http://gdl.graphisoft.com/tips-and-tricks/explore-the-project23-command

The example object used is available in the link at the start of the page.



Ling.

[Nader Belal]

And that is why it should be included in the manual

[Nader Belal]

@LazloNagy

9. Some neat tricks related to GDL creation would be nice.

For example, the difficulty of using cutpolyA (& variants) is that there is no direct way to see them in the GDL 3D preview, but you can write this for the manual (as an example😞

Tips & tricks:
Working with CutpolyA (and variants) can be a little difficult to use since that there is no direct way to see them, especially when they don't give you the result that you wish.

But modifying the code to be prism_ compliant then by commenting the first line as seen in following example can make your work process a lot more easier ...

!cutpolyA 4, 3, 1,
prism_ 4, 1,
0.5, 0.5, 7,
0.75, 0.5, 7,
0.75, 0.75, 7,
0.5, 0.75, 7

[Laszlo Nagy]

Moonlight,
You do not need to address your posts to me, it is enough to post them in this thread. I have forwarded it to GRAPHISOFT,

[Nader Belal]

Done

[Nader Belal]

@LazloNagy

This note should have been included in the GDL manuals
https://archicad-talk.graphisoft.com/viewtopic.php?p=11333#p11333

[Nader Belal]

By the way CWALL_ command doesn't even have a tiny whiny lousy example, and in the forums there is only 4 entries, being 1 as moderately related.

[Nader Belal]

NON GDL Side Note

Graphisoft should start to ship it's API manuals as PDFs (2 to be accurate):
1. One for reference.
2. Second for first steps using API

[Ralph Wessel]

Moonlight wrote:
Graphisoft should start to ship it's API manuals as PDFs (2 to be accurate):
1. One for reference.
2. Second for first steps using API

The API reference documentation is fine the way it is:
- It comes with linkage to VS and Xcode (for interactive use)
- It's far quicker to open a small document for the info you're interested in (a PDF with the API reference would be enormous)

Is there some specific advantage you're seeking from a PDF?