Custom Conversion schemes?

[Fuzzy]

Would it be possible to have either an event fire, or be able to configure and external java class for a conversion job? (I'm thinking like using some sort of pluginclass .properties entry)? The list of plugin classes could be added to sage's conversion choices, and be an option for both manual or auto-conversion.

[PLUCKYHD]

Can't sjq do this?

[Fuzzy]

Of course it can - but not from the default sage conversion/autoconversion queue. That's what I'm looking for (for a user-ease type thing). Then, things like Handbrake and such could be simply added to the list of conversion options. No need to go through the sjq learning curve. All that is really missing is the API end from Sage.. :-)

[PLUCKYHD]

I think the sjq learning curve will go way down with the next version.

[Fuzzy]

I'm not so sure about that. It looks so far like just a new learning curve, where people ahve to write their own scripts, in whatever language they choose (batch, vbs, etc) instead of the 'simplified' SJQ language.

[tmiranda]

Originally Posted by Fuzzy

I'm not so sure about that. It looks so far like just a new learning curve, where people ahve to write their own scripts, in whatever language they choose (batch, vbs, etc) instead of the 'simplified' SJQ language.

Hopefully there will be enough examples to make SJQ4 usable by mere mortals and not just programmer geeks. That's the goal anyway.

[Fuzzy]

Originally Posted by tmiranda

Hopefully there will be enough examples to make SJQ4 usable by mere mortals and not just programmer geeks. That's the goal anyway.

Hopefully - but there were plenty of examples for the old SJQ scripts as well.

And that's still no reason for sage NOT to implement this into the core itself - at least for the conversion aspect. They've already got a good, working queue system - this, and the ability to run conversion tasks on client is about all that would be needed to give people a LOT more flexability, with no learning curve.