Judson Valeski wrote:
> At the 12/14/00 meeting we discussed the following interfaces. Visit the
> said URL and view the most recent notes for details.
>
> nsIClipboardCommands -
> http://www.mozilla.org/projects/embedding/apiReviewNotes.html#nsIClipboardCommands
The only thing that needs to be added to the API is probably a
copyLinkLocation(). This will differentiate between copying the selected
data (say the text of a link, or the bits of an image, handled by
copySelection()) and copying the URL associated with it. Needed because
they are different items in context menus and it's impossible to devine
the user's intent with just one "copy" command.
We don't need a new api to select an item. Images are "selected" as
well, so we can always just work with the selection in the focussed area.
Image copying is being worked on, we will probably just have gecko
interact with the clipboard via nsIImage and code internal to the
clipboard will convert between nsIImage and platform-native image
formats. Embedding applications will not be exposed to any of this, and
will only see the platform-native image data on the clipboard, just like
with other apps. Pavlov was worried that I'd screw unix, so now he gets
to help ;)
I'm not sure what bstell is asking about text encoding...we'd do
whatever we do now in Seamonkey, and the platform's specified encoding
is used for translating from unicode -> ascii plain text.
In the future, it would be nice to directly email the owners of the APIs
being discussed. I get so much API spam these days, I don't have time to
read them all, and thus missed the one I actually cared about! An email
with "We're discussing your nsIFoopy API this week" in the subject might
get much better turnout ;) Just trying to be helpful.
--
Mike Pinkerton
Mac Browser Weenie
[EMAIL PROTECTED] http://people.netscape.com/pinkerton
