Release an update for a STVi: What's best practice?

[ehanekla]

Hi experts,

I may have missed that information while skipping through the SageTV studio guide. I couldn't find an answer for my problem:
I created an STVi for the Default STV. Now I want to release an updated version of my STVi.
Is there a way to handle the following both cases in a single STVi?
- a user imports the STVi from the plain default STV
- a user already has the first version of my STVi imported

Best regards,

Eyk

[razrsharpe]

Originally Posted by ehanekla

Hi experts,

I may have missed that information while skipping through the SageTV studio guide. I couldn't find an answer for my problem:
I created an STVi for the Default STV. Now I want to release an updated version of my STVi.
Is there a way to handle the following both cases in a single STVi?
- a user imports the STVi from the plain default STV
- a user already has the first version of my STVi imported

Best regards,

Eyk

not that im aware of... you would need to create to 2 STVi's... one for first time users, and one upgrade.... of course you could package both stvis in the same zip file...

just an fyi most programmers here only release full versions... in the installation instructions they specify that you must start from an STV without the import being upgraded/installed and that it will not import on top of itself

[ehanekla]

Hi,

thank you for your answer. I was afraid someone could say that...
Especially I noticed that you have the same "problem" with TVExplorer.

Something like incremental updates would be nice. So that every new version contains all previous version or so.

Ok, that's life...

Thank you,

Eyk

[razrsharpe]

yup it would be nice if the importer handled all the versioning and updating but unfortunately its not the case.....

[Fuzzy]

If you keep your entire import in the stvi, then just replacing it in the STVs folder will trigger the manage imports to regenerate the STV. It looks at file date, and if it changes from the last time it was rebuilt, it will notify the user that it has been updated and ask if he want's to rebuild.

[razrsharpe]

Originally Posted by Fuzzy

If you keep your entire import in the stvi, then just replacing it in the STVs folder will trigger the manage imports to regenerate the STV. It looks at file date, and if it changes from the last time it was rebuilt, it will notify the user that it has been updated and ask if he want's to rebuild.

thats a good point... i glossed over the default stv part...

[GKusnick]

There is no general solution to the problem of incrementally updating an STVI. (What if somebody else writes an STVI that modifies yours? How will you incrementally upgrade yours without hosing theirs?) So really the best approach is to start over from the base STV and reimport the full STVIs. As Fuzzy says, the stock STV's STVI Manager handles the reimportation automatically, so that's what you should be coding for.

[Fuzzy]

I would hope that any 3rd party STVs on the way forward also implement this style of import management. I don't expect SageMC to be changed at this point, but hopefully Phoenix and Ortus are taking this into consideration.