On Wed, 05 Jan 2005 12:50:31 -0500, Gili <[EMAIL PROTECTED]> wrote:
> On Wed, 5 Jan 2005 17:38:17 +0100, Juergen Donnerstag wrote:
>
> >Good point. They are obviously not populated from CompoentTag to
> >Component yet. Hmm, while thinking about it ... ComponentTag is
> >exposed to handleComponentTag() which is executed at the beginnging of
> >the render process and it is non-final protected and you may subclass
> >it for your component. Because the params are available only after
> >rendering that tag, it probably makes sense the way it currently
> >works. An improvement could still be to call setters during render.
> >But I'd like to leave that change for the near future. Most of us
> >won't have as much time as we had over christimas and I think there
> >are important things, like the documentation. In order not to loose
> >that idea though, may I suggest you open up a feature request for it.
> >Thanks.
>
> Filed RFE #1096585. As for the getting at the attributes
> without the setters, I did not understand your explanation on how it
> should be done? At one point you mentioned I should subclass
> handleComponentTag() but then later on you say that the attributes
> won't be available until the tag is already rendered ... so I can't get
> at them? ... Please explain.
render was probably not the right word. I meant parsed. The parameters
are parsed from markup and you could than call a setter, provided the
Component already exists and is available. And that is during the
render process.
>
> >Panel actually doesn't need a model. Panel doesn't have anything like
> >a label text or a list of element to be displayed in a table. A Panel
> >might have zero, one or many components and their model object might
> >be from a single model object. Though Panel is just lacking the
> >constructor. If you plan to subclass panel where a model object makes
> >sense, just call setModelObject().
>
> I'd like to propose we change two things about Panel:
>
> 1) It should allow a body (that gets ignored) -- so when you preview
> index.html which contains a panel you can preview how it'll look.
> Currently you cannot embed a body which means that you cannot preview
> where it'll get displayed relative to everything else or how it'll
> look. I expect to be able to do:
>
> <span id="myPanel">
> username: <br>
> password: <br>
> </span>
>
what is wrong with
<span id="myPanel/>
<wicket:region name=remove>
username: <br>
password: <br>
</wicket:region>
I don't like the magic build in your sugestion that a panel body gets
removed. It is not obvious.
> 2) It should support a model. Why? Well, for the login panel you might
> want a default username/password filled in at page display. This is
> just one example. I'm sure we will think up of other Panels in the
> future where it makes sense to have some fields pre-filled.
>
Panel loginPanel = new LoginPanel();
loginPanel.setPasswort("mydefault");
add(loginPanel).
What is wrong with that?
Juergen
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
