[wp-hackers] phps for plugins

Jeremy Wright jeremy at ensight.org
Mon Jul 17 23:21:04 GMT 2006

Snazzy. I say it's a keeper. You may want to put an interface around it to
copy the code, explain what it's for, etc (and so people don't try and just
save it), but I say snazzy.

Jeremy Wright
Skype: jeremy_wright
Phone: 506 466 3855
Author of Blog Marketing
Order at: http://www.ensight.org/book
President, b5media
Website: http://www.b5media.com
Blogger, Business Consultant
Personal Blog: http://www.ensight.org
Disclaimer: All information contained in this email is for the entitled
recipients only. Any dissemination of the contents of this email verbally,
electronically in print or otherwise is strictly forbidden without the
express consent of the author. If you believe you have received this email
in error, please let me know via email at jeremy at ensight.org.

-----Original Message-----
From: wp-hackers-bounces at lists.automattic.com
[mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Computer Guru
Sent: Monday, July 17, 2006 8:18 PM
To: wp-hackers at lists.automattic.com
Subject: [wp-hackers] phps for plugins

I'm finally getting around to doing what I've always wanted, and that's
churning out the plugins.

My webserver supports the phps extension as highlighted php code. It takes
the PHP and formats it as colored HTML. You can copy and paste the code just
fine to a new document to create your plugin.


Now my question is, is this the 'preferred way' or is it more preferable to
save it as plain-text files that can be downloaded straight to the plugins


For example,

It's a _lot_ easier on the eyes, but if anyone were to save the target and
upload, it wouldn't work since it's formatted HTML, not PHP.

What's the right way?


Computer Guru

NeoSmart Technologies <http://neosmart.net/> 



wp-hackers mailing list
wp-hackers at lists.automattic.com

More information about the wp-hackers mailing list