#18 Integrate WineskinLauncher and WineskinX11

Engine
open
doh123
3
2012-02-14
2011-03-18
doh123
No

Wineskin, WineskinLauncher, and WineskinX11 all need to try to be bundled into a single app... everything in WineskinX11.

This will be very hard to do since WineskinX11 is built from xorg source with some patch files... but could lead to a better running wrapper.

Might need to take and make a full branch of WineskinX11 in the git, and not just use patch files anymore.

Discussion

1 2 > >> (Page 1 of 2)
  • doh123
    doh123
    2011-03-18

    • milestone: --> Engine
     
  • doh123
    doh123
    2011-03-29

    • priority: 1 --> 5
     
  • doh123
    doh123
    2011-03-29

    I've been thinking about this more.

    If its all in WineskinX11, that means its all part of the engine, making updates to the wrapper basically impossible without updating the whole engine base, which isn't a good idea.

    What might work better is just to integrate WineskinLauncher into WineskinX11, so that it will work as a single Application, unlike the 2 in one it does now.... but keep Wineskin.m a separate program that WineskinX11 launches, so it can be updated and changed separate of the engine. The Launcher and X11 are basically the 2 programs in one, and I think this would not only be much easier to do, but a much better overall plan for updates and bug fixes.

     
  • doh123
    doh123
    2011-03-29

    • summary: Integrate Wineskin, WineskinLauncher, WineskinX11 --> Integrate WineskinLauncher and WineskinX11
     
  • doh123
    doh123
    2011-03-29

    • priority: 5 --> 1
     
  • doh123
    doh123
    2011-03-29

    looking at X11 more... this is not going to be that easy... it'll take a lot of changes how WineskinX11 launches since another program will not be launching it... lowering priority down, as this won't be happening by me anytime soon.

     
  • andreaplanet
    andreaplanet
    2011-09-17

    Note: Actually when a wrapper is ready to use with a specific application then right now I (can) remove the WinSkin.app because it is no longer necessary to configure the application/wrapper. One application less for the delivery.

     
  • doh123
    doh123
    2012-01-06

    not sure mixing these would be great.

    I think the easiest solution is to try to make WineskinLauncher run correctly as is without needing a NIB file, then every problem with them being separate should be fixed.

    *note to andreaplanet, I was never referring to Wineskin.app. It is made to be removable.

     
  • doh123
    doh123
    2012-01-06

    • priority: 1 --> 5
     
  • doh123
    doh123
    2012-01-07

    ok.. I fought for hours and hours, but there is no way getting around the issues with using 2 apps in one... so WineskinLauncher just needs to go. i need to start troubleshooting the issues of getting WineskinX11 to start up properly by itself and not launched separately... so that the whole wrapper will basically be a self contained WineskinX11 app that auto starts the program in Wine correctly... and be a single app.

     
1 2 > >> (Page 1 of 2)