Groups | Search | Server Info | Login | Register

Groups > alt.os.linux > #80235

Re: Linux Program

Cross-posted to 2 groups.

Show all headers | View raw

On 7/30/2024 12:21 AM, Paul wrote:

> 
> #Hello Newsgroups!#The time now is: G#The numbers are: -The even Numbers are: +The Odd Numbers are: a** Hope you enjoyed this short exercise . . . **/##### Bye for now #####
> 

This is a shame. I could have used some extra numbers.

> Do you know whether WINE can run Metro.Apps ? Or Universal Windows Programs ?
> Even Windows can't always run the latter ones :-)
> 
    I worked with the WINE people very briefly, looking into adapting
Windows VB6 software to WINE. The redirect Windows calls (Shim?
  Some kind of shepherding? I don't understand that part.) Over the
years the WINOs have adapted specific Win32 API calls to coorelate
WINE libraries. Unfortunately, it's not a 1-to-1 correlation. One user32
function might be in one library while the next one is in another
library. And of course, no docs to speak of. Real coders don't speak
English.

   I didn't last long with the WINE people because they had no interest
in sharing information about how I could code to accommodate WINE.
They only wanted me to test my software and report bugs. Then I was
to be in charge of that bug until it was resolved by WINO lackeys --
temporary college student coders. (I had no idea that geeks were so
often paramilitary in their social structures.)

   An example: I had used a quick hack in the ChooseColor function.
I'd never had any use for the color pallette that could be saved at
the bottom left of the colorpicker window. The lpCustomColors member
of the CHOOSECOLOR structure is supposed to take an array of long
integers to represent 24-bit colors for the grid. For whatever reason,
VBers were using an array of string pointers, which worked fine on
Windows if the custom colors were never used. In WINE those
details got lost in translation and the string array cause a crash.
The WINOs were adamant that I shouldn't code such things better.
They didn't want me to strain my little brain. They actually didn't want
me to unsderstand.They just wanted me to keep track of bugs until
a coder fixed them on the Linux side.

   I don't claim to be able to program anywhetre near the level of
low-level detail that those people can, but they could have cooperated.

   WINE is mostly geared toward running Photoshop and video games.
The WINOs wanted Microsoft games. Which is an important point. It
was never about bringing Windows software to Linux. The primary
motivation was to bring video games and maybe MSOffice to Linux geeks.

    They'll take up the
challenge of whatever interests them. Then they have a chart showing
not how well the WinAPI is supported but rather the quality of support
for specific software. Put Cortana in a tight, transistor-festooned
bodysuit and hose her down, then put her in a Metro app,
and you can bet you'll get more WINE Metro support. Or at least
more WINE Cortana-all-wet-in-a-bodysuit support.

   When I tried WINE maybe 15 years ago it was very spotty. For
example, Irfan View worked OK but had gaps in the GUI. Just
missing window areas. Odd glitches. Years later it seemed more polished,
though I tried my own software and WINE couldn't see subclassed windows
at all. I have an editor with a system richedit window and the richedit
just doesn't show up. On Windows there's also notable difference
between versions of richedit, with various little things. So you can
imagine how WINE would do it. They'd give you a Linux equivalent
and map some or most of the richedit messages to the Linux window,
with a shoehorn if necessary.

   So the Windows version needs to be thoroughly orthodox, the
specific APIs used must be supported, and a Linux equivalent must
be adequate as a substitute for the Windows function. Thus, WINE might
support all sorts of things, such as .Net and Metro, but will likely
never support any of them fully.

   I imagine you probably know all this, but it's an interesting topic
and probably most people haven't looked into how WINE works.
I ended up deciding that any idea of moving to Linux without leaving
behind favorite software was not realistic and never would be realistic.
(Lately I've had enough trouble just adapting richedit50 to what I
expect from richedit20. So how could I expect WINE to match the
expected behavior in the Linux equivalent?)

Back to alt.os.linux | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Linux Program Murray <noreply@hhhhh.com> - 2024-07-28 05:45 +0000
  Re: Linux Program VanguardLH <V@nguard.LH> - 2024-07-28 02:35 -0500
  Re: Linux Program Richard Kettlewell <invalid@invalid.invalid> - 2024-07-28 10:59 +0100
  Re: Linux Program "Carlos E.R." <robin_listas@es.invalid> - 2024-07-28 14:07 +0200
    Re: Linux Program Newyana2 <newyana@invalid.nospam> - 2024-07-28 08:34 -0400
      Re: Linux Program Big Al <alan@invalid.com> - 2024-07-28 08:41 -0400
        Re: Linux Program Newyana2 <newyana@invalid.nospam> - 2024-07-28 12:42 -0400
          Re: Linux Program Jasen Betts <usenet@revmaps.no-ip.org> - 2024-08-03 13:39 +0000
          Re: Linux Program Paul <nospam@needed.invalid> - 2024-08-03 15:05 -0400
      Re: Linux Program Paul <nospam@needed.invalid> - 2024-07-28 13:20 -0400
        Re: Linux Program Newyana2 <newyana@invalid.nospam> - 2024-07-28 15:33 -0400
          Re: Linux Program Paul <nospam@needed.invalid> - 2024-07-28 17:18 -0400
  Re: Linux Program Paul <nospam@needed.invalid> - 2024-07-28 09:01 -0400
    Re: Linux Program Richard Kettlewell <invalid@invalid.invalid> - 2024-07-28 17:06 +0100
    Re: Linux Program "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2024-07-28 12:37 -0400
    Re: Linux Program "Carlos E.R." <robin_listas@es.invalid> - 2024-07-30 04:10 +0200
      Re: Linux Program Paul <nospam@needed.invalid> - 2024-07-30 00:21 -0400
        Re: Linux Program "Carlos E.R." <robin_listas@es.invalid> - 2024-07-30 13:51 +0200
        Re: Linux Program Newyana2 <newyana@invalid.nospam> - 2024-07-30 08:43 -0400
          Re: Linux Program "Jeff Gaines" <jgnewsid@outlook.com> - 2024-07-30 13:27 +0000
            Re: Linux Program Newyana2 <newyana@invalid.nospam> - 2024-07-30 12:40 -0400
              Re: Linux Program "Jeff Gaines" <jgnewsid@outlook.com> - 2024-07-30 18:41 +0000
                Re: Linux Program Newyana2 <newyana@invalid.nospam> - 2024-07-30 17:28 -0400
                Re: Linux Program "Jeff Gaines" <jgnewsid@outlook.com> - 2024-07-31 07:12 +0000
          Re: Linux Program "Carlos E.R." <robin_listas@es.invalid> - 2024-08-29 14:42 +0200
  Re: Linux Program MR <MR@invalid.invalid> - 2024-07-29 01:20 +0100
    Re: Linux Program vallor <vallor@cultnix.org> - 2024-08-03 18:24 +0000
      Re: Linux Program Paul <nospam@needed.invalid> - 2024-08-03 14:40 -0400
      Re: Linux Program John G <ghyhg@hyws.gfrd> - 2024-08-04 04:55 +0000
        Re: Linux Program danmin@danminart-dot-com.no-spam.invalid (Danart) - 2024-08-29 10:57 +0000

csiph-web