> Michael Baierl wrote:
> > There is a convention - an parameter array for receiving data ("named
> > parameters") and returning data as an array. Done. Never touch the input
> > array.
> > This rule is relatively easy to check during QA and it is easy to use
> > and developers are used to that.
> >
> > Every class you create has to be understood and makes stuff more
> > complicated. KISS.
> >
> Amen!
I only belief to RFC! But I am convinced.
Thanks for all comments. I'll go on with arrays.
Again: because of lot work I will be able to show a second prototype in 2
weeks or so.
I have one important point left we should discuss:
(I know, I can be annoying)
What do we need to implement the plugin-arch in the frontend part, such like
in A.L.E.C.'s list:
> Typical plugin needs are e.g. adding a button in tasklist, adding a tab
> in Settings interface, adding a configuration option in User Preferences
> (simple tasks, just for start).
I have no insight of the frontend in RC and I do not want to develop these
things right now.
But I need to know how they work that anyone can implement these things
later without rewriting my code.
I asked jeroen for his sieve patch (to find it out myself) but I havn't got
it so far.
Anyone?
--
Florian Lagg
-
Florian Lagg - IT-Komplettlösungen
Juch 7, 6631 Lermoos
tel +43 (699) 10 20 10 24
www.lagg.at - [EMAIL PROTECTED]
-
Xing: http://www.xing.com/go/invite/7372113.3da562
-
_______________________________________________
List info: http://lists.roundcube.net/dev/
