* Eelco Hillenius:
> > > I'm closing this issue now and keep Velocity panel as
> > > it was. I found that parsing the markup might lead to
> > > additional issues
> >
> > Which specific issues do you have in mind? Is it something
> > that I should also be aware of?
>
> Just the simple fact that the current panel doesn't do any
> interpretation of the output, and that people may already be
> using it for unstructured output. It's a break with previous
> behavior that might lead to the component suddenly not working
> for people.
Right, then we need something like:
VelocityMarkupPanel extends VelocityPanel
> I have an alternative: if I give you access to wicket-stuff,
> would you be willing to maintain Velocity panel? What we could
> do then is fold this behavior in that component in a conditional
> fashion. Users could decide themselves whether they want to have
> the output parsed or not.
I appreciate your offer, that would maybe save you some patching
and testing work.
I guess the code will need to be different between branch 1.2.x
and trunk, as IIUC your improved patch with newMarkupStream() can
only work in trunk, being the only development tree where cache
can be disabled. Can you confirm that?
I think an update to the [1]home page will also be necessary to
reflect the changes. Are web pages managed in Subversion as well?
Cheers,
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
[1] http://wicket-stuff.sourceforge.net/wicket-velocity-panel/index.html
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop
