[TYPO3-ect] Final goal of the new framework ?

[steve ryan]

seems to me that typo3 has a pretty amazing track record for keeping 
backward compatibility

Defining some standards and prototyping control models is a great start 
to making it easier for developers/kickstarter users.

I'd like to see
* standard TCA based rendering libraries for forms, lists, searchboxes, 
links ...  These libraries would include features for relationship 
management including selector boxes and ability to embed 
forms.Preferably with some sexy ajax.
* standard TCA based validation libraries
* list of standard static utils eg isBitwiseOptionEnabled, t3lib_db... 
   , handleFileUploads - the div library
* code output from the kickstarter that does 
search/list/view/edit/delete on a table that is easy to customise to 
fill a range of other roles. For example list a list renderer could be 
driven by configuration which can then be easily customised even at the 
typo3 administration level.
* standard API for authenticating record access using FE or BE users.

The name of the game is being able to turn out an application in short 
order. If the kickstarter can generate many common interface components 
tied together in a simple editor controller for all the database tables 
it creates you can build applications pretty quickly.
Also
I know a dozen people who are out there building database applications 
with the admin interface extension which does some of the above. These 
people know nothing about computer programming. There are lots more of 
them than us.


Stever


-






Elmar Hinz wrote:
> Jean-Baptiste Rio schrieb:
> 
>>Hi list,
>>
>>I'm following all the threads in this list, and i'm a lot disturbed. I
>>try to see how the new framework will find its place in the Typo3 galaxy.
>>
>>I see two ways :
>>- It aims to be an alternate way to build extension
>>- It aims to be the new standard for extensions
> 
> 
> Both is true. But the new standard doesn't come overnight nor is it
> planned in details. It is in dynamic development.
> 
> 
>>I'm not against the new framework concept, i'm just wondering if you
>>have thought to all consequences in terms of works, backwards
>>compatibility, product stability, etc... if you decide to make it the
>>only one for extensions or if you decide to change the structure of
>>extensions (see "Zend style extensions scheme").
>>
> 
> 
> Since 20 years the standard is CD, today also DVD. But the old
> standard of vinyl still exists and you can use it pleaese you. :-) Do you?
> 
> 
> 
>>Last but not least, i've seen that SOAP integration is planned for Typo3
>>5.0 (roadmap). Why not build the new extension concept as Typo3 Web
>>Services ? It will have many advantages without the disadvantages of the
>>extension manager rewriting.
> 
> 
> I am sure SOAP opens some interesting aspects. But I doubt that it is
> a fast way to access the own server via SOAP. If I am hungry I go
> directly into the kitchen and don't send myself a parcel with a bread
> mail.
> 
> Have a nice evening
> 
> Regards
> 
> Elmar
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>