Franck,
thanks for the feedback :). Here are a few specific remarks.
> * hard to make contrib in the contrib demo browser way (ie, documented,
> clean, full time job to make a good contrib, but quality have a price (time)
> !)
That's a bit surprising. If you have re-usable components in your work,
just put them in their own library. Then, from a 'contrib' skeleton
('create-application.py -t contribution') copy over the "demo" folder,
adapt the demo config.json and the code to showcase your library, and
you're good to go. The setup shouldn't take you more than half an hour.
The real effort is in writing the demo code. But this is all optional,
in the first step you can provide a contribution without any demos.
> * too few "little examples", provided by the community (all tests made in
> the sandbow should be browseable for inspiration)
What exactly do you mean with "little examples"? Code snippets that
cannot run on their own? The demos in Demobrowser are often only a few
couple of lines long, and they are complete programs. Even shorter code
is often conveyed as Playground samples (although, yes, the standard
samples are only few). Which granularity of code are you looking for?
Has it to be immediately runnable? Where do you look for it
(Demobrowser, manual, Apiviewer, ...)?
What do you mean with "all tests made in the sandbox"?
T.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
