Re: [B2-devel] TESyncScrap (Thoughts on SheepShaver and Basilisk II)

[Alexei S. <ale...@gm...>]

On Mon, Jun 18, 2012 at 9:06 PM, Josh Juran <jj...@gm...> wrote:

> On Jun 18, 2012, at 3:51 PM, Alexei Svitkine wrote:
>
> > On Mon, Jun 18, 2012 at 2:38 PM, Robert Munafo <mr...@gm...>
> > wrote:
> >
> >> In my scientific apps, written by me and running within SheepShaver,
> >> the clipboard PICT data includes a label with important
> >> information as
> >> text strings (DrawString). These label text strings need to survive
> >> the transfer to the host OS in order for cut/paste to be useful.
> >
> > Assuming there's no good open source library to handle arbitrary
> > PICT data,
> > the solution here would be to add some functionality to TESyncScrap
> > or a
> > similar extension that would intercept clipboard data on the guest
> > OS side
> > and when it's a PICT, rasterize it into PICT bitmap-only data,
> > putting that
> > back on the guest clipboard.
>
> This would be a separate extension which patches PutScrap().
>
> > Then, when SheepShaver gets that data, the PICTs will be guaranteed
> > to only
> > have bitmap data, which could be handled by paintlib (or possibly
> > even some
> > simpler code we can just write for SheepShaver) which would then be
> > easily
> > convertible to the host OS clipboard format.
>
> I don't think replacing the PICT data is a good idea, since the pre-
> rasterized picture would no longer be available to other Mac
> applications.  But adding it as, say, 'Pict' or 'Bits' should work.
>
> > This solution would then work cross-platform, instead of being tied
> > to Mac
> > OS X as the host.
>
> Shall I do this?
>

I think that would be useful. If you store them in a separate data type,
then it doesn't have to be a PICT at all - maybe something even simpler so
we could process it from the SheepShaver side without needing any library.

By the way, maybe the sources for these extensions should live in the
SheepShaver repository? What do you think?

-Alexei