basilisk-devel — Basilisk II development-related discussion

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

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

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.

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.

This solution would then work cross-platform, instead of being tied to Mac
OS X as the host.

-Alexei

Re: [B2-devel] Linking to Cocoa for a 64-bit forward development path

[Charles S. <bas...@ch...>]

On Jun 18, 2012, at 5:39 PM, Alexei Svitkine wrote:

> And indeed for things like the 64-bit copy/paste support, the solution is to rewrite the clipboard code to use Cocoa APIs. Patches welcome.

Jean-Pierre already posted a patch for this in the TESyncScrap thread a little bit earlier today. It looks like he used the Pasteboard Manager APIs in HIServices instead of the Cocoa APIs, but both should work equally well.

Charles

Re: [B2-devel] Linking to Cocoa for a 64-bit forward development path

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

>
> My main point here is (IMHO) linking to Cocoa or other Objective C
> libraries is quite feasible


Yes, I'm not sure why this is such a surprise since SheepShaver has been
linking to Cocoa forever. For example we use SDLMain.m which is all
Objective-C code and the built-in prefs editor on Mac OS X is built with
Cocoa.

And indeed for things like the 64-bit copy/paste support, the solution is
to rewrite the clipboard code to use Cocoa APIs. Patches welcome.

-Alexei

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

[Charles S. <bas...@ch...>]

On Jun 18, 2012, at 4:24 PM, Charles Srstka wrote:

> On Jun 18, 2012, at 4:13 PM, Robert Munafo wrote:
> 
>> I have Xcode 3.2.6 on both of my Snow Leopard machines, but I'll need
>> instructions on how to create the project and where to put the missing
>> main() routine, and/or how to compile it from the command line with
>> /usr/bin/xcodebuild.
>> 
>> I tried making a new project from templates "Cocoa Application" and
>> "Quick Look Plug-In", but your code doesn't seem to fit into either of
>> those.
>> 
>> (Anyone else aside from Charles, feel free to clue me in. I don't mind
>> looking foolish :-)
> 
> You just paste it into the Document-Based Application template. Then, you put an NSImageView in the .xib file and bind it to the “image” property on File’s Owner, and put in a button, menu item, whatever you please, and bind it to -convertToTIFF: either on File’s Owner or on First Responder.
> 
> However, the snippet I posted was ARC, which Xcode 3 doesn’t support, so you’ll want to stick a release after assigning self.image, in order to avoid a memory leak. I should have thought of that, since you already mentioned you were on Snow Leopard. Sorry about that.

Oh, one other change you’ll have to make for Xcode 3 is to stick a declaration for the -convertToTIFF: method in the header file; otherwise Interface Builder probably won’t see it.

As for main(), there’s rarely anything in there in a Cocoa app. Typically it’s just one line that calls NSApplicationMain() and returns the result. The framework handles all the actual initialization stuff.

Charles

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

[Charles S. <bas...@ch...>]

On Jun 18, 2012, at 4:13 PM, Robert Munafo wrote:

> I have Xcode 3.2.6 on both of my Snow Leopard machines, but I'll need
> instructions on how to create the project and where to put the missing
> main() routine, and/or how to compile it from the command line with
> /usr/bin/xcodebuild.
> 
> I tried making a new project from templates "Cocoa Application" and
> "Quick Look Plug-In", but your code doesn't seem to fit into either of
> those.
> 
> (Anyone else aside from Charles, feel free to clue me in. I don't mind
> looking foolish :-)

You just paste it into the Document-Based Application template. Then, you put an NSImageView in the .xib file and bind it to the “image” property on File’s Owner, and put in a button, menu item, whatever you please, and bind it to -convertToTIFF: either on File’s Owner or on First Responder.

However, the snippet I posted was ARC, which Xcode 3 doesn’t support, so you’ll want to stick a release after assigning self.image, in order to avoid a memory leak. I should have thought of that, since you already mentioned you were on Snow Leopard. Sorry about that.

I can just send you a binary if you want; send me a message off-list if you want me to.

Charles

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

[Robert M. <mr...@gm...>]

I have Xcode 3.2.6 on both of my Snow Leopard machines, but I'll need
instructions on how to create the project and where to put the missing
main() routine, and/or how to compile it from the command line with
/usr/bin/xcodebuild.

I tried making a new project from templates "Cocoa Application" and
"Quick Look Plug-In", but your code doesn't seem to fit into either of
those.

(Anyone else aside from Charles, feel free to clue me in. I don't mind
looking foolish :-)

On 6/18/12, Charles Srstka <bas...@ch...> wrote:
> Out of curiosity, would you mind trying -[NSImage imageWithData:] on one of
> your PICT files with the text label? I am curious whether NSImage preserves
> the label text or not.
>
> Here’s the code for a minimal PICT viewer app:
> [...]
>
> If you don’t have the dev tools installed or would just prefer for me to
> send me a binary, let me know.

-- 
  Robert Munafo  --  mrob.com
  Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 -
mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com

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

[Jean-Pierre <cho...@fr...>]

Le 18 juin 2012 à 22:48, Robert Munafo a écrit :

> I'll take a look at it, thanks!
> 
> Why is there "#ifndef _CARBON_BUILD_" around the "#include
> <Carbon/Carbon.h>" ? Isn't that backwards? (The rest of the ifdefs
> seem right though)

Carbon API does not exist for x86_64 code in Mac OS X, this was the reason of my patch, as I was working on the 64 bit part of Mach-O JIT code and this file couldn't compile.
I guess this macro is defined somewhere when you add the Carbon Framework. I don't remember how I did, this was too many years ago. ;)

 -JP.

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

[Charles S. <bas...@ch...>]

On Jun 18, 2012, at 2:05 PM, Robert Munafo wrote:

> On 6/18/12, Charles Srstka <bas...@ch...> wrote:
>> Are there any OS X / Windows apps that currently accept pasteboard data in
>> PICT format though?
> 
> No, that's why SheepShaver converts it. Here are the steps, to make it clear:
> 
> 1. I start SheepShaver, and start my old app within SheepShaver.
> 2. Copy to clipboard.
> 3. Switch to Snow Leopard's TextEdit, hit Paste.
> 4. I get my image, with the original bitmap image and the label text
> nicely rendered below it.
> 
> Somewhere in the process (SheepShaver and/or TextEdit) it has turned
> the PICT, including the label text, into a TIFF image.
> 
> The text is there because something in the Carbon libraries is making
> it happen. But it we use that stand-alone PICT conversion library
> instead of Carbon, the text label would be missing.

Out of curiosity, would you mind trying -[NSImage imageWithData:] on one of your PICT files with the text label? I am curious whether NSImage preserves the label text or not.

Here’s the code for a minimal PICT viewer app:

@interface Document ()

@property (copy) NSImage *image;

@end

@implementation Document

@synthesize image = _image;

- (NSString *)windowNibName {
    return @"Document";
}

+ (BOOL)autosavesInPlace {
    return NO;
}

- (NSData *)dataOfType:(NSString *)typeName error:(NSError **)outError {
    NSException *exception = [NSException exceptionWithName:@"UnimplementedMethod" reason:[NSString stringWithFormat:@"%@ is unimplemented", NSStringFromSelector(_cmd)] userInfo:nil];
    @throw exception;
    return nil;
}

- (BOOL)readFromData:(NSData *)data ofType:(NSString *)typeName error:(NSError **)outError {
    self.image = [[NSImage alloc] initWithData:data];
    
    if(self.image == nil) {
        if(outError) *outError = [NSError errorWithDomain:NSCocoaErrorDomain code:NSFileReadUnknownError userInfo:nil];
        return NO;
    }
    
    return YES;
}

- (IBAction)convertToTIFF:(id)sender {
    NSSavePanel *sp = [NSSavePanel savePanel];
    
    sp.allowedFileTypes = [NSArray arrayWithObject:(__bridge NSString *)kUTTypeTIFF];
    
    [sp beginSheetModalForWindow:self.windowForSheet completionHandler:^(NSInteger result) {
        if(result != NSFileHandlingPanelOKButton) {
            return;
        }
        
        NSError *error = nil;
        if(![self.image.TIFFRepresentation writeToURL:sp.URL options:NSDataWritingAtomic error:&error]) {
            [self presentError:error];
        }
    }];
}

@end

If you don’t have the dev tools installed or would just prefer for me to send me a binary, let me know.

Thanks,
Charles

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

[Robert M. <mr...@gm...>]

I'll take a look at it, thanks!

Why is there "#ifndef _CARBON_BUILD_" around the "#include
<Carbon/Carbon.h>" ? Isn't that backwards? (The rest of the ifdefs
seem right though)

On 6/18/12, Jean-Pierre <cho...@fr...> wrote:
> Le 18 juin 2012 à 20:40, Robert Munafo a écrit :
>> Handling text-only clipboard transfer is a very good first step. It
>> will benefit a lot of end-users.
>
> Here you are.
>
> It's still incomplete, but it could be a good start for sharing pictures as
> well.
>
> Best regards,
>
>  -JP.

-- 
  Robert Munafo  --  mrob.com
  Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 -
mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com

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

[Jean-Pierre <cho...@fr...>]

Le 18 juin 2012 à 19:37, Charles Srstka a écrit :

> But this is only for pasteboard support between the emulated and host systems, right? Do we really need 100% compatibility for that? As long as a PICT image on the emulated pasteboard gets translated to a TIFF or PNG or something on the host pasteboard and vice-versa 99% of the time, any rare corner cases should be only a minor inconvenience.

BTW, the patch I've just posted seems to work also for pictures, as I could copy a sample image from Picture Viewer in Mac OS 9 and paste it in Mac OS X's Preview.
I have no picture editor in my classic environment, so I can't tell for pasting into Classic, but it might worth trying.

 -JP.

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

[Jean-Pierre <cho...@fr...>]

Le 18 juin 2012 à 20:40, Robert Munafo a écrit :

> On 6/18/12, Jean-Pierre <cho...@fr...> wrote:
>> I wrote a small patch to exchange text clipboard for the Mac OS X 64bit
>> version when I worked on the 64bit Mach-O support, but It was never
>> merged.Not sure if I ever submitted it either...
>> If you want it let me know.
> 
> Yes, that would be great!
> 
> Handling text-only clipboard transfer is a very good first step. It
> will benefit a lot of end-users.

Here you are.

It's still incomplete, but it could be a good start for sharing pictures as well.

Best regards,

 -JP.

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

[Robert M. <mr...@gm...>]

On 6/18/12, Charles Srstka <bas...@ch...> wrote:
> Are there any OS X / Windows apps that currently accept pasteboard data in
> PICT format though?

No, that's why SheepShaver converts it. Here are the steps, to make it clear:

 1. I start SheepShaver, and start my old app within SheepShaver.
 2. Copy to clipboard.
 3. Switch to Snow Leopard's TextEdit, hit Paste.
 4. I get my image, with the original bitmap image and the label text
nicely rendered below it.

Somewhere in the process (SheepShaver and/or TextEdit) it has turned
the PICT, including the label text, into a TIFF image.

The text is there because something in the Carbon libraries is making
it happen. But it we use that stand-alone PICT conversion library
instead of Carbon, the text label would be missing.

-- 
  Robert Munafo  --  mrob.com
  Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 -
mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com

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

[Ronald P. R. <ron...@xs...>]

Op 18 jun. 2012, om 20:05 heeft Robert Munafo het volgende geschreven:

> So does that mean we can boot Lion in 32-bit mode and run 32-bit
> SheepShaver and get a working copy and paste?
> 

I can run SheepShaver fine in 32-bit mode in Lion, booted into 64-bit mode. That is true for all applications (also many of Apple's own applications) that are built for both i386 and x86_64 architectures. One can choose to run an application in either 32-bit or 64-bit mode in Finder Info for the app.

With SheepShaver running in 32-bit mode, one can copy and paste text between MacOS and OSX, with limitations.

I do agree, though, that working on 64-bit SheepShaver (and BasiliskII) is essential for maintaining compatibility with future OSX versions.


Ronald P. Regensburg.

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

[Charles S. <bas...@ch...>]

On Jun 18, 2012, at 1:38 PM, Robert Munafo 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.
> 
> There are many other cases of real users transferring object-based
> (i.e. not bitmap) PICT data between MacOS classic applications via cut
> and paste.

Are there any OS X / Windows apps that currently accept pasteboard data in PICT format though?

Charles

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

[Robert M. <mr...@gm...>]

So noted. I'm definitely going to buy Mountain Lion.

I mainly only bought Lion so I'd have it in the future in case I need
to do some testing.

On 6/18/12, Charles Srstka <bas...@ch...> wrote:
> Don’t upgrade to Lion now. Mountain Lion is coming out in probably less than
> a month [...] you should definitely upgrade to Mountain Lion rather than
> Lion.

-- 
  Robert Munafo  --  mrob.com
  Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 -
mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com

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

[Robert M. <mr...@gm...>]

On 6/18/12, Jean-Pierre <cho...@fr...> wrote:
> I wrote a small patch to exchange text clipboard for the Mac OS X 64bit
> version when I worked on the 64bit Mach-O support, but It was never
> merged.Not sure if I ever submitted it either...
> If you want it let me know.

Yes, that would be great!

Handling text-only clipboard transfer is a very good first step. It
will benefit a lot of end-users.

-- 
  Robert Munafo  --  mrob.com
  Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 -
mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com

Re: [B2-devel] git!

[Christian B. <cb...@ce...>]

Hi!

On 06/16/2012 07:38 PM, Alexei Svitkine wrote:
> Can you create a new GitHub repo containing both SS and BasiliskII
> sources from the CVS TOT and add me as a collaborator?

Let me know whether this works for you:
https://github.com/cebix/macemu

Bye,
Christian

-- 
   / Physics is an algorithm
\/ www.cebix.net

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

[Robert M. <mr...@gm...>]

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.

There are many other cases of real users transferring object-based
(i.e. not bitmap) PICT data between MacOS classic applications via cut
and paste.

On 6/18/12, Charles Srstka <bas...@ch...> wrote:
> But this is only for pasteboard support between the emulated and host
> systems, right? Do we really need 100% compatibility for that? As long as a
> PICT image on the emulated pasteboard gets translated to a TIFF or PNG or
> something on the host pasteboard and vice-versa 99% of the time, any rare
> corner cases should be only a minor inconvenience.

-- 
  Robert Munafo  --  mrob.com
  Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 -
mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com

[B2-devel] Linking to Cocoa for a 64-bit forward development path

[Robert M. <mr...@gm...>]

On 6/18/12, Charles Srstka <bas...@ch...> wrote:
> [...]
> Yep, and -[NSImage initWithData:] gets you an NSImage containing an
> NSPICTImageRep when you use it with PICT data. However, there’s a disclaimer
> in the documentation stating that because it’s not using QuickDraw, the
> image might not look *exactly* the same as the original. However, that
> disclaimer’s pretty much always been there, so I wouldn’t worry too much
> about it.
> https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/ApplicationKit/Classes/NSPICTImageRep_Class/Reference/Reference.html
> [...]
> Just tried it; -[NSImage initWithData:] works fine with PICT on 64-bit Snow
> Leopard too.

Wow, this is great. So it's just Carbon that got deprecated, not the PICT stuff.

If we link to Cocoa objects we can do this, and perhaps all the other
stuff that we're using Carbon for at present.

I know we can link the C to Objective-C using small bits of glue
routines -- I know, because I implemented such routines to add an
NSAutoreleasePool handler for SheepShaver (back when I was trying to
use my MacPorts-installed X11 version of SDL). (I know there is a
NSAutoReleasePool_wrap in BasiliskII/src/MacOSX/utils_macosx.h but it
doesn't seem to be used, and there are some other .mm files that all
seem to be for the GUI-based Prefs editor).

I made SheepShaver/src/MacOSX/autorelease.mm containing:

  #include "autorelease_pool.hpp"
  #import <Foundation/NSAutoreleasePool.h>
  t_autorelease_pool::t_autorelease_pool() : d_pool([NSAutoreleasePool new]) {}
  t_autorelease_pool::~t_autorelease_pool() { [this->d_pool drain]; }

and in SheepShaver/src/MacOSX/autorelease_pool.hpp:

class t_autorelease_pool {
public:
    t_autorelease_pool();
    ~t_autorelease_pool();
private:
#ifndef NO_T_ID
    id d_pool; // << you may opt to preprocess this out when not needed.
#endif
private:
    t_autorelease_pool(const t_autorelease_pool&);
    t_autorelease_pool& operator=(const t_autorelease_pool&);
};

Then in about 10 places, e.g. SheepShaver/src/Unix/ether_unix.cpp I added:

  #define NO_T_ID
  #include "../../../SheepShaver/src/MacOSX/autorelease_pool.hpp"

  //...
  // in slirp_receive_func:
    t_autorelease_pool pool;

Later I figured out that the recurring autorelease messages were SDL's
fault, and I switched to the "build SDL from source first" method like
everyone else uses, and then my autorelease messages went away.

However when I get the SIGSEGV crash, my console output still shows a
lot of __NSAutoreleaseNoPool errors, so I might try it again if I get
really frustrated with the crashes.

My main point here is (IMHO) linking to Cocoa or other Objective C
libraries is quite feasible and perhaps a good way to move B2 and SS
further ahead.

-- 
  Robert Munafo  --  mrob.com
  Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 -
mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com

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

[Frank T. <fra...@gm...>]

On Mon, Jun 18, 2012 at 1:05 PM, Robert Munafo <mr...@gm...> wrote:

> Wow, Frank, this is cool! I love being wrong this way.
>
> (I feel like if I keep saying things that I hate about Apple, you'll
> keep telling me I'm wrong :-)
>
> If you complained about the sharp-edged aluminum casings that scratch
themselves and other things at the slightest provocation or about the
inconsistency of Apple's update packaging or about how Apple intentionally
accelerates the depreciation of its products so as to shorten purchase
cycles, I would not tell you that you're wrong. There are plenty of
absolutely awful things that Apple does. If you are using an Apple product
as something other than a disposable consumer product, you will be
disappointed quite often.


> I found some examples of people booting Lion in 32-bit mode:
>
>  https://discussions.apple.com/thread/3225388?start=0&tstart=0
>  https://discussions.apple.com/thread/3943837?start=0&tstart=0
>
> So does that mean we can boot Lion in 32-bit mode and run 32-bit
> SheepShaver and get a working copy and paste?
>
> 32-bit applications can run even when the kernel is running in 64-bit
mode. This does not work for certain things like drivers, but it ought to
work for anything that you would put into the Applications folder. A Mach-O
package can hold code for multiple architectures, and most of the Lion
libraries have 32-bit and 64-bit code. If you run a 32-bit application, it
calls stuff from the 32-bit code in the libraries. This is why mach_kernel
on Snow Leopard had PowerPC code, for example.


> I hope so... then maybe I'll actually try out that copy of Lion I
> bought last winter for $30. PICT files and SheepShaver cut/paste were
> holding me back.


I am not sure of whether that works when running the operating system in
64-bit mode, but it is worth a try.


> (Also the lack of Save and Revert commands in the
> standard suite, what were they thinking? Oops, I'm complaining again.
> Please tell me I'm wrong.)
>
Standard suite? You mean the things like TextEdit?


>
> On 6/18/12, Frank Trampe <fra...@gm...> wrote:
> > Not exactly. Certain kernel-related things must run in 64-bit mode, but
> > there is still i386 support.
> >
> > {
> > cambridge:~ admin$ uname -v
> > Darwin Kernel Version 11.4.0: Mon Apr  9 19:32:15 PDT 2012;
> > root:xnu-1699.26.8~1/RELEASE_X86_64
> > cambridge:~ admin$ file /mach_kernel
> > /mach_kernel: Mach-O universal binary with 2 architectures
> > /mach_kernel (for architecture x86_64): Mach-O 64-bit executable x86_64
> > /mach_kernel (for architecture i386): Mach-O executable i386
> > }
>
> --
>  Robert Munafo  --  mrob.com
>  Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 -
> mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>

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

[Charles S. <bas...@ch...>]

On Jun 18, 2012, at 1:05 PM, Robert Munafo wrote:

> So does that mean we can boot Lion in 32-bit mode and run 32-bit
> SheepShaver and get a working copy and paste?

You can’t boot Lion into 32-bit mode, but you don’t have to. 64-bit Lion can run 32-bit i386 apps (but not PowerPC apps) just fine.

> I hope so... then maybe I'll actually try out that copy of Lion I
> bought last winter for $30. PICT files and SheepShaver cut/paste were
> holding me back. (Also the lack of Save and Revert commands in the
> standard suite, what were they thinking? Oops, I'm complaining again.
> Please tell me I'm wrong.)

Don’t upgrade to Lion now. Mountain Lion is coming out in probably less than a month. It’s *much* improved, although I can’t disclose how or why because of NDA. But you should definitely upgrade to Mountain Lion rather than Lion.

Charles

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

[Robert M. <mr...@gm...>]

Wow, Frank, this is cool! I love being wrong this way.

(I feel like if I keep saying things that I hate about Apple, you'll
keep telling me I'm wrong :-)

I found some examples of people booting Lion in 32-bit mode:

  https://discussions.apple.com/thread/3225388?start=0&tstart=0
  https://discussions.apple.com/thread/3943837?start=0&tstart=0

So does that mean we can boot Lion in 32-bit mode and run 32-bit
SheepShaver and get a working copy and paste?

I hope so... then maybe I'll actually try out that copy of Lion I
bought last winter for $30. PICT files and SheepShaver cut/paste were
holding me back. (Also the lack of Save and Revert commands in the
standard suite, what were they thinking? Oops, I'm complaining again.
Please tell me I'm wrong.)

On 6/18/12, Frank Trampe <fra...@gm...> wrote:
> Not exactly. Certain kernel-related things must run in 64-bit mode, but
> there is still i386 support.
>
> {
> cambridge:~ admin$ uname -v
> Darwin Kernel Version 11.4.0: Mon Apr  9 19:32:15 PDT 2012;
> root:xnu-1699.26.8~1/RELEASE_X86_64
> cambridge:~ admin$ file /mach_kernel
> /mach_kernel: Mach-O universal binary with 2 architectures
> /mach_kernel (for architecture x86_64): Mach-O 64-bit executable x86_64
> /mach_kernel (for architecture i386): Mach-O executable i386
> }

-- 
  Robert Munafo  --  mrob.com
  Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 -
mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com

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

[Jean-Pierre <cho...@fr...>]

Le 18 juin 2012 à 15:04, Ronald P. Regensburg a écrit :

> It would be nice to be able to copy and paste graphics between emulator and host, but I would rather see that efforts are directed first to clipboard integration for text. As it is now in SheepShaver on OSX, clipboard integration for text does not work at all in 64-bit mode and only works with severe limitations in 32-bit mode.

I wrote a small patch to exchange text clipboard for the Mac OS X 64bit version when I worked on the 64bit Mach-O support, but It was never merged.Not sure if I ever submitted it either...
If you want it let me know.

 -JP.

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

[Charles S. <bas...@ch...>]

On Jun 18, 2012, at 12:30 PM, Robert Munafo wrote:

> On 6/18/12, Alexei Svitkine <ale...@gm...> wrote:
>> We could always do our own decoding of PICT data and convert it to a
>> different format that is suitable to put on the host clipboard (in which
>> case, the host wouldn't even need to be a Mac!)
>> 
>> For example, this open source library is able to parse PICTs:
>> 
>> http://www.paintlib.de/paintlib/
> 
> That one appears to implement only bitmaps within PICT files, not the
> full QuickDraw opcode set needed for B2 and SS. I quote from
> http://paintlib.cvs.sourceforge.net/viewvc/paintlib/paintlib/common/plpictdec.cpp?view=markup
> 
> "This class decodes macintosh PICT files with 1,2,4,8,16 and 32 bits
> per pixel as well as PICT/JPEG. If an alpha channel is present in a
> 32-bit-PICT, it is decoded as well. The PICT format is a general
> picture file format and can contain a lot of other elements besides
> bitmaps. These elements are ignored."

But this is only for pasteboard support between the emulated and host systems, right? Do we really need 100% compatibility for that? As long as a PICT image on the emulated pasteboard gets translated to a TIFF or PNG or something on the host pasteboard and vice-versa 99% of the time, any rare corner cases should be only a minor inconvenience.

Charles

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

[Robert M. <mr...@gm...>]

On 6/18/12, Alexei Svitkine <ale...@gm...> wrote:
> We could always do our own decoding of PICT data and convert it to a
> different format that is suitable to put on the host clipboard (in which
> case, the host wouldn't even need to be a Mac!)
>
> For example, this open source library is able to parse PICTs:
>
> http://www.paintlib.de/paintlib/

That one appears to implement only bitmaps within PICT files, not the
full QuickDraw opcode set needed for B2 and SS. I quote from
http://paintlib.cvs.sourceforge.net/viewvc/paintlib/paintlib/common/plpictdec.cpp?view=markup

"This class decodes macintosh PICT files with 1,2,4,8,16 and 32 bits
per pixel as well as PICT/JPEG. If an alpha channel is present in a
32-bit-PICT, it is decoded as well. The PICT format is a general
picture file format and can contain a lot of other elements besides
bitmaps. These elements are ignored."

I once found a project trying to implement QuickDraw emulation for a
similar purpose, I don't remember how complete it was.

It's important that it be as small as possible (no external libraries
except what we can count on from Apple, no code for other formats like
GIF, BMP, DICOM, etc.) and of course all open source.

I do agree with the general idea, that adding QuickDraw emulation in
the host side would be a good idea to investigate.

-- 
  Robert Munafo  --  mrob.com
  Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 -
mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com