Frank Richter wrote:
>On 10.04.2008 09:47, pure_evil at mail.bg wrote:
>
>
>>However, since control panel does not utilize Unicode yet, the additionalb
>>Bulgarian translation matches the English one.
>>
>>
> Even for non-Unicode apps you should have no
> However, since control panel does not utilize Unicode yet, the additionalb
> Bulgarian translation matches the English one.
> So what's the point of that "translation" then? Right now it doesn't add
> anything worthwhile but increases the patch size - not good.
Well, it was intended as a templ
> You patch is wrapped. Also please for new files follow standard Wine codding
> style - 4 spaces indentation, no tabs.
Sorry about that, I'll fix it in the morning. (I should've attached it as a
text file :( )
> This is ugly and redundant.
yes, but at least it's easily readable - same local var
> I would like to have the applets should be part of wine's control program.
Hmmm, I followed usual windows proceedings, e.g. the applet is not actually a
part of the control panel program itself, it's a .CPL.
> They would be better be as files in the /programs/control/
Well, cpls are basically D
Well, this is my first patch. Here goes.
It *enhances* winecfg's source and creates a winecfgcpl.cpl, which, when
placed into ~/.wine/drive_c/windows/system32 shows the different "tabs" as
different applets (six of them), visible via "wine control".
1.) Enhancements to winecfg - now the winecfg
Woah, that's ubercool.
The presentation is excellent! However, you could add five collosal IMHO
advantages of wine:
1. NO 1000 DISCONTINUED WIN VERSIONS
That's what largely made me dump 'doze and go for Linux - got 6 W98 licenses,
and at some point, upgraded the hardware to discover that 98 doe
> Worked first try. (Good thing, too, since I was just copying what wine
> already does to build its dlls, and I wouldn't have known what to do if it
> failed.)
>
> Does that work for you?
> - Dan
Steven Edwards beat you to it, he sent me a patch ;)
It works! It's alive!
@all sorry folks 'bout
Okay, this is as far as apparently I can make it on my own.
This is the *basic* control panel applet. I used Dev-c++ (it's C though).
It compiles with mingw and works flawlessly - you know, exports what it should
export etc. etc. etc. The result, copied onto c:\windows\system32 shows up in
the
Sorry bout that, went a lil' /too/ paranoid. Thing is, I've spent
so many days obsessing with the cpls, trying to get anything resembling a
somewhat stable dev environment to produce anything resembling a *compilable*
code, reverse-engineering Makefiles, and Makefile.ins, and defs and specs and
> __declspec(dllexport) is a MSVC-only feature. Hence, when compiling with
> gcc (even using winegcc) it won't actually export the function. As has
> been stated before, you need to use a .spec or .def file to export it.
Yes.
> A DLL compiled as a winelib DLL won't be parsed by a tool that reads
No dice.
CPls are DLLs that export a function - CPlApplet().
winegcc coughs on dllexport. - not implemented.
I've been hacking at it for days on end now.
Result: CPl can be compiled under windows and run under wine. CPls compiled
with winegcc don't export that function => not treated as control
On Wednesday 26 March 2008 12:39:39 pm you wrote:
> If you build a wine dll inside the wine source tree we use gcc in
> combination with some wine magic for compilation. Exporting of functions in
> that case happens through a '.spec' file.
>
> When you want to work outside the wine tree (as it can
Folks, I've been trying to make a bunch of control panel applets
for wine for some time now.
a CPL is basically a DLL which (the most importnat part) exports a
function called "CPlApplet"; Without it, the cpl isn't worth a thing.
It is the presence of that export which basically iden
Folks, I'm working with Dan Kegel on the idea of a winecfg/control panel
merger; I did a .cpl or two a few days ago, but it seems I didn't quite
understand the rules of the dev on wine/ or on linux for that matter :(
I need someone to show me the ropes...
Basically, The Toolbox.
Question 1: I ne
I made the first cpl (intl.cpl), and, the actual executable that goes with it.
http://www.keepandshare.com/doc/view.php?id=460541&da=y
that should link to a file called intl_wine.zip.
It contains 2 things: intl.cpl which goes into c:\windows\system32
and a folder - winecontrolapplets containing the
On Monday 17 March 2008 09:30:33 am you wrote:
> <[EMAIL PROTECTED]> wrote:
> > I'm not sure how changing the decimal (in the example case) on linux
> > would affect the linux apps themselves - will I have to switch it back
> > and forth if another, linux app demands it to be ',' whilst the windows
On Sunday 16 March 2008 11:35:39 pm you wrote:
> Hi,
>
> While I think writing control panel applets for Wine may be a good
> idea in general, I wonder whether the specific example you propose--a
> locale setting control panel--might be better served by trying to
> infer the correct settings from t
Hey folks
I was thinking of writing some substitutes/stubs for the windows .CPL files.
I migrated to using linux as a desktop fairly recently /used it for servers
for a while, though/. Adapting to the linux equivalents of the programs I
use, using wine for the rest etc.
Whilst "reinventing" the
18 matches
Mail list logo
