Commonality of Open Alliance based images

[2stein]

i have used openvix before but just as a user. now i'm starting to do some development like plugins, skinning, etc.
so far i thought that open alliance based images use the same oa base like enigma2, skin support etc, so that plugins, skins, etc can be shared across those images.
after studying the code a bit, it looks to me like that is not the case. i studied openvix and openatv code and came to the conclusion that at least enigma2 and skins are not compatible. there seem to be vix and atv unique changes/enhancements.
is my observation correct?
thanks.

 

[Huevos]

We share oe core a lot of plugins and some skins. Not enigma.. every distro has their own.

 

[Huevos]

But in general most stuff is compatible if not using special features.

 

[2stein]

well, i stumbled over eServiceReferenceFS that openatv's enigma2 is providing... which is not available in openvix's enigma2... looks like only stuff that uses the lowest common denominator will work on multiple platforms. but nobody knows what the lowest one is...

 

[Huevos]

well, i stumbled over eServiceReferenceFS that openatv's enigma2 is providing... which is not available in openvix's enigma2... looks like only stuff that uses the lowest common denominator will work on multiple platforms. but nobody knows what the lowest one is...

What do you need that for?

 

[2stein]

well, i dont really need it, just wanted to try something and found that the code is not portable.

 

[birdman]

well, i dont really need it, just wanted to try something and found that the code is not portable.

So something you don't need isn't compatible.
Have you tried writing the code that you do need and checking how that fares?

 

[2stein]

will do. just trying to figure out whether that can be done without lots of image unique switches.

 

[Huevos]

In general all plugins from oe-alliance plugins, enigma2-plugin and opene2-plugins work. And OpenWeIf. In openvix we even add extra (redundant) functions and variable for compatibility with openatv. But if you want to use one of openatv's "special features" you will need to switch to openatv and forget about compatibility with other distros.

 

[Huevos]

will do. just trying to figure out whether that can be done without lots of image unique switches.

No need for unique switches. That just ends up with terrible code.

 

[2stein]

i dont even know about atv "special features".
how about skin features? looks like vix has some advanced features like hierarchical structures, scaling, etc. that others dont have...

 

[Huevos]

how about skin features? looks like vix has some advanced features like hierarchical structures, scaling, etc. that others dont have...

Most stuff is the same. Why do you need scaling? That is only needed for the emergency skin and skins embedded in the code. And for scaling simple embedded skins just use the "resolution" attribute in the "screen" element. Works in OpenViX, OpenATV, OpenPLi and derived images.

Well actually OpenATV has a bug in "resolution", but for basic values, not formulas, it does work well.

 

[2stein]

ok, thanks for the explanations. that helps me decide which code base to use for my development activities... and i think it's going to be vix.

 

[Huevos]

If you need help just ask.