[kepler-dev] [Bug 5174] Reduce the number of modules in Kepler CORE.

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5174

Christopher Brooks <cxh at eecs.berkeley.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cxh at eecs.berkeley.edu

--- Comment #1 from Christopher Brooks <cxh at eecs.berkeley.edu> 2010-09-08 16:34:25 PDT ---
My theory about the number of modules is that tool developers want
to have many modules because they see all the combinations and see
them all as useful.  Tool users just want one module, because they
see the tool as a monolithic object and don't care if they get
extra stuff.

This is true of Ptolemy, where I see it as many modules and Kepler
developers and users just see it as one module.

One possible solution would be to includes ways to group modules -
a hierarchy of modules.  We may even have this now.  The idea
is that a product consists of a number of groups of modules or
groups of groups etc.  Modules don't necessarily belong to a specific
group, for example the ptolemy.util module is used by both the
headless ptolemy runtime engine and the plotter.

By using groups, it might be possible to help the user decide what
modules are needed.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.