Hi, Yes, this is what I initially meant and apparently it works fine without custom MarkupFactory/MarkupParser/etc.
What will not work is markup inheritance and any other usage of <wicket:xyz> tags. Here is how I imagine it: - override #getMarkupType() in JadePanel and use .jade as an extension - extend MarkupFactory and override whatever is needed so that you first load the .jade file, parse it, transform it to .html and finally pass it to the default impl that is used at the moment I think this should be enough. On Wed, Aug 7, 2013 at 12:10 AM, Decebal Suiu <[email protected]> wrote: > Hi Martin > > I created a branch > https://github.com/decebals/wicket-jade/tree/children-components for your > idea. > I increased the complexity of demo application a little bit. > Now, the HomePage contains a BooksPanel that contains an AuthorPanel. Both > panels extend JadePanel. > BooksPanel.jade contains a div(wicket:id="authorPanel"). The markup for > authorPanel is AuthorPanel.jade. > > Everything works fine. > > Is this what you want or I misunderstand you? Can you explain your idea in > more words? > > Best regards, > Decebal > > > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Announce-wicket-jade-tp4660722p4660739.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
