[TYPO3-core] RFC #8232: Creating and editing of fields, forms, etc. in FCE's is impossible if there is a section inside

Dmitry Dulepov [typo3] dmitry at typo3.org
Fri Aug 15 21:24:16 CEST 2008


Hi!

Benjamin Mack wrote:
> Dmitry Dulepov [typo3] wrote:
>> I guess it is better to put it now unless Andreas makes a complete 
>> rewrite of TCEforms (which is questionable for 4.3).
> I'm glad you put the "unless" there. (And yes, I am NOT joking).

Better if such things are announced because I though about doing the same. We could end up in conflicting independent implementations. After all there is still a team. If such a big activity is to come to the core, it is nice to know about it. Otherwise it can be rejected because it may be inappropriate or lack certain features. Does Andreas know all these small things about flexforms, sections, containers, non-implemented things to implement, etc? If no, new implementation is no replacement for the old one. Imagine if he spends hours on it and then we find that implementation lacks support for different translation models. What's next? Work lost?

We had examples of problems created by individual work without announcement. The change of sections in TCEforms by Kasper is a good example: he did them without consulting anyone. As a result we have screwed up RTE and non-working rearranging of elements. Such things should not happen. If we are a team, we must work like team works. At least we must coordinate activities. Otherwise we are not a team but a collection of individuals who work erratically. Bad thing to do given our competitors strength these days.

> If you refuse to redo the patch (which will not be difficult, I will 
> assure you), then I'll do that once Andreas' changes are coming.

Yes, I refuse to rewrite it. I already did it. So if my work is lost, I am not to repeat it.

-- 
Dmitry Dulepov
TYPO3 Core team
My TYPO3 book: http://www.packtpub.com/typo3-extension-development/book
In the blog: http://typo3bloke.net/post-details/typo3_code_formatting_in_eclipse/


More information about the TYPO3-team-core mailing list