We’re moving along constantly. I consider this new build beta grade, i.e. feature complete but still some bugs.

Main changes

• all apps compiled for 32bit… this should help with 2006 Intel machines
• developed on paths with spaces… this should help with user-accounts that have spaces in it
• bottled apps have a toolbar now… sort of, with the most important tools like filemanager

for full changelog.

What’s down the pipeline?

• bugfixing
• proper versioning of wrapped apps
• howtos & wiki
• new predefined apps… suggestions are welcome

So?
Head down to WineBottler’s new page at http://winebottler.kronenberg.org
grab a build and happy testing
Mike

Things are moving and they’re looking more stable now. I’m still not entirely happy with the Wine.app building process, but things should run. It’s a vanilla build from the sources from winehq.org with no patches.
WineBottler has received some updates, too. Thank You very much for all the constructive feedback. More is in the Pipepline.
www.kronenberg.org/wine

I’ve set up svn and trac for WineButtler now. This is only for WineBottler and the launching program (WineStatus) used in the Wine.app package. For everything related to Wine itself, please refer to the winehq. So if you find bugs or have proposals for enhancements, just register and submit a ticket.
winebottler.kronenberg.org/trac

We’re coming along, but again I hiss the red alpha flag.
Enjoy & keep the feedback flowing
Mike

[update]
Changed faulty bottler.sh script from wine.app
Ahhh, yes…. if you install ie7… DON’T install the update, when asked.

So,
here we go with the results of the (slightly prolonged) weekend of coding . But because of the split of Wine and WineBottler I had to generate some more code. I hope by creating a clean lean Wine bundle, people that use that bundle will get support from winehq.org again (for the records: this is a vanilla build of wine, just a separate starter app, to handle OS X stuff and updates).
I have to apologize, the new tutorial did not make it yet. Glen, you are most welcome to help with the documentation or help files

Get your copy at www.kronenberg.org/wine.

What is new in Wine?

• Sparkle update (Wine.app will update itself for future releases)

What is fixed in Wine

• loads of library links
• “Taskmanager”

What is new in WineBottler

• new looks
• you can create selfcontained apps (apps that have Wine directly integrated, for distribution)
• custom prefixes do support localized “Program Files”
• automatically convert the windows icon for your app
• statusmessage after creating a prefix (good, aborted, error)
• search for prefix, predefined and winetricks

What is fixed in WineBottler

• Sparkle Signature
• Show Wine Log
• better working exit codes
• normal window level
• ie6 template updated to include flash
• ie7 template updated to include flash

Again – this is alpha
Enjoy!
Mike

BTW.
No update to Wine 1.1.30 as it was not working properly for me.

There are some questions that bother me right now.
Mainly – should I separate the statusbar item from WineBottler and put it into a separate app (maybe include it in the wine binary)?

This way, the WineBottler would act as a normal app, that you specifically call to create/configure wineprefixes. Predefined apps and custom-app-creation would be found here. You can alt-tab to it, windows are at expected level (not floating, like now), etc….

While the WineStatus app would help with tasks closer related to the currently running wine instance(s), like start cfg/filemgr/winetricks or force-quit a task. I think the current prefix manager would be situated in this one, as it mainly helps to choose, in which prefix the tool should be executed.

Other things to consider:

I want a clean Wine.bundle (maybe Wine.app).
Now I have a startup-script that replaces the wine executable to handle with OS X custom behavior. Instead I’d like to have a cocoawine binary alongside the genuine wine binary that handles OS X bundle/Statusbar related things, like auto-starting with exes, bats, lnks and msis. The clean and separate Wine.bundle is important to get help from the mother-project, as altered binaries may introduce inconsistent behavior, that will render proper bug-hunting impossible, i.e. no-go.

2 separate bundles, 2 separate downloads, 2 separate updates?
I might offer a separate Wine.bundle/app download and a WineBottler.app download. This way, I can update the two independently. But what about the initial install? I think users can handle to install two apps separately, as it was with the ies4osx/darwine combo.

Any thoughts?
Mike