Is the Visuals API (for writing your own visuals) still a possibility for 2.0 or some other soon upcoming release or has it been entirely tanked? (If it's been tanked, I'm quite sad...)

Not 2.0 - we're trying not to get too carried away with feature creep (he says).

Hopefully later.

Rob

Hopefully later.

Rob, where would you rank this on the list of post-2.0 priorities? Given that it's not likely to benefit the product that much to a consumer, is this really just a "copious spare time" feature? Do you have a rough idea of what the programmers will want to do in the future? It seems to me they just sneak things in when they're feeling frisky.

Don't forget that empeg run a small incentive as in all new programers seem to get their own empeg to play with

This i think lead to the CFB

Because the car player is EOL it has no development plan. Therefore it gets new features either off the back of other products, or because developers want to implement them and have some time to do so.

I suspect the net result might be more new features than if the product were not EOL, but don't quote me

As for a visuals API, I have no idea where it might rank in priority.

Rob

Therefore it gets new features either off the back of other products

Well then a follow-up question... Would a visuals API be useable on those "other products" including the new home streaming thing? I haven't followed the HSX threads much but I thought I remember hearing it has Prolux visuals...