wine-devel March 2005

wine-devel@winehq.org

178 participants
443 discussions

Re: winetest, winrash and new volunteers
by Steven Edwards 13 Mar '05

13 Mar '05

Hi, --- Chris Morgan <cmorgan(a)alum.wpi.edu> wrote: > I can give devel access to winrash cvs to anyone that wants it. I'm too busy > to work on this stuff myself these days. Is there some good documentation on how winrash and winetest work and communicate with the server? I am interested it in using it as part of the ReactOS build system. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

2 1

Wine Start Menu in the Desktop Applications Menu
by Scott Ritchie 13 Mar '05

13 Mar '05

One of the most commonly requested features for Wine is for Wine to be aware of applications that put themselves into the Windows Start menu. We've talked about it on the Wine lists before, but there have been some difficulties. The first is that we don't yet understand how to read Windows shortcut files and interpret them: this can probably be overcome with some work. However, there are some other barriers to entry that are now turning around thanks to the Freedesktop.org specs. Here, I propose a short plan of action for getting Wine applications into the Applications menu. Some of these need to be done at the distribution level and some need to be done within Wine. When we have it working nice and smoothly we can submit whatever changes we made to freedesktop.org as well if they need to become a cross-distribution standard. Here's how I see we can do this in Ubuntu: 1) Create a new Menu entry in the .menu file at /usr/share/gnome-app-install/applications.menu This one will be named "Windows Applications" and will need to point to two locations for .desktop files: system-wide ones, and user-specific ones. Instructions for how to do this are here: http://standards.freedesktop.org/menu-spec/latest/index.html 2) Create some Wine .desktop files that can go in /usr/share/applications that will be readable by this menu entry. These will be for system-wide Wine apps that are common to all users. This will include Wine's own apps (like the configuration tool and the uninstaller) as well as packages which depend on Wine (such as Winetools). 1 and 2 will get us some nice launch icons for the important pieces of Wine that most users aren't yet aware of (such as the new uninstaller and winecfg tools). Combined with Wine's ability to make desktop launcher icons when a program says to install an icon on the desktop, this should be a fairly good start at making Wine console-free. 3.) The menu specification can also point to a new location in the local user's .wine directory, probably something like ~/.wine/menu. Here we'll have the user-specific .desktop files that link to the Windows applications that user has installed. Once we figure out how to make Wine build a start menu and translate the shortcuts into .desktop files, they can be created there. These files can be kept up to date (such as when a user installs a new windows application) by the wineserver program. What will then tell Gnome to update the applications menu (since new .desktop files will have been created) I'm not sure yet. 4.) Once we get all that working, then we can start playing around with icons. This should be fairly easy to translate across platforms. It would be nice to have icons that Windows apps install available centrally - this could perhaps be another dekstop integration task on the Wine todo list. 5.) Different architecture issues. One of these days a working amd64 version of the Wine packages will be available (perhaps whenever I manage to afford a new amd64 computer). It's entirely doable to make it work transparently, once the upstream quirks in compiling Wine on 64 bit get worked out. We can also install 32 bit libraries (so we can run 32 bit windows programs) in a way similar to what we do with Open Office. The PowerPC version of the packages, however, is another issue. Obviously, we can't make Wine work with i386-compiled apps on PPC, however we can make it work with Winelib ones. If I ever finish packaging up eMule after getting it to compile in Winelib, a PPC Wine package version could put the .desktop files into the same place as Winetools goes, and then put eMule right there alongside it on PPC. Alternatively, on PPC we could just not use the new Windows Applications submenu altogether, and instead put Winelib apps like eMule in a normal place like Applications->Internet. I still have no idea exactly who is going to do which part of this work, or when, but it all seems like the right way forward to me. Comment is very appreciated. Thanks, Scott Ritchie

2 1

Re: Warcraft 3 - "no program start menu found"
by Juan Lang 13 Mar '05

13 Mar '05

> I am beginning to I suspect it should really go in > dlls/shell32/shellpath.c It is. I think I see where the bug is, and I'm working on it. I should have a patch sometime this weekend, maybe later tonight. --Juan __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

2 1

winetest, winrash and new volunteers
by Paul Vriens 13 Mar '05

13 Mar '05

Hi, as can be seen from the test.winehq.org site the number of test-runs dramatically dropped. Apart from the fact that there were problems with the automated download of new tests by winrash: http://www.winehq.org/hypermail/wine-devel/2005/03/0373.html winetest will not run but bail out because there is no visible desktop. 3 of the 5 (!) tests that are now there, where done by me. Where in a 'normal' case we should already have dozens. I don't want to go into a discussion about the fact that 'running as a service' and 'on a visible desktop' can/cannot live together properly. Or why we should have 'visible' tests or not. I just want to have as much tests run as possible. I mean that was the whole idea behind it right? An approach should be decided upon: - Have (again) volunteers who run the winetest manually/interactively - Use winrash and have every test decide whether it needs interactivity - 'Fix' winrash so tests run, maybe semi-automated, on a visible desktop - .... An approach for the last is to have winrash fill in one of the 'run' keys (as it does on win98 already during install). I will be/stay a volunteer for the first approach until we decide what to do. Cheers, Paul.

3 2

Re: [ARTWORK] icon: "My Computer"
by egore 13 Mar '05

13 Mar '05

Am Samstag, den 12.03.2005, 16:34 -0700 schrieb Brian Vincent: > On Sun, 13 Mar 2005 00:08:04 +0100, egore <egore(a)gmx.de> wrote: > > Am Samstag, den 12.03.2005, 23:02 +0100 schrieb egore: > > > Hi list, > > > > > > I drew a simple icon that COULD be used as a replacement for the current > > > one. I don't know if anyone of you likes it, so please tell me what you > > > think. Tell me if you like it, if you hate if, what could be done > > > better, etc. > > > > > > The icon can be found in different sizes (and in a scalable format) at > > > http://www.egore911.de/vype/wine/ > > I really like the 128x128 and 64x64. I think they're great. The > 32x32 version is hard to distinguish. I think the only reason is > because the outline of the computer needs to be in black and maybe the > monitor a little smaller. Also, I think we need a 16x16 version more > than a 128x128, so it needs to scale small. You're right. I added it in 16x16 to the website. The problem is that the icon is not recognizable at that size. I will check how to tweak them to scale them down (and both ideas you pointed out sound good to me). > > Ultimately what needs to happen to use them is to insert them as a > resource and use the Wine Resource Compiler on them. I think we have > a bunch of tools that do this, but I'm not sure. If you read the > Developers Guide it will explain this process. However - don't feel > like you need to go that far if you're not comfortable with it. I think integration of the icons is a bit early. I think some more wine-devel readers (Alexandre for example) should say if they like them or not and what can be done better. As soon as we can agree on an icon, I will look at the guide and try to use the "bunch of tools". > At > this point we really need some good artists to clean some of our ugly > crud up. I will see what I can do :D > For instance, the new winecfg tool has a decent logo on the > "About" tab. However it could be a lot nicer - drop shadow inserted > or something. I think the logo is much better than the icons from the picker. But I will look at it later. > > Good work! Thanks :D Chris

2 1

Re: Theming for Wine via the registry
by Oliver Stieber 12 Mar '05

12 Mar '05

> > Ah, that's different. That'd actually require using > Gtk/Qt which we cannot > do, the best we can get is to look like them. > What's the problem, licensing, integration or thread-safety (I know QT isn't thread safe) > To be fully accessible we'd need to implement the > OLE Accessibility > framework and bridge it to AT-SPI or something > similar. > I may have a look at that too, it would be useful if QT/GTK could use some of the existing Windows accessibility software. I was thinking about going on a fund finding mission, or at least trying to find someone who wants to pay for an initial integration, it shouldn't be too hard as most companies are no where near their requirements. Send instant messages to your online friends http://uk.messenger.yahoo.com

2 1

Re: [OLE #82] Implement VT_BYREF | VT_BSTR marshalling
by Rob Shearman 12 Mar '05

12 Mar '05

Mike Hearn wrote: >Implement VT_BYREF | VT_BSTR marshalling > > Hi Mike, I've got a bigger patch in my tree at the moment that has your patch plus VT_BYREF|VT_BSTR unmarshaling, plus some other types. The thing now blocking InstallShield seems to be a nasty deadlock in the COM code that I haven't figured out yet. Rob

2 1

Re: wine/ misc/registry.c documentation/samples/config
by Mike Hearn 12 Mar '05

12 Mar '05

Hi Alexandre, What is the thinking behind this patch? If we don't load the Windows registry on startup where should it be loaded? Will this code re-appear at any point in the future? A significant number of users still expect to be able to point Wine at an actual Windows install despite what we recommend. thanks -mike On Fri, 11 Mar 2005 07:10:25 -0600, Alexandre Julliard wrote: > ChangeSet ID: 16565 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 2005/03/11 07:10:25 > > Modified files: > misc : registry.c > documentation/samples: config > > Log message: > Get rid of the Windows registry loading on startup, this needs to be > done differently. > > Patch: http://cvs.winehq.org/patch.py?id=16565 > > Old revision New revision Changes Path > 1.149 1.150 +6 -1498 wine/misc/registry.c > 1.73 1.74 +0 -2 wine/documentation/samples/config

4 5

Re: Discussion on Bug tracking database
by Tony Lambregts 12 Mar '05

12 Mar '05

tony_lambregts(a)telusplanet.net wrote: > Ann and Jason Edmeades wrote: >> I'd like to completely clarify that : >> - If _easily_ recreatable then a comment can be put in to keep it >> active by >> the person looking at it, but otherwise anything which is inactive for 2 >> months when the action was with the raiser can be closed. >> >> If so, which closing code (does it matter?!)? With no changes to >> bugzilla I >> would suggest an INVALID closing code with appropriate words added. >> >> Once agreed, we can have some fun clearing out some old rubbish. Looking >> through the old bugs and trying to reproduce a few, there are some easily >> recreatable basic bugs but those where there is nothing to go on >> really cant >> be progressed! > > > Well if the attached patch is OK for Jeremy then you will not need to > use "INVALID" and you use "ABANDONED" instead. ;^) > Jeremy committed the patch... You can now resolve a bug as "ABANDONED" :^) -- Tony Lambregts

4 5

Theming for Wine via the registry
by Scott Ritchie 12 Mar '05

12 Mar '05

This thread on the forums caught my attention: http://www.ubuntuforums.org/showthread.php?p=86939&highlight=wine#post86939 1) Is there a way we can make Wine respect the current GTK themes? Wasn't someone working on this a while ago? What's the status? 2) If I want to hack around this by changing the default registry for the Ubuntu packages, what's the best way to do that? Thanks, Scott Ritchie

3 3

← Newer
1
...
24
25
26
27
28
29
30
...
45
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel March 2005