city has to be adjusted for the new project location
>> of wicketstuff-scriptaculous.
>> - is it ok if I check in an udpated Eclipse project? It's still named
>> "wicket-contrib-scriptaculous' and uses M2Elipse's
>> MAVEN2_CLASSPATH_CONTAINER v
Let me know if you have ideas for improvements or changes. I'd be happy to
hear other people's thoughts on this area. This small project has been
really useful for me, and I'm still a firm believer that there's nothing
else like it for other java web frameworks!
On 5/27/08, Rodolfo Hansen <[EMAI
whoops, sorry about that.
I didn't know anyone setup a teamcity build for scriptaculous. my bad.
On Mon, May 26, 2008 at 4:37 PM, Martijn Dashorst <
[EMAIL PROTECTED]> wrote:
> And everything runs again
>
> Martijn
>
> On Mon, May 26, 2008 at 11:31 PM, Martijn Dashorst
> <[EMAIL PROTECTED]>
t;
>>> BTW
>>> - did you have time to check my other patch for sorting of arbitrary
>>> containers?
>>> - it seems that teamcity has to be adjusted for the new project location
>>> of wicketstuff-scriptaculous.
>>> - is it ok if I chec
s it ok if I check in an udpated Eclipse project? It's still named
> "wicket-contrib-scriptaculous' and uses M2Elipse's
> MAVEN2_CLASSPATH_CONTAINER variable instead of M2_REPO. Or should we just
> remove it from the repository?
>
>
> Regards
>
> Sven
>
wicket-security
> > wicketstuff-lightbox
> > wicket-flickr
> > wicketstuff-minis has a documented dependency (and there might be others
> > too)
> >
> > Of course wicket users who want to enhance their own components with
> > some prototype javascri
I'm open to suggestions. The scriptaculous project is coupled to prototype,
but i don't have an issue with depending on a separate project for the
prototype scripts.
On 5/16/08, richardwilko <[EMAIL PROTECTED]> wrote:
>
>
> hi,
>
> I wrote wicket prototip integration, (its in wicket-stuff-minis).
AIL PROTECTED]> wrote:
> Dear Ryan,
>
> are you interrested in any collaboration concerning Wicket integration of
> Scriptaculous? E.G. gererifying things like DraggableTarget? I did not yet
> receive any response from you.
>
> Stefan
>
> -----Ursprüngliche Nachricht-
Thanks for the post!
I'm all for extending the scriptaculous project if there are useful
additions! can you point me to the scriptaculous documentation for these
hooks? what are they typically used for?
On Tue, May 6, 2008 at 7:40 AM, Stefan Lindner <[EMAIL PROTECTED]> wrote:
> Dear Ryan,
>
>
any thoughts on using hudson for the build server?
I overhauled my employer's build servers changing from bamboo to hudson
specifically because of memory constraints. hudson is very lightweight and
worked great for us.
just my 2 cents.
On Fri, May 2, 2008 at 7:21 PM, Martijn Dashorst <[EMAIL PR
t;
> I guess it could just be done with some effects chaining right?
>
>
> Ryan Sonnek wrote:
>
> > i don't have permissions to setup a jira project, but if a wicketstuff
> > admin
> > can grant me privileges, i can create one. my user account is wireframe.
&g
i don't have permissions to setup a jira project, but if a wicketstuff admin
can grant me privileges, i can create one. my user account is wireframe.
On Wed, Apr 30, 2008 at 1:36 PM, Sven Meier <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I'd like to contribute some patches for wicketstuff-scripta
I just published a new wicketstuff-rome component that will allow
users to consume rss feeds in wicket. This is something that I've
been meaning to do for a *long* time, and finally got around to it.
http://www.jroller.com/wireframe/entry/consume_rss_feeds_within_wicket
I've seen a few posts on t
commons-logging? Seriously?? *shudders*
Why does wicket depend on commons-logging when slfj is used?
On Tue, Mar 25, 2008 at 3:54 PM, Timo Rantalaiho <[EMAIL PROTECTED]> wrote:
> On Tue, 25 Mar 2008, Martijn Dashorst wrote:
> > -1
> >
> > Upgrading these kind of things in a stable release is
+1, Wicket 1.4 is 1.3 + generics, drop support for 1.3
On Mon, Mar 17, 2008 at 3:13 AM, Martijn Dashorst
<[EMAIL PROTECTED]> wrote:
> This thread is for voting only. Use the [discuss] thread for voicing
> your opinion or asking questions. This makes counting the votes much
> easier.
>
> The di
> > On 3/14/08, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> > > is the next release an evolution or revolution? :) i think first we
> > > need to make a list of all major things we want to go into it, and
> > > then decide.
> >
> > I think it counts as revolutionary: abandoning Java 1.4 i
I'm definitely not against the idea, but I would caution introducing
an application wide ID generator. This would introduce a *single*
synchronization point for component creation which *could* introduce a
performance bottleneck.
Only way to find out is to try, but this is just a word of caution.
this is the second time i've heard of this breaking. please re-open
this issue. if you have a quickstart project that'd be great.
https://issues.apache.org/jira/browse/WICKET-987
On Jan 26, 2008 3:01 PM, Luke Ma <[EMAIL PROTECTED]> wrote:
>
> Deployment javascript problem: this bug manifests
> But those projects ended up adding the annotation option because they had
> something ugly like XML configuration hell that they were trying to improve
> upon. Wicket does not.
True! Good point! =)
+1 for separate project regardless of the outcome. Tapestry,
hibernate, and spring are all examples of projects that provide the
*option* to use annotations if you want.
On Jan 11, 2008 9:00 AM, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> On Jan 11, 2008 1:02 AM, Maeder Thomas <[EMAIL PROTECTED]
> Playing the advocate of the devil: the thing with those is that it
> doesn't actually solve anything. I mean, you hardly decrease the lines
> of code you have to write to achieve something, annotations are
> arguably harder to discover than overridable methods, and we end up
> with having multipl
> Well, if you're going to do that, why not just mount the page in the
> application class and skip the annotation + registration altogether?
*IF* annotation support only includes mounting the url, i agree with
you. but if you start specifying url encoding strategies or other
useful page annotati
+1 for some R&D time. I think this could turn out to be *really* cool.
One comment I have about classpath scanning is that *if* it turns out
to be a nightmare, you could go the route of Hibernate where you have
to register what annotated pages you want to support. ex:
public class MyWebApplicat
Just curious if anyone has run clover or cobertura maven reports
against the codebase to see what kind of unit test coverage their
currently is. I have *no* doubt that wicket's unit test coverage is
*extremely* high compared to other web frameworks, but it might be
good to see if there are any imp
This is great to hear.
out of curiosity, what kind of annotation validation does it support?
is this similar to the wicketstuff-hibernate project? if so, it might
be worth putting in wicketstuff and trying to create an abstraction to
support both Hibernate and JPA annotations.
I think facebook s
25 matches
Mail list logo
