Hi James,
Using dojo it's a very different approach. The idea of using dojo is to
use everything that dojo gives...
I think it has powerfull features:
* Full support for lots of widget (calendar, hour,
autocomplete text fields, etc).
* Theme support. It automagically draws beautiful
widgets with different styles.
* Fully interaction between dojo and wicket. Via ajax.
It's great you can interact without reloading anything.
* Support for mobile devices.
Thought I have some doubts about interaction between your metadata
implementation and the one I have in place. Mainly because what I
explained about the hibernate metadata (that is very robust). It also
support automatic search.
https://github.com/gadLinux/Level2-CLT-Segmentator
It builds a query search for the whole database. Also still in alpha...
I will setup some screenshots so you can see it in action. Have to port
to dojo also. :D
Too many things as I said.
Tnx again.
El mié, 01-06-2011 a las 16:43 -0400, James Carman escribió:
> On Wed, Jun 1, 2011 at 3:41 PM, Gonzalo Aguilar Delgado
> <gagui...@aguilardelgado.com> wrote:
> >
> > Your project looks good. Clean code, modular, well organized. I got a
> > little bit confused about the PropertyComponentFactory. I cannot find
> > where you define the right provider... Was looking into configuration.
> >
> > In the code it takes to an interface. But not implementation, I looked
> > around and seem to find one.
> >
>
> PropertyComponentFactory isn't something that you'd be implementing as
> an "extender" of the framework most likely. You'll be adding your own
> property editors. For an example of how to do that, take a look at
> the Joda stuff probably.
>
> > The idea is great, everything is pluggable. Even property editors as I
> > can see in the example.
> >
> > The use of your other library, metastopheles, is good enough. The
> > problem with it will be automatic detection of links (foreign keys) to
> > other clases, specific database types and so on. Something that is
> > resolved just sticking to hibernate metadata (I only want one
> > persistence engine for now).
> >
>
> Right now, Wicketopia doesn't support automatic editing related
> entities. It's on the to-do list for sure. Basically, the next big
> thing for Wicketopia would be a "search" abstraction. Because, to
> find an entity to associate with the entity you're editing, most
> likely you'll be doing some type of search (unless it's just a
> drop-down, but that will not be the case when there are many objects,
> obviously).
>
> >
> > Will you discuss about integrating it with dojo libraries?
> >
>
> Sure will! Alexandros Karypidis is working with me on Wicketopia
> right now. He showed interest by wicket-1.5-izing Wicketopia, so I
> just gave him access to SVN and let him have at it. If you want to
> add a dojo module, as long as its scope makes sense to be part of the
> framework itself, I see no reason why you can't be made part of the
> team! I don't plan on maintaining this thing all by myself. The more
> the merrier, I say! We just have to make sure we keep our approach as
> user-focused as possible, because Wicketopia is intended to be used by
> other folks, not just us. :)
>
> What exactly is it that you want to do with dojo that you can't do
> with the built-in ajax libraries? Are you thinking of using a
> specific dojo component of some sort?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
