here are some notes:
under integration mention: guice
components and markup: borders also have their own markup files
is it possible on behaviors page to subclass simpleattributemodifier and
move that %2 logic into it, i think that will make it clearer what behaviors
are all about.
models:
"models are the brains of your app", i wouldnt go that far, you shouldnt
have business logic in the models
"Solution: OGNL dynamic expressions" - i wouldnt mention ognl because we do
not depend on it. i would say ognl/el-like property path expressions
example:password strength: you can put a preview into the spaen tag so
something like <span wicket:id="strength">[[strength bar]]</span> so it at
least shows that in the preview.
instead of strength.add(new attributemodifier() might be better to do
strength.add(new abstractbehavior() { oncomponenttag(tag) { tag.put("class",
PasswordField.this.getModelObjectAsString()); }
it ties into the behaviors which you have explained which means one less
concept and its more transparent then an attributemodifier.
-igor
On 8/23/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
>
> A first version of the presentation slides is available here:
> http://people.apache.org/~xavier/wicket-javazone-07.ppt
>
> The section about custom component doesn't have much slides, but I will
> spend most of the time demonstrating stuff with eclipse and firefox, so
> the
> slides are mainly there as a backup and to give an idea of what I'll talk
> about.
>
> Do you see anything wrong in these slides? Any idea of improvements? Any
> feedback is welcome!
>
> Xavier
>
> On 8/22/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> >
> > On 8/22/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
> > > On 8/22/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Looks good to me Xavier. A danger about the example is that it would
> > > > probably be easy to be focussed on determining the password strength
> > > > rather than how to create a custom component,
> > >
> > >
> > > That's why I provide only a very simple implementation. It could even
> be
> > > delegated to another service, I think audience can understand that.
> >
> > True. Don't get me wrong, I think it could be a very nice example.
> >
> > > but then again, the
> > > > example by itself is nice, and can't just be found in the examples
> > > > projects.
> > > >
> > > > The kind of example I was thinking about for my presentation would
> > > > probably try to show off the fact that Wicket components are
> stateful
> > > > and that the component hierarchy is flexible (Al's talk points that
> > > > out nicely for instance).
> > >
> > >
> > > Are you referring to his talk on bean editor? Maybe you could give me
> an
> > > example of component you were thinking about?
> >
> > I wasn't done with the thinking tbh... But for instance a simple bean
> > editor would have a big cool factor. Though you example would score
> > high on that as it uses Ajax :) I think both would be good examples,
> > and the advantage of your idea is that it wouldn't be too much code,
> > so that you can focus on your story.
> >
> > Eelco
> >
>
>
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://incubator.apache.org/ivy/
> http://www.xoocode.org/
>
