#MEDIAPORTAL CLIENT ANDROID MANUAL#
#MEDIAPORTAL CLIENT ANDROID ANDROID#
#MEDIAPORTAL CLIENT ANDROID CODE#

We used technologies like Drupal and Bootstrap to ensure that the content creators and the users would get the best experience both on desktop and mobile devices, as the portal was made responsive and compatible for all devices. ).The des team wanted to use the open-source Drupal platform, since it facilitates the building of amazing digital experiences and is more convenient and affordable than other solutions that the market has to offer. detail screens for programs/schedules/recordings, more actions for items, downloading of recordings to device, playback on client.

#MEDIAPORTAL CLIENT ANDROID ANDROID#

The only problem is that this needs a complete custom view since using standard android layouts for this is too much of a performance hog (I tried ).Īnd of course many small improvements for the existing screens (e.g. The goal is to implement a view like the one from kiwijunglists mockups (see ): Still on the todo list is mainly the epg view. Schedules: Show all schedules, delete schedules.Channels: Show all groups/channels, show epg for channels, record programs from epg.

#MEDIAPORTAL CLIENT ANDROID MANUAL#

Manual control (Show active timeshifts, start/stop timeshifting).

Hi, I've started with the implementation of the tvserver functionality (provided by tv4home) in ampdroid and it's progressing quite nicely. You can find the thread for aMPdroid 0.6 in this thread.

Showing the tvserver section of ampdroid.

#MEDIAPORTAL CLIENT ANDROID CODE#

The current source code and issue tracker can be found on the project page. Keep in mind that project is still in a very early stage and much of the work has been made on the parts you don't see (background services, architecture.

The bottombar has buttons to control the currently active client (play/pause/prev/next/volume/.) and a slider that can be dragged up to display information on the currently running item. Long-pressing on a media item for example shows a menu for downloading the file to the sd card.

Long-clicking on an item will open a context menu with actions related to this icon. It also has a textual description of the current screen and buttons for a) changing the client and b) accessing the application search. Instead of the (old) standard android title bar this new titlebar includes a home button that will bring you back to the homescreen from any screen within the app. So if anyone wants to help out with gfx, it would be highly appreciated. still wip and open for discussion, also the icons aren't what I want (same goes for actionbar) but as you can see I'm not really a graphics guy. Currently this links to the following sections The central entry point with links to all essential parts of the application. The app will use a couple of 'new' android ui patterns that have been introduced on the google i/o 2010 ( YouTube - Google I/O 2010 - Android UI design patterns): Each client consists of an tv api (tv4home), a media access api (gma) and a client control api (!?! tbd). The idea of the app is that the user can define multiple virtual clients. Also there will be a part to control MediaPortal clients through a plugin, but it is at this point not clear which plugin will be used / if a new one has to be written. This one is called aMPdroid and makes use of the upcoming webservices for MediaPortal, Tv4Home and GMA (General Media Access). As you might know there is not one, but two android projects for MediaPortal in the making.

Mediaportal client android