Pierre van Rooden <[EMAIL PROTECTED]> wrote: > The toSTring() for node now gives different (or no) results depoending > on whether you use it in the bbridge or the core, and whether you call > it on a normal or a clusternode.
There is even another one, namely the toString of RemoteNode (of RMMCI), which is now simply (iirc) the toString of Object. > So, what should toString() of MMObjectNode return? And should this or One should add: the _default_ toString of MMObjectNode. For certain builders e.g. relations, and typerel, certain other toString can (and are) be defined. > 2. Return the gui() of the node. For nodemanagers this would return the > guiname of the buidler. Clusterbuidler should implement a useable gui() > function. > This is the current bridge toString(). I think it obvious that gui() is dependent on the output type, ie, in practice text/html now. This is proved by the gui() of an image (someone decided that that should give <img src etc... So gui() is for text/html. I imagine that this output format should actually be confirable by an (optional) argument of gui(). Since toString has no arguments, I think the gui() is no real option for toString, they are simply different things. > > 3. Return all fields in the node. This is pretty hard to read though. > This is the current core toString(). > > 4. Nothing. Just use Object.toString() > > Maybe people have other ideas? Let's add: 5. Return the first (non-empty file) of the node. This will normally be 'title' or so, and be sufficiently descriptive for the complete node. Michiel -- mihxil' Michiel Meeuwissen Mediapark C101 Hilversum +31 (0)35 6772979 []()
