[TYPO3-ect] RFC: Result Browser Service for lib/div - part 1 + 2

[Franz Koch]

Hi Elmar,

> even writing good working coding guidelines takes some time. Give us the
> resources and we do it immidatley. Directly after the kickstarter__mvc, the
> pear dependencies, the resultbrowser service, the resultbrowser
> implementation, the bugfixing, the API documentation, the tutorials,
> directly thereafter we do this coding guidelines. Immidately. We just need
> the resources, not more.

I know that it's hard to find enough resources and that currently you are the most active user in ETC (thanks for your efforts btw.). Your answer before just sounded like:

"let's see how the acceptance of lib/div will be, and if the acceptance is good and there are many many extensions built on lib/div we might suggest coding guidelines"

and that definately would have been a wrong reason for waiting.


OffTopic:
---------
I'd really like to contribute to typo3 and ETC in special, but currently my spare time equals a negativ ten or so. I mostly can only contribute project specific, as I did it for cal (finding bugs and provide bugfixes and improvements) when I needed a calendar for a customer. Soon I need another small ext and I will use kickstarter__mvc for that. Hope that I can give some feedback. I'd also need a pagebrowser (who not) but the project is to small for developing the ETC-RFC-compliant pagebrowser - so it might simply be a quickly generated one in the view-template for now. But the ext could be a base for a general commenting system - let's see - I still have problems with good MVC coding :(.

-- 
Kind regards,
Franz Koch