[Typo3-dev] extension reviewing

[Christoph Moeller]

Mathias Schreiber [K1net] schrieb:

>>The latter could be a project going hand in hand with maintenance of
>>the Extension Kickstarter Wizard! So I could wish that a team would
>>form who would dedicate themselves to provide what this thread (in
>>particular Wolfgang) touched: a) better default code, b) dummy
>>extensions with examples, c) documents.

Wasn't there a document already used in some cases by the extension 
reviewers, some time ago, that contained some pretty detailed guidelines 
on code structure, quality, communicativeness of the author, etc. pp.? 
Have to dig on my HD for that one...couldn't that one be extended to 
match the current situation and incorporate a more modern workflow in 
terms of open, distributed and transparent processes of reviewing?

> I would like a little switch to set whether I want default code or not :)
> Everything except for the header comment and the main function gets deleted
> within the first 15 seconds of extension developement in our cases.

Good idea - I second that.

> I do see the pros of more or "better" default code, whatever that means.
> But with 3.6.0 and the fully commented code (thanks Kasper, this is really
> making our lifes easier) combined with an PHP IDE makes writing extensions
> soooo simple, fast and thus cost efficient.

Nevertheless, as somebody in this thread already suggested, demo 
snippets for common tasks (mode switching via GPvars, correct GPvar 
names, widely used API funcs, gfx handling, cObjects, RTE parsing for 
your output, accessing/modifying TS, you name it) would be a 
nice-to-have gadget. We are currently working on sth. like that to be 
able to train co-workers faster on how to write clean T3 extensions.

Greets,
Chris

-- 
network.publishing
internet & network service
moeller westbunk gbr