ArcBees/gwtp-website — pull request #3 by spg (2013-01-30 15:43:53+00:00)
Title: Header view

I'm experimenting something:
Rather than having all *Resource interfaces under com.arcbees.gwtpwebsite.client.resource, I'm putting those interfaces nearer to the classes that use them (the views).

So, I put HeaderResource in com.arcbees.gwtpwebsite.client.application.header, instead of com.arcbees.gwtpwebsite.client.resource.

I believe that the nearer those interfaces are to their clients (the views), the easier it is to find your way around the app!