Re: JavaZone presentation, feedback wanted

>
> Thanks for your feedback Igor!
>
> On 8/23/07, Igor Vaynberg <igor.vaynberg@...> wrote:
> >
> > here are some notes:
> >
> > under integration mention: guice
>
>
> will do
>
> components and markup: borders also have their own markup files
>
>
> indeed
>
> 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.
>
>
> it makes sense
>
> models:
> >
> > "models are the brains of your app", i wouldnt go that far, you shouldnt
> >
> > have business logic in the models
>
>
> I picked this up from martjin's presentation, Ibut I agree it goes too far
>
>
> "Solution: OGNL dynamic expressions" - i wouldnt mention ognl because we
> > do
> > not depend on it. i would say ognl/el-like property path expressions
>
>
> Indeed, this is something that has changed since Martjin's talk. I'll
> update it accordingly
>
> 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.
>
>
> makes sense
>
> 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.
>
>
> I think the attribute modifier is pretty obvious to understand, and
> there's already an example with AttributeModifier when talking about
> Behaviors. But I like your code too, it makes more obvious there's a lot
> more you can do with a behavior than modifying an attribute. So there's pros
> and cons for both IMO, I'll see if I can show the two (one when talking
> about behaviors, one in the example).
>
> Thanks again for your valuable input,
>
> Xavier
>
> -igor
> >
> > On 8/23/07, Xavier Hanin < xavier.hanin@...> wrote:
> > >
> > > A first version of the presentation slides is available here:
> > > http://people.apache.org/~xavier/wicket-javazone-07.ppt<http://people.apache.org/%7Exavier/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 <eelco.hillenius@...> wrote:
> > > >
> > > > On 8/22/07, Xavier Hanin < xavier.hanin@...> wrote:
> > > > > On 8/22/07, Eelco Hillenius <eelco.hillenius@...> 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/
> > >
> >
>
>
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://incubator.apache.org/ivy/
> http://www.xoocode.org/
>