Below is the features list that I gathered sofar. The annotations are
quotes from the mailinglist, I'll condense these into uniform
descriptions later on.
Any more suggestions of features to add?
Regards, Rob
FEATURES LIST:
- generic workflow support
- a standardized and documented packaging
At 11:56 +0200 18-05-2005, Rob van Maris wrote:
Below is the features list that I gathered
sofar. The annotations are quotes from the
mailinglist, I'll condense these into uniform
descriptions later on.
Any more suggestions of features to add?
I would like to add, and that is maybe in line
Ernst Bunders wrote:
It has been mentioned lately that fascilities for creating more
'intelligent' clients for mmbase would require some kind of metadata
availability.
Some steps have been made to share mmbase config information across the
network, but perhaps these could be tuned and
This may partially be addressed by the field-types project; it is about
configuring more meta-data about fields and providing access and use of
that. That would. e.g. elimate the need for specifying those kind of
things again in your editor-implementation (like occurs now in
editwizard).
Michiel wrote:
I have no real clue how to communicate in some comprehensible way this
kind of information to the client, for javascript impelmentaiton of the
same or so.
This is where I figured the client-side XML would earn it's keep.
I figure that much of this stuff will for some time
Emile wrote:
Michiel wrote:
I have no real clue how to communicate in some comprehensible way this
kind of information to the client, for javascript impelmentaiton of the
same or so.
This is where I figured the client-side XML would earn it's keep.
I figure that much of this
I think a seperation of layers would be advisable, but in a more abstract
fashion than core and bridge - how about Toolset, Services, Application
and Package (such as CMS - which is functionality consisting of multiple
applications and services).
Obviously, the more generic stuff filters it's way
Rob van Maris wrote:
I also think we should include 'Core2' in the roadmap.
What's Core2?
A new core implementation that implements the bridge interface and
possibly allows for some new features such as extending nodes. It would
also be in a more logical package than org.mmbase.module.core
--
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Michiel Meeuwissen
Verzonden: donderdag 12 mei 2005 17:08
Aan: Discussion list for developers
Onderwerp: Re: [Developers] Roadmap features request
Ernst Bunders wrote:
i think it would
At 13:31 +0200 12-05-2005, Michiel Meeuwissen wrote:
- From the 'bugtracker':
Total Bugs: 986 Open Bugs : 171 MMBase is 17.342796 % broken
Closed Bugs : 815 MMBase is 82.657196 % working
Total Wishes: 127 Open Wishes : 43
Submitters want 33.85827 % new features
Closed Wishes : 84
ernst
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Rob van Maris
Verzonden: woensdag 11 mei 2005 12:13
Aan: Discussion list for developers
Onderwerp: [Developers] Roadmap features request
Hi developers,
The committers have recognized
-core2 (Bridge node managers)
-java developer and framework friendliness
___
Developers mailing list
Developers@lists.mmbase.org
http://lists.mmbase.org/mailman/listinfo/developers
-java developer and framework friendliness
Please explain.
When developing mmbase based applications that do not use the mmbase taglibs
an great amount of custom programming has to be done.
40% of that code is creating simple or complext queries
40% of that code is O/O mapping (MMBase objects
13 matches
Mail list logo
