I don't think a road map for demos is necessary. If you are interested
in a particular topic and want to write a sample application or
article that showcases it, go ahead! It will only help improve Pivot's
visibility. If a demo is interesting enough and doesn't have any
external dependencies, maybe we'll include it in the distribution, but
I don't think that should be the focus.
On Sep 4, 2009, at 11:26 AM, Sandro Martini wrote:
Hi Michael,
thanks for your comments ...
With your hints maybe the "Fast Input Demo" (or whatever we call it)
could use a local Derby DB (but only for SELECT, and not a fully CRUD
application, at least for the moment), instead of using WebQuery
(already covered as you said), or instead call static json files ...
and we shouldn't have licensing problems to bundle it with our demos.
So probably also the name and the things to show in this demo should
be updated, and described in the related Web page.
What I think it's missing at the moment is a sort of Road Map (but not
for Code or features for the next n Releases) for (User) Features
already done and covered in some Tutorial or Demo, and what we think
is important to show but currently it's missing, like the "Fast Input
Demo" proposed here, and for example another little feature (already
present in Pivot) like using a custom json file for changing colors of
the Tera skin, already present but not explained (I have a JIRA ticket
for this, but it will stay only in code, so probably could be useful
to write on this also in a Tutorial page, or in a Detailed description
of the related application, Kitchen Sink in this case).
What other think ?
Maybe for this we could ask also to pivot users mailing list, right ?
Bye
