Re: Metadata (was: Plugin API (was Re: new ideas))
Andreas Zehender <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kpovmodeler |
|---|---|
| Message-ID | <[email protected]> |
Hi! On Thursday 11 July 2002 15:07, Greg Copeland wrote: > On the other hand, if only the plugin that creates the meta data is able > to access it, one could argue that it's privately owned by the object > but this does no one any good and would only serve to waste time in > development. If it's privately owned by the object and accessible by > only a single entity, I think we are REALLY saying it's privately owned > by the *plugin*. After all, what value would there be in this when it's > all said and done if only the plugin that creates it can access it > (sounds more and more like private data to the plugin to me). Why > develop a storage medium and API to support what would be more efficient > for each plugin to do on a case by case basis which could then be > optimized for the type of data it needed to store/manage? But then the plugin has to store a list of all objects and take care, if objects are created or deleted. That's what I don't like. The data should be stored inside the object whether it is protected or not if it belongs to the object. Andreas -- -------------------------------------------------- Andreas Zehender, Dipl. Ing. (BA) Student, 10th semester computer science http://www.azweb.de [email protected] | [email protected] -------------------------------------------------- List archive and information: http://mail.kde.org/mailman/listinfo/kpovmodeler-devel