Thanks Igor.

So having your css and js collected off under another path is not the
wicket way?

Are you saying the following for best-practice:

com/acme/myweb
 HelloWorldPage.java
 HelloWorldPage.html
 style.css
 Javascript.js

What about images used by the css? Would these live alongside the
style.css as well?


-----Original Message-----
From: Igor Vaynberg [mailto:[email protected]] 
Sent: Monday, 21 December 2009 4:23 p.m.
To: [email protected]
Subject: Re: Location of css and js files

<head>
<wicket:link>
<link rel='stylesheet' href='style.css' type='text/css'> <script
type="text/javascript" src="javascript.js"></script> </wicket:link>
</head>

and have the files in the same package as the page

-igor

On Sun, Dec 20, 2009 at 7:21 PM, Dale Ogilvie
<[email protected]> wrote:
>
> Hello,
>
> For html page markup containing style and javascript, what is the best

> practice for positioning the css and js files, so that they are 
> available both at design time, and at run time?
>
> I want the designer to be able to see the markup in full glory, while 
> still having this translate properly at run-time.
>
> I'm thinking of an html file such as:
>
> <html>
> <head>
> <link rel='stylesheet' href='style.css' type='text/css'> <script 
> type="text/javascript" src="javascript.js"></script> </head> <body> <p

> class="pretty" onclick="doit();">Hello world</p> </body> </html>
>
> If this markup is alongside the java source, that would imply that the

> css and js would also have to be there. But tradition would have these

> files under a sub directory like so:
>
> ...
> <link rel='stylesheet' href='/style/style.css' type='text/css'> 
> <script type="text/javascript" src="/js/javascript.js"></script> ...
>
> What is the wicket way?
>
> Thanks!
>
> Dale
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to