[TYPO3-ect] Lauching the "Partner Framework" project

Elmar Hinz elmar.DOT.hinz at team.MINUS.red.DOT.net
Wed Jan 25 19:31:42 CET 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ernesto Baschny [cron IT] schrieb:

> 
> I like that idea. But there are still things that need to be "core",
> which is what glues all "extensions" together (e.g. t3lib, which can get
> a whole lot slimer if we move most of the classes to extensions).
> 

Hello Ernesto,

logicaly some basic libraries will mostly be there, that other extensions depend
on. For the installer that is of now importance. It doesn't know anything about
core or extensions. It only reads config files to search for dependencies,
versions etc.

Imagine an extension "phpinfo" with one line of code. It would not depend on any
other extension and could be the one and only extension that you have installed.
Would work.

Let's imagine an extension (or a set of extensions) that are programmed in
another language like perl, ruby, java. I.e. a service that is running on it's
own and communicates by exchange of XML. That could be an ajax server, an
indexer engine or a game server.

See the melange of php and java that midgard uses. Imagine to use the installer
to install JCR to index the TYPO3 content tables.

http://www.midgard-project.org/midgard/1.7/architecture.html

Just to give your brains synapsis something to start them firering and produce
more ideas.

> Reviewed and "approved" extensions is a nice thing that has been
> discussed many times as it not only serves the marketing folks, but also
> all TYPO3 users who cannot find the "right" extensions. The extension
> coordination team should do that, under the wings of the Association.
> 
> Major issue seems to be nomenclature. Maybe we should call extensions
> "components", which would fit more the "block-building" approach. The
> "core" can be renamed to "typo3-glue" or something more unattractive, so
> that noone will dare to state that his company is sponsoring the
> development of the "typo3-glue". :) It will be more interesting to be
> sponsor "components", which can be "core components" or "extension
> components" or whatever other category one creates.
> 

Midgard calls them components. But I think it would probably result in a huge
chaos, if we would start to rename extensions to components only for reasons of
sponsoring.

As to the core I would simply speak of libraries or core libraries.

Regards

Elmar

- --
Climate change 2006 is killing people: floods in California, drought and fires
in Australia, Texas, Sahel, Oklahoma, South Africa. The Bush administration is
responsible for corruption of the Kyoto Protocol. The US majority is responsible
to the world for reelection of a convictable [...censored by Echelon...].
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD18QOO976RNoy/18RApqKAJ9s7ZMAwGYMM+rqSKjAA8J5guxdswCgs8V1
7lXi43prpkcQ8FITTKIoeuU=
=wdJT
-----END PGP SIGNATURE-----



More information about the TYPO3-team-extension-coordination mailing list