I'm a big fan of enforcement of static/non-static + alphabetical ordering, as it stays consistent over time and can be automatically performed by IDEs. I made it the rule in my last team.
I wish we were actually enforcing the GWT-SDK style rules! On Thu, May 30, 2013 at 6:22 PM, Goktug Gokdogan <gok...@google.com> wrote: > Hi folks. > > We currently have a coding style guide for GWT-SDK here: > https://developers.google.com/web-toolkit/makinggwtbetter#codestyle > The guide has some enforcements like static/non-static + alphabetical > ordering. Alphabetical ordering is as good as no ordering in many cases and > these rules are already broken in many places. > > I propose following Guava and many other java libs and just enforce > logical ordering during code reviews (which is also internal recommendation > at Google). One good approach for logical order is to group related public > APIs and then slot in other methods and nested-classes to keep them close > to the related context. This usually helps to follow the code with less > jumps around the class. > > Anyway, I know this can quickly turn into a bikeshed discussion so please > try to resist the urge to oppose unless you have a big concern =) > > Cheers! > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > --- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
