Re: What else do we want to do before 8.0.0 final ?

Hi, great to hear and thanks for the feedback. :-) kind regards Tobias > Am 01.02.2017 um 09:00 schrieb Maxim Solodovnik : > > Hello All, > > JFYI I have moved Apache OpenMeetings to Wicket-8 without any issues > in ~30 minutes :)

Re: What else do we want to do before 8.0.0 final ?

Sure, working on it. Created WICKET-6318 to track the configurable property resolver implementation. Pedro Santos On Tue, Feb 7, 2017 at 8:16 PM, Martin Grigorov wrote: > Hi Pedro, > > Please create Pull Requests for your proposed changes! > Thanks! > > Martin Grigorov >

Re: Proposal: Remove all component lambda-based factory methods before 8.0.0 final

Do we want to do a similar thing for factory methods around models, such as LoadableDetachableModel#of? Andrew On Wed, Feb 8, 2017 at 2:53 PM, Andrea Del Bene wrote: > I think we all (more or less :-) ) agree about moving factory methods away > from components. I don't

Re: Proposal: Remove all component lambda-based factory methods before 8.0.0 final

I think we all (more or less :-) ) agree about moving factory methods away from components. I don't think we need a dedicated and experimental module for them. I'd rather move them to class Lamdas and, if we need it, we can deprecate them in future. On 08/02/2017 17:24, Sven Meier wrote: I

Re: Proposal: Remove all component lambda-based factory methods before 8.0.0 final

I like Edmond's suggestion: "We can also move them all to a factory class and place this class in experimental. That way we can do with it whatever we like." So we have a place to refer questioners to when they are looking for these factory methods. Regards Sven On 08.02.2017 16:55,

[GitHub] wicket issue #211: Added lambda factory function for Behavior's onConfigure ...

Github user vrozkovec commented on the issue: https://github.com/apache/wicket/pull/211 Hehe, good that I've made your decision easier :) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] wicket issue #211: Added lambda factory function for Behavior's onConfigure ...

Github user martin-g commented on the issue: https://github.com/apache/wicket/pull/211 @vrozkovec You might want to participate at this discussion: http://markmail.org/message/q4gb57wmyrkkbr2s at dev@ --- If your project is set up for it, you can reply to this email and have your

Re: Proposal: Remove all component lambda-based factory methods before 8.0.0 final

https://github.com/apache/wicket/pull/211 :-) Let's drop them all! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Feb 8, 2017 at 4:34 PM, Emond Papegaaij wrote: > I can live with the following: > > Factory methodes should: > *

[GitHub] wicket pull request #211: Added lambda factory function for Behavior's onCon...

GitHub user vrozkovec opened a pull request: https://github.com/apache/wicket/pull/211 Added lambda factory function for Behavior's onConfigure method. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vrozkovec/wicket master

Re: Proposal: Remove all component lambda-based factory methods before 8.0.0 final

I can live with the following: Factory methodes should: * accept exactly 1 lambda (and possibly an id) * be a static method on the component or behavior they create * be given meaningfull names * be limited to at most 1 or 2 per type * not pass the instance they create to the lambda This

Re: Proposal: Remove all component lambda-based factory methods before 8.0.0 final

I agree with Martijn, especially when he warns about the huge risk we take overusing lambdas and making API inconsistent. But I don't agree to take such an extreme choice like removing EVERY factory methods. Like Martin suggested these methods can be very useful when they are limited to the very

Re: Proposal: Remove all component lambda-based factory methods before 8.0.0 final

On Wed, Feb 8, 2017 at 3:08 PM, Martijn Dashorst wrote: > There are many things to consider when designing an API. Usability of > the API, readability of the resulting code, maintenance burden for the > core developers, but also performance, memory consumption and >

Re: Proposal: Remove all component lambda-based factory methods before 8.0.0 final

The problem with creating sub-classes with the lambda functionality (e.g., LambdaAjaxButton) is that external sub-classes of the Wicket libraries don't then have this functionality (e.g., BootstrapAjaxButton). The purpose of the core library is to provide this common functionality, functionality

FINAL REMINDER: CFP for ApacheCon closes February 11th

Dear Apache Enthusiast, This is your FINAL reminder that the Call for Papers (CFP) for ApacheCon Miami is closing this weekend - February 11th. This is your final opportunity to submit a talk for consideration at this event. This year, we are running several mini conferences in conjunction with

Re: Proposal: Remove all component lambda-based factory methods before 8.0.0 final

There are many things to consider when designing an API. Usability of the API, readability of the resulting code, maintenance burden for the core developers, but also performance, memory consumption and serialization overhead. Adding lifecycle fields to Component for any extension point will

Re: Proposal: Remove all component lambda-based factory methods before 8.0.0 final

Hi Andrew, you can easily create your own subclasses that use lambdas for what you need. Thus I don't see a reason why Wicket should support this additionally to the well-known hook-methods. Have fun Sven On 08.02.2017 11:45, Andrew Geery wrote: Rather than using static factory methods,

Re: Proposal: Remove all component lambda-based factory methods before 8.0.0 final

Hi, no confusion on my side either - regarding lambdas at least :P. > lines of code is not the only metric for a good API. Lines of imports is a good metric too, and this doesn't look to good for the Lambdas class :/. > These methods are trivial for anyone to implement Yes and everyone

Re: wicketstuff/wicket-jquery-ui M4 release

Many thanks! :)) WBR, Maxim (from mobile, sorry for the typos) On Feb 8, 2017 19:02, "Martin Grigorov" wrote: > WicketStuff 8.0.0-M4 is on its way to Maven Central! > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Wed, Feb 8,

[ANNOUNCE] WicketStuff 8.0.0-M4 Released

WicketStuff core 8.0.0-M4 based on Apache Wicket 8.0.0-M4 is released and soon will be available at Maven Central! The changelog since 8.0.0-M3 is: Joachim Rohde (4): don't add js code twice Removed deprecated methods Removed deprecated constructor calls Removed the

Re: wicketstuff/wicket-jquery-ui M4 release

WicketStuff 8.0.0-M4 is on its way to Maven Central! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Feb 8, 2017 at 11:27 AM, Martin Grigorov wrote: > The release is running! > > Martin Grigorov > Wicket Training and Consulting >

Re: Proposal: Remove all component lambda-based factory methods before 8.0.0 final

Rather than using static factory methods, would we ever consider pushing the lambdas into the component classes themselves? For example, if we did this with the Button class, the change would be: - Add two private fields, SerializableConsumer submitHandler, errorHandler - Add "setters" for these

[GitHub] wicket issue #209: Add static lambda builder methods.

Github user martin-g commented on the issue: https://github.com/apache/wicket/pull/209 @ageery You might want to participate at this discussion: http://markmail.org/message/q4gb57wmyrkkbr2s --- If your project is set up for it, you can reply to this email and have your reply appear

Re: wicketstuff/wicket-jquery-ui M4 release

The release is running! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Feb 8, 2017 at 4:05 AM, Maxim Solodovnik wrote: > Hello Martin, Sebastien, > > Could you please release wicketstuff/wicket-jquery-ui M4? > > I have fixed one

Re: wicketstuff/wicket-jquery-ui M4 release

Thanks a million Sebastien! :) On Wed, Feb 8, 2017 at 5:00 PM, Sebastien wrote: > Hi Maxim, > > Wicket jQuery UI 8.0.0-M4 is on its way to maven central! > > Enjoy, > Sebastien. > > > On Wed, Feb 8, 2017 at 4:05 AM, Maxim Solodovnik > wrote: > >> Hello

Re: wicketstuff/wicket-jquery-ui M4 release

Hi Maxim, Wicket jQuery UI 8.0.0-M4 is on its way to maven central! Enjoy, Sebastien. On Wed, Feb 8, 2017 at 4:05 AM, Maxim Solodovnik wrote: > Hello Martin, Sebastien, > > Could you please release wicketstuff/wicket-jquery-ui M4? > > I have fixed one minor issue in

Re: Proposal: Remove all component lambda-based factory methods before 8.0.0 final

It is that your trivial use case is not my trivial use case and that we will end up with a 100,000 trivial use cases. And no, confusion is not the big issue (though for onsubmit+onerror it is) but creating a good API is hard. It takes time and understanding. Minimizing lines of code is not the