Hi! On Di, 7.07.2015, 13:37, Fabien Chéreau wrote: > Hi Alex, > > On Wed, Jul 1, 2015 at 8:33 PM, Alexander Wolf <alex.v.w...@gmail.com> > wrote: > >> Howdy all! >> >> Qt 5.5 has been released yesterday (for my local time zone) and this >> release has good and bad news. >> >> Good news: >> Qt3D in the official Qt now. >> > > Yes, although I don't see a need for this for the moment. We should avoid > this dependency unless we really need to (maybe it could be useful for the > 3D landscape plugin)
I have not looked into it, but as long as it is experimental I would not change the currently running scenery3d, I think that implementation is quite OK. >> Bad news: >> Few modules is deprecated now. >> >> Quote (http://blog.qt.io/blog/2015/07/01/qt-5-5-released/): >> With all these new features coming, some older ones are being >> deprecated, >> namely Qt WebKit, Qt Quick 1 and Qt Script. All of these modules are >> still >> available with Qt 5.5, but we strongly recommend using their >> replacements >> for any new functionality: Qt WebEngine, Qt Quick, and Qt QML, which >> also >> provides a fully compliant JavaScript engine. For most uses cases, the >> new >> replacement modules should be more suitable and provide better >> functionality than the replaced ones. >> >> We use QtDeclarative (QtQuick1) and QtScript in the Stellarium now and >> apparently we'll be have troubles in Stellarium in next year (maybe in >> 2017 >> year). >> > > I agree, we now really need to re-code the whole GUI in QML, and replace > the script engine (I didn't check but I don't think this will be a big > trouble). It will be a good opportunity to fix several design flaws: > - cleanly separate the GUI from the C++ code: > - ideally the GUI should only use the script API instead of doing > direct C++ calls > - could allow to completely control stellarium with the GUI running on > a remote computer (a much requested feature for planetarium people) Florian is doing this in his SoCiS project! (Some permanent configuration is not planned to be available remotely, though.) This should allow building touch kiosks or tablet control for guides, etc., or scripts launched via wget cronjobs or such... And some sophisticated time control or non-western calendar display/control could be even implemented only in JS? (Not planned to be done by us in this task for now.) I think he also improved something about the actions, but have not looked into it in the last weeks. > - move the movement/click logic in the GUI code as much as possible > - allow plugins to inject their own GUI in the program in a clean way > - allow for 100% QML plugins > - in term of look and feel: > - improve objects search > - display nicer information about selected objects > - improve time navigation > >> Plus our Scripting Engine has serious bug - >> https://bugs.launchpad.net/stellarium/+bug/1468986 Florian has fixed this already! :-) However, is our script engine depending on the Qt Script module and in danger of becoming obsolete as well? Maybe going for QtQuick2 also enables support for RaspberryPi2? (Currently eglfs causes problems, but I don't know how to solve.) Based on ~10fps on my Odroid C1 (1.6GHz/Mali400) I expect about 5-9 fps, maybe just enough. Kind regards, Georg ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ Stellarium-pubdevel mailing list Stellarium-pubdevel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel
