Hello, > So, with the examples, is it only just the XML code > or are we allowed to include the business logic that > tends to drive the user interface with event > handling (again as several of the XULs do)?
I suggest that you include everything, that is, XUL/XUI/XAML code and your code-behind/backend code. I also suggest including a short readme docu in plain text that outlines how to start/run your sample and where to download your toolkit/parser and where you can find out more. - Gerald PS: I just rethought the directory layout. I think it's best if everybody takes charge of their own directory/module. e.g. purnama + counter + calc + ... myxaml + counter + calc + ... If we use a directory layout like counter +- purnama +- luxor +- ... browser +- purnama +- luxor +- ... I think it will be too much hassle to check in your examples because they are all spread over the place. One option might be to use a common root directory e.g. challenge2004 and everybody checks out everybody else's code so you end up with a "single" module again. Let me know if you want to check in your own code or if you want me to play admin so that I collect your code samples send in by mail that I check in later all at once. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ xul-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xul-talk
