Application Database

It is imperitive for the continued user acceptance of wine to have an upto date, concise software catalogue which can be accessed and edited by the wine community, new users as well as existing users. The current wine application database has some notable features which users will be reluctant to lose, however there are other more advanced features which the application database lacks.

A way of integrating the features of wine-doors and the features of the application database needs to be investigated. Currently some ideas are in existence but without accurately developed standards for managing applications its still floating around.

If for instance we use the following url request to retrieve packlists there isn't a great deal of complication involved as this is mostly already dealt with as part of the application database.

http://appdb.winehq.org/wine-doors.php?file=available.packlist.xml

There are also requirements for retrieving individual application packs, this becomes slightly more difficult as an application pack consists of a number of inclusive files like icons, scripts and various other supporting components and therefore must be transmitted to the user in a tarball format. One method of doing this would be as follows;

http://appdb.winehq.org/wine-doors.php?app=Application%20Name&version=2&file=appname.tar.gz

These ideas are only preliminary suggestions and must be clarified before the repository support for wine doors can be implemented.

Rough todo list

• User interface styles
• click n' run style wine-doors integration from a web browser! .wdi file (tar.gz renamed)
• ApplicationPackDesigner, wiki script editing, repo updating.
• screen shots, icons, groupings, ratings etc...

Repository building

• The individual xml files can be created by php scripts
• A cache should be stored