> On a more reflective note, if I were Aparajita, I'd think twice before > promoting the idea that people should move away from implementing Active4D in > components.
> I speak non-authoritatively because I'm not an expert in the plugin API and > readily accept that my assessment of the problem may be far too superficial. One out of two ain't bad! ;-) Here's the deal. 4D has not provided a way for plugins to access variables or methods in a component. Active4D relies on access to both its own variables and its own methods. So it just can't work out of the box as a component. Can it work as a component? Yes, but you have to write some glue code in the host to make that work, and you have to remember to add glue any time you want to call a method or access a variable in *any* component from Active4D. I spent 10 months writing v5, and after that ordeal I did not have the time or inclination to write, test, and document using Active4D as a component. So it's just a matter of my limitations as a lone developer. Philosophically I have nothing against using Active4D as a component, so I am not "promoting the idea" of not doing so. If one of you wants to take the time to make an Active4D component that works out of the box, I will be grateful and more than happy to promote it in the next release. Kind regards, Aparajita www.aparajitaworld.com "If you dare to fail, you are bound to succeed." - Sri Chinmoy | www.srichinmoy.org _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
