Thread: Integration Re-Defined

.... using a standardized graphics engine. .... through standardized interfaces,

Out of curiosity, what do you define as standardized? You mean GUI items are all generated by the frontend rather than individual plugins so everything looks the same, and all plugins communicate with each other in the same way?

Originally Posted by malcom2073

Out of curiosity, what do you define as standardized? You mean GUI items are all generated by the frontend rather than individual plugins so everything looks the same, and all plugins communicate with each other in the same way?

Well generated by the plugins, drawn by the graphics engine but yea. That part isn't exactly novel..same thing as done by centrafuse and revfe if I remember correctly. This was more about the integration rather then just embedding aspect.

Originally Posted by justchat_1

This was more about the integration rather then just embedding aspect.

Please elaborate. If you're going to make the claim that you're the first frontend to do something, expect to be interrogated (in a friendly manner of course) about it :-P

That, and if you've genuinely found a better way to do something I'm all ears

Originally Posted by malcom2073

Please elaborate. If you're going to make the claim that you're the first frontend to do something, expect to be interrogated (in a friendly manner of course) about it :-P

That, and if you've genuinely found a better way to do something I'm all ears

Well I said its a push towards the first...not that we're there yet.

But fair enough i'd be happy to elaborate.... traditionally front ends are a loose glue holding together a variety of programs not really designed for how they're being used (linking to windows media player, embedding internet explorer or GMPC for example). This type of integration i call loose integration...buttons launch the things you expect but its not true integration.

The videos above are various ways we're working to change that traditional "cut and paste" approach. Garmin Mobile PC is fully integrated as a navigation plugin, no borders or original buttons. The location from the GPS (translated to a physical location by GMPC) is used by the web browsers geolocation services. The web browser itself is designed specifically for in vehicle use. Asking for directions or dialing a number tie into navigation and bluetooth respectively (just like they would on a smartphone). Even the browser itself is designed for touchscreen use (touch screen compatible web pages are used when available). I'm currently working on tieing youtube videos into the existing media framework so that youtube playback is identical to other videos or DVDs. The whole idea being that all the plugins are communicating, using the full power of the framework to deliver a consistent easy to use experience to the end user.

Originally Posted by justchat_1

Well I said its a push towards the first...not that we're there yet.

But fair enough i'd be happy to elaborate.... traditionally front ends are a loose glue holding together a variety of programs not really designed for how they're being used (linking to windows media player, embedding internet explorer or GMPC for example). This type of integration i call loose integration...buttons launch the things you expect but its not true integration.

The videos above are various ways we're working to change that traditional "cut and paste" approach. Garmin Mobile PC is fully integrated as a navigation plugin, no borders or original buttons. The location from the GPS (translated to a physical location by GMPC) is used by the web browsers geolocation services. The web browser itself is designed specifically for in vehicle use. Asking for directions or dialing a number tie into navigation and bluetooth respectively (just like they would on a smartphone). Even the browser itself is designed for touchscreen use (touch screen compatible web pages are used when available). I'm currently working on tieing youtube videos into the existing media framework so that youtube playback is identical to other videos or DVDs. The whole idea being that all the plugins are communicating, using the full power of the framework to deliver a consistent easy to use experience to the end user.

So you're saying that you're adding in features that most people use external applications for. Cool.

I assume most everything you're talking about would be cross platform? Do you have plans for integrating Navit in linux?

Originally Posted by malcom2073

So you're saying that you're adding in features that most people use external applications for. Cool.

Well a little more then that.... were adding in features that aren't possible when using separate applications (Like using GMPC for geolocation in a web browser or entering addresses using speech or gestures).

Originally Posted by malcom2073

I assume most everything you're talking about would be cross platform? Do you have plans for integrating Navit in linux?

Well the same techniques work on all platforms yea...but the web browser for example needs to be compiled on each platform so that will take a little work to get right and GMPC is windows only. Navit should be pretty easy to do once its mature enough.

Well lets just say it's the first front end that supports a plugin for nearly seamless integration of Garmin Navigation for Windows users. And if you ask me, GMPC is the most reliable navigation software out there for laptops. It has its issues, but it does navigate well, and looks good doing it! So essentially by version 0.7, it looks like OpenMobile will have a completely integrated solution between Speech Recognition, Gestures, Navigation, and its other elements. Not to mention pending plans for bluetooth phone integration in a later release. Sounds like a winner to me!

Oh and GMPC runs in WINE on linux. Not sure if that could be of use.

The integration between the browser and OM is really cool! It sure opens up for a much better user experience. Forget poi updates.... google is way better at that!

Offtopic: is GMPC locked against a gps from garmin or can it use any usb gps?

What I would like to see if a single location to configure and modify the core FE, add-ins, skins, etc... in a single location. To me, it would make sense if all the configuration was done in a single location and let the FE handle it, instead of letting each plugin handle their own customizations.

How this could be handled is by each plugin/app using 2x XML files. The first XML file is the settings.xml file where the plugin app reads its configured settings. The second XML file is for the FE to read and to show the user what to configure.

To show an example, lets use an audio player plugin. The first XML file would be the configure XML file and it would have things like default music directory, color and skinning info, and what to play on first load up.

The second XML file would be for the FE. The default music directory would be a browse button + label to show path. The color choices could be radio buttons, check boxes, list box.... etc.

<configureform name="defaultpath" type="browse" text="browse" />

<configureform name="defaultcolor" type="radio" text="Choose your color scheme:">
<option text="blue" value="blue">
<option text="red" value="red">
<option text="green" value="green">
</configureform>

Whats great about this approach is that plugin devs can now offer more customization options using this. Also, the XML files do not need to specify X/Y values for the form elements as the FE will automatically format and parse the form elements and make it suitable for whatever sized screen.

What do you think? I have yet to see a FE take this approach. And since you yourself have used Joomla CME, I think you know what I mean about seperating the plugin like this.