SageTV Studio & Android

[Brent]

Question for you developer types: Is there anything Google can gain from the SageTV studio stuff? Or would all plugins and such need to be re-written for Android?

Just trying to wrap my head around Google's reasoning...

[bialio]

Studio is a far cry from developing android applications.

I would switch in a NY Minute, which I hear is pretty quick, to doing Android apps in Eclipse vs working in Studio - I think most would agree.

Don't get me wrong, I love that Studio exists and makes things like SageMC and Phoenix possible - but it'd be a lot easier (I think) to use androids GUI building tools.

btl.

[Fonceur]

Studio is to Android what LaTeX is to MS Word... Or like building a web site with Notepad instead of an HTML editor...

[stuckless]

Android is very much like a plugin system on it's own. While you write "Apps" for android, apps can leverage the abilities that are exposed in other apps, and your apps can poentially contribute to the functions in existing apps. Much of this is done using Android's messaging achritecture, called Intents.

Because of this, I don't see Google utilizing the SageTV plugin system or the Studio application framework.

Studio is basically a programming language defined in Xml. While much of Android is based around Xml, the Xml is mainly for UI work (layout, colors, animations, etc), and not actual logic.

[Fuzzy]

I think what Studio DOES bring isn't the language itself, but the Presentation widgets. The tree based widget system is very good for a configurable UI (where you can easily create many panels, with any combination of items, all completely scalable and scrollable within each panel). This is something that is NOT easy to do with windows forms, and something that just started entering into windows development with the Windows Presentation Foundation (basically a branch of Silverlight).

[stuckless]

Originally Posted by Fuzzy

I think what Studio DOES bring isn't the language itself, but the Presentation widgets. The tree based widget system is very good for a configurable UI (where you can easily create many panels, with any combination of items, all completely scalable and scrollable within each panel). This is something that is NOT easy to do with windows forms, and something that just started entering into windows development with the Windows Presentation Foundation (basically a branch of Silverlight).

True... but again... Android has that already (ie, completely scalable panels), so that's not a reason for Google to want to incorporate Studio or the STV language.