- Taschenbuch: 264 Seiten
- Verlag: Packt Publishing (26. Juli 2011)
- Sprache: Englisch
- ISBN-10: 1849515166
- ISBN-13: 978-1849515160
- Größe und/oder Gewicht: 19 x 1,5 x 23,5 cm
- Durchschnittliche Kundenbewertung: Schreiben Sie die erste Bewertung
- Amazon Bestseller-Rang: Nr. 1.953.943 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
Rhomobile Beginner's Guide (Englisch) Taschenbuch – 26. Juli 2011
|Neu ab||Gebraucht ab|
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
Über den Autor und weitere Mitwirkende
Abhishek Nalwaya is a Ruby, Rhomobile, and Rails enthusiast. He is a regular participant at Ruby/Rails Meetup and has taken technical sessions on Rhodes framework within company and at Ruby Meetups. His blog is listed on the official third-party tutorial section at the Rhomobile site.
He was associated with Tata Consultancy Services and is presently working as an application developer with Column Software Technology. He has worked in many projects providing solutions to Fortune 500 companies using Ruby, Rhodes, and Ruby on Rails.
Die hilfreichsten Kundenrezensionen auf Amazon.com
You see, the biggest problem with Rhodes right now is that it is incredibly hard to get started with because the official documentation and tutorials are organized in such a way that makes it look more like a magazine than a framework reference. It is particularly hard to understand what all the products/components do, the licensing and costs of each one and how the overall development process is supposed to work (at least how the people in Rhomobile understood it when they created the tools). Even though I have experience dealing with Rhodes it was nice to read someone else's opinion on how to best introduce someone to the technology.
The author does a nice work of keeping the level of detail to an introduction, but keep in mind that this book is meant for people that have experience developing software and have some understanding of the issues involved in mobile application development. For example, the book takes for granted that you understand the difference between native apps and web-based apps and that have some experience with the native SDKs or at least are familiar with the fragmented device landscape. I did miss a better comparison of Rhodes with the other multi-platform frameworks out there like PhoneGap or AppAccelerator Titanium.
The book includes a chapter on each of these:
+ Intro to Rhomobile products
+ Rhomobile setup
+ Basic app tutorial
+ RhoSync and Metadata
+ View Styling
+ A VERY light Testing and Logging
+ Rhodes System class
As people that are experienced with Rhomobile can tell, the book is focused on the typical "enterprise application" scenario where you have a running system that you want to make accessible through a mobile app and hence most of your problems deal with making that system available to the app and synchronizing data. This is the main scenario that Rhomobile targets and the one the official documentation centers on, but I felt a more in-depth discussion about the role the different Rhomobile products play in this was in order. For example, RhoSync is a great product that makes data synchronization easier when used but is not the best choice if you are thinking of building an app that does not have a need for synchronizing a lot of entities or that wants to use an API oriented towards services rather than CRUD operations. There is no mentioning of the ability of Rhodes to use web services directly and the architectural discussion makes it feel like RhoSync is an essential part of a Rhodes app in every scenario.
I loved the "Digging the code" sections that took an in depth look at some of the code and explained how Rhodes worked behind the scenes to make it all happen, I wished it was used in every chapter. The "Quiz" section at the end of some chapters was also a nice touch. The book also includes a VERY helpful Index at the end that is painfully lacking in the official documentation and is worth the price of the download on its own. I also found myself missing a final chapter on "the next steps", it feels like the book was cut abruptly specially because it is so common on introductory books.
The other major issue with the book is that it's based on Rhodes <3.0.2 and hence all examples are based on JQTouch instead of JQuery Mobile plus there is no mentioning of NFC capabilities which is a major selling point for Rhodes. There is also a strange lack of references to the official documentation or videos although I can understand this since Rhomobile is in the process of revamping them. Still, it would have been nice to have a "for further reading look at..." kind of directions.
Smaller issues are the lack of a more detailed explanation on how the MVC pattern works on Rhodes, specially on how the different components communicate with each other, how navigation is affected by the different button types and JQTouch, the caveats of using background/ajax calls and when to use webview.navigate vs redirect; but these can all be understood given the introductory level of the book, just be aware there are some major pitfalls still out there you will have to learn the hard way.
Overall "Rhomobile Beginner's Guide" is a good introductory book that will save you days of battling with Rhomobile's documentation and videos; and I'm personally looking forward to the next edition of it.
Nalwaya's examples reflect this, by talking about a hypothetical company that needs its employees to access corporate data via their cellphones. Frankly, the examples have only a minimal UI as you might expect. What the point of most examples is to show how to get data from a central relational silo and also how to update this with changes that the user could input on her phone. In part this uses the classic Model-View-Controller pattern which you might already be familiar with.
The text demonstrates that you do not need much in the way of relational database knowledge, like how to build interrelated tables. The examples that access the back end do not create those tables, but take them as given. So you are facing a static structure of tables, because after all how plausible is it that a user on a cellphone, even an advanced one, will be or even should be making and destroying tables. Note that you can certainly delete lines in a table. So CRUD is allowed, and one example focuses on this.
Rhodes is object oriented, while the table objects are not. So there arises the need for an object relational mapper, which in this case is called Rhom. You are encouraged by the book to keep to an object oriented approach while coding, and Rhom finesses accessing the backend.
Ähnliche Artikel finden