Mac Emulator for Windows XP Professional Edition !!

[codeexploiter]

Hi all,

I am using a Windows XP Pro but i want to test my web pages in Safari (default browser of Mac OS).

I am looking for a Mac Emulator which will give me a Mac kind of environment to carry out my tests.

Please share your suggestions/comments if you are using one such emulator.


Regards

code exploiter

[DimX]

I don't know if it's a good idea but, here's the first google result on "mac emulator": http://www.emulators.com/softmac.htm

[Twey]

PearPC (http://pearpc.sourceforge.net/) is said to be very good.

[codeexploiter]

Thanks Twey for your answer it really helped me to get a direction.

regards

Code Exploiter

[blm126]

Have you tried Swift (http://www.getswift.org/) yet?

[didiman]

If you need help confiuring pearpc. There is a tutorial here

http://www.reabo.co.uk/_tutorials/running-mac-os-x-in-windows.aspx


Hi all,

I am using a Windows XP Pro but i want to test my web pages in Safari (default browser of Mac OS).

I am looking for a Mac Emulator which will give me a Mac kind of environment to carry out my tests.

Please share your suggestions/comments if you are using one such emulator.


Regards

code exploiter

[jr_yeo]

Have you tried Swift (http://www.getswift.org/) yet?

Swift link supplied is a dead link. it just have a "it works" message

[jscheuer1]

As I'm pretty sure you know, Safari runs on Windows now. It will not help you a lot for folks using older Safari versions, though some of the rendering and script quirks are preserved. However, I've heard some strange things about even FF on a Mac, so I'm not confident that running an emulator would give you all that much more than Safari 3 Win, as subtle quirks would almost invariably be different on the Mac vs. Emulation vs. a port of the browser(s) run under Windows.

Safari 3 Win has helped me tremendously though in at least getting the broad strokes of my code into line with what Safari can handle and to see how it will (generally) look.

If you write valid code, keep things as simple as possible, use object rather than browser testing in scripts, a port of the browsers you are targeting should be all that is required for testing. If you require more than that, you should acquire a Mac, preferably one that typifies the Mac environment you want to write for. The thing is, code will react differently from Mac to Mac as well, so just having an emulator or a single Mac may not be all that much more useful than a port anyway.

[magicyte]

Remember: the time this guy wrote the thread wrote it in 2006. I don't know for sure, but Safari might not have worked back then.

-magicyte

[Medyman]

Remember: the time this guy wrote the thread wrote it in 2006. I don't know for sure, but Safari might not have worked back then.

Lol, nice catch. I was thinking the same thing as John posted. But, in the light of the original date this was posted, it makes a bit more sense.

[jscheuer1]

Remember: the time this guy wrote the thread wrote it in 2006. I don't know for sure, but Safari might not have worked back then.

-magicyte

Notice too that other recent replies were still going the emulator route, and that I prefaced my response with, "As I'm pretty sure you know, Safari runs on Windows now."

In any case, regardless of when the original question was posted, people reading this today should know (if they don't already) Safari runs on windows, making a Mac emulation undertaken solely for that purpose a waste of resources.

[magicyte]

Agreed!

-magicyte