Hi Al, The PAD file system may not be ideal, but it is the one and only format that is already widely used. Information about device and/or functionality support is indeed mostly left to the application developer's web page, for which an Info/Order URL can be used in the PAD file. Actually, as an application developer with experience in Java ME development, I can say that I often simply do not know - except from user feedback - on which phones my Java MIDlet properly runs, so I would not desire to have this information in my PAD file, and I would not be able to keep it up to date anyway as new Java ME camera phones come out by the week or so. Some functionality info can be put in the various PAD file description fields (up to 2000 characters for the long description).
Moreover, nothing prevents you from putting additional information, for instance about device compatibility, on your Android download/ distribution site, either based on application developer input (if available), or user feedback, or automated compatibility testing. Websites like http://www.getjar.com do this to some extent. > P.S. Where is their DTD/XML Schema?, I've seen their propriatary > XML-based spec description language, the web page with the spec in it, > and the on-line validator, but it seems there isn't an DTD or schema to > help people construct PADs. I'm not sure what you mean. As an application developer you are not bothered by the XML syntax, and just fill in the fields in the PADGen tool available from http://www.asp-shareware.org/pad/padgen.php - from this, PADGen automatically generates the XML file with the proper syntax, making construction of the PAD file really easy to use for developers. Regards On Nov 13, 7:11 pm, Al Sutton <[EMAIL PROTECTED]> wrote: > When I looked at supporting it in AndAppStore one of the first things > that hit me was the inability to provide device and/or functionality > support information. > > There may be devices in the future that don't support a keyboard,touch > screen,GPS, and/or some other feature, and without the ability to > specify a feature set of supported device list it could be a frustrating > user experience when more devices are available. > > I'm not ruling out PAD support, and I'll happily arrange for it to be > added in to AndAppStore if it becomes popular, but I think that at the > moment it's not ideally suited to android apps. > > Al. > > P.S. Where is their DTD/XML Schema?, I've seen their propriatary > XML-based spec description language, the web page with the spec in it, > and the on-line validator, but it seems there isn't an DTD or schema to > help people construct PADs. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
