I don't want to comment on TPF. Nothing wrong with TPF but if you want responses from different communities you should be willing to return to those communities in order to get responses. There is your first bit of advice.

I don't understand why you need $4K to write a book. In college they taught us to actually read all of those parts of a book that precede the chapters like the preface, etc. Those sections show you what it took to write the book itself, so I would recommend that (if you have not done so), peruse your existing collection, sort out those that you liked best, and see if you can glean things that might help you in your endeavor. From my perspective here are a few things that might help:

• Lots of authors write after work. Last time I checked publishers give you advances for book writing and/or pay for good books. Of course you will need to produce a proposal and, I think, a sample chapter.
• Technical reviewers really are meaningful.I purchased one book purely because Randal Schwartz was listed as a technical reviewer. Before going too far with even your sample chapter, find some technical reviewers and list them in your proposals.
• Somewhere, somehow, the author tells me how devoting weeks to reading this book will improve my work/life.Time is precious and diving into books takes time so a few words about how a book will improve my skillset is helpful.
• Ignore cultural cues at your own peril. When I read your proposal I found the following which distressed me: "The starting point for the book would be C# Programming, a book available on the Wikibooks website ...the completed project would thus be made available under the same licence.. I read this to mean you are going to teach me how to program OO Perl much the same way one would code in C#. Some part of my brain, that part that motivates me to do things, suddenly starts to shut down. I don't want to code the same way one does in C# -- I want my Perl OO code to be leaner, quicker, slicker, and far more fun to produce.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.