../ syntax is just as prone to refactoring errors as the absolute path, so i dont buy that argument
-igor On Sun, Mar 16, 2008 at 11:51 AM, Phil Grimm <[EMAIL PROTECTED]> wrote: > Yeah, as a new user to Wicket, I just see it as another feature of Wicket. > > There's no issues with it, if all your pages are in the same package. > Is that what most Wicket developers do? > > I agree that searching the classpath could be problematic and more involved > to implement. But, the "../" support seems reasonable and would really help > when you'd otherwise have to resort to full absolute paths (which it seems > to me is most the time). > > In general, if a framework allows things to break easily when refactoring > occurs, this is not good. > > BTW, NetBeans (even with the Wicket plugin) does not fix the paths when I > refactor the package name. It's nice that IDEA does. NetBeans kinda blows > (buggy as hell), but I'm stuck with it for now :( > > Phil > > > > On Sun, Mar 16, 2008 at 1:21 PM, James Carman <[EMAIL PROTECTED]> > wrote: > > > > > On 3/16/08, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > > you guys do both realize that wicket:link is nothing more then > > > convinience. it isnt really meant to support all these complex > > > usecases. it is nice when you need to quickly include an image or link > > > to a near by page, but nothing more then that. > > > > The usecase we're talking about is hardly complex. Nor is it > > unreasonable to think that <wicket:link> should be able to handle it. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > -- > Phil Grimm > Mobile: (858) 335-3426 > Skype: philgrimm336 > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
