🚀 go-pugleaf

I hope this doesn't come across as (too) inflammatory.

1.	The Documentation. First of all, nobody wants all three languages in one PDF. It makes searching a nightmare. It seems to be up to the user to split out the sections they want. Secondly, nothing is linked. When I see that the return type for a method is PageItem, I should be able to click on the word PageItem and go to the PageItem page. Thirdly, there is no explanation of the hierarchy of objects. What extends from PageItem? I think Adobe could learn some things from JavaDocs or RubyDocs or even Macromedia�s LiveDocs for ActionScript/Flash.

2.	The Object Model. The collection objects are a little odd. For many objects, there is a corresponding object that is a collection of the objects. So you have a Document and a Documents. What�s wrong with just using arrays?

3.	The complete lack of examples or human sounding sentences. Most of the stuff in the documentation looks like it was written by a robot. How many times have you seen this: Parent � The parent of the object. It�s also frustrating when the description of the object is just the object�s name, but with spaces. For example: DataMergeOption�s description is, �Data merge options.� GraphicLines� description is, �A collection of graphic lines.� Oh, great, let�s check out the GraphicLine description. �A graphic line.� Argh!

4.	The forums. Is there any way to show 10, 20, or 50 messages from a thread on the screen at once? I seem to only ever be able to see like 4 or 5.