On my taste package-by-feature strategy is more concise and generally more on point, than package-by-layer. In your case I would gather all event classes under client.event and have an inner static class named Handler for each corresponding NotificationSomethingEvent (just like the modern events in gwt). Therefore clients would call something like addHandler(new NotificationClickEvent.Handler(){...}, NotificationClickEvent.getType());
On Friday, February 7, 2014 at 11:26:29 AM UTC+3, Marcel K wrote:
-- On Friday, February 7, 2014 at 11:26:29 AM UTC+3, Marcel K wrote:
Hey,after some coding with gwt i want to publish a component that i wrote. It's an api for desktop-notification and should work with Chrome, FF and Safari (according to https://developer.mozilla.org/en-US/docs/Web/API/ ).notification#Browser_ compatibility I would really appreciate if someone could take a look at it and maybe give me some advices ;) or.. maybe even use :)CheersMarcel
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment