Hi Thomas, I'm cutting your post a bit for better reading...
> [...] > Exactly! To make it more tangible I'd like to get back to Peter's > posting. If you look at his text file... > [...] > and then at the generated XML for the same class: > [...] > it looks like it would be straight-forward to XSLT the XML into the > target format. (Only thing missing are the "// <num>" parts of the > method lines; are these line numbers? Could you do without?) Yes (to both questions ;) ). The line 'number comments' were left in for debugging reasons. Please do also note that the file I attached should be seen as an example; It has many flaws as well (are Properties listed?, can comments enhance the aptana-usage?, etc. pp.) > Maybe we should set up some project infrastructure for efforts like these?! I would welcome any progress in this 'project', but I'm afraid to be of little help. But I will continue to look at the progress and try to help. As you proposed, something like <code> #> make api #> make aptana_api </code> would be veeeeeery nice! By using the same generator that is used for the API, users can both build "code assist file" for qooxdo-API only _and_ for their complete project. Regards, Peter ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
