Chapter 17 has grown to 53 unprinted pages. I’ve taken a lot of time to discuss all of the code that are the five classes of the application tier. Some feel that this is a huge issue, where the printed version of this chapter can swell above to 60 pages, adjusting to Manning’s typical typeface. I need help in figuring out what’s best for this chapter, and how to convey the content. Please view the following video and post your comments or email me directly at jgarcia at tdg-i.com

Click here to see this video in the full screen

Share and Enjoy:
  • Print
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Blogplay

8 Responses to “Looking for suggestions for chapter 17”

  1. I personally think that it is unreasonable to print page after page of code in a book. The code is provided on your site so if someone doesn’t get what the workflow is saying then you can reference it in the online code.

  2. ficeto says:

    I think that going through the workflow of the application is a much better idea than commenting the code mainly because you can put the important comments or even the workflow points straight into the source of the application. That way we can have the source and comments and know the workflow from the book. I see it as hitting two rabbits with one bullet :)

  3. matakari says:

    Hi out there!!! I am really new with this library EXT js, and the best thing I could find is this book. I have seen you many times in EXT JS forums and I really appreciate your participation answering questions for us. What I would like to learn is about how to export single record of a grid or an entire grid (PDF, EXCEL) using any server-side language. I do not know if you are considering in the future to talk about this. Thank you very much and I really appreciate the work you do.

    Mahatma.

  4. Jay Garcia says:

    Thank you all for your comments thus far. It seems like a split down the middle. :-\ … awaiting more input…

  5. I suggest online code and printed workflow diagrams. I think this chapter should emphasize on how to structure a big app (event model, pre-configured classes, reusability…).

    There are examples on how to use each feature of Extjs, what’s really missing is how to put all of this together, how to structure a large application and not get lost in your own code (you obviously can’t write a single huge config object and give it to the viewport ;-) ), how to write the app so that it easy to add a feature, etc.

    I believe reading the source code of your application is a great way to learn but I think it doesn’t need to be printed in its entirety.

    You did a lot of great work with this book !

  6. robertfurr says:

    I agree with floriancargoet. I have been looking for a detail explanation of how to structure a large EXT JS application that follows current design patterns and best practices. This one chapter would make the book a must have, even though our company is already buying a number of copies. This would just be icing on the cake.

  7. scottsweep says:

    Jay,
    First I want to say a sincere thank you for all of your efforts thus far. The book has already helped me in ways that would’ve taken a great deal of trial and error working through the ExtJs docs/samples.
    As for Chapter 17 I can understand both approaches. Either way I would include the work flow, it certainly simplifies and clarifies the requirements. I’d almost argue towards using it in the earlier chapters as well. However I’m leaning towards the approach of including the code. It keeps the flow similar to the rest of the book. After using books like this to gain the skills they become reference books for me, the “Jay solved this issue I just ran into in the book.” This is were the value of code and explanation together works well.
    I think as developers there’s always a tendency for us to try to re-factor and improve things. This is great in code, but the purpose of the book is to inform, and not necessarily in the shortest, most elegant way. If page count is a real issue the alternative would be to place a complete code listing in an appendix or reference similar code in other chapters.

  8. walldorff says:

    I vote for the printed workflow, with comments and an index to online code. In a later state you even can update the code, which you cannot do if it’s printed :)
    Great job, Jay. Really looking forward to this.

Leave a Reply

You must be logged in to post a comment.