That's exactly my problem. The Wicket projects I work on usually
consists of many Wicket pages, which include panels, which include
fragments.
I know that you can include all the css references in the head of every
Wicket page or panel page, and that you can view only that component
with the css styles in a browser. But the problem is that css id's and
classes outside of that component can also be needed to influence the
component. Besides that seeing your component in context with the rest
of the page makes it a lot easier to spot layout errors.
I know of one solution, it includes Dreamweaver templating. I haven't
tried it yet because we all work with open source applications at my
company, so I use Eclipse with the Aptana plugin. But it's worth a try:
http://www.2rue.de/hacking/wicket/leveraging-wicket-templates-for-offline-viewing-with-dreamweaver/
--
Sjoerd Lohuis
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500
David Leangen wrote:
I'm interested in this problem, too... question below.
Then what I did was I installed Tortoise SVN and Apache Web Server (not
Tomcat) on the designers machine. Also on their machine, I created a
wwwroot/myproject directory and under there I linked:
wwwroot
- myproject
- home -> svn://...src/main/resources/..../home
- user -> svn://...src/main/resources/..../user
- css -> svn://...src/main/webapp/css
- img -> svn://...src/main/webapp/img
Then I configured apache for that directory, and that's the "test website"
Dreamweaver launches after they make edits and want to preview. When the
designer is all done, they do an SVN Commit through Tortoise.
I don't quite understand this second part. What do you mean by you
"linked" wwroot/blah/blah" to "svn://blah/blah"? You mean you just
checked out svn into that dir?
Why do you need to install Apache on the client machine if you're just
using static files? Can't your designer just access with the file://
url?
Finally, the most important thing for the designer is to view the stuff
in context. It doesn't mean much for the designer to see this html:
<wicket:panel>
<div wicket:id="someReallyComplicatedComponent"/>
</wicket:panel>
Are you saying you don't set up anything so your designers can view
someReallyComplicatedComponent in context with the application?
Cheers,
David
---------------------------------------------------------------------
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]
