Abdelrazak Younes wrote:
Andre Poenitz wrote:
On Thu, Oct 04, 2007 at 09:19:04PM +0200, Andre Poenitz wrote:
I am looking for a way to solve the "controller problem".
[...]
Hm, with all the fuss about insets and ranges, any comment on that?
I think that what we call "controllers" are really just abstraction
layers created for the benefit of code sharing between multiple
frontends. I am still in the opinion that non obvious algorithms
should be kept outside the frontends and I hope that you won't
transfer everything to qt4/. I am personally perfectly fine with the
idea of removing the controller API layer but, if you do that, I'd
prefer that you isolate relevant codes that is frontend independent
and put them in helper functions. Those helpers functions can stay in
frontends/controllers/ or in a new frontends/helpers/ I don't really
care, but I think it is a good idea to keep them separate. A new
frontend could then choose to use those helpers or not.
Basically, frontends/qt4 should contain everything about
_visualisation_ on screen and frontends/helpers/ should contain
advanced algorithms like data searching, etc.
That's my understanding of the rationale, as well.
Richard
--
==================================================================
Richard G Heck, Jr
Professor of Philosophy
Brown University
http://frege.brown.edu/heck/
==================================================================
Get my public key from http://sks.keyserver.penguin.de
Hash: 0x1DE91F1E66FFBDEC
Learn how to sign your email using Thunderbird and GnuPG at:
http://dudu.dyn.2-h.org/nist/gpg-enigmail-howto
