1> I agree with such OSD optimizations. Maybe i'll execute some of them from time to time.
First i would love to see the (i suppose) core bug fixed, that only the VideoOSD shows the "already recording - you can stop the recording by pressing this button" button. In all other OSD and also on home screen this functionality doesn't work, even when you fix the code according to the VideoOSD (where it works).
6> I looked at the player controls within the sidebar and although i almost never use them, i think the KODI guys still left them in there by purpose. I also don't think they are really needed for remote-control using ppl... Will see.
8> I took a look at the script and seems nice and all, keeping in mind staying close to Confluence, i don't want to use added external features like that because i think there are enough basic things that should be reworked before adding new "external" stuff. For example, the movie/episode information dialog could be further optimized in it's basic existence before extending it with online or other features.
9> "It's bad UX-design;" Yeah. Somehow i agree. Still TBH, i don't think a serious media player should not be operated by mouse, so i don't indend to invest that much of a time fixing mouse UX design bugs which are basically a part of KODI i consider "legacy support" (no offense towards mouse guys)
10> I understand what you getting at. I tried some variations some time ago and ended up keeping things as is conceptionally, which is okay for non-mouse for now i think.
11> I agree. If i was in charge of original Confluence i would think about fine-tuning/adding such small things, but for my fork i won't add such descriptions, since there are more important things to invest the time on.
12> I agree. I'll look at cutting the RSS feed before hitting the buttons.
12.1> I'll try and check.
13> Already changed in reworked widgets section
14> Visually i like it the way it is (sub menu base is also a bit longer than the actual items) and consider the global search script "legacy support" for now. Maybe i'll recheck at a later time.
14.1>
15> reworked widgets section
16> I know this bug but had no time to take a look since (you already know now) i consider mouse legacy support.
Still, i could'nt believe this bug is in stock Confluence - if it's not that hard to fix, i'll check.
And does it really pays off to start working from jarvis Confluence? Or adapt
those changes to your Isengard Zeitgeist?
> I good some good compare tools for files, but i think i'll have to use the Jarvis base and re-integrate my changes. Both ways are nasty work sometimes, but well. I can't go back to stock Confluence now.
Rapier like shutdown menu texts
> Looks like the strings Confluence uses are from KODI core and besides my few new Skin Settings which are just plain english for now, i intend not to make and add new language strings which replace original KODI/Confluence strings. If they should change, the should in KODI itself, so Confluence also uses them.
(2015-11-13, 18:38)Robotica Wrote: [ -> ]All icons in home.xml have that square look once selected. Same is for the submenu's. Inverting all icons (so all outlining is highlighted instead the complete container) would make things look a lot cleaner once a icon is active. So when "Favorites" is active the star becomes blue instead of the square around it. Similar, when navigating to pictures the camera would become blue instead of the square around it.
Thinking further, same concept would also look great on text (like the library views, context menu, OSD, slide-in screens)
Navigating would be so much more tranquil.
This is somehow how the main menu items were when i started working on the Skin. I did not like it. I wanted the main menu items to have a large filled area like it is now and still like it. Maybe i'll recheck at a later time.
Greets to the (good) feeback guy.
btw: new version online.