From: Asko K. <ask...@sc...> - 2004-01-14 21:51:26
|
Rodrigo Hernandez kirjoittaa keskiviikkona, 14. tammikuuta 2004, kello 23:27: > Hello Asko, > > Well, currently the API is continually evolving, the way something is > being done today will not necessarily hold true > tomorrow, hence the version starting with 0, right now we are not > really concerned about backwards compatibility and such. I don't mean that, and I fully understand. On the other hand, the demos already work and I can already come "to par" with your C++ implementation. If you will.. > > Perhaps I am rambling on a different topic here, but anyway, I do > think the API needs a whole revision to make things > more homogeneous, get rid of some "old way of doing things" code and > to start integrating each component in a more > seamless fashion (the current widgets' author is not always the same > for each different one, different approaches, different perspectives). Yes, this will evolve. On the other hand, it's crucial that "good examples" be set early in the project since others will then -hopefully- mimic them. :) > > I'd like to see the doc, and I am sure some other developers may be > interested in it. I'll send it over, thanks. ;) > > Cheers! > > At 03:14 PM 1/14/2004, you wrote: > >> I'd like to go through the whole aedGUI API from a "user's >> perspective", any volunteers? ;) >> >> The reason is, I'm doing a scripting language interface to aedGUI and >> in a few places, it is not so clear as to what's really part of the >> API and what's not. Also, I have some suggestions as to how the API >> could be made easier to grasp. Nothing major, though. >> >> If you raise your hands, I'll send you the .doc I've done so far. >> It's got the open issues highlighted. >> >> thanks, >> - asko >> |