El lun, 27-02-2006 a las 12:06 +0100, Andreas Hartmann escribió: > Thorsten Scherler wrote: > > > El sáb, 25-02-2006 a las 02:07 +0100, Thorsten Scherler escribió: > >>> can you explain a bit more? Maybe give a real-world example? > >> Well, I am researching to extend lenya with a mediaType resource type. > >> Above interface is responsible to add assets (resources) to lenya. If > >> you add an asset then you add as well some meta data (e.g. height) > >> regarding the asset. > >> > >> Now in the case of mediaType documents you need this information in > >> the > >> meta data of this doc. The now implemented code change allows to pass > >> any metada to the ResourceManager and storing the asset information as > >> well there. > > I don't see why this can't be handled by the previously available > methods.
How? > What is the additional meta data parameter good for? The whole point of a media type document is to give information about the media. Now since we have made the determination between assets and documents (which does not make sence) I need all information in the *document* and not so much in the asset. The asset in reality *is* the document! > Is this the CustomMetaData object of the Document? yes > Shouldn't this > rather be handled by client code? ¿? What do you mean? The document is determined by the asset props, which are stored in the meta data. > BTW, the new code in DefaultResourcesManager contains some 2-space > indentation lines and inline Strings ... Sorry will reconfigure my IDE. Thx for the headsup. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
