4 ms·
Looking at BeOS screenshots make me relive the disappointment I felt as a Mac owner in the 90s when Apple decided not to use BeOS as its next generation OS. It
by pcurve 13y ago
Looking at BeOS screenshots make me relive the disappointment I felt as a Mac owner in the 90s when Apple decided not to use BeOS as its next generation OS. It was quite a bit ahead of its time.
- __float 13y agoNeXTSTEP was way ahead of its time too.
- scoot 13y agoAs was AmigaOS in its own way. Is it really accurate to call all these ahead of their time, or rather that what was in common use at the time was behind the times?
- malkia 13y agostraight C++ is just too hard to use for GUI. Trolltech at least bite the bullet, and decided that you need some kind of preprocessor (moc) to get around dynamic objects and exposing their properties, signals/events/connections/etc.
- __float 13y agoWhat do you think of the "modern" Windows API?
- malkia 13y agoI'm now on the Qt wave, but had to use wxWidgets, .NET Windows Forms, MFC and few others. Never been too proficient in them, just enough to support and add features. So far having the best experience with Qt - things like styleSheets and the data models (table, tree, etc.) are th best things I've seen. (I'm not much familiar with CSS, but somehow I'm getting exposed to the concept through qt-ones). With .NET Forms it always seemed like I hack to go low-level and do some Win32 GUI stuff (which for some strange reason i love - since I do love "C" at heart). I've also seen WPF, Reactor, etc. - and I simply could not understand them - either they look too foreign for me, or I don't know. As for non-C/C++ ones - I loved LispWorks CAPI - it mimicks wxWidgets that it wraps native controls, but it's so easy to write bulk UI stuff in it (for me) - for example this unfinished p4win replacement (hahaha) - https://github.com/malkia/p4bee https://github.com/malkia/p4bee
- agumonkey 13y agoIf you're strong enough you can watch some demos on youtube.com.