please find a patch for it attached (including test case)
-Juergen
On 8/24/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
> * Juergen Donnerstag:
>
> > No I haven't. Interest was rather low. If nobody has a need for
> > it, than ... It is still on my laptop if want to follow up.
>
> I can'
I'm (non-binding) +1 for custom levels, 0 for another level.
On 8/31/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
> i don't care to much, how much extra work is it for us?
> can't we just have something where you can add levels what ever you want?
> like FeedbackMessage.addLevel(new Level("", 10));
-1 for adding another level, +1 for adding support fo
ick, just create whatever subclasses of feedbackmessage you need
and use those
it will probably have a abstract string getlevel(), afict it is only the
feedbackpanel that needs to know the level so it can set the appropriate css
class, and message filters for filtering.
there is no semantic meani
addFeedback(String class, String message)
addFeedback(String class, IModel message)
But before you know it, we're implementing Log4j in our feedback
mechanism. Isn't there a JSR that standardizes this and we could
implement/get inspiration on?
Martijn
On 8/31/07, Johan Compagner <[EMAIL PROTECTE
ha... also my idea :)
On 8/31/07, Igor Vaynberg (JIRA) <[EMAIL PROTECTED]> wrote:
>
> refactor feedback to allow users to easily add custom levels
>
>
> Key: WICKET-911
> URL: https://issues.apache.org/j
i don't care to much, how much extra work is it for us?
can't we just have something where you can add levels what ever you want?
like FeedbackMessage.addLevel(new Level("", 10));
johan
On 8/31/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
>
> we need to have a vote on
> https://issues.apache
dont know if we should do that, i believe you can already map this as
error - error
warning - info
info -success
heh, i think we should consider adding one more, unless it's too much
hassle, your mapping doesn't seem very intuitive to me :)
+1
-Matej
On 8/31/07, Igor Vaynberg <[EMAIL PROTECTE
we need to have a vote on
https://issues.apache.org/jira/browse/WICKET-907and decide whether or
not we want this in core
-igor
Thanks for that quick fix, a follow-up question though:
Localizer uses IStringResourceLoader.loadStringResource(Component component,
String key).
While most of the IStringResourceLoader implementations correctly handle
a null component as parameter, BundleStringResourceLoader doesn't - it needs
a c
10 matches
Mail list logo
