thanks bro On Sat, Jun 5, 2010 at 5:16 AM, Indicator Veritatis <mej1...@yahoo.com>wrote:
> Hi, Mayank- > > The best two books I have found and read on Design Patterns are not > the 'classics' everyone keeps referring too. But if you read either of > them, you will see why they are much more accessible than any of the > classics, especially the "Gang of Four" books. > > They are http://www.holub.com/goodies/patterns/ and > http://mindview.net/Books/TIPatterns/. > > The big advantage of the latter is that 1) it is free, 2) it is a > great sequel to another great Eckel book, "Thinking in Java", whose > 3rd edition is also free. The biggest disadvantage is that he never > really finished the book. > > But it is the former book by Holub that is really good, addressing all > the beginner concerns the "Gang of Four" never address in their books, > showing the benefits of using Patterns in real, live code. For a deep > understanding of OOP/OOD and Patterns, it has no equal. > > However, be warned: many of the good practices of pure OOP using > Patterns are still not recommended on cell phones, as described at > http://developer.android.com/guide/practices/design/performance.html > and at > http://developer.android.com/guide/practices/design/responsiveness.html. > > For example, the former warns against creation of many objects, since > that still tends to make phones sluggish. But both Eckel and Holub > recommend making more objects rather than fewer, even saying that when > the existing classes don't do what you want, the 'default' solution is > to make an object of a new class. Similarly, somewhere else it was > mentioned that inner classes take up more memory than interfaces, but > this may already be out of date. > > That said, one of the many good things one can say about Android is > that the list of violations of OOP practices that one must follow for > optimal code is far, far shorter for Android than for any previous > Java mobile environment. > > On Jun 3, 12:07 am, mayank bisht <mayank.and...@gmail.com> wrote: > > I have an application in which on front screen there are 7 > > buttons.Through these seven buttons navigate to different screens. But > > on all screens these buttons will be appear in lower portion so how > > should I have to develop this application. My way > > > > 1:- I am creating an activity for starting application as all do > > nothing new. > > 2:- Then on clicking on any button i again call " > > startActivityforResult(intent) " for every button . > > 3:- I am just taking data from web services and parsing data and show > > it on screens. > > > > My Question :- > > 1:- So i want to know is this right way or standard way to develop an > > application ? > > 2:- and what will happen in my application if i develop it in this > > way ? > > 3:- If it is not correct then plz tell me the way how should I develop > > my application > > 4:- Is there any design pattern for android application development ? > > 5:- where i can found the design patterns ? > > -- > You received this message because you are subscribed to the Google > Groups "Android Beginners" group. > > NEW! Try asking and tagging your question on Stack Overflow at > http://stackoverflow.com/questions/tagged/android > > To unsubscribe from this group, send email to > android-beginners+unsubscr...@googlegroups.com<android-beginners%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-beginners?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
