my 2 cent would be to force the setting to be present, else the startup would fail - so the developer *has* to set it manually in any way
but your and Martijn's idea sounds very nice to me. An idea would to extend the logo/ link and bring up a console where the current page is displayed together with the whole component tree, all used models and memory consumed by each of them... that would IMHO speed up developement as you see bottlenecks or wrongly implemented models very early! WDYT ? > -----Ursprüngliche Nachricht----- > Von: Eelco Hillenius [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 29. Mai 2007 23:14 > An: Wicket Development > Betreff: development mode being the default > > List, > > I'm still worried about the fact that development mode is our > default setting. Imho, this is a mistake as the development > setting is a dangerous setting for production systems: it > uses more memory (for precise line reporting), is less > efficient (render check) and can potentially bring down a > server (when it runs out of file descriptors due to resource > polling). I'd much rather have a safe default than a > convenient default. > > Anyway, we've had endless discussions about this, and > unfortunately I seem to be alone having this opinion. I'd > still like to do something extra though, and Martijn > mentioned a good idea, which is to have something similar to > the debug link we have for Ajax when in development mode. If > we would implement this idea, we could e.g. place an icon > that represents this (maybe combine with the Wicket logo, > wouldn't that be nice?) in the lower right corner of the > browser, much like the ajax debug link is placed right now. > > WDYT? > > Eelco >
