Guest - Testers are needed for the reworked CDateTime core component. See... https://forum.kodi.tv/showthread.php?tid=378981 (September 29) x
  • 1
  • 18
  • 19
  • 20(current)
  • 21
  • 22
  • 77
Mod Arctic Zephyr: Generations (Jarvis / Leia) [3.4.70 / Coming Soon]
(2016-06-26, 02:26)mdh99 Wrote:
(2016-06-25, 05:51)Guardian Hope Wrote: Q: Slideshow?
A: A lot of the fan art is pretty good depending on where you are scraping it from and what your settings are (I've only ever used MediaBrowser/Emby- I don't know what type of quality generic Kodi has) but I believe the setting is in there somewhere.

It's not just poor quality and inappropriate (I have kids and fan art from a horror or violate movie isn't something they need to see) fan art, it's also the delay in displaying. When I open SPMC the background is black for up to 10 seconds and often when I return to the home screen. I thought Kodi stored/cached art in the local database, but maybe I'm wrong.

The ability to set my own local/smb folder with pictures is a feature I really miss.

Another issue, I had to dig way to too deep into add-ons to disable "up next", can a toggle be added to the skin settings?

Apart from missing the personal slideshow feature of the original skin, this is by far the best skin and many thanks for bringing it back to life!!

When I was writing that it didn't even occur to me about the horror genre (I think all horrors are predictably boring) nor have I thought about the more violent movies because most I've come across keep their art PG-13 but again, that's because of finer controls on the art and really a personal choice for each parent to make because when I see parents arguing about the content of a show like "Girl Meets World" (the successor to the 90's "Boy Meets World") I just give up on them because every time I have been invited to see the show in person (during filming) it's just really everyday things. However, your point is very valid and a very good reason to bring back a feature.

New features won't be added to the Jarvis version after the Summer 2016 Update (meaning the Autumn 2016 Update is Krypton only) will feature a redesigned settings (courtesy of a very great contributor @minus0 who has made mock ups that look really nice) that should be much easier to navigate.

We can patch in the slideshow which I thought was already there into the Autumn 2016 Update and by that release an official site will help you get to know and better use features that maybe you didn't even know were there (getting the rights to use promotional images from shows and movies is not difficult since this is free).

Finally, as to SPMC performance, From Ashes is a resource intensive skin. It runs on a Raspberry Pi 3 just fine which is ARM architecture as well as the nVidia Shield which uses Android but naturally, we cannot guarantee the same performance for every device. If you are using something low powered than yes, it might take some time for the skin to load.
Arctic Zephyr: From Ashes
The New Arctic Zephyr: Exploded Experience for Kodi Jarvis
Arctic Zephyr: Generations - Coming Soon
Reply
For those brave few... the wastelands await. It may not be pretty and I haven't even tested it yet (the VM I have running Krypton is updating) but I did push the change for DialogConfirm.xml. Just be aware that there are many changes still to be made for the Danvers version for the Summer 2016 Update and only a few left for Jarvis.

Please Provide Debug Logs and Images Your Encounter with Krypton if You Pull it From GitHub

Do Note: AZ:FA Anniversary Edition (Codenamed "Danvers") does not use "skin.arctic.zephyr.fromashes" as its namespace. The internal folder from the zip you download from GitHub needs to be named "skin.arctic.zephyr.fromashes.danvers" for it to work.

Image

Update

Well, at least it starts but it's not anywhere near pretty yet. Nothing's loading or aligning correctly yet and some settings become inaccessible. Hopefully all will be fixed by 6/31. But it at least it can be installed now:

Image
Arctic Zephyr: From Ashes
The New Arctic Zephyr: Exploded Experience for Kodi Jarvis
Arctic Zephyr: Generations - Coming Soon
Reply
Update for Users Regarding OSMC, OpenELEC, and LibreELEC

As of the current and any future release, LibreELEC will not be supported in any single way. This includes bugs or enhancements in regards to the user experience on LibreELEC. Anyone using LibreELEC should migrate to OSMC or OpenELEC. Please note that we prefer users on ARM platforms like the Raspberry Pi to use OSMC but the choice between OSMC and OpenELEC is yours to make.Usage of this skin on the LibreELEC device makes up under 3,000 users. We recommend OSMC for better support from both them regarding their platform and from us regarding the skin. We will also append this notice into the next version of Arctic Zephyr: From Ashes as a temporary popup with a disable button within the skin's settings.

Essentially what you are being told is: use LibreELEC and you're on your own.

This decision was made after interacting with their fairly unprofessional staff and will continue to stand permanently. See the attached image:

"Exhibit A: Report a Bug on LibreELEC and You Get 'Forum Troll' Status"
Image

If you have any concerns or questions about transitioning to OSMC or OpenELEC, you are welcomed to post them here.

Arctic Zephyr: From Ashes "Summer 2016 Update" will be available on or shortly after 6/30/2016 if everything continues as planned.
Arctic Zephyr: From Ashes
The New Arctic Zephyr: Exploded Experience for Kodi Jarvis
Arctic Zephyr: Generations - Coming Soon
Reply
Wow. What a disgraceful way to treat developers. I was really pleased with OSMCs response.
Reply
@Guardian Hope: After your increasingly patronising and condescending posts on the LibreELEC forum, your forum status was changed to reflect your behaviour as it was perceived by other users of the LibreELEC forum.

How you decide to support the users of your skin is of course entirely up to you. LibreELEC users (and users of other distributions) can decide for themselves if they want to use a skin from someone who denies support due to personal animosity outside of their control. My advice would be to choose another skin.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
(2016-06-27, 20:25)Milhouse Wrote: @Guardian Hope: After your increasingly patronising and condescending posts on the LibreELEC forum, your forum status was changed to reflect your behaviour as it was perceived by other users of the LibreELEC forum.

How you decide to support the users of your skin is of course entirely up to you. LibreELEC users (and users of other distributions) can decide for themselves if they want to use a skin from someone who denies support due to personal animosity outside of their control. My advice would be to choose another skin.

@Milhouse: Ironic that the one thing missing from that thread is that my last post on the LibreELEC forums which literally dictated how the events should have played out as they did on OSMC: Report a Bug, Acknowledge a Bug, Ask for it to be Reproduced (if need be), Fix the Bug seems to be missing.

Please do not muddy up this thread in regards to LibreELEC's problem. If the LibreELEC staff cannot help but feel offended by being called a "small distribution [yet successful]" that is there own accord and not something I would support.

My reasons to deny LibreELEC any further support is pretty simple when you compare how the interactions went between OSMC versus LibreELEC.

With that said, I will step out of the respectful boundary for a moment to say "do not comment on matters unless you provide the entire picture. Dealing with LibreELEC is like running your nails across a chalkboard - not worth the headache or effort for something that is free. My advice would be to not comment again unless you understand and can acknowledge everything."
Arctic Zephyr: From Ashes
The New Arctic Zephyr: Exploded Experience for Kodi Jarvis
Arctic Zephyr: Generations - Coming Soon
Reply
a reply from yourself

"And so that there is no misunderstanding: don't be crass and try to throw around numbers as it's very unprofessional."


yet your first post contains

"We have received reports from users of the Kodi Skin Arctic Zephyr: From Ashes which is currently installed on hundreds of thousands of devices "

^^^ also crass and unprofessional ?
Reply
(2016-06-27, 20:45)sparklyballs Wrote: a reply from yourself

"And so that there is no misunderstanding: don't be crass and try to throw around numbers as it's very unprofessional."


yet your first post contains

"We have received reports from users of the Kodi Skin Arctic Zephyr: From Ashes which is currently installed on hundreds of thousands of devices "

^^^ also crass and unprofessional ?

I can't believe I am about to teach English on an internet forum but I will and this will be the one and only other time I will dignify a response regarding LibreELEC.

When dictating a small subset of users (Raspberry Pi running LibreELEC) are experiencing a very specific issue compared to the greater usage than it is appropriate to use numbers.

For example, if the following statement was made (this is an example):

Quote:Of the 50,000 downloads of LibreELEC, about 2,500 people are experiencing issue X, Y, and Z in comparison to all other devices (...)

Is a proper use of number indication.

An improper and rather crass way to use numbers is to try and turn a compliment of success (a relatively small distribution justifying its numbers which turned into the only focus rather than the bug report) to try and essentially say "hey, [we're] not a small distribution."

Just accept the compliment of success and move forward to the bug report. It is all in the way it's written as text does not translate well sometimes.

Take for example a statement I made in this post:

Quote:I can't believe I am about to teach English on an internet forum but I will and this will be the one and only other time I will dignify a response regarding LibreELEC.

This is crass as well. However, as I did indicate, dealing with LibreELEC is not worth the time for something that is free.

Now I will not make any further statements on the issue. There is a clear professionalism difference between LibreELEC and OSMC and that difference is something that makes it not worth it as previously described.

The irony of this is that OSMC was stated as a "small distribution" as well on the OSMC forums I believe and absolutely no one had any issues. I frankly believe that the administration of a community reflects on its members and OSMC was very professional while LibreELEC was not.

So, in conclusion: LibreELEC is simply not worth the headache for something that is offered completely free just based on the interactions with its administration. That is my final word on this issue.
Arctic Zephyr: From Ashes
The New Arctic Zephyr: Exploded Experience for Kodi Jarvis
Arctic Zephyr: Generations - Coming Soon
Reply
(2016-06-27, 20:58)Guardian Hope Wrote:
(2016-06-27, 20:45)sparklyballs Wrote: a reply from yourself

"And so that there is no misunderstanding: don't be crass and try to throw around numbers as it's very unprofessional."


yet your first post contains

"We have received reports from users of the Kodi Skin Arctic Zephyr: From Ashes which is currently installed on hundreds of thousands of devices "

^^^ also crass and unprofessional ?

I can't believe I am about to teach English on an internet forum but I will and this will be the one and only other time I will dignify a response regarding LibreELEC.

When dictating a small subset of users (Raspberry Pi running LibreELEC) are experiencing a very specific issue compared to the greater usage than it is appropriate to use numbers.

For example, if the following statement was made (this is an example):

Quote:Of the 50,000 downloads of LibreELEC, about 2,500 people are experiencing issue X, Y, and Z in comparison to all other devices (...)

Is a proper use of number indication.

An improper and rather crass way to use numbers is to try and turn a compliment of success (a relatively small distribution justifying its numbers which turned into the only focus rather than the bug report) to try and essentially say "hey, [we're] not a small distribution."

Just accept the compliment of success and move forward to the bug report. It is all in the way it's written as text does not translate well sometimes.

Take for example a statement I made in this post:

Quote:I can't believe I am about to teach English on an internet forum but I will and this will be the one and only other time I will dignify a response regarding LibreELEC.

This is crass as well. However, as I did indicate, dealing with LibreELEC is not worth the time for something that is free.

Now I will not make any further statements on the issue. There is a clear professionalism difference between LibreELEC and OSMC and that difference is something that makes it not worth it as previously described.

i'm not part of LibreElec by the way, i was just pointing out your hypocrisy.

and your above drivel is just more evidence of your condescending tone.
Reply
I understand and acknowledge the following:

  1. The bug had already been fixed before your initial post on the LE forum.
  2. It's cause was actually determined by an LE developer independently several days before your post - this may come as a surprise to you, but LE and OSMC developers are not entirely disconnected from each other
  3. You made no attempt to contact LE developers through the normal channels, but for whatever reason decided to be openly critical of the LE project and thought that was a great way to start a relationship (it wasn't)
  4. You like to throw random numbers around in an effort to justify how important your skin is, yet chastise others for doing the same
  5. You repeatedly made unnecessarily condescending and inappropriate - verging on snide - remarks which you surely knew would only undermine your already tenuous position. Your posts were very tiresome to read.
  6. Your determination of a distributions user base size (small, large, whatever) based on how many users use your skin is woefully flawed - there is no correlation between the users of your skin and a distributions userbase, other than how popular (or unpopular) your skin may be with any particular distribution.

Please keep your replies civil.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
(2016-06-27, 21:09)Milhouse Wrote: I understand and acknowledge the following:

  1. The bug had already been fixed before your initial post on the LE forum.
  2. It's cause was actually determined by an LE developer independently several days before your post - this may come as a surprise to you, but LE and OSMC developers are not entirely disconnected from each other
  3. You made no attempt to contact LE developers through the normal channels, but for whatever reason decided to be openly critical of the LE project and thought that was a great way to start a relationship (it wasn't)
  4. You like to throw random numbers around in an effort to justify how important your skin is, yet chastise others for doing the same
  5. You repeatedly made unnecessarily condescending and inappropriate - verging on snide - remarks which you surely knew would only undermine your already tenuous position. Your posts were very tiresome to read.
  6. Your determination of a distributions user base size (small, large, whatever) based on how many users use your skin is woefully flawed - there is no correlation between the users of your skin and a distributions userbase, other than how popular (or unpopular) your skin may be with any particular distribution.

Please keep your replies civil.

@Milhouse - Since your response is not one of "he said, she said" I will be happy to answer your statements so that points are absolutely clear.
  • It may have been fixed but the fix was not released and therefore in good faith and responsibility, we brought it to the attention of LE
  • This was not indicated by LE Developers prior and the only known distribution we knew of which had corrected the issue was OSMC. In our eyes, it was an OSMC developer who identified the problem and this is why the OSMC GitHub commits were indicated in the bug report;
  • LE has no indication of how to contact developers through "proper channels" which is of course the first thing we look for. Typically, you can find "proper channels" easily outlined but this is not the case on the LE website. In fact, to this very day there doesn't appear to be any indication. No "/contact" or no "/about" which is where most reputable places keep such information. IRC is not a "proper channel" but they do state on their website that developers can be found on the IRC [normally]
  • Stating a distribution is "small" does not equate to being openly critical. Statements made now however, are openly critical and I will not deny that. Please note that this was all triggered by one statement: an indication of how small the distribution was in comparison to the larger install base (Windows, OS X, regular Linux, etc.).
  • Do know that numbers are not random when they are pulled from Cloudfront and other various sources. The random number throwing started with LE and it is important to remember that. I already demonstrated how one way a number throw can be crass and one way it cannot. OpenELEC shows a 450,000 (estimated) install base. This, for example, is not crass. Trying to rebut a compliment (I do believe I said they were successful even for being 'smaller') is however crass. People will normally accept a compliment on success.
  • Do know that due to the fact internet is text, you can read my text however you feel like it. For example: I write this and in my head I read it normally. You might find it condescending and that is your choice but that is not how I intended it. How you perceive my statements is entirely up to you and has been shown to be a result of life experiences and is a psychological thing. I cannot change that.
  • I do not know where this keeps coming from where it is believed that I determined LE to be "small" due to how it's used by users of the skin but that's not where I determined the distribution size. I did so by reviewing its general userbase and then compounding it with what I know about these distributions and users who are using it. It's not an exact science; I do not have analytical data (which is also not an exact science) of the three distributions and I will and did freely admit that.

Now personally, I am ill at the moment which is why I've delayed the next release so much. Frankly, I don't care to deal with this nor will I continue in such discourse unless it is something that is respectful because I believe in respectful discourse. You presented respectfulness and as such I replied to your latest statements.
Arctic Zephyr: From Ashes
The New Arctic Zephyr: Exploded Experience for Kodi Jarvis
Arctic Zephyr: Generations - Coming Soon
Reply
The Road to Danvers and Krypton

With the nonsense regarding LibreELEC out of the way with a simple "the skin is provided free and thus we will only support it on all distributions except LibreELEC," I wanted to turn the page to the next chapter: Danvers and Kodi Krypton (Kodi 17). In the coming days, the Arctic Zephyr: From Ashes Summer 2016 Update" will be released adding a whole bunch of fixes for Jarvis and starting the Preview Availability for Krypton.

As Krypton is suspected to be released in a more stable preview form by the end of this month it means that all attention needs to be diverted away from Jarvis and the Dormer line to Krypton and the Danvers line where a lot of work will need to be done. So, how does this effect Jarvis/Dormer? Well, once the Summer 2016 Update is released it will enter the "Long Term Support" status. No new features will be added to it and if a critical bug comes up it will receive the appropriate fix. Hopefully, no breaking bugs occur because Danvers is based on Dormer's codebase meaning 3.2.20 and 4.0.20 are virtually the same minus the Krypton changes.

Jarvis users - continue to use AZ:FA's Dormer Line as you normally would until you feel comfortable upgrading to Krypton. The Danvers line needs a lot of work and there are destined to be bugs that will break the user experience on Danvers/Krypton.

Krypton users - the very first working AZ:FA Danvers Line release is coming soon. It is extremely rough around the edges and you will likely find a lot of bugs. Report your bugs here on the Kodi forums and on GitHub if you can at https://github.com/NortheBridge/skin.arc...hes/issues which will now serve as a public bug tracker as well.


Many have asked for an official site to get more details and learn how to best take advantage of the user experience provided by Arctic Zephyr: From Ashes. I am pleased to announce that development on such a site has begun and should be coming online as the development of AZ:FA "Danvers" continues.

With that said, you all may have noticed we have switched to "seasonal updates." As development on the "Danvers Preview" of AZ:FA happens that will change until we go from Preview Availability to General Availability at the release of Krypton. Then it will be back to "seasonal updates."

Now, with all of that said, Arctic Zephyr: From Ashes Anniversary Edition ("Arctic Zephyr: From Ashes Danvers Preview") for Krypton is getting a whole new look when it comes to Skin Settings thanks to @minus0 who has and continues to be an invaluable contributor to this skin. I figured since these are semi-final versions (subject to change), a little feedback from the community wouldn't hurt:

Image

Image

The second image is actually the default bar while the first image is a setting I believe.

Let us know what you think. I know there have been complaints about navigating all the skin settings and with Danvers we want to make is much easier.

For the official record, I do believe as of the commits I make today to Dormer, the Summer 2016 Update for Jarvis will be complete. Danvers on the other hand is a work in progress. So expect releases soon!
Arctic Zephyr: From Ashes
The New Arctic Zephyr: Exploded Experience for Kodi Jarvis
Arctic Zephyr: Generations - Coming Soon
Reply
Does anyone else have a Deja Vu of typical Xbox vs Playstation argueing when reading about OSMC and LibreELEC in this thread? xD

Both have its audience, so calm down please everyone, neither one is better, both have its uses. And please note that LibreELEC itself is pretty new, of course at the moment there might be more OSMC users out there, but how much OpenELEC users are still out there eventually switching to LibreELEC someday? Not talking numbers, but talking facts. :p

@ Milhouse: I LOVE your builds and contribution to LibreELEC, keep up the good work!

@ Guardian Hope: I LOVE your skinning work of Arctic Zephyr, please keep up the good work because your AZ:FA is my all-time favorite! (Just came back from mimic when 7.0.2 LE was released, and yes i was basically counting the days until I could do so.)
Reply
(2016-06-28, 16:45)Guardian Hope Wrote:
The Road to Danvers and Krypton
a little feedback from the community wouldn't hurt:

I don't mean to be rude, so please don't take this the wrong way. Consider this just constructive criticism.

After reading your post above regarding this skin and it's release, I'm sort of left scratching my head... And just plain confused.

In the single post above you mention: dormer, danvers, summer 2016, preview availability, general availability, seasonal release, anniversary edition... All this, tucked away in a sub section of a forum labelled as a "mod" for a skin that's development has ceased for months.

Perhaps a new forum section for this skin? It doesn't appear to be much of a "mod" but more of a skin of its own.

I mean, most skins just have a point release version, or a simple "Jarvis beta" or "krypton beta" which is pushed to kodi repo when stable. this makes sense and is pretty obvious and simple.

In regards to this skin, my feedback: keep it simple.

I don't mean to be discouraging in any way, it's great to have a lot of skins to choose from so
Keep skinning away!

Cheers,
Loggio.
Reply
This is turning into a unique thread...

I gotta agree with the post above about all the naming things being thrown around. Seems like a confusing way to present updates, IMHO simple is 9 times out of 10 the way to go.

Why the need to change the folder name after altering the addon id to include danvers? That shouldn't mean you need the folder name to match the skin id. At least I cannot think of a reason one would need to do that.

On second thought, why even alter the id in the first place as now auto updates from a repo won't ever happen when anyone updates to a newer Kodi version.

I am not criticizing just curious as to why make that decision Huh
Reply
  • 1
  • 18
  • 19
  • 20(current)
  • 21
  • 22
  • 77

Logout Mark Read Team Forum Stats Members Help
Arctic Zephyr: Generations (Jarvis / Leia) [3.4.70 / Coming Soon]7