On 8/8/05, Emile <[EMAIL PROTECTED]> wrote: > Here's an example where a change in policy could add a raft of code to > mmbase: "utilities". I've had to develop my own little utilities for > getting the next posrel pos field, for ordering resultsets, for getting the > "n'th" position, etc. I wondered if anybody else had done this sort of > thing before, then it occurred to me that surely MOST people have done this > before - in a similar veign, ie. as a utility within their code. That code > is not finding it's way back into mmbase - I assume because most utility > writers are application developers and not core developers. > > Perhaps I'm mistaken regarding posrel and don't know mmbase well enough to > judge it, but it's the principle of sharing code that's at stake here. > > At the moment there is the core and there are applications, what about the > things that every coder repeats for every application? Surely there should > be an "utilities" section with anyone allowed to contribute code - assembled > by someone at some stage as the much touted "framework" (of which there > could be many)?
I for sure have done this multiple times, and even wrote even more tree builders. I have never managed to create anything reusable in this area. in this case I would love to set the bridge return RelatedNodes (node that contain the relation and the related node) But if we can start with util classes that can represent such thing that would be great -List builder (build around the posrel builer) that can be sorted and updated -LinkedList builder for prev/next relations _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
