Sorry for the delay guys. I almost missed the latest posts because there is so much traffic here.
The attached package could be a start for such a library. It contains a single TGraphicControl-derived arrow component. I've made it compatible with the existing TArrow in terms of properties and defaults, but disengaged it from any widgetset, and published Color and ArrowColor properties which TArrow lacks.
[...]
Vey nice!
I replaced the old TArrow component with yours. I only changed the name to TArrow and registered the component on "Industrial" tab, otherwise no changes.
I was able to remove tons of useless widgetset binding code, see r41221 yourself.
Thank you howardpc for this contribution.
This component is needed in the IDE, that is why I did not put it in a separate package. It is in LCLBase just like the old version was.
For example it is needed in the designer menu editor. The future "IndustrialStuff" package (or whatever name it has) should not be pulled in for the basic IDE compilation.
Now, the plan still is to have a new package. The components in that package would go to the same "Industrial" tab as the TArrow.
The requirements are :
1. Cross-platform
2. License is usable, LGPL or similar.
3. Not too many dependencies.
Number 3. worries me the most now.
Extracting from Cindy components is basically OK, but does it mean pulling lots of extra code with it?
If yes, then it would be better to include the whole Cindy lib.
There is also a question of positioning our project in the "market". Should we compete with CodeTyphon by including external libraries? IMO no, we have enough work with the IDE + LCL.
Yet, some light and often needed graphics components (led, semaphore etc...) could be usefull.
Jurassic Pork, what is your opinion?
Regards,
Juha