On Wed, Sep 21, 2011 at 12:42 AM, Sébastien Huss sebastien.huss@gmail.com wrote:
Hi there, If we only want to inform the users before hand, then why indroducing yet others fields (that dev have to take care of, front-ends too ; what about these ~400 already exisint PNDs) when the current one could be used. The package description could already include that. I think the issue is more that, like pickle said, most dev are lazy on the instructions side (at least I do too).
Well the idea is if there was a field to enter requirements, maybe it would encourage people to actually use it. Right now when you make a pnd you do: - see author element - fill it in - see titles element - fill it in - see descriptions - fill it in ... done.
the system doesn't even offer you to specify requirements, and you don't do it. If there was such a field, chances are you would fill it in. Descriptions don't really ask a question "what does your app require?".
And I'm not talking about super magic dependency resolver or library checker - just a free text form field for emulators, quake-like games that need data files and the likes. This is just to save the user from having to parse the readme for this info.
Expanding <descriptions> for this would be fine for me.
Maybe, we need to communicate more to the devs on "how to package your apps/games in a PND cleanly"
Maybe someone could code a web-based PXML generator? Basically you fill a form of several fields and it spits out valid PXML? I think it would be quick and useful project someone like Milkshake could take.