Re: Counter Sample Showcase Update: Let's Welcome Xoetrope XUI, Flex and SwiXml

Gerald Bauer <[email protected]>
Newsgroups gmane.comp.lang.xul.general
Message-ID <[email protected]>
Hello Kevin,

> I have a question - some entries are complete in
> that they show handler
> code as well as the UI markup, and for some it's all
> together.

  Well, some markup samples are "complete" because the
contain inline code/scripts.

  If you read the XUL challenge guidelines you will
understand why. If I may quote:

  * Please create real working examples not just
pretty UI mockups.

  * Please keep the markup in challenge #1 and #2
clean and if possible avoid inline code and use
separate code-behind files instead. Note, if your
XUL/XUI/XAML/XML-UI toolkit/parser/player/etc. can't
separate code and markup go ahead and use inline code
(after all we want real working samples).
 
> While it doesn't matter too much on a simple ++/--
> application, should it
> be asked of all submissions, if at all possible, to
> be complete with
> handler code? Even for very simple applications, it
> might be interesting
> to see (and compare) the whole picture.

   I agree. We want to publish complete examples (that
is, including all handler code). As I wrote before: I
plan to check-in everything into the CVS repository
and create a new "front-page" later on so everyone can
easily browse all examples (including the code-behind
e.g. Java/JavaScript/C# sources, etc. and readme docs
and more).

   - Gerald


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.