I set the resource polling to one second for developement and then don't do a reload when I'm only updating an HTML file. Saves a lot of time, especially since Tomcat likes to completly crap itselft and sit down about every 5th reload.
-Phil On 6/29/05, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > Ralf Ebert wrote: > > > - Sometimes you have things like "if it's selected, show it bold" > > (for example for a list item). This can be done easily with > > AttributeModifiers, right. But I think, this is something that should > > possible to do using html only. I would like to say: "it's selected". > > The meaning to the html should be the decision of the web designer > > creating the html pages. Is there some solution or approach for this? > > Use stylesheets. This is the recommended approach all over the web. > Modify the 'class' attribute to the value 'selected' and have your > designer assign 'font-weight : bold;' to that class. When the item is no > longer selected, remove the selected' value attribute. > > > - Same thing goes for nesting components. Let's say we have a Link > > component and in this Link we have two Labels. So far, so good. With > > templating solutions the web designer could easily say: the link goes > > around the first label, but not around the second one. This isn't > > easy with Wicket as it needs a change in the java classes. Can I > > create components in a way which allows changes like this? (While I > > like the way in which the things a Web designer can do with the > > templates are limited, I'm trying to get them as much freedom when it > > comes to their task: creating the html/css layout of the pages). > > Currently I don't see a solution for this. As far as I know, the order > in which components are added is not important, but the nesting is. My > advise would be to seperate the GUI layer from the backing business > layer using mocks for the business layer, and work closely with your > designer. > > > - Some general question, not limited to Wicket: I'm using Tomcat as > > development environment. Every little change (since wicket html pages > > are in the classpath, even when a html page is changed) triggers a > > full application reloading cycle, which can take some time > > (especially if there's Spring and Hibernate as well). Is there any > > way of speeding this up (at least when changing html pages only, but > > in general too)? > > I would say: don't use tomcat :-). However, you can put the html pages > outside of the classpath, alleviating some of your problems. See > http://wicket.sourceforge.net/wiki/index.php/Custom_resource_paths > > Martijn > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
