[Thyapi-developers] Congrats on new release. Some comments.

[Leif W <war...@us...>]

Hello,

Congratulations with your second release.  I've barely had time to 
preview the first, and here's a new one.

* You need to include the GNU LGPL license file with each and every 
distribution.  All of your code must state that it is licensed under the 
LGPL at the top of each source code in the library.

* It'd be nice to mention more prominently that ThyAPI is based upon 
DynAPI, to give credit to all those dozens of developers that came 
before us, and not trivialized or take for granted their work.  Give 
proper respect.  Many of the core code still has the DynAPI and license 
comments, which is good.

* The naming convention I have mixed feelings about.  I understand the 
importance of treating all life forms as sacred, to make people more 
aware of the ones in danger.  But this is software and the names remind 
me of the annoying and obnoxious Microsoft tradition to call their 
software strange things that have nothing to do with anything and make 
it difficult to distinguish between products.  Personally, I need to see 
numbers or dates, I need to know what version is newer than another.  I 
need that number or date to come after the package name and before any 
superfluous descriptive name, so that it sorts nicely in my file folder, 
or on your SourceForge download pages.  Even if you plan to release a 
TXT file or HTML matrix of all versions, it requires too much time and 
energy from my already short supply.  perhaps a compromise, like 
package-version-genus-species or preferably 
package-version-date-genus-species.  I realize that this necessitates 
making the numbers more important than the animals, and may have 
detriment to the attention it brings in the early releases.  But later 
on when you have 50 old versions, it won't be such a nightmare.  :p

* Looking forward to learning how to backport any browser-specific bugs 
to DynAPI proper.

* Wondering how you handled the automatic documentation system.

* I am still waiting for examples.  :p  Descriptions are great for a 
reference manual, but I have no idea about any of that.  I am a visual 
learner.  I learn by seeing pictures, or by dynamic examples with well 
documented code.

Well, keep up the good work and best regards to you all,

Leif