On 3/14/06, Ryan Sonnek <[EMAIL PROTECTED]> wrote:
> I think that's a good question.  What would be the best way to
> distribute this feature to users?  I've commented on my blog the steps
> I believe are necessary for this to be integrated into wicket, but I'd
> appreciate any feedback on it
> (http://jroller.com/page/wireframe?entry=wicket_preview_with_one_javascript).
>

I'll check it tonight (hopefully)

> There are a couple changes to wicket to support this:
> 1.  update the DTD to support the wicket:preview attribute
> 2.  make sure that wicket can strip the wicket:preview attribute at
> runtime (just like wicket:id)
>

both should be easy to accomplish

Juergen

> Then it's just a question of how to package this for users?  I think
> it would make sense to distribute the javascript files for this
> feature in a seperate folder so that users could upgrade the whole
> suite of javascript when updates are released...
>
> On 3/14/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
> > I am interested to do it, but got only very little time currently.
> > What do you want me to do?
> >
> > Juergen
> >
> > On 3/14/06, Ryan Sonnek <[EMAIL PROTECTED]> wrote:
> > > I've updated the wicket:preview feature with new functionality.  I
> > > think it pretty much covers the use cases people have provided, and I
> > > would like to work with the wicket developers to integrate this (if
> > > it's still wanted).
> > >
> > > main "selling" points
> > > * uses html and ajax to dynamically include components into page for
> > > offline preview (outside of wicket)
> > > * only need to include one javascript file (all others are dynamically
> > > included at runtime)
> > > * previewing of nested components is now supported!  that means you
> > > can preview a page that imports a component which imports another
> > > componet....etc....
> > >
> > > http://jroller.com/page/wireframe?entry=preview_multiple_levels_of_components
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by xPML, a groundbreaking scripting 
> > > language
> > > that extends applications into web and mobile media. Attend the live 
> > > webcast
> > > and join the prime developer group breaking into this new coding 
> > > territory!
> > > http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
> > > _______________________________________________
> > > Wicket-user mailing list
> > > [email protected]
> > > https://lists.sourceforge.net/lists/listinfo/wicket-user
> > >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> > that extends applications into web and mobile media. Attend the live webcast
> > and join the prime developer group breaking into this new coding territory!
> > http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
> > _______________________________________________
> > Wicket-user mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/wicket-user
> >
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
> _______________________________________________
> Wicket-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to