What gets upgraded

[spike5884]

With 4.1 being out now, how do we know what part got updated? That is, if we have changed the STV, how do we know when we have to go back to the "new" original STV and apply our changes to it?

[Narflex]

You can use the 'diff' feature in the Studio to find out exactly what's changed in the STV.

[Opus4]

In the past, I've found it useful to keep a copy of the previous version's original default STV to compare to the one in the new version -- that way, the comparison will only show the changes made to the default STV, not the ones you made.

- Andy

[ke6guj]

I like how the new xml stv's work. If you import in an stvi to Sage3TV.xml, it makes a new xml called SageTV~1.xml, do another import, SageTV~2.xml. Makes it easy to "roll back" an import.

Just don't reload an .STV instead of an .xml, if you do, you can't load an .xml without editing your properties file.

[Opus4]

Originally Posted by ke6guj

Just don't reload an .STV instead of an .xml, if you do, you can't load an .xml without editing your properties file.

That's only because older STVs were written to filter all but .stv files when choosing an STV to load. The new default STV allows .stv or .xml.

But, you can also choose an xml file to load via Studio w/o exiting & editing the properties file.

- Andy

[mkanet]

Can somebody please make a little import stvi which includes all the UI changes/enhancements from 4.0 to 4.1? I loaded my custom .stv after the upgrade, now I dont have any of the new features available in the menus (ie no way to import .xml based UI's, option to enable/disable menu transition effects).

Eventually, I guess I need to create an STVI for my custom SVI using the Diff feature.

Thanks!

[gplasky]

You can use Studio to load any stv or xml you want. Load the xml, disable the menu transitions, then load your stv back up again.

Gerry

[mkanet]

Huh? I just was asking for an stvi which includes the UI delta from 4.0 --> 4.1.

I dont have a clue what the below would accomplish or how to do it. I'm just a novice at studio.

Originally Posted by gplasky

You can use Studio to load any stv or xml you want. Load the xml, disable the menu transitions, then load your stv back up again.

Gerry

[gplasky]

Originally Posted by mkanet

Huh? I just was asking for an stvi which includes the UI delta from 4.0 --> 4.1.

I dont have a clue what the below would accomplish or how to do it. I'm just a novice at studio.

Right. Just an easy way to make those new setting changes witout editing the .properties file.

But wouldn't you just want to make YOUR changes into a STVI? So you could import your changes into any new default that comes along? I mean what if a new default comes along that has 100 changes in it? Wouldn't that be more work?

Gerry

[mkanet]

I guess if there isn't an STVI which includes all the UI changes from 4.0->4.1, I have no choice but to make my own STVI.

The problem is that I have no clue how to make an STVI and have that integrate with the new XML. I tried reading the "Creating STVI imports" thread and got lost after the first few sentences.

Can somebody PLEASE help me with this? I really dont want to have to learn Studio just to update my installation of SageTV.

[mkanet]

I'm not sure if I should sit here and wait for somebody to help; or if I will get any help at all.

I had no idea that it was going to be so difficult to keep the changes I have made to SageTV 4.0 and integrate the 4.1 "upgrade".

Would somebody PLEASE be kind enough to take http://68.126.200.8/download/SageTV3-MKA.stv and make an STVi out of the changes I made to the original SageTV 4.00 UI??

Or, if it's easy enough for a complete Studio novice, maybe somebody wouldn't mind outlining a step-by-step procedure to do this myself.

I would never have painted myself into a corner like this had I known upgrading from a customized version of SageTV 4.00 would be so difficult!

Thanks so much in advance!

EDIT: *Sigh* I guess I would even resort to paying somebody to help me get this done if that's what it takes

[stanger89]

Unfortunately STVi's are not trivial to make, in fact I'm quite amazed neilm seems to have such an easy time making them.

You can use the STV file difference tool in Studio to see what's different vs the original V3 STV.

[mkanet]

Hmm... I thought studio had a tool called DIFF which will create an STVi from the delta between two STV's. That seems pretty simple.

Now I'm really confused. Man, I'm just shaking my head wondering how I got myself into this mess.

[Opus4]

The diff option just shows you a window w/the differences. As I mentioned above, I used to keep the various versions of the default STV that shipped w/each upgrade. I also had a list of changes that I had made, so I could remember which changes I had to do when a new version came out, if the default STV changed too much to simply add those changes.

- Andy

[mkanet]

This is pretty frusterating. I am currently looking at the differences between the default 4.0 STV and the default 4.1 STV via the DIFF tool.

So, even if Studio could export all the changes it finds via the DIFF tool to an xml file, there still isn't an automatic way to convert the xml to an STVi? Am I right?

[nielm]

one option:
Save the 4.0 original STV as XML in studio
Save the 4.0 modified STV as XML in studio
use text comparison tool to do a 3-way compare/merge with the original 4.0 stv as a common ancestor

No idea how well this will work though... if the widget ID's have changed it will not work at all..

And no an STVI for 4.0->4.1 changes would not be at all trivial...