11 replies to this topic

[PommeGolden]

Uploaded with ImageShack.us

instead of popping up a small separate wine window :)  :)  :)

[doh123]

That would be nice... but that is a Wine issue... its not really something a X11 program can do as far as I know, and its definitely not implemented in Wine.  It would be easy if Wine was using a Quartz driver and not X11, but this is not something I can implement in Wineskin without some major changes to Wine... unless someone else can think of a way.

[Tetsu]

As far as I know a quartz driver is something the main WINE team would have to implement first before it can be implemented in wineskin am I correct?

[doh123]

smoketetsu said:

As far as I know a quartz driver is something the main WINE team would have to implement first before it can be implemented in wineskin am I correct?

they could do it... or I could.. or anyone could implement a macquartz driver.  Doesn't matter who does it... but it'll have compatibility problems between it and X11... so it would still be best to have both options.

The problem here is that it is a very very hard job to do.  Even the preliminary stuff some people has worked on is a huge amount of very complicated code.  Its pretty much a more complex project than all of Wineskin is right now.

[Tetsu]

Sure due to the open source nature anyone could given the proper requisite knowledge on how to do it. I myself can't code my way out of a paper bag. I even have a hard time getting eduke32 to compile properly on the Mac as it needs more than minor edits to some make files and then compile it... It's because it seems to me the builds the main devs release always seem to turn out better than mine much less if I where to code up something as big as a quartz driver for WINE.

Not everyone has coding as their forte\aptitude nor even the prerequisites for it. It's a fallacy for open source devs to assume everyone can just do it themselves or that they should be required to.

Although what I meant more is "You are waiting for them to implement it before you put it into wineskin as you would rather not do it yourself, right?" From what you are saying on how much work it'd be you don't want to do it yourself.

Also it'd probably have compatibility problems at first but it'd probably improve after being revised for a while just like WINE itself.

[doh123]

smoketetsu said:

Although what I meant more is "You are waiting for them to implement it before you put it into wineskin as you would rather not do it yourself, right?" From what you are saying on how much work it'd be you don't want to do it yourself.

Also it'd probably have compatibility problems at first but it'd probably improve after being revised for a while just like WINE itself.

its not just about how difficult it may be.. its the fact that it is way beyond what I'd even have a clue how to start... if it was just difficult, I'd jump on it  :-)

[PommeGolden]

i can imagine integrating Windows' menu bar to OS X's menu bar would even be 100X times more difficult hehe :D  :D  :D

[Tetsu]

There's actually an application for windows that reads the menubar resources in many applications with standard menubars and displays it in a bar that you can configure to be anywhere on the screen you want such as the top to simulate a Mac desktop. The application is called objectbar.. I used to use it when I was a windows user. Unfortunately as with all things not all windows apps follow the same menubar standard so while on the one hand it's possible and it's even possible to intercept the window and hide the menubar while at the same time reading that menubar resource inside the app and display it elsewhere it wouldn't work with all apps that have menubars only some of them... mostly the older ones.

Here's an example screenshot of what I used to do in windows with objectbar: http://smoke999.devi...allery/#/d2y2v1

You might notice the ampersand underlines in the menubar though.. many menubars in windows have certain letters underlined using andpersands in the menubar resources and those would either need to be ignored when read by the function that would display them in the mac menubar or one would have to manually go into the .exe and edit the resource with a reshacker application to remove the & in front of the letters that are underlined.  

But then again WINE probably isn't getting that kind of function any time soon especially since the prerequisite would probably be the quartz driver which has yet to even come... and like I said.... it'd only work with some apps.

Most of the apps we use in WINE don't have menubars anyway though.

[UnconventionalT]

In theory it wouldn't be all that difficult. It would essentially come down to implementing menu-bar integration inside of X11/XQuartz. However, the issue is development isn't focused on the area of keeping the X11/XQuartz problem alive, they are more focused in bringing all of the tools to the Mac natively, meaning using native system calls (instead of X11/XQuartz which essentially emulates the X desktop).

For example, another Linux application known as pidgin can be run natively, without X11/XQuartz AND includes system bar integration. (See system bar icon that doesn't look native.) This is a gtk effort, and not a wine specific one.



This could also be supported by Wine on Mac with a Quartz backend, like the one being developed here. http://wiki.winehq.o...SX/QuartzDriver However, the last changes made to that version were 3 years ago.

Long story short, I don't see it happening unless someone over at XQuartz decides to implement it. Or maybe it's already implemented (although I've NEVER seen ANY x application take advantage of it). Then it would be up to the wine developers to add some code to access the system tray calls in X11/XQuartz when running on a Mac.

[Battlefiler]

it would be nice :) i dont like this window

[doh123]

Well a native quartz driver for Wine is actually a bigger project to implement than all of Wineskin currently is... its not even close to easy or Crossover would have had it long ago...  Even Crossover, with all the devs for it, still don't have anything like this.

If someone wants to write in a patch for xorg-server that includes something like this and show me how they did it, I'm sure I can get it integrated into WineskinX11.

[mknox]

i seem to remember i wrote a piece of objective-c code that did something similar to this a while ago...... (looks back at the GB's of code)