New Versions (1 Viewer)

[MrLobster]

Even though I dont use this skin (I did try it out at version 1.8), I keep seeing updates (or fixs) every few days.

I feel there are too many new releases.

I think you should have 2 threads for versions.

#1. Main stable version (i.e 2.1).

#2. Beta Version (2.1.x).

Once the beta version (2.1.x) has enough time to settle down (few weeks perhaps), then you can convert it to a stable version (2.x).

This means you can still release the updated skins, but people dont have to download it every few days.

I do see that if there are problems in the current stable version they need to be addressed. However implementing new features in the beta and testing them out that way would be a better way.

 

[lqpl]

I do not mind frequent updates!

But perhaps it is an idea to let the Black Glass folder inside the Rar file, have a version number.
I rename the folder myself to Black Glass 2.1.1 before coping into the Skins folder,
this way I can keep several versions and easily switch back to an earlier version if needed.

 

[ysmp]

same her , i like that have so fast updates for the skin ,
i also rename the new version , evrey time ....

i say keep it up....

 

[DreadFury]

He is saying to have two different version stickied I think.

One 'stable' version, and the current 'dev' version.

 

[Tgx]

#1. Main stable version (i.e 2.1).

#2. Beta Version (2.1.x).

Once the beta version (2.1.x) has enough time to settle down (few weeks perhaps), then you can convert it to a stable version (2.x).

This means you can still release the updated skins, but people dont have to download it every few days.

I do see that if there are problems in the current stable version they need to be addressed. However implementing new features in the beta and testing them out that way would be a better way.

Hi!

This is a small project of a Mediaportal enthusiast. I'm developing this little skin for my personal pleasure (and of course for anyone else who likes it) and it has become an hobby. Keeping track of 2 versions at a time would become too much demanding and bothersome. It would be a too much scientific approach for a tiny project. I'm doing this at my very best to keep the skin working well and if there are any mistakes, i hurry up to fix them. I like the Mediaportal community because it's full of people who likes to experiment new solutions. I feel that if i stop releasing fast updates, many people would not like it!

Thanks!

Tgx

 

[MrLobster]

Dont take what I said as an attack on the creator or the skin, its just updates (for anything) normally take a while to come out.

If I was using this skin then I would too probably update every time, I personally install the latest version of streamedMP when it gets released.

Its a great skin and your doing a wonderful job on it.

 

[Tgx]

Dont take what I said as an attack on the creator or the skin, its just updates (for anything) normally take a while to come out.

If I was using this skin then I would too probably update every time, I personally install the latest version of streamedMP when it gets released.

Its a great skin and your doing a wonderful job on it.

There's no problem! I appreciate your advice! You are right. The way you suggest is used in many bigger and more serious projects, but i feel comfortable in the way i'm used to... and it seems many others like it!

Thank you very much!

Tgx

 

[Jean-Marc]

Maybe what would be interesting is to have an "update package" containing ONLY the files that changed (for those who yet have the skin installed) and, of course, the complete new release for other people.

Why?

Because, for example, I updated 2.0.1 to 2.1 and I lost my configuration for the home page (basichome): the pictures are ok but the different links no more (I unfortunatly not made a copy of the basichomebuttons.xml file)
I also did some personal changes into some files (to modify or translate some words, to eliminate some usefuless info for me, and another things...) and everything is lost as I didn't backup my own settings. And even if have had done this backup, it is difficult to be sure of which files changed or not.

So now I must configure again everything, what I would not have to do with a single "update package".

for your understanding!

 

[Tgx]

It could be, but if the update involves the same files you have not backed up? It's not the same?

Thanks

Tgx

 

[mr viggo]

I'm one of those that like frequent updates too. But I'm really glad that you made a "bugfix" thread. That way it's easier to keep up with what the changes are. And even though some of us wants the updates as fast as possible I think that cul8ers initiative to start a beta testers thread was a good idea. That way, people with much spare time for the moment and willingness to try the new things out can do so for the cost of reporting flaws/bugs.

just my 2 cents.

Keep up the good work Tgx, I love what you're doing.