Category: wine

Keep me going
give me coffee!

We Love Bitcoins

x

1PvaWQouvP64gvqyhiddDfGhxNVYGScyfi

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.

I've replaced the startup script of the Bottler with a cocoa app. This way I have more control over the wrapped app. Right now it supports the following things:

• Drag'n'Drop of file(s) on the Bottle
• the prefix of the bottle is copied to "~/Application Support/wine/prefixes" the first time it is run. This way we don't get into troubles with writing privileges in "/Applications". The prefixes can easily deleted from the prefix manager.
• the Bottle stays in the Dock once launched (allows selecting of the app)
• fast App switching to the Bottle (cmd-tab)
• fast App switching & termination of the Bottle (cmd-tab, cmd-q)

Lots of small improvements to the app like

• predefined apps sit in a .plist now, that could be maintained and hosted on the internet for rapid updates (again a shout for the appdb to offer an interface for wine front-ends)
• new Bottler window (we're still not there, but better 🙂 )
• Sparkle works from this version on (i.e. autoupdate of wine) you can manually see the rss entries of the sparkle appcast here: //www.kronenberg.org/wine/appcast.php

My mind is on:

• Status menu: Better support to display and terminate all exe's running (ps aux | grep .exe)
• replace the overlay displayed while prefix creation with the "action window" from the bottler
• finer grained feedback in the "action window"
• visual feedback when bottles are started to assure people that something is happening
• is there .otf font support in wine?

Long talk, here is the file: WineBottler_1.1.21.zip, and again, this is deepest dev work:

• it has loads of errors
• hide all previous Winehelper.app, Wine.app and WineBottler.app.
• bottles created with earyer versions are probably not going to work with this.

enjoy.
Mike

PS.
If You really need "Internet Explorer 7.0" You could give this build a try. "Internet Explorer 6.0" is not working atm.