While some CMSs are great for putting up a dynamic website in a snap, others are too difficult to implement and use. While we all know about content management systems such as SageFrame, DNN, Joomla, wordpress and Drupal, you may be surprised to learn that there literally dozens and dozens of other content management systems out there, many of which do have their special niche. but I'm hoping that for an app with a simple UI like Free42, that would be manageable.At BLORGE we’re great fans of open source, and in particular, open source content management systems (CMS). Regarding the consistent user experience, I think all the Qt apps I've seen so far have been desktop apps, and they looked OK, but of course building desktop and mobile apps from the same codebase must be a challenge, since the small screen and the touch-based UI changes things a lot. I wouldn't count on having Qt available as shared libraries anywhere other than on Linux or other desktop Unixes.) How chunky are we talking here? (Actually, I guess that would affect the Windows and MacOS versions, too. Yes, I suppose that's hard to avoid on mobile, where the libraries would have to be statically linked. This guy makes decent tutorials, this one for Flutter: A drawback for you is probably that it uses a language called Dart, which is similar to javascript/like languages. Things may have changed, but today I would much rather write a new mobile app with the new hot Flutter framework from Google, which also creates speedy native executables. Yes, it creates native executables (no VM) and you can write in C++, but the QtCore, QtGui ++ libraries makes your app quite chunky, and I found it hard to create a nice consistent GUI experience. I did a Bluetooth mobile app project in Qt a few years ago, and must say it was a mixed experience. But the real benefit, if I do complete that port, is that Qt supports all five platforms that Free42 supports, so in theory I may be able to unify the code base to a large extent, and if that pans out, UI work in Free42 would become up to 80% less painful. This is mainly a learning exercise: I want to know more about Qt, and porting some real-world code to it is a great way to learn how to use it and what its strengths and weaknesses are. Having said that, I do intend to port Free42 to the Qt toolkit. I'm not looking forward to doing something like that again soon! (The "core" changes to support that feature are nothing to sneeze at, either, but for that I could at least take advantage of the work that has already been done by Byron Foster and by SwissMicros.) That factor of five can be pretty brutal, as I experienced when I implemented the state file manager in 2.5 it's not a particularly large bit of UI work, but not-particularly-large times five turned out to be stressful and exhausting. Apart from not finding the bigger display very interesting myself, one big problem is that because I maintain Free42 for five platforms, every change that isn't purely "core" has to be implemented five times, and the bigger display will require significant changes in the "shell" side of things. My impression after occasionally reading things Mr O writes, this won’t happen unless you jump into the code yourself. Next, hold the device horizontally and wait for it to rotate the UI accordingly then Main Menu -> Select Skin -> Landscape. Only the selection you make from that list is mode-dependent.įor example, to restore the skin selections to their defaults, perform these steps: hold the device vertically and wait for it to rotate the UI accordingly (make sure the orientation is not locked, neither in the OS settings nor in the Free42 preferences!) then Main Menu -> Select Skin -> Standard-4". Loading a skin, using the Load button in the Select Skin view, only adds it to the list of available skins, and that list is the same whether you're in portrait or landscape mode. Selecting a skin while in portrait mode sets it only for portrait mode, and selecting a skin while in landscape mode sets it only for landscape mode. Just be aware that the skin settings for portrait and landscape modes are separate and independent of each other. The problem is that the portrait skin got shown when my iPad was in landscape orientation - and when my iPad was in its portrait orientation, a different layout was shown.
0 Comments
Leave a Reply. |