You're right of course. It would blow up link quite some, but that's
just code; nothing that would hurt your runtime system. Can anyone
(you?) provide a rock-solid patch for this and/ or open up an issue at
JIRA?
Eelco
On 12/12/06, Paolo Di Tommaso <[EMAIL PROTECTED]> wrote:
I disagree about th
I disagree about that.
Methods semantics for components should be uniform, this is the most
important rule for API simplicity and coherence.
If Button#setEnabled( false ) is rendering a button in disabled state, I
will expect that Link#setEnabled( false ) attached to a tag will do the same.
I agree with that remark, and like the idea of components attaching to
markupfiles whatever kind of component they are. However, what we'd
gain in flexibility by getting rid of Panel (hypothetically), we'd
loose in clarity. If you wouldn't explicitly instantiate a panel that
matches markup, how wo
> On 11/29/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
>> what makes a formcomponent a formcomponent?
>
> That, of course, is the main question :) But not an easy one,
> certainly not to extract a robust interface from it. The component
> like I proposed (but that should have the header stuff in
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> OT: is it really true that default resource lookup is case insensitive on
> windows and not on linux? Shouldn't it be the same?
As far as I know, resoure location on the disk is a function of the OS.
the JVM just passes the path to the OS and
Hey
After having looked briefly at kronos and tried to get it up and running I
have the following comments and thoughts (unsorted and not by importance :-)
- case-sensitivity: Since I'm on linux I had a hard time getting it up
and running because the following files is in wrong case:
-
I'm not even using 1.2 myself, so I don't need it. I thought it would
be a good improvement for a small price for many people. But as no-one
reacted that way, consider this vote scratched.
Eelco
On 12/12/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
if you want to do it then fine by me
but i
+1, very nice!
but all that orange stuff? Dutch web gerilla lurking here? ;)
No seriously, it looks great.
Per
Martijn Dashorst wrote:
>
> Vincent delivered, and came up with a nice follow up to the previous
> design.
>
> http://issues.apache.org/jira/secure/attachment/12346927/wicket_v2.pn
Martijn Dashorst wrote:
Vincent delivered, and came up with a nice follow up to the previous
design.
http://issues.apache.org/jira/secure/attachment/12346927/wicket_v2.png
Any feedback on this one? Can we move forward and rework
http://cwiki.apache.org/WICKETxSITE using this design?
Looks go
This sets a pretty high standardis Wicket 2.0 going to be as much better
than Wicket 1.x than this new look is compared to the old?
:-)
if you want to do it then fine by me
but i agree with Gwyn that we should avoid adding new stuff to 1.2 only
really needed fixes.
And try to focus on getting 1.3 as fast as possible out of the door.
johan
On 12/11/06, Gwyn Evans <[EMAIL PROTECTED]> wrote:
On 11/12/06, Eelco Hillenius <[EMAIL
+1
But can't Vincent really don't do better? ;)
johan
On 12/11/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
Vincent delivered, and came up with a nice follow up to the previous
design.
http://issues.apache.org/jira/secure/attachment/12346927/wicket_v2.png
Any feedback on this one? Can w
12 matches
Mail list logo
