By the way: DWR is under the ASL, no licensing problems here for sure! regards,
Martin On 6/22/05, Werner Punz <[EMAIL PROTECTED]> wrote: > Richard Wallace wrote: > > Werner Punz wrote: > > > >> Richard Wallace wrote: > >> > >>> Actually, on reflection, I can't really think of a good way to get > >>> everything I want for free anyways. I think I will need to develop a > >>> custom component, probably something that is composed of other > >>> existing UI elements. The three primary use cases I'm looking at > >>> currently are a dynamic, editable table with at least 2 text fields > >>> where rows can be added/removed without the need to roundtrip to the > >>> server, an editable, dynamic table with a drop down list and a text > >>> field in a row where rows can be added/removed without roundtripping > >>> and an element where a user can add multiple file upload elements > >>> without having to roundtrip. i don't really see a way this can all > >>> be done in JSF without using custom elements. > >>> > >>> Of course, I'm open to suggestions. > >>> > >> > >> Not really suggestions, I see it as you, there is no real free lunch > >> in this case, but hard work. > >> > >> But there is a small project on sourceforge which already has an ajax > >> component in place, not something as sophisticated as what you want to > >> do, but you can check it out it might give you a headstart with your > >> things (and also a small push towards donating code yourself if you > >> want :-), your components sound interesting ) > >> > >> > > I have looked at those components. Very neat. I'm a little curious why > > you didn't use the DWR library > > (http://www.getahead.ltd.uk/dwr/index.html) for doing the AJAX stuff. > > I'll definitely consider donating the code and it shouldn't be a > > problem, just have to clear it with the higher ups. > > > Easy answer, the ajaxed autocomplete was adapted under a lot of time > pressure and I was totally new to the Ajax stuff. It basically came > as a side requirement for a project with an extremely tight schedule. > So I basically took the easy approach and looked for preimplemented > solutions, which I found halfway in the sun blueprints. I basically > adapted the component, fixed the javascripts to the degree that they > also work with the IE, added keyboard handling and let them out in the > wild, because I had to move on projectwise, to keep the schedule. > > I am however not very happy with the autocomplete/ajax javascripts as > they are now. My long term plan is to clean up the javascript mess, of > the autocomplete control and move it towards the prototype library, or > something similar. > The prototype library is very interesting, because it is under a very > free licensing (MIT) and is heavily driven by rails (thus under very > active development) and overall very cleanly written. > > As for DWR, I was not aware of that one until now, if I had known that, > I probably would have started with that one instead of the blueprints. > I will look into it, it looks really promising. > >
