Re: [xine-devel] a todo list before 1.0

[Christer P. <pa...@no...>]

Casper Boemann Rasmussen wrote:

> Shouldn't we have a todo list on the upcoming 1.0 release. 

One thing that strikes my mind when playing around with the xine-lib API 
is that there, IMHO, are a few inconsistencies in the interface.

Perhaps it would be a good idea to clean that up before 1.0?
I mean, once xine moves into 1.0 it would probably be too late for any 
major changes to the API.

A few examples of what I had in mind;

* Inconsistencies in how data is returned to the caller, i.e. array of 
structures vs. string with newline-separated elements vs. string with 
semicolon-separated elements vs. array of strings.

* Inconsistencies in how objects are manipulated, i.e. separate function 
calls vs. function pointers vs. a "catch-all" function call (i.e. the 
property functions).

* Inconsistencies in how non-trivial data types are represented, i.e. 
encoded strings vs. structures vs. separate arguments.

-- 
Christer Palm