https://bugs.documentfoundation.org/show_bug.cgi?id=149018

--- Comment #7 from sdc.bla...@youmail.dk ---
(In reply to Mike Kaganski from comment #6)
> is it consistent to call a linked object "embedded"?
Naive user POV.  Sure!

As a naive user, I would just accept that some objects (including "external
links") are called "embedded" in LO, and not think further about it.  (And from
an everyday pov, "external links" sound "embedded")

To some extent these distinctions are arbitrary* from UI pov (even if not
arbitrary from technical implementation pov).  

Given that "frame" and "image" get their own labels in the Properties dialog,
then it appears that the word "Object" was used as the leftover "Other"
category for other objects that have a properties dialog.

=> any chosen adjective before "object" (even if not a perfect fit) would at
least limit the scope of that group of "objects" and allow differentiation from
Shape and Textbox, which are also called "objects" (in the generic meaning).


* To elaborate this point about a certain amount of arbitrariness, from a
user/UI POV -- as noted "frame" and "image" get their own labels in the
properties dialog, but in principle, they could be considered as "embedded
objects" as well, no? 

Understandably, "frame" and "image" are used more frequently (and in different
ways), so they get their own individual labels, which makes it easier to refer
to them in help, etc.  No problem (imo).

But why (as a rhetorical question) are QR code and media files treated as
"Drawing objects" (in Navigator, and do not have an Object Properties dialog),
even though, in everyday meaning, they are embedded? And why shouldn't
textboxes and shapes also (from user pov) be considered "embedded objects"?  

As user, it is easy to accept that QR code is listed under Insert > Object
(even if technically in LO, it is not), and I accept that QR codes and media
files are treated as "drawing objects" -- which primes expectations about which
dialogs to use for positioning, formatting these objects.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Reply via email to