Just wanted to drop a short notice...
on the status of the sourceforge stuff if you guys want
to integrate parts of it into myfaces
ajaxAutocomplete works, currently I am rewriting the javascripts because
I am unhappy about the old ones both from the cleanlyness of the code,
and the way the code is structured itself
client side tabbed panes fully working
coloring controls for client side pattern checking working since stoneage
coloring focus controls in there, sort of a proof of concept yet
demo app got a new layout, I have not done a build file yet on it or
rolled a new war, but if anyone wants to see it working I can turn on a
demo server tomorrow. Also the config files were reorganized
into a clean splitting of navigation, demo app and control faces-configs
new addition: as posted on the user list, a demo datamodel for generic
orm mappers which uses page prefetching
others which use servlet filters or other filter/listener mechanisms
will follow in the long run
ajax control panel: work currently in progress, will be done hopefully
next week.
an effects control: various effects which can be used for special
effects (straight from the prototype library)
Jan also dropped his layouting select boxes in there, should be working
hopefully havent had time to test them and to integrated them in the
demo app.
On the backend side of things:
An ajax event mechanism which connectes
the backend with the ajax controls in a clean and JSF compatible way
A script controller mechanism which resolves a javascript library
and its dependencies within the OO javascript prototype library so that
each class of the prototype library just gets one import per page
depending on the parts of the library needed.
Backend classes for auto serving all the javascripts used by the various
controls
Some demo backend beans
what is missing:
a) a better organisation of the entities (still have not figured it out
fully on how to use that stuff from eclipse, from ant, with builds into
component packs it is easy, but debugging hell)
b) ant build files
what is currently done from my side but not working yet:
a) currently a rewrite of the autocomplete javascripts is going on, so
that they will become easier to maintain, and much much more readable in
the future. I am working on a split MVC component model for this stuff
on the javascript side of things, so that in the long run for new ajax
functionality which just needs a list as view part, only the controller
has to be derived.
b) The biggest thing, which only can be implemented once (a) is fully
working is, an ajaxed panel, where you can stack several components,
define some of them as query components, send an ajax request with a
result list and upon choosing one entry having the components
automatically filled with their values.
(I got that request for my current project, because they want to have
person data automatically filled in upon the given inputs, to save input
time)
Once a and b are done I hopefully will have time to add some additionaly
Datamodels so that users have working blueprints if they need it (the
mailinglist request for how to use hibernate with JSF comes up regularily)
