[mikeSiLVO]

@mikeSiLVO  

Thanks mike for you kind words. I hope to push an update on git in the next few weeks, any feedback will be great.

@mikeSiLVO and @Slipass 

As you said Mike, Aeon Madnox is a heavy skin.

A compatibility update and other fixes for Leia may not be enough to make it run smooth on low spec systems. I spent some time looking at the the code for Aeon Madnox and the amount of changes required for a huge performance boost may not be possible with out re-coding the whole skin. On the other side, the git changes from mike, will improve the performance on lower spec system like Ordroid or Pi Zero. If it is enough time will tell.

The suspects i believe are (a big list), string compares, color picker, duplicate textures, variables with in variables within variables ect. , includes within includes within includes ect. , too many visibility conditions, too many animations, too may scripts pulling info from the web, bloated fonts, bloated localized strings and too big textures, hence the 300mb+ skin size. This pretty much sums up the whole skin from a coding perspective.

The end result is a skin that requires good cpu power and good memory. What ever the system specs required atm i am unsure of.

@Slipass 
V2 is in the works. It may take six months, it may take a year. ArieS and myself are getting the alpha version ready for the community. Everything mentioned, i have taken into consideration for performance of low spec systems. Time will tell.

@All
Right now!!!, we have Mike's improved version of Aeon Madnox, who is doing a great job in improving the skin and performance. Feature complete and running rather well on higher spec systems. https://github.com/mikesilvo164/skin.aeon.madnox

I am glad you posted, @M. V! (I really do not know how to make usernames with spaces work with the new notification system, so I hope it is working...).

You really have done a superb job, not only with the MadNox rewrite but the widgets you have spent so much time on for both Aeon MadNox and SiLVO.

You did what you should not have had to even consider doing which was to apologize to me for how I perceived things. I am truly sorry for that, I am an asshole .

While I try my best not to be, I often fail at that endeavor.

I agree with your assessment:
"The suspects i believe are (a big list), string compares, color picker, duplicate textures, variables with in variables within variables ect. , includes within includes within includes ect. , too many visibility conditions, too many animations, too may scripts pulling info from the web, bloated fonts, bloated localized strings and too big textures, hence the 300mb+ skin size. This pretty much sums up the whole skin from a coding perspective."

Tracing all that is such a pain in the ass-cheek... my goal is to work on what is here now to perhaps give you a better "framework" to (maybe?) add to the base skin. Just cause it exists in Aeon MadNox does not mean you should consider adding it. Aeon MadNox may continue but MadNox is and will be the future.

Seriously, I would use what you got now. I don't care about all the extra stuff but that may just be me .

I plan to continue working on Aeon MadNox and keep it updated for the foreseeable future. I will gladly work on what you want me too as well but I need you to be OK with telling me what to do. I have no desire to be in charge or lead the way, so feel free to boss me around, slap me like a child, and give me something to work on .

If you gonna slap me though, at least give me something to do first