On Tue, Oct 19, 2010 at 7:56 AM, Jezz_X <[email protected]> wrote: > Although I disagree with most of what TheUni has said about this as have > other team members, the main things I think we need are the skin must work > out of the box 100% for everyone. Now this doesn't mean that all those > fancy extra images should show to me but last time I looked AEON versions > relied on the not always true fact the users store their movies > in separate folders for each movie and if you didn't lots don't work. > If this is no longer the case then I'm happy for it to go in as is since > AEON65 really is nothing like the original AEON at all aside from general > design > > On Tue, Oct 19, 2010 at 8:50 PM, Ppic <[email protected]> wrote: >> >> hi, >> >> don't know if it will help, but i'll soon pull a new version of logo >> downloader which support poster and banner from the tvdb and support custom >> naming. >> this will populate your tv show folders with banner.jpg / poster.jpg >> etc... in one shot. >> this will make easier for end user to get all this kind of varieties >> necessary for aeon. >> >> Ppic >> >> 2010/10/19 Cory Fields <[email protected]> >>> >>> On Mon, Oct 18, 2010 at 9:20 PM, Philipp Temminghoff >>> <[email protected]> wrote: >>> > Got an answer from DJH: >>> > >>> > "Funny that. I was just thinking about Aeon the other day. You're >>> > welcome >>> > to do whatever you like with it. :o)" >>> > >>> > >>> > >>> > On Mon, 18 Oct 2010 21:16:30 +0200, Philipp Temminghoff >>> > <[email protected]> wrote: >>> > >>> >> >>> >> 1. Ok, I understand this. Will try to contact DJH. >>> >> 2. there are only 3 mods which are Dharma-compatible (mine, showcase >>> >> and >>> >> AeonMQ2) and >>> >> the other ones don´t have correctly licensed fonts and are much >>> >> bigger. >>> >> Don´t really understand your comment about animosity though. >>> >> 3. Aeon is probably the most hardware-consuming skin, that´s right. >>> >> but that could be shown in the addon description for example. >>> >> I also included a first start guide where you´re asked about your pc >>> >> performance. >>> >> the most hardware-consuming things are disabled then. >>> >> 4. I´m makin use of several additional files like logo.png and some >>> >> more, >>> >> nothing different >>> >> to the other skins in the official repository >>> >> >>> >> would be a pity if no Aeon version would make it into the official >>> >> repo, >>> >> because it´s still one of the most popular skins for xbmc (at least >>> >> concerning forum participation) >>> >> >>> >> concerning stability: Aeon65 is stable since an xbmc bug fix (by >>> >> jmarshall >>> >> I think) several months ago. >>> >> just test it (http://github.com/pix/aeon/tree/font_rework) >>> >> >>> >> >>> >> ------------------------------------------------------------------------------ >>> >> Download new Adobe(R) Flash(R) Builder(TM) 4 >>> >> The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly >>> >> Flex(R) Builder(TM)) enable the development of rich applications that >>> >> run >>> >> across multiple browsers and platforms. Download your free trials >>> >> today! >>> >> http://p.sf.net/sfu/adobe-dev2dev >>> >> _______________________________________________ >>> >> Xbmc-addons mailing list >>> >> [email protected] >>> >> https://lists.sourceforge.net/lists/listinfo/xbmc-addons >>> > >>> > >>> > -- >>> > Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ >>> > >>> > >>> > ------------------------------------------------------------------------------ >>> > Download new Adobe(R) Flash(R) Builder(TM) 4 >>> > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly >>> > Flex(R) Builder(TM)) enable the development of rich applications that >>> > run >>> > across multiple browsers and platforms. Download your free trials >>> > today! >>> > http://p.sf.net/sfu/adobe-dev2dev >>> > _______________________________________________ >>> > Xbmc-addons mailing list >>> > [email protected] >>> > https://lists.sourceforge.net/lists/listinfo/xbmc-addons >>> > >>> >>> That's a good start. Please have him commit a license to his github >>> repo, then it's a matter of public record. >>> >>> The other issues still stand. I'll be honest with you... the word >>> "Aeon" does not sit well with most XBMC devs. We associate it with >>> skin hacks, users doing crazy things, forks, half-completed features, >>> bloat, the list goes on. We certainly appreciate your work, and don't >>> want to discourage your effort, but there's a lot of history with >>> Aeon. >>> >>> I'm not averse to adding it, but things have to be simplified. I'm not >>> saying it will be easy, but here's my proposal: >>> >>> 1. Get the original licensed. Sounds like Duncan is ok with doing this. >>> 2. Merge the forks. Yea, I know. This will be rough. I fear that once >>> one is added, the other forks will cry foul, and say "You added his, >>> why won't you add mine? Mine is better/more original/slimmer/etc.". >>> Keep in mind, addons in the repo are for regular users. They have >>> likely not been to the forum, and know nothing of Aeon's history. And >>> they have no idea why one Aeon version is betteer/different than >>> another. Besides, having a few developers work on the same skin is >>> much more productive than each maintaining their own fork. >>> 3. Make it work out of the box. This might already be the case with >>> yours, I'm not sure. If you want to add 10 different options for extra >>> fanart, thumbs, 4d trailers, fine... just be sure that users switching >>> from confluence will see similar functionality. If a skin requires >>> hours/days of configuration that's fine, but it doesn't belong in the >>> official repo. >>> >>> Sorry if that was a bit blunt. With the above things fixed, the skin >>> would be a great addition to the repo, and we could put the issue to >>> rest once and for all :) >>> >>> Cory >>> >>> >>> ------------------------------------------------------------------------------ >>> Download new Adobe(R) Flash(R) Builder(TM) 4 >>> The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly >>> Flex(R) Builder(TM)) enable the development of rich applications that run >>> across multiple browsers and platforms. Download your free trials today! >>> http://p.sf.net/sfu/adobe-dev2dev >>> _______________________________________________ >>> Xbmc-addons mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/xbmc-addons >> >> >> >> ------------------------------------------------------------------------------ >> Download new Adobe(R) Flash(R) Builder(TM) 4 >> The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly >> Flex(R) Builder(TM)) enable the development of rich applications that run >> across multiple browsers and platforms. Download your free trials today! >> http://p.sf.net/sfu/adobe-dev2dev >> _______________________________________________ >> Xbmc-addons mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/xbmc-addons >> > >
Yep, there's clearly going to be some disagreement here. Internal and external. All of which is fine as long as we can keep this civilized and on-track as it has be so far :) I certainly agree with Jezz that it needs to work out of the box. I think that where we differ is that he and some of the others want all skins and mods to be accepted to the repo. To be clear, the xbmc.org repo is one that we maintain. So far, it has been a significant amount of work for the maintainers to keep up with the additions and updates. Very significant. So it is not realistic to say that all additions will be accepted, while still maintaining a good user experience. In the beginning, we decided that (for now), skin mods would not be allowed. Only full skins. This is to discourage one-time submissions; As I stated before, we want the addons in the repo to be living, evolving things. The difference is hard to determine since there is no real metric. I installed Aeon65 last night and took it for a spin and it is indeed its own skin. But I think we can all agree that people who change a few lines of XML have created a mod. So we're going to have to use our judgment to determine what is a skin and what is a mod. I believe I acted too quickly in lumping Aeon65 in with the others and for that I apologize. In my opinion, having several skins in the repo that look/feel very similar is a bad thing. It only confuses users and encourages forks. I realize that this seems a bit contradictory because of Alsaska/Revisited, but I would change that if I could redo it. So I suggested that the authors work together. If each believes that their skin is completely independent and should be evaluated on its own, then that's how it will be. But someone is going to have to make a judgment call on each. Philipp: You're center stage. What's your take on this? Cory ------------------------------------------------------------------------------ Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev _______________________________________________ Xbmc-addons mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbmc-addons
