Why winetools is utterly useless, once and for all.

[Segin]

Tom Williams wrote:

>Tom Spear wrote:
>  
>
>>Java, anyone? lol oh wait wait I got one better.. Fortran... or no,
>>how about................... COBOL!!  LMFAO  gimme a break..
>>
>>Seriously though, why not break winedoors up into different
>>components, and then have different submaintainers, and each component
>>can be written in the language that that submaintainer is most
>>comfortable with?  Obviously each piece of code would go thru the
>>project maintainer, and so if someone started writing another "door"
>>in bash, then that door could quickly be closed (pun intended).
>>
>>
>>As for the GUI, make it C or C++, only because that is the most widely
>>used language in linux..
>>    
>>
>What about perl?  I'm not a perl programmer or anything but wouldn't
>that be as prevalent in a Linux environment as C or C++?  I believe GTK+
>could be used for the UI and I don't know if QT could also be used or not.
>
>  
>
It is possible to link to GTK+ and QT with the same binary, but it's 
best to use a system of modules and common calls/elements to do the GUI 
stuff in seperate dlopen()ed modules so that anyone that has a taste for 
a odd, weird, or obsolete toolkit could also make a UI plugin for such, 
while not modifying the core at all (Motif plugin, anyone?)

>I'm sitting back and watching this discussion and I just wanted to
>mention perl for you guys to consider.   :)
>
>I'll shut up now.  :)
>
>Peace...
>
>Tom
>
>
>
>  
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winehq.org/pipermail/wine-devel/attachments/20060329/20ba15e8/attachment-0001.htm