Thuban more modular?

Bernhard Reiter bernhard at intevation.de
Sat Apr 2 16:22:55 CEST 2005


Am 31. Mar 2005 um 09:03:24 schrieb Jonathan Coles:
> what are people's thoughts on moving some of what is now
> core-functionality into Extensions? 

> in general, thuban should provide a very basic framework onto which all
> the real functionality is added. the concept of a layer is part of that
> framework, but specific implementations of that concept are extensions,
> no?

I have seen this approach to modularisation raised as idea quite a few times, 
but often the implementation did not really lived up to the expectations.
One reason is that it add more bureaucracy to the developers,
like the checks which components are here yet.
In this way it also prevent to make one interface great for the users, 
because optimising a huge number of possible component combinations
puts more burden on the interface design side.

Our progress with Thuban currently is slow and we do have competition.
So my tendency is to not put more into Extensions, because it is more work.
Instead we should extent functionality and speed to get it to
enlarge the number of users.

Just my 0.02 Euro Cent.
	Bernhard


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.intevation.de/pipermail/thuban-devel/attachments/20050402/3b9d076c/attachment.bin


More information about the Thuban-devel mailing list

This site is hosted by Intevation GmbH (Datenschutzerklärung und Impressum | Privacy Policy and Imprint)