Very interesting ...

[dflachbart]

SeriesInfoAPI, TranscodeAPI, TVEditorialAPI ...

Looks like cool things are about to come soon ... :D


Dirk

[Opus4]

We've been waiting to see how long it would take before someone noticed the API doc changes. ;)

- Andy

[dflachbart]

We've been waiting to see how long it would take before someone noticed the API doc changes. ;)

- Andy
:clap:

Is there more to come, or is this pretty much complete ? I know you won't tell, but I try anyway ... :D


Dirk

[Opus4]

Is there more to come, or is this pretty much complete ? I know you won't tell, but I try anyway ... :DI think I'll just answer with: "yes".

- Andy

[Jason]

:clap:

Is there more to come, or is this pretty much complete ? I know you won't tell, but I try anyway ... :D


Dirk

You'll like the changes/additions... ;)

-Jason

[silkshadow]

SeriesInfoAPI

Hmm, that sounds really good if its what I think it is. However, wouldn't it just be easier to allow us to import our own formatted metadata into wiz.bin? Just a thought for the Sage guys to consider. Correct me if my non-coder brain is wrong, but doesn't an API imply a requirement for a 3rd party to create something to access it? Instead, personally, I would prefer just a mechanism where Sage gives me the field mappings to, say, an xml sheet and a way to import my data using that map. Wouldn't that just be easier for Sage as well? Apologies if I am way off here because this covers things I am not totally familair with.

[GKusnick]

Wouldn't that just be easier for Sage as well?
No, it wouldn't. The API for adding items to the database has to exist in any case. Any sort of generic importer would be written on top of that, regardless of who writes it. So the easiest thing for the Sage devs is to just publish the API and let the third-party coders loose on it, rather than trying to cover all the possibilities themselves.

[silkshadow]

Ah, I see, thank you for the knowledge!