> I guess I can now continue this when we have been properly introduced > again or something :D Hi Toni, glad to hear from you. I just realized that you were also the author of filemaster which I used a lot. > You wouldn't never accept anything anyway except if it has been double > and triple checked and 100% guaranteed to be perfect. No wonder UAE > development got too slow. I guess all filters and autoscale and stuff > that users WANT is your so called crap because it technically is not > needed and can be considered bloat. > > YOUR CRAP IS NOT MY CRAP. > > We ("we" what?) are not developing something like Linux Kernel that > needs high coding standards, especially if there is only something like > max 3 people in the whole world that really knows UAE and Amiga hardware > inside out.. Yeps ! You're probably right when saying that we could count on one hand's fingers the number of people that really knows UAE and Amiga hardware inside out. This is why joint efforts would be better if possible. Being rude won't help for sure ! I don't know if you had bad words with Bernd in the past but I don't even want to know. That said, it seems to me that it would be hard to make the two uae's fathers working together again. > -> I decided to do everything in my own which clearly has been > successful method for me. I can do whatever I want, when I want and I > can only blame myself if and when I do stupid things. Of course I don't > want to do everything alone but nobody else knows about Amiga (both > hardware and software) enough to be able to help me (I have tried, I > always get totally bogus answers or no answer at all) Much easier to > just research it myself. I understand that. And I think that adding modularity through plugins for video/audio, etc ... would allow real amiga hackers to delegate stuff and concentrate on the amiga emulation stuff only. > Seriously, we can start from clean table but old way won't work for me. > Not enough freedom. Your crap-answer shows exactly the problem. The > exact same problem from years ago. I found simple "fix". Fix is still > working fine. Well I guess that a bit of clarification should be done. I don't know your story (you & Bernd) but it seems you often disagree both of you. Too bad you don't live in the same country so you could just go & drink some beer ;-) But of course, if *uae evolve to something modular, it means more people working on it and therefore it imply to use both the same versioning system. I see you use CVS ? right ? Bernd doesn't seems to use a versioning system. ( not sure about this ) > btw, there are 2 things I am never going to accept: > > 1) Other GUI toolkit because 1) they look alien compared to other > Windows programs (see Java Windows GUIs..) 2) need huge libraries that > nobody has installed by default. I guess that macosx users could say the same. I don't think the GUI would be the same on *nix and windows. But if the GUI is seperated as branch/plugin/whatever then it should not be a problem for anyone. Each platform could have it's own gui in it's platform branch. Someone in this list proposed an in-screen GUI (like dosbox, mame, zsnes, ...) I think the *uae GUI as needed might be too complex for an in screen menu, but the idea is not to be rejected because there could be a minimal cross platform gui using in-screen mode and a more complex gui for each os branch. The advantage is that it's easier for some ports on phones, handset, game consoles, or whatever. (Don't know if uae has been ported in the phone land tough) > 2) any portable toolkit like SDL that has less and worse features than > native APIs. Again, if video is abstracted, I guess there could be seperate branches for win32 and other. I guess that for other platforms, sdl would be kept. But I agree it's nonsense to use SDL on windows when we see the work you did for directx integration. The only question I have for you is : "Would you accept to work on a tree that would include branches for other OS / ports than Windows ?" Regards. -- Fabien Meghazi Website: http://www.amigrave.com Email: agr@xxxxxxxxxxxx IM: amigrave@xxxxxxxxx