Frank Schoenheit, Sun Microsystems Germany wrote:
Hi Paolo,
[...]
> "Consistency" from the user POV would be:
> I design a dialog into a document embedding some images.
> Then, I copy/paste the dialog (or even the single image control) into
> another library (e.g. into a different document or into a shared
> library) and images are still there, just like other properties.
I fully agree, everything else is a bug. But I don't see how this
contradicts the suggestion to store the "embedded image" in the
document. That's an implementation detail which you as user shouldn't
bother with. We developers need to bother with it, and we need to find a
solution for dialogs/images in a non-document Basic library, or an
extension. But from a user's POV, the behavior should be exactly as you
described it.
Frank is correct, 'where' the image is stored is an implementation
detail [*]. For non-document Basic dialogs I always thought that the
status quo of using a file url was sufficient, having an embedded image
( where embedded means embedded in the document ) associated with the
control didn't seem to make sense at all . I must admit I didn't even
consider extensions ( just not on my radar ) But in theory there is
nothing to prevent the implementation propagating the same solution to
non-document basic dialogs. For sure extensions which are self
contained, relocatable entities this imo makes perfect sense, for
normal application level libraries this could work too ( but not sure
if it really is necessary as it gives nothing extra ) otoh why not
[*] there is a good reason for using the document itself where the
embedded images are stored, using a central place means a single image
can be shared amongst many clients that use the same image ( a kindof
reference counting of images ) and that is in fact what happens
currently :-)
So, Frank for your ucp solution which I would guess will somehow
somewhere re-use the GraphicObject stuff, assuming that is the case we
should perhaps agree a common location ( such as the root folder e.g.
just as in documents ) where the 'Pictures' folder will be located, that
way at least whenever Dialogs in extensions are enabled to handle
embedded images it can take advantage of any pre-existing instances of
embedded images.
Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
