If you have a device and you want know the capabilities, you use wurfl.xml. If you have am application and you want to know on which devices the app runs, you will use wurfler.
Feature which are implemented and working
This section describes the search capabilities of the server. The following REST interfaces gives you the possibility to query the wurfl file by :
get device by id get device by user agent
get brand by name get all brands
get devices by capabilities
get the list of new/changed devices since a given timestamp
import of devices
the initial upload of a wurfl file
the partial upload of devices handled by a wurfl_patch file._
notifictian of changed devices
Every time you add or change existing devices, wurfler will notice these changes and will do the following things for you.
Feature which will be implemented in the near future
The features which are listed below will be implemented in the future
export of devices
Wurfler will be able to export the existing data in a wurfl file. That means, that someone can easily change the data and than she can export the list for using elsewhere
export of deleted devices
Wurfler will be able to export deleted devices. Every time someone deletes a device, wurfler will create a wurlf_patch file for this device.
First you have to run install.sh which creates the schema and the db tables.
To import data you have to follow these steps:
In the directory test there is a wurfl-2.0.25.xml file. Please, rename it and copy this file in the directory wurfl. Everything else will be done by the system. If this is not available, you have to create it.Normaly, it will be created using the install.sh script.
To insert new data or to modify existing data you have to use the wurfl_patch.xml. After creating a wurfl_patch.xml file you can copy this in the wurfl_patch directory. Everything else will be done by the system.
Before running the following line you have to modify the cover.spec and test.spec. Inside these files you have to specify your own absolute path. Later i will build a script which will do the work for you. In the cover.spec you also have to specify the name of your node. Note: If ct_run is not in the PATH you have to create the link. In /usr/local/bin : sudo ln -s ../lib/erlang/bin/ct_run ct_run
Then you can run :
ct_run -spec test/test.spec -pa deps/*/ebin/ ./ebin
To start the server
ct_run -vts -spec test/test.spec -pa deps/*/ebin/ ./ebin -dir test