[Typo3-shop] New tt_products

[JoH]

> > As i mentioned in another thread:
> > We should think about a "shop plugin" for current tt_news since the
basic
> > funcionality and structure is nearly the same, regarding items,
categories,
> > latest items, old items a.s.o.
> > This would have three advantages:
> > 1. We had a working structure that "only" had to be extended with
pricing,
> > calculation and some other features and ERP functionalities
>
> i don't know the new tt_news. before we start this way, which is fine
> for me, one of the gurus should review the latest extension. if
> everything is fine - lets start. btw. how is multilanguage solved in
> tt_news?

AFAIK they are currently working on this task.

> > 2. We could do it in a way, that updates to the current tt_news version
> > would update the new tt_products as well.
>
> how?

If we used tt_news as the "engine" for tt_products.
It would be enough having an interface that provides this "engine" that
doesn't change with every update of tt_news.

Something like this but of course not as a TS-solution ;-)

plugin.tt_products < plugin.tt_news
plugin.tt_products {
    useTable = tt_products
    extendFunctions < plugin.shop
}

tt_products would have tt_news in the dependencies list to make sure the
"engine" is available.

> should we start a thread 'feature request' for tt_products or how you'd
> like to start collecting ideas?

Well - IMHO best thing would be to list some standards everybody needs in a
shop system.
Anyone who knows about one of those standards (means: something that is used
by many shop systems in the same way) should provide such a list.
Then we should ask possible clients about a wishlist.

After that we can see how we can group standards and wishlists together to
some feature-blocks that could be handled by one PHP-class.
Then we need a main class where all available variables are defined and the
subclasses are called.

After that we could start creating those subclasses independently in small
teams.
Each class should be a PHP-code that could be working as a standalone
version, when called from the frontend and provided with some parameters.

Maybe we can create this self igniting firework Kasper once has been talking
about ...

Joey