Comments on: Le roi est mort … http://mike.kronenberg.org/?p=190 Wed, 25 Aug 2010 18:50:23 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: BC Collins http://mike.kronenberg.org/?p=190&cpage=1#comment-1237 BC Collins Wed, 01 Jul 2009 15:23:13 +0000 http://mike.kronenberg.org/?p=190#comment-1237 You should call it Cork! :) You should call it Cork! :)

]]> By: mike http://mike.kronenberg.org/?p=190&cpage=1#comment-1111 mike Tue, 02 Jun 2009 10:41:46 +0000 http://mike.kronenberg.org/?p=190#comment-1111 Hi James, Yes I know. I had the same discussion on qemu and other OS projects I participated. Thing is, OS X is not c but obj-c. I might bow to implement the UI in obj-c instead in nib. But I don't see the sense in it at all. In other days, devs argued by saying nibs and other binary files are not suitable for cvs/snv/git. I, too, don't like binaries in my svn. But todays nibs are plain xml, so no trouble with that. But I know that I'd bite on solid rock with wine-dev. It's not written anywhere, but I get the impression that raw wine is just developed as a base (library so to speak) and all UI is implemented by other projects (like cross-over, ubuntu, bordeaux or winehelper on OS X). To keep it that way, all checkins are limited to pure c (which is great for library stuff and de facto a no-go for comprehensive UIs). I'm fine with that, as it really makes sense to leave UI stuff outside the lib, especially with so many platforms supported. I'll host "WineBottler " (still codename) sources separately as was it done with winehelper. I'll build wine and add WineBottler as a separate starter/controller app to the bundle like it is with winebottler. By accepted I just mean, being a "Friend of Wine", so to speak for wine-devel savvies ;) Mike Hi James,

Yes I know. I had the same discussion on qemu and other OS projects I participated. Thing is, OS X is not c but obj-c. I might bow to implement the UI in obj-c instead in nib. But I don’t see the sense in it at all.
In other days, devs argued by saying nibs and other binary files are not suitable for cvs/snv/git. I, too, don’t like binaries in my svn. But todays nibs are plain xml, so no trouble with that.
But I know that I’d bite on solid rock with wine-dev.
It’s not written anywhere, but I get the impression that raw wine is just developed as a base (library so to speak) and all UI is implemented by other projects (like cross-over, ubuntu, bordeaux or winehelper on OS X).

To keep it that way, all checkins are limited to pure c (which is great for library stuff and de facto a no-go for comprehensive UIs).

I’m fine with that, as it really makes sense to leave UI stuff outside the lib, especially with so many platforms supported.

I’ll host “WineBottler ” (still codename) sources separately as was it done with winehelper.

I’ll build wine and add WineBottler as a separate starter/controller app to the bundle like it is with winebottler.

By accepted I just mean, being a “Friend of Wine”, so to speak for wine-devel savvies ;)

Mike

]]> By: James M., Tuscon, Arizona http://mike.kronenberg.org/?p=190&cpage=1#comment-1108 James M., Tuscon, Arizona Tue, 02 Jun 2009 01:51:00 +0000 http://mike.kronenberg.org/?p=190#comment-1108 Mike: Word of warning. If you want your project accepted by AJ, you have to use 'just plain c' Luckily, there is a 'c' version of the Cocoa interface. I don't know where its at, but if you search wine-devel, it's there. James Mike:
Word of warning. If you want your project accepted by AJ, you have to use ‘just plain c’ Luckily, there is a ‘c’ version of the Cocoa interface. I don’t know where its at, but if you search wine-devel, it’s there.
James

]]> By: mike http://mike.kronenberg.org/?p=190&cpage=1#comment-1088 mike Fri, 29 May 2009 15:02:53 +0000 http://mike.kronenberg.org/?p=190#comment-1088 Me too, but it's a nogo if I want any support from wine-devel. And with the winehelper replacement, it's of no use to change paths from Darwine to Wine, just to change it again in some weeks time. Maybe it's going to be a Wine folder that consists of the wine.bundle and the replacement. But "Darwine" is gone . Whatever we do, it's got to be well thought thru. Me too, but it’s a nogo if I want any support from wine-devel.
And with the winehelper replacement, it’s of no use to change paths from Darwine to Wine, just to change it again in some weeks time. Maybe it’s going to be a Wine folder that consists of the wine.bundle and the replacement. But “Darwine” is gone . Whatever we do, it’s got to be well thought thru.

]]> By: pinchies http://mike.kronenberg.org/?p=190&cpage=1#comment-1087 pinchies Fri, 29 May 2009 14:56:34 +0000 http://mike.kronenberg.org/?p=190#comment-1087 It sounds good, but I can see that some people will prefer the older method of builds to continue, at least until this is rock solid. I'm thinking of posting some builds myself, but I need a bit more time, as I am packed with upcoming exams... It sounds good, but I can see that some people will prefer the older method of builds to continue, at least until this is rock solid.
I’m thinking of posting some builds myself, but I need a bit more time, as I am packed with upcoming exams…

]]>