#5753 HIGH Update.: A shared copyText() method should exist in the common Sugar API.

[Zarro Boogs per Child]

#5753: A shared copyText() method should exist in the common Sugar API.
------------------------+---------------------------------------------------
  Reporter:  legutierr  |       Owner:  marco    
      Type:  defect     |      Status:  new      
  Priority:  high       |   Milestone:  Update.2 
 Component:  sugar      |     Version:  Build 650
Resolution:             |    Keywords:           
  Verified:  0          |    Blocking:           
 Blockedby:             |  
------------------------+---------------------------------------------------

Comment(by legutierr):

 Replying to [comment:2 tomeu]:
 > Well, the problem is that it is not only text. We have plain text in
 different encodings plus rtf, html, etc. As activities can offer and
 accept a subset of those formats, some negotiation needs to happen. AFAIK,
 the situation is the same in other X-based desktops, win32 and osx.
 >
 > We certainly want the users to think that it is only text, but for that
 we need some cooperation from activity developers.
 >
 > In my opinion, the most we can do is to decide some standardized formats
 for each kind of data.

 tomeu-

 Well, I've never had any issues copying text out of one Mac application
 and pasting it into another, and that's not just because of Apple's QA.
 Apple does a little more than rely on its external (and internal)
 developers' adherence to standards to maintain consistency in the
 implementation.  By implementing extensive frameworks that encapsulate
 app/os interactions (including special cases like diverse text encodings)
 in a highly usable and encapsulated way, Apple gives developers tools that
 they are likely to use to implement common tasks (like clipboard
 interaction), so that they avoid trying to do those things
 (incorrectly/inconsistently) on their own.

 In other words, I believe that there is a design-oriented solution to this
 problem.

 I'm trying to think of ways to contribute to this project (thanks for that
 API link BTW), and I would love to spend some time working on a way to
 make it easier for developers to obey the standards set by sugar (like
 providing more extensive tools in the API).  Contributing anything in that
 area would require some close coordination with the core design team,
 however, so I don't know.  What do you recommend?

-- 
Ticket URL: <http://dev.laptop.org/ticket/5753#comment:3>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system