Just for fun and to refresh my bash skill, I wrote this little script to build
all demos (even the new ones hosted on github). It’s not as nice as the contrib
demo browser, but it let’s you try all available contributions with their
respective qooxdoo versions:
https://gist.github.com/cboulange
… as a final note: I had in mind something along the lines of (pseudocode)
for each (contrib-catalog/contributions/*/*/Manifest.json) as manifestObject
if ! manifestObject.buildDemo skip to next contrib
download and unzip file at ${manifestObject.download}
demoPath = "${manifestObject.name}/${
Hi Christian,
interesting point of view. It surely would motivate contrib
authors if all such automation would exist and I'm not denying the
usefulness of such an infrastructure. But if I would be a contrib author
(which I am not) I would also welcome as much freedom as I can get, i.e.
I wouldn
Ah ok. I don't think that external demos are good idea - again, I think
you create a stumbling block that takes away an incentive to pontential
contrib authors. If your goal is to have a lot of high-quality contribs
that fill the infrastructure with life that you have put so much thought
and work
Hi Christian,
> [...] new web interface - when will that be online?
As soon as it's prioritized again. Can't give you a date.
> [...] how long does it take until a contribution's demo
> is in the demo browser? Is that an automated process or do you have
> to manually upload the demos?
Most
Hi Richard,
thank you for the detailed information. I am looking forward to seeing the
new web interface - when will that be online?
One more question: how long does it take until a contribution's demo is in
the demo browser? Is that an automated process or do you have to manually
upload the demo
Hey Christian,
first of all thanks a lot for your feedback - it's even more valuable
cause in my mind all of your points are valid and true! :)
* documentation scattered
Short term solution:
I've added a note regarding the more current manual page about contribs.
Long term solution:
I've file
I have just updated two contributions (will announce it when they are in the
contrib demobrowser) and it made me think about why so few contributions
have been updated to the new contrib infrastructure. I think that the
qooxdoo team should invest some more time into this to get more contrib
authors
