A good review, thanks. Loïc Minier wrote: > Thanks for your lists! > >> 1 Bronze Level (minimum to be linked from moblin.org) >> 1.1 Build and Install >> 1 Compiles cleanly >> 2 Buildable in target environment with autogen, configure, make >> 4 Contains installable .deb package(s) > > => Replace with "Builds Debian Policy compliants packages with no > more build-deps than those of the dev SDK".
Good. > >> 3 Shows up in UI >> 6 Screenshot available > > So only graphical apps? I can clarify "when applicable" > >> 5 Installs cleanly in target environment > > "Packages install cleanly in..." perhaps > >> 1.2 Hildon Application (Bronze) >> 3 For applications that can be built for Mobile and non-Mobile >> environments, check for LPIA architecture in configure and >> define USE_HILDON flag to use in code for Hildon version. >> <example> I kind of want to group Hildon-related changes in one area, even though it is a build topic. > > I think you should move this to 1.1 and require packages to build > under the lpia architecture. Regardless of grouping, I should require LPIA compat. > > I don't think you should recommend checking for lpia to enable > USE_HILDON. You should just rely on the package build rules to do > the right thing. > > I would only keep "C source code specific to the Hildon libs should > be protected by #ifdef USE_HILDON which should be defined by the > build system". > OK, I like that. >> 4 Register with libosso. <example> >> 5 Create DBUS service file <example> > > Mandatory? For UI apps it is in order to get the application to behave as a singleton. > >> 6 Singleton behavior. Registered with libosso for startup. >> Correctly brings its window to the top when requested. >> <example> > > Having a window is mandatory? I'll add "when appropriate" > >> 7 Have correct .desktop file format and contents <example> > > Might want to refer to the freedesktop standard + required fields. Right.. Actually Hildon is not freedesktop compliant (I don't think). I need to follow up on exactly where they are or aren't and clarify. Thanks for the reminder. > >> 2 UI works on 800x480 and 1024x600 >> 2.a Can read text on both resolutions <suggested font >> sizes> > > Apps should use the system's default font size, no? True. And "readable" is subjective anyway. I can't read the Sony UX screen at default resolution. Perhaps a better wording would be: "Text is displayed at system default size and is not inappropriately or unexpectedly cut off" > >> 2 Silver Level >> 2 Supports the following DBUS / OSSO messages: <list> <example> > > What for?? I was thinking of examples like the browser should support notification to load URL. This comes from an interested App via DBUS msg. We need to look at all the useful dbus / osso messages and make this clearer or remove. > >> 4 Recommended >> - Consistent mechanism to notify apps to go Full Screen >> and non-full screen An example of a dbus message. I believe all apps should listen for the same message to go to/from full screen mode. >> - Xephyr supported by apps Ability to run the application in Xephyr on the desktop. > > What do you mean with these two? > > Thanks! > -- > Loïc Minier Bob -- Ubuntu-mobile mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
