Category: ies4osx

Keep me going
give me coffee!

We Love Bitcoins

x

1PvaWQouvP64gvqyhiddDfGhxNVYGScyfi

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

If you want a stable release, please stay with 1.0.1//www.kronenberg.org/wine

For Intel Macs with Tiger, Leopard or Snow Leopard.
Comes with all needed libraries, bins and WineBottler.

This is a test for my new Wine building environment/setup.

• The package is called Wine now (instead of Darwine).
• All Wine licenses are changed to lgpl.
• No custom patches, except the 100% CPU bugfix.
• Loads of dependencies where updated.
• Added WineBottler as default alternative for WineHelper (WineHelper still ships with this version).

Small updates for WineBottler.

• WineBottleStarter now supports custom apps which contain a wine.bundle (for fully self-contained windows apps).
• updated ie7 template
• added ie8 template (not working yet)

/me waves big red ALPHA-flag, stay away, if You don't know what you're doing 😀

enjoy

As mentioned below, I'm not going to provide kind of two unstable binaries of wine :). For now, I'll push the WineBottler path... it includes the same Wine as Darwine did.

So whats new? (just the biggest)

• partial Tiger support (need feedback on this)
• drag'n'drop support to drop files onto bottles
• new controlcenter for prefixes, predefined, custom and preferences
• custom bottles can be built from templates (i.e. any other prefix)
• see all wine processes that are currently alive
• gorgeous icons from Andy, txs!

Still unstable, sharking and testing for leaks now.
WineBottler_1.1.22.zip

enjoy!
PS. SVN and TRAC are ready... sources and ticketing will follow soon.

PSS. Just forget one other major feature: a GUI for winetricks. It always works with the current winetricks and can be applied to any prefix. The option to create custom prefixes makes use of it, too.

As some might have read on Wine-Devel, Darwine is dead for good :). The OS X port of Wine formerly known as Darwine is now Wine.

What does this change? There will be no more "Darwine" packages from me.
It would be a simple thing to rename the package to "Wine". But there are more things to consider. Winehelper, the starter App from Darwine is really dead, this is why I'm developping a new one called WineBottler.

For simpleness sake, I'd love to call the new package Wine, but it does not give justice to the fact, that it's a none Wineproject wrapper around the Wine package. Nor gives it justice to the other wine derivates like crossover or bordeaux.

So the next "Wine" Release from me will be inside "WineBottler". Maybe if we can make WineBotter really good, it could be accepted as part of Wine like the old winehelper, which would do away with the troubles of having another name for the same ;).

Mainly because of Macish simplicity I'd love to only have one Package which can be autoupdated. Distributing the bottler alongside a wine bundle like now could be another solution.

Like to hear your thoughts about it. Going to consult the list, too.