Hrmm. Now what if, instead of a socket (which is a kernel-level thing and
thus harder to regulate), each activity gets
A. Telepathy tubes, for real-time communication. (Activities already have
this, we just need a "directory" service that lets activities find other
activities' tubes. *but only tub
Gary, Yioyos, Martin,
The trick is to prevent circumstantially malicious co-Activities from doing
harm, without at the same time preventing cooperation between functional
blocks essential to the satisfaction of user needs.
I ran into this issue, when I was writing my python debugger "PyDebug". I
--- On Sat, 7/24/10, Gary Martin wrote:
> From: Gary Martin
> Subject: Re: [support-gang] Fwd: Redesigning: Library, Read, Get-Books, and
> Content bundles
> To: "Community Support Volunteers -- who help respond to help AT laptop.org"
>
> Cc: "Andreas G
Gary, Yioryos,
Here are a couple of thoughts for you on isolation issues. (I have thoughts on
the Journal issues too but I'll save them for another occasion.)
>> Step 3 is to introduce marks (hyperlinks?) in Read and Write where hovering
>> over you get the tag opened to tell you what is about, a
document, so once saved
your annotations can not be removed/edited. I usually end up with a trail of
separate documents saved just in case I need to revert.
I'm digging around in Reads Epub support at the moment, I'll keep my eyes open
for possible annotation support.
Regards,
--Gar
or that there is nothing we can do about the
> Read/ETexts issues and better focus elsewhere, or none of
> the above.
> > At the end of the day is up to the developers to do
> what they want, but is nice to be clear on what we would
> like to have if we could.
> >
> >
>
