[TYPO3-paymentlib] paymentlib with flexforms

[Thijs Hakkenberg]

Tonni Aagesen schreef:
> Thijs Hakkenberg wrote:
>
>   
>>> My main worry is that I'd like to keep the paymentlib extension as 
>>> "clean" as possible and focus on its primary task. For example, 
>>> supporting any number of import/export is likely to have a lot more 
>>> release cycles, which might interfere with a perhaps more conservative 
>>> development approach to paymentlib enabling payments.
>>>
>>> Actually, as I'm writing this I'm getting more and more convinced, 
>>> that it should be a separate extension.
>>>       
>
>   
>> Yes, I totally agree with you there, we are developing these imports 
>> seperatly and have always done so.
>> The only thing I woul like to see 'added' to paymentlib is the option to 
>> edit a transaction item in the backend- at this moment there is a list 
>> item in the backend called 'transaction', but you can't edit this element.
>>     
>
> Actually, I was planning to remove the BE-module from paymentlib and 
> leave it up to separate extention to handle these things as well.
>
> If you are up for it, you could create extensions like:
>
> paymentlib_admin
> paymentlib_admin_X
> paymentlib_admin_Y
>
> where "paymentlib_admin" could be a general interface to 
> paymentlib/transaction administration and the X/Y could be specific 
> implementations like CSV and the Dutch format GMU-thing etc... The 
> sample principle that applies to paymentlib and providers.
>   
That's actually very smart- then you acutally have the choice to 
implement the posibility to edit transactions or not.

We will be starting a wiki and maybe even a mailinglist for the whole 
membership/donation/invoicing system, and create a roadmap etc.
>
>   

-- 
Thijs Hakkenberg
Stichting Varkens in Nood
m 	06 48761131
t: 	020 6177757
w: 	www.varkensinnood.nl <http://www.varkensinnood.nl>