Magic Sam said:
Hi,
@ B-ZaR and dflemstr: do you think panorama could "officially" make it to HF6 ?
Bye and thanks for your amazing work
Magic Sam
No, since Panorama requires Qt 4.7 and Zaxxon only has 4.6. When Yars hits it's a matter of maturity. What would you want it to do at the point it's included? Also thanks
Esn said:
It does look really nice, and it has some of the features I've suggested for PNDstore, such as being able to read the description, being able to view just "installed" PNDs, and being able to view them by category.
Like PNDstore, it would greatly benefit from being able to check off a number of PNDs, then install or uninstall them all at once while you go and do something else in the meanwhile (browse the internet, for example).
I also suggested a single "install/uninstall" button for PNDstore because often, you see updates of programs with the same name that have been given a different package ID by the developer. So it would be very convenient to check off both the new update and your old version of it, click "install/uninstall", and wait while it does the equivalent of an update. In any case, any particular app can either be installed or uninstalled, not both, so a single button makes sense. (Tempel objected because PNDstore currently also uses the "Install" button to upgrade a package, but I think the need I mentioned is a greater one. Besides, I doubt anyone would use the "Install" button for a single upgrade when the much better "upgrade packages" button is nearby)
Basically these are up to the UI. The plugin that gives Panorama UIs the ability to do package management (milky-plugin, a wrapper around Cloudef's libmilky package management backend) doesn't limit these things. You can queue operations all you want, mark packages for install/uninstall/update and apply the changes while still being able to use the UI and queue more operations. The MilkyTest UI you see above is my test UI for the plugin, and focuses on simplicity.
I do UIs mostly to test panorama and the plugins at this point. They of course reflect some idea I have of a UI and I tend to add a little extra animation here and there just to show off, but they are primarily ways for me to test panorama and its plugins. If/when I'm ever satisfied with the state of the engine I'll probably spend a little more time on making a polished UI or two, but currently I think my time is better spent on working out the bugs, optimizing stuff, and adding useful features like package management or a system configuration frontend.
We are finite resources, but anyone willing to do UIs is welcome to do so
. QML isn't really hard to understand once you get the basic idea, and any programming required is javascript, though usually the (traditional ["imperative" for you CS people]) code part is either really simple (think a couple of ifs or a single statement), or practically non-existent. The rest is just defining what's in the UI and how they work (declarative). The best way to start is to get QMLViewer from Qt downloads and try out the various QML tutorials offered in Qt documentation. Get to know the basic components, layout stuff and handling input. Then look at how some simpler Panorama UIs are made, like simplicity and go on from there. If specific examples are needed, I think I can squeeze out some time to do some, if I'm told what is wanted
A status update: Currently I'm solving a nest of bugs I uncovered while working on milky-plugin (a couple of the ones I've mentioned in previous posts are a part of this). The problem is not in any specific part, but in the way they work together and how they are built. Funny fact: the problems only come out on the pandora build
. I'll let you know when I'm back to adding features
