atom feed20 messages in org.apache.wicket.usersRe: encapsulation, extension and tran...
FromSent OnAttachments
Jan KriestenMay 12, 2008 2:08 am 
Martijn DashorstMay 12, 2008 4:07 am 
Jan KriestenMay 12, 2008 5:28 am 
Martijn DashorstMay 12, 2008 5:34 am 
Jan KriestenMay 12, 2008 5:39 am 
Igor VaynbergMay 12, 2008 8:25 am 
Johan CompagnerMay 12, 2008 8:34 am 
Jan KriestenMay 12, 2008 9:14 am 
Jan KriestenMay 12, 2008 9:17 am 
Igor VaynbergMay 12, 2008 10:12 am 
Jan KriestenMay 12, 2008 10:25 am 
Igor VaynbergMay 12, 2008 10:31 am 
Gerolf SeitzMay 12, 2008 3:00 pm 
Johan CompagnerMay 12, 2008 3:19 pm 
jWeekendMay 12, 2008 4:59 pm 
Jonathan LockeMay 12, 2008 6:24 pm 
Jonathan LockeMay 12, 2008 6:36 pm 
Eelco HilleniusMay 12, 2008 6:51 pm 
Jan KriestenMay 12, 2008 9:44 pm 
Jonathan LockeMay 12, 2008 10:52 pm 
Subject:Re: encapsulation, extension and transparent resolvers
From:Igor Vaynberg (igor@gmail.com)
Date:May 12, 2008 10:12:00 am
List:org.apache.wicket.users

ive seen the issue, and your comment on it:

"Jan Kriesten - 23/Apr/08 01:21 AM Just realized: Maybe it doesn't has to do anything with transparent resolvers at all but only with nested repeaters and adding cells from the innermost."

so i am a little confused as to why we are talking about transparent resolvers, and why gerolf did not apply that code himself...

personally i do not like to change code if it "maybe" helps, especially if it is markup parsing code which is a pretty fragile area in wicket.

-igor

On Mon, May 12, 2008 at 9:14 AM, Jan Kriesten <jan.@renitence.de> wrote:

hi igor,

you want something done that we dont consider a priority and is not a quickie for us to fix, provide a patch.

hello? if you'd taken a look at the jira, you'd seen that there _is_ a patch. [1]

my issues are surely not high priority for you - you're not affected by them, so i can understand.

but since there _is_ a workaround which can be applied - why not doing so?

i've taken a look at the datatable, sure it's not big. the point is, i can't just replace datatable but would have to go all the way down to the AbstractDataGridView. also - all components like navigation + toolbars would have to be implemented as well...

i'm not hacking, i'm using what wicket has got. in this case wicket's 'has got' isn't working. i know about that, i can live with that - when i'm able to work around those issues. and i can't at the moment cause i can't replace MarkupFragmentFinder programatically. if i could do so i would happily replace that and all would be fine...

best regards, --- jan.

[1] https://issues.apache.org/jira/browse/WICKET-1560

--------------------------------------------------------------------- To unsubscribe, e-mail: user@wicket.apache.org For additional commands, e-mail: user@wicket.apache.org