PUAE 2.2.1 beta series

[GnoStiC]

http://github.com/GnoStiC/PUAE

while trying to sync with winuae 2.2.1 (almost there), i'm also trying to improve the gtk-gui. we have new features but gui does not support them yet.

i even have a beta winuae gui clone glade gui but then i thought would a sdl gui better?
________
Suzuki GSX-R1100

[chiark]

Excellent! This is brilliant news! Thanks!!!

I guess xaind is doing the Mac specific stuff here, and again I guess that GTK can be used on the mac for the UI?

Building a UI in glade for GTK sounds like a good idea to me: it take a load of hassle out of the interface design. Now, if you could get TOni to consider using glade for the Win32 stuff then that would be nirvana, but I seriously doubt it will ever happen

[Pyromania]

Thanx for all your hard work GnoStiC.

[gilgamesh]

That's good news. The old gtk-gui was so unreliable that I preferred to do without it. I'd definitely vote for SDL or wxWidget though, because they are easier to build under Suse (which has problems with 32bit gtk) and look better in Windows.

[xaind]

New Mac OS X build up in the zone. It's built from GnoStiC's July 7, 2010 commit 716e8cf.

[xaind]

I'm still seeing problems with "filesystem" hard-drive mounts.

My uaerc is attached. I am mounting a ClassicWB HDF as the system drive, and a folder as a second drive named Stuff:

If I start the shell and type the following commands:

Stuff:
cd UnixCmds
dir
cd /
dir

I get what you see in the attached screenshot.

[GnoStiC]

@xaind:
i'll look into it.

btw, ppc (and aos4) fixes are on the way.
________
GT550

[GnoStiC]

@xaind: i can't reproduce the error. i guess it's wchar (is macosx utf8?) related.
________
Yamaha XT250

[Toni Wilen]

I wouldn't attempt to merge 2.2.1 changes just yet, lots of stuff broken here and there

GUI, I have already said my portable GUI requirements, here they are again:

- it must use native GUI elements
- it must come with OS or must be possible to link statically (asking users to download extra files is not really expected in Windows world)
- it must not have lowest common denominator feature set (SDL..)

so far wxwidgets is the only acceptable library (but it also lacks some nice Vista/7 features, probably will be added sooner or later, I hope)

[chiark]

Good point Toni, it seems wise to get 2.2.0 completely finalised and use that as the basis...

[Jimbo]

Does this allow for adding real Amiga HD's? If so is it in the GUI or does a line need to be added to the config.

Cheers

[GnoStiC]

http://eab.abime.net/showthread.php?t=46283

Originally Posted by Jimbo

Does this allow for adding real Amiga HD's? If so is it in the GUI or does a line need to be added to the config.

Cheers

________
CT110

[slaapliedje]

Originally Posted by Toni Wilen

I wouldn't attempt to merge 2.2.1 changes just yet, lots of stuff broken here and there

GUI, I have already said my portable GUI requirements, here they are again:

- it must use native GUI elements
- it must come with OS or must be possible to link statically (asking users to download extra files is not really expected in Windows world)
- it must not have lowest common denominator feature set (SDL..)

so far wxwidgets is the only acceptable library (but it also lacks some nice Vista/7 features, probably will be added sooner or later, I hope)

Have you looked into Qt? Gtk+ can also just be included. I know Pidgin does this, and it can be set to use the 'native' look. The Nokia Qt SDK has the added bonus that when you compile, you can choose to compile for Windows, Mac, Linux, Symbian, and Maemo. So instant Mobile UAE.

Kontact for Windows is a good example of the install process of a Qt based program under Windows.

It would be awesome if we could get a universal UAE, instead of having different branches of the same code.

http://qt.nokia.com/downloads

[Toni Wilen]

Originally Posted by slaapliedje

Have you looked into Qt? Gtk+ can also just be included. I know Pidgin does this, and it can be set to use the 'native' look. The Nokia Qt SDK has the added bonus that when you compile, you can choose to compile for Windows, Mac, Linux, Symbian, and Maemo. So instant Mobile UAE.

Native look != native GUI elements. Also I thought I said no lowest common denominator builds. (only way to make easy builds in all platforms you listed..)

[gilgamesh]

Originally Posted by Toni Wilen

Native look != native GUI elements. Also I thought I said no lowest common denominator builds. (only way to make easy builds in all platforms you listed..)

Afaik that has been changed by now:

Qt uses the native graphics APIs of each platform it supports, taking full advantage of system resources and ensuring that applications have native look and feel.

(http://qt.nokia.com/products/)
And Qt is not a lowest common denominator, is it? Then again it is probably a fairly large library.

[Toni Wilen]

Originally Posted by gilgamesh

Afaik that has been changed by now:
(http://qt.nokia.com/products/)

Ah, OS X and Windows versions use native GUI elements. Interesting...

And Qt is not a lowest common denominator, is it? Then again it is probably a fairly large library.

I meant WinUAE won't become portable just by switching to portable UI.. Sockets, CDROM, harddrives, serial ports, display, sound etc.. still needs to have port-specific code. (or lowest common solution..)

[Leffmann]

TCP/IP, sound, graphics acceleration etc. is also supported. Qt has evolved far beyond just GUI and is pretty much a complete platform today and could support the major part of WinUAE, but of course things like low level device access is not something that belongs in Qt and has to remain platform specific.

[Toni Wilen]

Originally Posted by Leffmann

TCP/IP, sound, graphics acceleration etc. is also supported. Qt has evolved far beyond just GUI and is pretty much a complete platform today and could support the major part of WinUAE, but of course things like low level device access is not something that belongs in Qt and has to remain platform specific.

Yeah but input, display and sound abstractions (especially on Windows) are always more or less "lowest common denominator"/directx wrapper-like stuff (see SDL) and only add latency or extra buffering.

vsync, fullscreen+refresh rate selection, very low latency sound, ability to read "special" keys, multiple mice etc usually require native APIs.

OS specific sound and input has always been modularized in UAE and is very small part (single source file), display not so much but can be done easily.

[gilgamesh]

Doesn't WinUAE already use the (portable) OpenAL framework? I am confused by
ahidsound_new.cpp and ahidsound_new2.cpp, etc.

[Toni Wilen]

Originally Posted by gilgamesh

Doesn't WinUAE already use the (portable) OpenAL framework? I am confused by
ahidsound_new.cpp and ahidsound_new2.cpp, etc.

It does, it is optional, but OpenAL is not very good for low latency dynamic samples on most sound cards that don't have native ("hardware") Windows OpenAL support where it is (again) only a directsound wrapper.. (that works worse than "native" directsound)

(There is huge difference between playing preloaded static samples that games use and real-time dynamically generated samples)

and you forgot rule number 2: no extra non-OS libraries must be required.

ahidsound stuff is something that was never finished.. openal is in sound.c