FOP developer's style guide? (Was: interface instead of implementation)
On Wednesday 06 November 2002 16:31, Rhett Aultman wrote: . . . Maybe we should seriously consider a FOP developer coding standard and start writing it down and putting it on the site. I'd offer to help with that. . . . How about using a wiki page (web page where everyone can very easily write and edit) to work together on a draft style guide. including links to existing guides so we don't reinvent the wheel? If I get some +1s on this I'll setup the page and publish its address here. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP developer's style guide? (Was: interface instead of implementation)
You get my +1. A Wiki for a draft, followed by a vote for commitment to a less malleable form, is the best way I could see for us to do this. -Original Message- From: Bertrand Delacretaz [mailto:bdelacretaz;codeconsult.ch] Sent: Wednesday, November 06, 2002 10:48 AM To: [EMAIL PROTECTED] Subject: FOP developer's style guide? (Was: interface instead of implementation) On Wednesday 06 November 2002 16:31, Rhett Aultman wrote: . . . Maybe we should seriously consider a FOP developer coding standard and start writing it down and putting it on the site. I'd offer to help with that. . . . How about using a wiki page (web page where everyone can very easily write and edit) to work together on a draft style guide. including links to existing guides so we don't reinvent the wheel? If I get some +1s on this I'll setup the page and publish its address here. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP developer's style guide? (Was: interface instead of implementation)
+1 On Wed, 6 Nov 2002 16:48:11 +0100 Bertrand Delacretaz wrote: On Wednesday 06 November 2002 16:31, Rhett Aultman wrote: . . . Maybe we should seriously consider a FOP developer coding standard and start writing it down and putting it on the site. I'd offer to help with that. . . . How about using a wiki page (web page where everyone can very easily write and edit) to work together on a draft style guide. including links to existing guides so we don't reinvent the wheel? If I get some +1s on this I'll setup the page and publish its address here. -Bertrand Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP developer's style guide? (Was: interface instead of implementation)
How about using a wiki page [ ... ] +1 -- Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP developer's style guide? (Was: interface instead of implementation)
Wow, that's a quick vote... I have setup the page at http://codeconsult.ch/wiki/index.php/FopDevelopersStyleGuide with a most basic style guide skeleton. I have to run now, but feel free to work on it. Make sure you keep copies of what you write, I cannot guarantee backups on this server yet. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
