future development of lib/div

View: New views
14 Messages — Rating Filter:   Alert me  

future development of lib/div

by Franz Holzinger :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

What is the common opinion of the extension developers?

1) The div/lib should still be developed in the ECT. It will be
refactored as much as needed and considered usefull.
2) The div/lib should be moved now into TYPO3 Core and only Core
developers will make decisions on it.
3) A completely new MVC framework shall be developed instead of lib/div.
4) Another MVC framework extension shall be taken und developed instead
of lib/div. All current code of lib/div will be put there.


See: thread 'ECT - teamleaders'

- Franz
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

Re: future development of lib/div

by Daniel Bruessler-4 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello Franz,

so here my answer:

NOW for the current extensions: 1)
for FUTURE extensions (in 1 year?) as alternative: 4) FORGE-MVC

> What is the common opinion of the extension developers?
> - Franz
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

Parent Message unknown Re: future development of lib/div

by philip.almeida :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


> What is the common opinion of the extension developers?
>
> 1) The div/lib should still be developed in the ECT. It will
be
> refactored as much as needed and considered usefull.
> 2) The div/lib should be moved now into TYPO3 Core and only Core
> developers will make decisions on it.
> 3) A completely new
MVC framework shall be developed instead of lib/div.
> 4) Another
MVC framework extension shall be taken und developed instead
> of
lib/div. All current code of lib/div will be put there.
>
Hello,
my vote goes to option number 2, but I must had the
following notes for your consideration:
- Development should also be
possible to ETC members in coordination with CORE (commit is CORE
responsability) .
- MVC Kickstarter extension must also be appointed
to core integration (It can not  be separate from Lib/Div).
- Main
tutorials should refer LIB/DIV as the choosen default MVC CORE paradigm
(this is the only way developers will start using it).
This
integration to core will "push"  new developers into
MVC.
Typo3 version 4 lacks a developing paradigm based on design
patterns lib/div may be the one.
Best regards,
Philip
Almeida 
>
> See: thread 'ECT -
teamleaders'
>
> - Franz
>
_______________________________________________
>
TYPO3-team-extension-coordination mailing list
>
TYPO3-team-extension-coordination@...
>
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination
>
Email and shopping with the feelgood factor!
55% of income to good causes. http://www.ippimail.com/
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

Re: future development of lib/div

by Michael Cannon-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Being a lib/div developer, I'd like to see MVC methodology migrated to
the TYPO3 core and it become the standard. The resulting code when
done right, comes out much cleaner and more flexible than our previous
do all in one class method process.

Even if lib/div transition into FLOW3 or something, while I'm not
asking for backwards compatibility, I would like information on how to
migrate lib/div extensions to FLOW3.
--
Michael Cannon
President of Cannonbose, LLC
+1 (800) 559-9773 | +1 (603) 559-9773 | Fax : +1 (802) 609-2776
http://www.cannonbose.com
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

Re: future development of lib/div

by omic :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi everyone,


 > Being a lib/div developer, I'd like to see MVC methodology migrated to
 > the TYPO3 core and it become the standard. The resulting code when
 > done right, comes out much cleaner and more flexible than our previous
 > do all in one class method process.

I do agree. But it seems to have a long and far distance until it could reach the core.

The first step would be to build a team that is continuing the work on the framework. Not easy to
find people that have the time and the skills... I see myself rather as a contributor.

Bonus: interesting reading on the sponsoring side. Read milestone 1. Ground work, MVC and Form objects.

http://typo3.org/development/sponsoring/list-of-sponsored-projects/new-form-object/
http://typo3.org/fileadmin/sponsored_projects/new_form.pdf

Michael Cannon a écrit :

> Being a lib/div developer, I'd like to see MVC methodology migrated to
> the TYPO3 core and it become the standard. The resulting code when
> done right, comes out much cleaner and more flexible than our previous
> do all in one class method process.
>
> Even if lib/div transition into FLOW3 or something, while I'm not
> asking for backwards compatibility, I would like information on how to
> migrate lib/div extensions to FLOW3.
> --
> Michael Cannon
> President of Cannonbose, LLC
> +1 (800) 559-9773 | +1 (603) 559-9773 | Fax : +1 (802) 609-2776
> http://www.cannonbose.com
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

Re: future development of lib/div

by Michael Cannon-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Fabien,

Isn't FLOW3 effectively replacing the div/lib modeling for TYPO3 5.0?

It seems FLOW3 pulls in the best software design patterns and makes
them real for us to use.
--
Michael Cannon
President of Cannonbose, LLC
+1 (800) 559-9773 | +1 (603) 559-9773 | Fax : +1 (802) 609-2776
http://www.cannonbose.com


On Thu, Jul 3, 2008 at 4:04 PM, Fabien Udriot <fudriot@...> wrote:

> Hi everyone,
>
>
>  > Being a lib/div developer, I'd like to see MVC methodology migrated to
>  > the TYPO3 core and it become the standard. The resulting code when
>  > done right, comes out much cleaner and more flexible than our previous
>  > do all in one class method process.
>
> I do agree. But it seems to have a long and far distance until it could reach the core.
>
> The first step would be to build a team that is continuing the work on the framework. Not easy to
> find people that have the time and the skills... I see myself rather as a contributor.
>
> Bonus: interesting reading on the sponsoring side. Read milestone 1. Ground work, MVC and Form objects.
>
> http://typo3.org/development/sponsoring/list-of-sponsored-projects/new-form-object/
> http://typo3.org/fileadmin/sponsored_projects/new_form.pdf
>
> Michael Cannon a écrit :
>> Being a lib/div developer, I'd like to see MVC methodology migrated to
>> the TYPO3 core and it become the standard. The resulting code when
>> done right, comes out much cleaner and more flexible than our previous
>> do all in one class method process.
>>
>> Even if lib/div transition into FLOW3 or something, while I'm not
>> asking for backwards compatibility, I would like information on how to
>> migrate lib/div extensions to FLOW3.
>> --
>> Michael Cannon
>> President of Cannonbose, LLC
>> +1 (800) 559-9773 | +1 (603) 559-9773 | Fax : +1 (802) 609-2776
>> http://www.cannonbose.com
> _______________________________________________
> TYPO3-team-extension-coordination mailing list
> TYPO3-team-extension-coordination@...
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

Re: future development of lib/div

by omic :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

> Isn't FLOW3 effectively replacing the div/lib modeling for TYPO3 5.0?

Of course!

And gimmefive is a kind of bridge in T3 v4 using some part of the FLOW3's code.

There is already a demo extension using it:
http://forge.typo3.org/projects/extension-gimmefive/news

> It seems FLOW3 pulls in the best software design patterns and makes
> them real for us to use.
> --
> Michael Cannon
> President of Cannonbose, LLC
> +1 (800) 559-9773 | +1 (603) 559-9773 | Fax : +1 (802) 609-2776
> http://www.cannonbose.com
>
>
> On Thu, Jul 3, 2008 at 4:04 PM, Fabien Udriot <fudriot@...> wrote:
>> Hi everyone,
>>
>>
>>  > Being a lib/div developer, I'd like to see MVC methodology migrated to
>>  > the TYPO3 core and it become the standard. The resulting code when
>>  > done right, comes out much cleaner and more flexible than our previous
>>  > do all in one class method process.
>>
>> I do agree. But it seems to have a long and far distance until it could reach the core.
>>
>> The first step would be to build a team that is continuing the work on the framework. Not easy to
>> find people that have the time and the skills... I see myself rather as a contributor.
>>
>> Bonus: interesting reading on the sponsoring side. Read milestone 1. Ground work, MVC and Form objects.
>>
>> http://typo3.org/development/sponsoring/list-of-sponsored-projects/new-form-object/
>> http://typo3.org/fileadmin/sponsored_projects/new_form.pdf
>>
>> Michael Cannon a écrit :
>>> Being a lib/div developer, I'd like to see MVC methodology migrated to
>>> the TYPO3 core and it become the standard. The resulting code when
>>> done right, comes out much cleaner and more flexible than our previous
>>> do all in one class method process.
>>>
>>> Even if lib/div transition into FLOW3 or something, while I'm not
>>> asking for backwards compatibility, I would like information on how to
>>> migrate lib/div extensions to FLOW3.
>>> --
>>> Michael Cannon
>>> President of Cannonbose, LLC
>>> +1 (800) 559-9773 | +1 (603) 559-9773 | Fax : +1 (802) 609-2776
>>> http://www.cannonbose.com
>> _______________________________________________
>> TYPO3-team-extension-coordination mailing list
>> TYPO3-team-extension-coordination@...
>> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

Re: future development of lib/div

by Franz Holzinger :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Fabien Udriot a écrit :
>> Isn't FLOW3 effectively replacing the div/lib modeling for TYPO3 5.0?
>
> Of course!

Hello,

if it proclaims to replace div/lib, where will the methods of div/lib be
put? Someone cannot move to another extension library if functions
already used in div/lib are missing there.

Franz
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

Re: future development of lib/div

by Daniel Bruessler-4 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello Fabien and Franz,

please don't mix it together. There's NO competition yet between the two
solutions. lib/div is a NOWADAYS framework and it's a very good one.
FLOW3-MVCpackage aka "gimmefive" is the FUTURE framework.

=> This should be TWO ECT-coordination efforts.

Cheers!
Daniel


> Fabien Udriot a écrit :
>>> Isn't FLOW3 effectively replacing the div/lib modeling for TYPO3 5.0?
>> Of course!
>
> Hello,
>
> if it proclaims to replace div/lib, where will the methods of div/lib be
> put? Someone cannot move to another extension library if functions
> already used in div/lib are missing there.
>
> Franz
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

Re: future development of lib/div

by Daniel Pšötzinger :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Franz Holzinger schrieb:

> What is the common opinion of the extension developers?
>
> 1) The div/lib should still be developed in the ECT. It will be
> refactored as much as needed and considered usefull.
> 2) The div/lib should be moved now into TYPO3 Core and only Core
> developers will make decisions on it.
> 3) A completely new MVC framework shall be developed instead of lib/div.
> 4) Another MVC framework extension shall be taken und developed instead
> of lib/div. All current code of lib/div will be put there.
>
>
> See: thread 'ECT - teamleaders'
>
> - Franz
I vote for 3, there is much possibilities to use the exoerience with
lib/div and build something new - also inspired by FLOW3 and ZEND...
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

Re: future development of lib/div

by Christof Damian-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

2008/7/2 Franz Holzinger <franz@...>:
> What is the common opinion of the extension developers?
>
> 1) The div/lib should still be developed in the ECT. It will be
> refactored as much as needed and considered usefull.
> 2) The div/lib should be moved now into TYPO3 Core and only Core
> developers will make decisions on it.
> 3) A completely new MVC framework shall be developed instead of lib/div.
> 4) Another MVC framework extension shall be taken und developed instead
> of lib/div. All current code of lib/div will be put there.

1 or 2 for me. We are using lib/div in a few projects and I think it
makes extension development a lot easier and maintainable. I also like
that it is a very small extension, which I can easily fix and extend
myself.

I am pretty happy with the features it has at the moment, it just
needs a bit more love to reach a 1.0 version. I would like better
support for back end modules and more support for testing. And maybe
ORM support for the models (though I probably can get that to work now
already). The main problem is the missing documentation, examples,
lack of kickstarter support and small community.

Regarding 4+5: I have projects which use lib/div, so I don't really
have the choice of switching. I also wonder why this should be better
then lib/div or faster reaching a stable version. You would also have
the same problems as lib/div which I mentioned above.

Just my 2c
Christof
--
Christof Damian
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

Re: future development of lib/div

by Franz Holzinger :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello Daniel,

> please don't mix it together. There's NO competition yet between the two
> solutions. lib/div is a NOWADAYS framework and it's a very good one.
> FLOW3-MVCpackage aka "gimmefive" is the FUTURE framework.
>
> => This should be TWO ECT-coordination efforts.

So I would like to develop the div extension to become independant from
lib. You could use the div API then without any needs to install lib.
Would you pass me over the div extension key?
Who wants to take over the further lib development?

- Franz
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

Re: future development of lib/div

by Daniel Bruessler-4 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello Franz,

please write an email to Robert, then he transfers the extension-key to
you. Elmar is the owner of the key and he's not answering in the moment.

Cheers!
Daniel

> Hello Daniel,
>
>> please don't mix it together. There's NO competition yet between the
>> two solutions. lib/div is a NOWADAYS framework and it's a very good
>> one. FLOW3-MVCpackage aka "gimmefive" is the FUTURE framework.
>>
>> => This should be TWO ECT-coordination efforts.
>
> So I would like to develop the div extension to become independant from
> lib. You could use the div API then without any needs to install lib.
> Would you pass me over the div extension key?
> Who wants to take over the further lib development?
>
> - Franz
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination

Re: future development of lib/div

by Steffen Kamper-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Daniel Bruessler schrieb:
> Hello Franz,
>
> please write an email to Robert, then he transfers the extension-key to
> you. Elmar is the owner of the key and he's not answering in the moment.
>
> Cheers!
> Daniel
>

Hi,

all exts are in forge now, together in the ECT project. Franz you are
also leader. So work can continue without Elmar.
If he's interested to continue he can join the project, otherwise he
should give the keys to ECT

vg Steffen
_______________________________________________
TYPO3-team-extension-coordination mailing list
TYPO3-team-extension-coordination@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination