PHP Cookbook, 2nd Edition

sklar.com/blog

Tuesday, August 10. 2004

PHP Cookbook, 2nd Edition

Adam and I are working on a new edition of PHP Cookbook.

What was left out of the first edition that you want to see in the second edition? What cool hacks do you use all the time that should be in the Cookbook? What was in the first edition that should go away?

Posted by David in php at 20:44 | Comments (6) | Trackbacks (0)

Trackbacks

Trackback specific URI for this entry

No Trackbacks

Comments

Display comments as (Linear | Threaded)

It feels kind of weird to need a second ed already, even if it wont go to print for what 6-8mnths?

#1 Paul Reinheimer (Link) on 2004-08-11 18:11 (Reply)

Paul -- Are you thinking of Learning PHP 5 (which just came out, and yes, it would be weird to be working on a 2nd edition already)?

PHP Cookbook has been out for a few years and there have been lots of changes to PHP since then.

#1.1 David (Link) on 2004-08-11 19:02 (Reply)

Yes, yes it has.

Sorry, the book was new to me, and having been lucky enough to win it at NyPHP when other new books have been given out, I assumed it was recently published.

Forgive me, I'm Canadian

#1.1.1 Paul Reinheimer (Link) on 2004-08-12 22:55 (Reply)

The darned PEAR Cache_DB problems -- a discussion of other options would be nice now that Cache_DB 'apparently never worked'...

#2 Wellington Fan on 2004-08-19 13:46 (Reply)

I cannot think of suggestions for your new cookbook because I haven't faced problems with php yet(total newbie), but I have to say that some sort of php workshop or tutorials book would be a real nice read for newcomers

#3 lenny on 2004-09-10 23:08 (Reply)

I would hit on using the jpSpan technology. I think it's incredibly useful to have javascript call your php functions so that you don't need a page reload or use hidden iframes when a user does anything.

#4 Dallas DeVries (Link) on 2005-02-11 15:45 (Reply)

Add Comment

Name
Email
Homepage
In reply to
Comment	Enclosing asterisks marks text as bold (word), underscore are made via _word_. Standard emoticons like :-) and ;-) are converted to images. To prevent automatted Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Only if the strings match, your comment will be submitted. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly. Enter the string from the spam-prevention image above:
	Remember Information?
Submitted comments will be subject to moderation before being displayed.