This is pretty interesting.. trying to figure what use it would be on a phone device.. what sort of app may take advantage of this. On a tablet though, I can see this being very useful, for like mail apps and such. Do you have any ideas what sort of apps would use this?
On Mon, Feb 14, 2011 at 3:14 PM, JAlexoid (Aleksandr Panzin) < [email protected]> wrote: > In Java CameCasing is also the norm. But methodNames, ClassNames and > fieldNames are CamelCased(See the difference in came casing). Just not > packages. Because packages == directories. > > Thnx for BSD'ing the code. LGPL would have been acceptable also for > components. > > PS: Since you are the sole developer you can change the license to > whatever you like any time. Just people that got your code under > previous license will have that code under that license that was > effective at the time. > > On 14 фев, 09:59, "Oded O." <[email protected]> wrote: > > Sorry for that... > > I'm coming from the .NET world (5+ years of C# development) where > > CamelCasing is the way to go... > > I'm still adjusting, and had no way of knowing that upper-cased > namespaces > > can be problematic > > > > BTW, why is this an issue, and on what machines? > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
