Currently we do kind of lazy loading and attaching which IMO is not
bad. But it simply does not meet our requirements. So there is only
one conclusion; we have to change it. Because of the work involved
it'll definitely take some time to do, and unfortunately I currently
do not have  plenty of them. We first thing we should do is create a
new branch and have a first draft to play with.

Juergen

On 8/27/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> Well... I think the DatePicker case alone is not enough to justify a
> lot of work. But the added functionality in general can be a big help
> when building compound components, and - even more important - as I
> understand it, we need to have the markup position to be able to
> render components isolated. Which is what we need for Ajax...
> 
> My guess also is, is that refactoring that part would make the
> workings of Wicket much more transparent. I never really liked the
> time-dependency that comes with the markup parsing thing. If that
> would be gone, we would have a clear seperation between parsing
> markup, attaching components to the markup, and rendering them. It
> might even make the whole auto-add business easier to manage.
> 
> But of course, you're the expert in this field, so I might be dead-wrong :)
> 
> Eelco
> 
> 
> On 8/27/05, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
> > May guess is, it is a lot of work. Currently it is one step: Get the
> > markup for a Page, iterate over the markup elements, if component tag
> > than assign the markup and render the tag. You request requires to
> > separate it into two phase. That sounds like a lot of work for me, but
> > I guess we have to do it, right?
> >
> > Juergen
> >
> >
> >
> > On 8/27/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > > Hi list, Juergen,
> > >
> > > I'm struggeling with getting DatePicker right. To solve things
> > > properly, I really need to be able to get the basic (immutable) tag
> > > information before rendering. In this case, I need to know what the
> > > attributes of the associated tag are. But for other cases - mostly
> > > ajax - information such as with which tag a component is associated,
> > > and it's position in the markup (so that we can render a component on
> > > it's own) would be very helpfull too.
> > >
> > > Is there any way we can efficiently 'pre-parse' this info (e.g. at
> > > creation time?), and have it avaible for clients?
> > >
> > > Eelco
> > >
> > >
> > > -------------------------------------------------------
> > > SF.Net email is Sponsored by the Better Software Conference & EXPO
> > > September 19-22, 2005 * San Francisco, CA * Development Lifecycle 
> > > Practices
> > > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> > > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> > > _______________________________________________
> > > Wicket-develop mailing list
> > > [email protected]
> > > https://lists.sourceforge.net/lists/listinfo/wicket-develop
> > >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is Sponsored by the Better Software Conference & EXPO
> > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> > _______________________________________________
> > Wicket-develop mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/wicket-develop
> >
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Wicket-develop mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
>


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to