I think that a new Link class and a new urlFor method is a lot of work for a simple think as make a link but i don't see another way to create BookmarkableResourceLinks
On 2/7/06, pepone pepone <[EMAIL PROTECTED]> wrote: > Yes i working with 1.2 and nice url from the begining of this post > > i change the codign strategy for use "_/" (I add a separator param for > this) as separator and this works ok for me. for work with nice url I > need do litel changes in my application because it use > getRequest().getParameters() in a few places and this don't work withy > nice url, but ok this is not a lot of work > > What i'm able to do and I think is samething basic in WebFramework for > real life applications is create a BookMarkableLink to a resource > that uses parameters and work with nice urls too. > > I haven't a big reason to use nice urls but who want ugly urls when > can have nice urls > > On 2/7/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > Pepone, did you check out URL mounting in 1.2? Those nice urls come > > much handier than in 1.1 now. There is a usuage example: niceurl in > > project wicket-examples. > > > > Eelco > > > > > > On 1/30/06, pepone pepone <[EMAIL PROTECTED]> wrote: > > > nobody see this as a problem?? > > > > > > On 1/24/06, pepone pepone <[EMAIL PROTECTED]> wrote: > > > > Hello all > > > > > > > > I using wicket and think that there is samething wrong in this > > > > framework when you have 10 diferents classes in > > > > wicket.markup.html.link and there isńt way to create a bookmarkable > > > > link to a resource that need params using any of them. > > > > > > > > and with my knowledge of wicket there isn't a simple way of do it. > > > > > > > > Other thing that i cosider is wrong in this framework is the way in > > > > you handle "nice url" because mount a Page can break it, if the page > > > > use params because params aren't in request->getParam() > > > > > > > > The user must changue the way in they retrive pageParams. this is not > > > > clean in WebFramework that try to simplificate the developers work. > > > > and it must be complety transparent for end users > > > > > > > > > > > > I view same inecesary complexity in this details. Or the way in you > > > > implement AbstractRequestTargetUrlCodingStrategy and hard code the > > > > charcter "/" four times in the same file and you must implement other > > > > class only for changue this seperator is excesive work for and end > > > > user point of view. > > > > > > > > I write this lines as a constructive critique of what i see wrong in > > > > wicket i don't try to disturb you. And in general Wicket is a good > > > > work and i experct it'll be better in a near future > > > > > > > > -- > > > > play tetris http://pepone.on-rez.com/tetris > > > > > > > > > > > > > -- > > > play tetris http://pepone.on-rez.com/tetris > > > > > > > > -- > play tetris http://pepone.on-rez.com/tetris > -- play tetris http://pepone.on-rez.com/tetris NŹHYŢľéXŹ˛'˛ŢuźŚ[§Ü¨ş ŢŚŘk˘č! WŹ~éŽĺzkśCŁ [EMAIL PROTECTED],şˇâ a{ ĺ,ŕHňÔ4¨mś˙ąéZ˛ë jYwţÇĽrg
