1. •Change Wineskin Structure... focus more on the wrapper.
   

2. •There are too many tools in Wineskin.app that should be part of a wrapper.
   

3. •get rid of normal and SC wrappers, normal is useless, Wineskin is a tool about making a finished Mac port, all wrappers should be self contained
   

4. •make new engine types install to a local apple approved area in compressed form, when a wrapper changes engine, this can be handled fine
   

5. •change WineskinSettings.app to Wineskin.app and make it contain ALL tools needed for wrapper management.  Make it more logically set up and user friendly as well
   

6. •change old Wineskin.app to something else... (Wineskin Management.app ??) and make it only take care of limited things.  Download and manage engines, build custom engines, create empty wrappers, check for updates and update to get newer version empty wrapper templates.  This app should do NOTHING else.  Everything else is taken care of from the wrapper and Finder.
   

7. •Re-code all the GUI tool parts from scratch...
   

8. •All of the GUI tool parts are written in Applescript Studio.  This was end of life’d with Mac OS X 10.5 and may or may not even run on 10.7.  DOing major redesign for Wineskin 2.0 anyways... going to recode everything into Java.  The main wrapper running for running Xquartz and Wine to run the Windows program will still be a bash process for speed and efficiency, only the GUI tools will be in Java.
   

9. •Get a build of Xquartz working right with RandR for a new WS5 engine base.
   

10. •RANDR will allow proper fullscreen and windowing switches as well as resolution changes, much like Crossover’s X11 server does.  I plan on making it an option to disable, so the “old” current way can still be used for games that have issues with it, like ones that don’t work right with Crossover’s implementation either..  This will be available around Oct. or Nov.... the same time as Wineskin 2.0.  Wineskin 2.0 will only work with WS5+ based engines at this point.  Engine updates after that *should* be just for newer Wine versions that need them, instead of replacing old engines.
    

11. •fullscreen needs stretched mode option (make sure its working right with WS5 and RANDR)
    

12. •add option to do video mirroring on fullscreen launch, quick fix to Xquartz multi-monitor issues. May not need with RANDR, make sure its working ok with RANDR and multi-monitors.  Look into a way to disable second monitor automatically for fullscreen using ‘old’ way.  RANDR doesn’t like multi-monitors much currently, might still need a way to do this.
    

13. •get the automatic downloads of engines hosted and enabled better...
    

14. •Wineskin Engines are already being hosted on this website.  Only the newest versions will be kept here, everything available will still be on the Mediafire site.  Going to make the latest version of the engines available as a download and managed from inside new Wineskin Management app ... older engines will still need to be manually downloaded.
    

15. •Add a refresh wineprefix button in WineskinSettings (old name), instead of just a rebuild which actually deletes stuff... useful when using WineskinSC and dragging and dropping a new WineskinEngine.bundle inside.
    

16. •Rename wineprefix buttons to wrapper instead of wineprefix... rebuild wrapper and refresh wrapper.
    

17. •try to make new GUI app usable during runs... only gray out buttons that can mess up an App if used while its running... whole menus don’t need to be blocked off from when 1 thing is running.
    

18. •Make a new WineskinLauncher program instead of the little place holder bash script it uses now.
    

19. •Need a launcher that handles getting paths to open file events, for open file associations in OSX, and also one that lets you hold down a modifier key (like Alt) when running the wrapper to launch wrapper tools instead of the wrapper itself.
    

20. •Fix Flags entry not working right... the whole line is being treated as a single flag in Wineskin 1.2.
    

Other stuff to do...

1. •Try to redesign some things to meet Apples guidelines better for apps... I’ll never be able to meet all their guidelines though just because of the whole design philosophy of Wineskin, and that some of Apple’s Guidelines are stupid.  A lot of this will be part of Wineskin 2.0... hopefully everything will be within guideline.
   

2. •figure out a way to get copy/paste on CMD instead of Ctrl.
   

3. •add some logic to paths Wine can use to launch, so it can handle ‘&’ and other symbols right.  Just needs to detect and add escapes in front I think... have to test. Testing looks like it can throw off the whole Info.plist format.... might only be able to do this if I move all the Wineskin config options in Info.plist out to their own config file.
   

4. •Get Icons to update right without the caching problem and having to reboot or copy the wrapper for the new one to show up
   

5. •make an uninstaller for Wineskin (why...?)
   

6. •add an option for a launch menu instead of only run the 1 exe instead.  Launch menu can show options, and all set EXEs.
   

7. •make applescript/java/whatever launcher instead of bash that handles file types for file associations.
   

8. •possibly keep a database of “approved” or certified wrappers that can be downloaded and managed through the new Wineskin management app in Wineskin 2.0