profile support

[fsck222]

from discussion on #318

I think we should start to use profiles to separate hardware configurations options from the others. My propositions is described below:

• I call JAJUK_HOME all current files in $HOME/.jajuk/
• As I wrote before, to make it simpler in the future, I believe we should start using profiles (in the same ideas as Mozilla product). This will help to locate or move JAJUK_HOME. The profile name should be configurable in a new $HOME/.jajuk/profile.ini file.

This sounds good, the profiles list can be stored in the .jajuk_bootstrap file. Please create a feature ticket for that.

• I am proposing to call the default profile 'default' hence by default, JAJUK_HOME will be stored in $HOME/.jajuk/default/.
• The new profile file ($HOME/.jajuk/profile.ini) will give for now: the name of the profile, the location of JAJUK_HOME profile and some hardware information specific to the current system such as (sound card conf, mplayer options, etc...). Content example of $HOME/.jajuk/profile.ini below:

  jajuk.profile.name=Default Profile
  jajuk.profile.path=$HOME/.jajuk/default/
  jajuk.player.mplayer_args=
  

I would prefer to keep all parameters in each profile conf.properties file.

• ($HOME/.jajuk/profile.ini file could be also configurable in the configuration menu?)

probably

• In the configuration perspective, if jajuk.profile.path is changed, all the data in the previous jajuk.profile.path must be moved to the new location.

This is very complex to achieve, for the moment, we ask user to move it manually, I think it's enough.

• When starting, Jajuk must look into in jajuk.profile.path, if the path doesn't exist (hence when the user will start Jajuk for the very first time) Jajuk must let the user file-browse his system, create directory, and specify an emplacement to store his profile. By default Jajuk should propose: $HOME/.jajuk/default/.

already implemented but without profiles