[TYPO3-dev] Product database with article booking system and history

Jochen Rau jochen.rau at typoplanet.de
Mon Dec 14 09:29:30 CET 2009


Hi Thomas.

schrieb Thomas "Thasmo" Deinhamer:
> =o) K, to get this going...
>
> I'm considering using Extbase/Fluid for this requirements;
> creating a TCA, some models, views and a controller already
> gave me some nice output - really straightforward.
>
> May there be any, not yet fully implemented, features, which
> may give me problems using extbase/fluid on this project?
>
> As I don't need a backend module, I won't run into limitations
> using the image viewhelper, which doesn't work yet - if I'm right.

I see no limitations for an implementation with Extbase and Fluid based 
on your requirements list.

We have no open issue regarding to the ImageViewHelper. Please report 
one on forge if necessary.

Regards
Jochen


>
> Thomas "Thasmo" Deinhamer schrieb:
>> Good evening,
>>
>> I'm looking for a solution for a categorized product database
>> including a booking system, where frontend users can order/book
>> products, which need to be returned after they have been lend.
>>
>> The articles or products should have a stock per storehouse. In
>> fact there are several storehouses which hold a specific stock amount
>> of all existing products. These products can be lend to customers
>> for a specific time and will be returned to the storehouses afterwards.
>>
>> The stock amount will vary therefor, if products are not inhouse.
>>
>> Furthermore each action (product update, stock change, order acceptance,
>> order deniance, order return, etc.) should be logged to a history
>> table per product - so it is possible to overlook which products
>> where lend out from which storehouses for which timerange to
>> which client, etc.
>>
>> Could you think of using several existing extensions for this
>> or should I write this on my own using frontend plugins and
>> backend hooks?
>>
>> And could this be done with Extbase/Fluid already without
>> a lot of headache regarding flexibility and consistency?
>>
>> Thanks a lot for help and your oppinions,
>> Thomas

-- 
Every nit picked is a bug fixed





More information about the TYPO3-dev mailing list