motyR Wrote:but this is exactly what the guy is saying, the all skining capabilities of xbmc is crap, don't believe me? well look at aeon skin and how it has abused the power that xbmc gave him, abuse? raped, molested.
the all design should have been entirely different, is there any reason why xbmc skining not using inheritance FFS why do we need to recreate each and every widget(and please i'm not talking about includes), xbmc should have given more formality and unified specs to the widgets and an explicit directive way when ever u want to use your own custom widget that way u could maintain your modes with no big fuss.
at the time being, for one to create a skin u'll need to have MIT diploma or a father that works as a NASA engineer, that for me is a DESIGN BUG, and lets face it, when it comes to functionality the only skin that can deliver the needs of a true media centre is pm.hd3 and guess what the skin had been written by xbmc developer.
SOME of what you say has some validity... the skinning of XBMC is VERY flexible, but not the easiest in the world to develop for... I'm about to start doing some skinning myself, and it's very hard to find resources and guidance starting from scratch.... however:
- It clearly is good enough to get some very impressive results
- You could always help by offering your design expertise and code to the community
- You could consider ways to express criticism in a manner that is seen as constructive and not destructive
I can point to 100 things in XBMC that suck. I can do the same with a Ferrari car. It doesn't mean it's a bad product... it means it's a realistic one. Compromises are made... people develop this for free, across multiple platforms, and whilst there ARE some grumpy developers, the vast majority will give you the time of day, IF you take a little time to be polite, have some sound reasoning in your arguments and make an effort in contributing 'something' to the community... even if it's just helping others overcome issues.
Inheritance (implied Object Orientation) is no guarantee of better code you know. It can in many cases lead to bloated and inefficient code. I support Object Orientation, but it's just a programming paradigm... an artificial construct designed to help stupid humans (all of us) think more easily.
I reiterate, some of what you say is entirely true, and most of the XBMC Team (I think) would agree in principle... they aren't stupid. What they are however, is pressed for time, more focused on other matters and finally masters of their own destiny!...
Come back with a better version of the criticisms and some possible ways to improve it.... you'll be welcomed with open arms!