So basically I was thinking that all that would need to be done (by someone who can actually program and is familiar with Mac OS X *.app files) is to take the *.app files for the Mac OS X version of these apps (if a version is available for MacOS) and modify the *.app packages so that they can be run from anywhere and create whatever they need to create relative to where the *.app is being run from (a lot of *.app files operate this way already but there are a rare few that are required to be placed into the Applications folder). Most Mac OS X *.app files work the same way, only they extract all the files and do whatever else right when you double click them with none of the wizards present in Windows installers. installers make very few, if any, changes to the registry. Installers for non-portable apps might do things like register DLL files and make changes to the registry and stuff like that. installers do this (extracts binaries and all related dependencies to a location of our choosing). Windows installers basically run scripts that extract the files from the installer and put them in their appropriate places on the Windows system. I was thinking that Mac OS X *.app files operate on similar principles to Windows app installers. That's all I have right now hope someone else is interested in this. I can say that 2 beta 4 has been working flawlessly for me I am currently testing out all the portableApps I have on my drive. Ok so first off I'm running Snow Leopard 10.6.3 and I use WineBottler 1.1.35 (intel only) ( This is the first time I've ever used Wine so I like it to be easy) this may not be the best way to run Wine on OS X and there are other ways just try google or Winehq for more info. So I thought I'd start a thread incase anybody else was interested and also so any Q & A or info could be easily found and shared in one place. Hi all I did a search and although I found lots of topics to do with Wine and a few sporadic posts about using Platform/Apps with Mac OS X.

Notepad++ mac wine