KdeGuidanceWineProgress
Differences between revisions 3 and 4
|
Size: 2262
Comment:
|
Size: 2288
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
| * Continued working on the module. The widgets on the Desktop Integration tab are done: ["people.brandeis.edu/~ykozlov/soc06/screenshot2.png"]. I can do the rest of the tabs like this just by hacking up the displayconfig code, but I need to start actually learning python/QT to get this stuff to do something. | * Continued working on the module. The widgets on the Desktop Integration tab are done: http://people.brandeis.edu/~ykozlov/soc06/screenshot2a.png I can do the rest of the tabs like this just by hacking up the displayconfig code, but I need to start actually learning python/QT to get this stuff to do something. |
| Line 21: | Line 24: |
| * My proposal: ["people.brandeis.edu/~ykozlov/soc06/proposal.html"] * A mockup: ["people.brandeis.edu/~ykozlov/kcontrolmockup.png"] |
* My proposal: http://people.brandeis.edu/~ykozlov/soc06/proposal.html * A mockup: http://people.brandeis.edu/~ykozlov/soc06/kcontrolmockup.png |
KDE-Guidance module for wine progress
Here I, YuriyKozlov, will keep track of my progress on my project for Summer of Code 2006. ["KDEGuidanceWineSpec"]
5-27-2006
- Tried to compile kwine. Not working yet...
5-26-2006
- Continued working on the module. The widgets on the Desktop Integration tab are done:
http://people.brandeis.edu/~ykozlov/soc06/screenshot2a.png I can do the rest of the tabs like this just by hacking up the displayconfig code, but I need to start actually learning python/QT to get this stuff to do something.
- Got in contact with kwine developer [kwine.sourceforge.net]. He's done a lot more work beyond what he posted on sourceforge that (it seems) he's mainly been using just on his own computer, and I think some of it could be very helpful to my project. He's already created a wine KIO slave and is working on "dcop/wine gateway to access wine registers".
5-25-2006
- Started creating a wine module by hacking on the display module's code
- Discussed possibilities of how to change wine settings with mike_m and vitamin on irc. The changing of the settings is going to be more difficult than I thought. There is no simple way to link to wine and access its functions, it has to be done with a winelib program such as winecfg or regedit. The best solution is indeed some "code glue" but this (at least as wine devs would like it) would have to be a proxy feature in winecfg so that it can accept commands to change settings. This isn't yet implemented and it is a pretty major project I'm told. Another possible solution they gave is to use regedit commands to change the settings. This isn't preferable because the registry keys/options to edit would quickly be obsolete, among other reasons. I will start out by building at least part of the python GUI, then implement it with regedit commands to get something working. Then I'll see if I can do it the proper way.
5-24-2006
- Project was accepted.
- Started dissecting guidance. Figured out how to create a new module by duplicating the display module.
Pre-acceptance
KDEGuidanceWineSpec/KdeGuidanceWineProgress (last edited 2008-08-06 16:31:32 by localhost)