On 11/23/05, David Chisnall <[EMAIL PROTECTED]> wrote: > One thing I would like to add is a lightweight component system. As > far as I can tell, the only modification required to GNUstep is the > addition of a notification to the source when an object in a drag and > drop operation is dropped. This would allow the source to notify > other places if it changed. > > On top of this, we would need to add some kind of standard types that > must be included in every inter-component pasteboard. I would > suggest: > Some kind of URL in an Etoile namespace signifying the origin. > A PDF or text representation of the object (either is allowed). > > Any drop target can then display the PDF or text representation and > link back to the original when the user wants to edit it.
Well, yes, in fact I mainly talked about the "desktop/projects" thing, not so much about the rest, particularly because I personally don't have a definitive solution for the component system, even if intuitively it should be doable to have something quite nice rather easily by: - finishing to implement NSDatalink -- that way you can link components, even with live links - add a light layer on top of the systems to provide roles The only problem with that idea of components is that it won't implement "live" components (like say konfabulator widgets or OpenDoc components), but on the other hand, they aren't that useful outside some known cases, while NSDatalink should cover a fair amount of cases with minimum efforts.. Now if we find a good idea for OpenDoc-like components, I'm all for it. -- Nicolas Roard "Any sufficiently advanced technology is indistinguishable from magic." -Arthur C. Clarke
