[mythtv-users] MythTV on Android
thomas at mashos.com
Tue Sep 11 04:22:02 UTC 2012
On Mon, Sep 10, 2012 at 7:59 PM, Joseph Fry <joe at thefrys.com> wrote:
>> > Also, the design pattern we
>> > > use aims to minimize network activity (thus saving battery) by
>> > > loading the
>> > > data locally to a database and most interactions with the data are
>> > > through
>> > > the local database. It would be far too slow from a UI/UX standpoint
>> > > to
>> > > always be loading data from the backend on demand, and it would
>> > > drastically
>> > > affect battery.
>> > I'm finding this a bit difficult to believe.
>> > Does any other frontend on any platform work this way?
>> I will jump in here, somewhat to Dan's defense, since I gave him crap
>> in the week about this.
>> If, as he suggests, and I'm not inclined to disbelieve him, the problem
>> is that the server side of this client/server system is not presently
>> optimized to support the query which his use case requires, then yes,
>> I could see why he might decide to take this approach, as pessimal as it
>> Whether other MythTV frontends work this way is only relevant if they are
>> as network constrained as a client on an Android phone might be -- it's
>> reasonable to evaluate this merely, say, in the context of an Android
>> tablet on the same WLAN as the backend.
> Would it be unreasonable for the application to perform a limited query on a
> smaller local dataset, and reach out to the backend for a more powerful
> quer?. For example provide a "search titles" option and have an advanced
> search screen for more indepth searches against the backend DB?
> mythtv-users mailing list
> mythtv-users at mythtv.org
Currently that is not possible. As I've previously stated, the minimum
amount of data you can currently get to display a list of titles is
all data about every episode. There isn't a "list titles" query.
More information about the mythtv-users