Re: FileTransform interface changes
Malcolm Humphreys <malcolmh...@...>
I leave it up to you to decide what makes it into 1.0. At the end of the day I would just be happy to somehow replace these:
FileTransform::setCCCId(const char * id)
But I think for 2.0 a full blown solution would be a great addition.
Could we find a halfway point?
FileTransform::setOptionString(const char * id)
This could take a 'token1=value1;token2=value2' string. This is a bit ugly but does allow for the interface to be not so format specific while also allowing to add other options if they are needed for fixing bugs on the path to 2.0.
I think that is a great idea and should be 2.0 as it's a big interface change. I like it even more after trying to wrap all the transforms types which is a hell of lot of boilerplate code.. (grumble)
yep just for the ui.
I would hope this would be just a straight FileTransform rather than a separate *Transform.
I was more thinking of being able to add it in a 1.xx minor version rather than it being ready for 1.0.
Well I'm all for that as it's originally what I suggested :) it would be good if this API also extended to adding additional file formats.
I would hope the long term goal would be to roll new formats into the core but this would allow adding/modifying existing support.
Sure, you kind can do that now as Ben has just posted so it's not really a big issue for 1.0 for me.