+1 on the importance of quick user input. Perhaps an isolated tutorial
would be best for users to understand the input API.
Can the data be read from an Apache Derby (er, JavaDB) database delivered
with the app? Seems like that would cover another common use case, web
queries are already covered.
Perhaps to best isolate the topics in tutorials we could build tutorials
that minimally show deployment of different data scenarios ("Derby
Tutorial", "Web Query Tutorial", "Cato Tutorial"...). Then we could build
other tutorials on top of these? The plusses are that the code for each
topic is learned in isolation, and learning a new tutorial would build on
knowledge of learning previous ones (and code reduction too). If we agree,
I'll create a tutorial just on delivering a local db.
Maybe demos would be combinations of tutorials? For example, the stock demo
would be a good demo to leverage quick user input.
If we broke the tutorials down, then would each tutorial have an a JIRA
issue but the overall plan is on the mailing list?
Michael
On Fri, Sep 4, 2009 at 9:25 AM, Todd Volkert <[email protected]> wrote:
> The title might be more clear after you start writing it and see what it is
> you end up creating...
>
> Also, I don't know that a JIRA ticket is needed for this, but that's your
> call. Our community, including committers, can contribute demos at will.
>
> -T
>
> On Fri, Sep 4, 2009 at 9:18 AM, Sandro Martini <[email protected]
> >wrote:
>
> > Hi, thanks to all for the feedback :-)
> >
> > > I don't think you need to create a JIRA ticket for it - if you want to
> > create such a demo, go ahead.
> > Mainly I'd like to do this to keep all informations on this in a
> > single place (and visible to all), to not search in mails ... and for
> > me, to remember what to do and for what release (if possible ...).
> > So, if there aren't problems, I'd like to put a summary of this
> > discussion in JIRA.
> >
> >
> > > It could also take advantage of window action mappings (which I am
> > actually including in the Menus tutorial).
> > Yes, thanks for the trick.
> >
> >
> > >> is it possible to simulate a real Web Call, putting some
> > >> Server-side simple pages / data files in the demos webapp (already
> > >> existing, but under a dedicated directory) and call them ?
> > >
> > > You should be able to do this using web queries - just point the query
> at
> > > the static file(s).
> > Ok, but in this case I have to put the Server resources (pages /
> > static data files) to be called inside the demos.war ... is this Ok ?
> >
> > > If you are truly going to focus on showing how to implement efficient,
> > > keyboard-based navigation, might reading data from the server
> > overcomplicate the demo?
> > I think Yes ... so maybe (to not create something too complex for a
> > simple demo, at least in the first version) I could bundle inside that
> > Demo also the static data files, like in the "Large Data Sets" Demo,
> > Ok ?
> >
> > > On the other hand, demos don't have to be as targeted as tutorials and
> > can
> > > be broader in scope, so demonstrating server interaction would not be
> out
> > of
> > > the question. In that case, though, a different title would probably be
> > appropriate.
> > Ok, if someone has some more info or suggestions on this, tell me or
> > update it in JIRA.
> > And also for the title :-) ...
> >
> > Byeeee
> >
>
