>
> 2) For plugins for which it is suitable, add a pluginlib fallback which
> can provide a minimal set of functionality
>
I thought it would be useful to provide a few examples:
Example 1: cube
The cube plugin currently has one more action than pluginlib provides. Thus
a trivial way to provide fa
Hi All,
I'm sorry to brought up this painful topic once more, but I feel I need
some solution here and some feedback.
The issue is that at the moment I have ports in progress: Fuze+, ZEN, ZEN X-
Fi, ZEN Mozaic, ZEN X-Fi2, ZEN X-Fi3 and NWZ-E360/E370. If you do the math,
removing touchscreen targets
Am 02.12.2013 11:35, schrieb Björn Stenberg:
Thomas Martitz wrote:
Therefore I propose that we relax the typedef rule and allow
typedefs for integral types (only) when reasonable. This would
basically be adopting the Linux kernel guideline w.r.t. to typedefs,
There are times when typedefs are u
Thomas Martitz wrote:
> Therefore I propose that we relax the typedef rule and allow
> typedefs for integral types (only) when reasonable. This would
> basically be adopting the Linux kernel guideline w.r.t. to typedefs,
There are times when typedefs are useful, but they are in fact exceptions. I
Am 02.12.2013 03:16, schrieb Jonathan Gordon:
Sounds pretty cool!
(Possibly a dumb question), Are you only targeting "*as App" type
builds or will this be used on (i.e) ipods with the rockbox core?
App-type builds, in particular as a library with an OS-native (or QT)
UI. I don't have plans
