On 11/4/05, Nathan Hamblen <[EMAIL PROTECTED]> wrote:
> But anyway, you can preview a component (in isolation) just fine in the
> component template without a web server. You can also preview the fake
> version in the page template without a server, though it's easy for that
> to get out of synch w
The problem at hand was : how to still have an html preview -before
having all the logic implemented- for a complex page, when the page is
technically separated into multiple parts/panels.
But now I see this question has no answers, and that is normal, due to
the fact that the real types of the pa
Yes, that's simple and that works, indeed.
Thanks for the idea.
On 11/4/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> I use around relative paths to the CSS in the webapp
> directory. So this looks like:
>
>
>
>
>
>
>
>
>
> The same can be done for JavaScript libraries that aren't p
It wouldn't be a "drawback," since nobody does it better.
But anyway, you can preview a component (in isolation) just fine in the
component template without a web server. You can also preview the fake
version in the page template without a server, though it's easy for that
to get out of synch
I use around relative paths to the CSS in the webapp
directory. So this looks like:
The same can be done for JavaScript libraries that aren't part of a component.
Martijn
On 11/3/05, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
> > > I don't know how to correctly preview a markup h
The fact that one cannot preview html only using panels without
running a web server means that java code it is mandatory. Do you
think this is a drawback to Wicket (as well as Tapestry) that claims
that designers and coders can work almost independently?
2005/11/3, Laurent PETIT <[EMAIL PROTECTED
On 11/3/05, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
> in order to be pre-viewable the html editor must be able to find the
> css file without the help of wicket. The easiest way to accomplish it
> is to put the css into your source path and by means of
> (autolinks) wicket is able to find th
> > I don't know how to correctly preview a markup html only when it
> > refers to css, javascript files, that are meant to be relative to the
> > webapp context.
in order to be pre-viewable the html editor must be able to find the
css file without the help of wicket. The easiest way to accomplish
nobody for this one ? ;-)
On 11/3/05, Laurent PETIT <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I don't know how to correctly preview a markup html only when it
> refers to css, javascript files, that are meant to be relative to the
> webapp context.
>
> I think this should be done by viewing the html
