Update Obsolete Component Option

Hi Crapadilla

I am writing some code to do this, It should be ready soon.

Ken.

Quote
Crapadilla wrote: I'm guessing this would work outside of FF by modifying the xml files directly?

Yes. The code for the 3 blends is finished. I just need to to write code to update
Min, Max and 2 switches.

I have written it so that I creates an entirely new filter (with a new name) for safety

I can change this later to overwrite the old filter

Ken.

http://www.filterforge.com/forum/read...5&TID=1677

Ken.

I got nothing to do with it, Stevie!

Quote
Kraellin wrote: if the programmers do add an auto-update of older components, PLEASE make it optional.

Of course, it can't be mandatory because we don't guarantee that the updated component will produce the same output as the old component with identical inputs.

Quote
Crapadilla wrote: I just revisited my older filters to update obsolete components, and it occured to me that there really should be a more elegant way to update those.

Bump!

Just had another session of updating obsolete components via notepad, searching and replacing 'Blend3's with 'Blend4's in the xml text.



While that was easy enough for a lazy type like me who abhors repetitive manual labor (and who doesn't), I'm wondering why this option still isn't available from inside FF! Can't be too hard to code up a 'Replace All Obsolete Components' option for the Filter Editor menu, eh?

Yup, it's quite straightforward, isn't it!

Basically you replace all <Blend3> tags with <Blend4> tags in a text editor. This turns all Blend 1.005 components into up-to-date Blend components (1.010). The same procedure can be performed for other obsolete components, of course, and the good thing is that it spares us from having to manually redo all connections and remappers inside the Filter Editor.

Still, I wish there was an option inside FF that would run a swift 'replacement' pass over the ffxml.

CTRL+S

Quote
Crapadilla wrote: We needs it automated... We needs it!

+ 1,000,000,000 Definite must have!!! Manually trying to update all those components is beyond a ridiculous time-consuming task!!!

If this happens, I would also like to have the reverse ability....batch revert V2 filter components (for filters that don't incorporate any of the new components) back to V1.xx versions....for those who have built filters with all "common" V2 components and want to submit filter as a V1.xx to obtain better usage stats towards getting HU....due to there being far more V1 than V2 users.....

I'm working on a script to do that....

Quote
Crapadilla wrote in 2007: I propose an 'Upd ate Obsolete Component' option on the context-menu of a selected component. This would replace the component, copy all its se ttings, and - most importantly - keep all the connections and remappings intact, so that we don't have to manually recreate them.

OH yes!! this would be a good idea and very useful and interesting, but regretably if this was requested in 2007 and 5 years after in 2012 is still not implemented is like MANY other requests that are not done

Quote
Ken wrote: Hi Crapadilla I am writing some code to do this, It should be ready soon. Ken.

OH YES!! This will be also possible to make using an external tool and is a good idea BUT regretably Ken uploaded this tool in this thread here BUT the downloads links are not available anymore

Quote
Crapadilla wrote: I'd even be happy with a command-line utility. FF Team! Please, pretty please! Don't tell us you've been updating all those obsolete components by hand! We needs it automated... We needs it!

YES!! It does not have to be included inside FF, with just a command-line utility I would be happy too IF this is easier and more possible to make

Pretty Please! Would be possible to have a tool to convert old filter with newer versions of the components ?

Quote
+ 1,000,000,000 Definite must have!!! Manually trying to update all those components is beyond a ridiculous time-consuming task!!!

I totally agree with you and this would be a must have, and is true that manually updating a filter that have LOTS of components is really tedious, boring and time-consuming.

Difficult thing to pull off, given that some components exhibit very different behaviors with the same input at the same settings (for example, Elevation Gradient 3.004). Also different versions sometimes have different controls?! Image 2.009 allows for a built in Particle Adapter, to modernize would be 2 components if I'm not mistaken.
"
So, it is doable, but it is not a "drop in" replacement scheme, and on some components warnings would have to be issued for changes in behavior in the newer component.

Which then begs the question: is it worth it? I suppose if you have groups full of old components...