Content

[Star Trader]

Greeting Friends,

I would like to propose some additional chapters, and ask some
questions about existing ones.

I believe we need to ad chapters on the following:

* Rack along with mongrel, thin ebb etc.. and something on Rack
Middleware
* Using ORM's other then DataMapper
* Rake and Thor, particularly how to use the built in task and how to
create your own.
* Resources and REST
* Using the API Documentation

Other content questions:

What belongs in 2.7 Models and what belongs in 3.x? There is a great
deal of overlap here.

Does something like presenter classes belong in this book? There are
a lot of different ways to work with models which ones do we want to
dig into?

What project structure do we want to describe in 2.3 just the full
stack or all of the generated apps?

I'm also having a problem with the 10 word limit. A lot of concepts
just take a lot of words to describe.

Star Trader
http://github.com/startrader/merb-book

[Matt Aimonetti]

Star Trader,

 First I'd like to thank your for your contribution. I just merged in a lot of content and did notice your work.

My goal for the first version of the book is to keep things simple and well covered. Things like other ORMS would be great but I'd prefer to focus on the stack first and then add more content. Rack middleware could go in appendix with Rake and Thor.

I'm not saying your suggestions are bad, I'm just trying to prioritize the content so we can get a first version of the book out pretty soon. The advantage of using PDF releases is that we will be able to add more content really quickly.

Finally, I'm open to discuss this matter, but for any type of advanced stuff not covered in the current TOC, I'd suggest to write content in the wiki for now and to import it in the book for the next release.

- Matt

[Rich Morin]

At 16:29 -0800 12/8/08, Star Trader wrote:
> I'm also having a problem with the 10 word limit.
> A lot of concepts just take a lot of words to describe.

First, it's not a "limit". The Guideline says:

Any sentence that contains more than ten words
should be regarded with suspicion.

Given that the guideline itself takes more than ten words,
this clearly isn't a hard and fast rule. Instead, it's a
simple way to raise a warning flag when a sentence may be
getting too long.

So, if you look at a sentence that's over ten words and it
is tight and well constructed, leave it alone. But first,
look...

-r
--
http://www.cfcl.com/rdm Rich Morin
http://www.cfcl.com/rdm/resume r...@cfcl.com
http://www.cfcl.com/rdm/weblog +1 650-873-7841

Technical editing and writing, programming, and web development

[Star Trader]

Matt,

Getting a first ed. out quickly makes a lot of sense when you put it
that way. I'll concentrate on the full stack application in that
case. I would still like to find some place to walk through the
resource concept within the MVC chapters sense it is so important
(IMHO) to designing good scalable applications.

Rich,

Thanks for the reply. I'll just say, I'm glad I'm not the one having
to translate all this stuff. I'm glad there are a lot of volunteers,
but some of these things are just plane complex.

Thanks all,

Star Trader

On Dec 8, 9:00 pm, "Matt Aimonetti" <mattaimone...@gmail.com> wrote:
> Star Trader,
>
>  First I'd like to thank your for your contribution. I just merged in a lot
> of content and did notice your work.
>
> My goal for the first version of the book is to keep things simple and well
> covered. Things like other ORMS would be great but I'd prefer to focus on
> the stack first and then add more content. Rack middleware could go in
> appendix with Rake and Thor.
>
> I'm not saying your suggestions are bad, I'm just trying to prioritize the
> content so we can get a first version of the book out pretty soon. The
> advantage of using PDF releases is that we will be able to add more content
> really quickly.
>
> Finally, I'm open to discuss this matter, but for any type of advanced stuff
> not covered in the current TOC, I'd suggest to write content in the wiki for
> now and to import it in the book for the next release.
>
> - Matt
>