From amarok-devel  Sat Oct 06 22:59:24 2007
From: Ljubomir Simin <ljubomir.simin () gmail ! com>
Date: Sat, 06 Oct 2007 22:59:24 +0000
To: amarok-devel
Subject: Kamion migration and backup tool
Message-Id: <200710070059.25070.ljubomir.simin () gmail ! com>
X-MARC-Message: https://marc.info/?l=amarok-devel&m=119171161426373
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--Boundary-00=_NNBCHDOZ7o8nyCr"

--Boundary-00=_NNBCHDOZ7o8nyCr
Content-Type: text/plain;
  charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi again,

I'm not sure if I'm supposed to post about non-core issues here, or rather on 
amarok@kde.org. I'll move the discussion there if necessary.

I've recently decided to help the Kamion project [1]. Kamion ("Truck" in 
Serbian language) is the (user friendly) migration tool, it allows to move 
and backup application data and settings. 

The idea is simple: application developers provide simple "recipes" - XML 
files which defines resources to be archived. Different kind of resources can 
be defined in one recipe, like application settings and data. Nothing more 
besides recipe is required from application developers. 
Users uses Kamion GUI tool to easily backup and restore their settings.

Personally, I think that the idea is great, and provides a valuable tool for 
both users and developers. Kamion is written in Qt4 with KDE4 in mind, but 
there are some efforts aiming for desktop independence in the future. It 
could be THE desktop migration tool for the KDE and other apps/desktops.

Kamion is in usable state, but we need feedback from application developers. 
Comments and ideas are highly appreciated, please tell us your needs. Some 
future plans includes:


* unification for different applications to export same 
data - for example to provide some standard for email programs - how to 
format it's resources so that you could pack the data from KMail and import 
into thunderbird on another installation.

* Scripting - optional pre-packing and post-extracting shell scripts - so that 
they could filter unnecessary data or something.

* Changeable file locations for resources - the developers would be able to 
tell Kamion to search for the file location inside another file (for example 
inside a config file)

* Dynamic resources - so that different accounts in mail programs appear under 
different resources, and not in one common - mail messages.


I really believe in this project, and would love to have you guys support it, 
as it will surely ease the further adoption.

PS. As our website is a bit sparse in details, I'm attaching a sample recipe 
for kopete, and a XSD of the recipe format.

[1] http://kamion2.sourceforge.net/
-- 
Ljubomir Simin 
Registered Linux User #351181
http://counter.li.org

--Boundary-00=_NNBCHDOZ7o8nyCr
Content-Type: application/xsd;
  name="appdata.xsd"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="appdata.xsd"

<?xml version="1.0" encoding="UTF-8"?>

<!--
    Document   : appdata.xsd
    Created on : 2 March 2007, 20:03
    Author     : ivan
    Description:
        XML Schema definition for the Kamion Application Data XML Format
-->

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">

  <xsd:annotation>
    <xsd:documentation xml:lang="en">
      Kamion Application Data XML File Format Spec
    </xsd:documentation>
  </xsd:annotation>
  
  <!--- Root element -->
  <xsd:element name="kamion" type="KamionDatabaseType" />
  
  <xsd:complexType name="KamionDatabaseType">
    <xsd:sequence>
      <xsd:element name="applications" type="ApplicationListType" />
      <xsd:element name="categories" type="CategoryListType" />
    </xsd:sequence>
    <xsd:attribute name="version" type="xsd:decimal" use="required" />
  </xsd:complexType>
  
  <xsd:complexType name="ApplicationListType">
    <xsd:sequence>
      <xsd:element name="application" type="ApplicationType" minOccurs="1" maxOccurs="unbounded" />
    </xsd:sequence>
  </xsd:complexType>
  
  <!--- Data for each application
    id - the unique id of the application - recommended to be the name of the 
      executable. If the Kamion Application Data XML Format file contains only
      one application, the file should be named <application id>.xml
      The same goes for the localization file <application id>.i18n
    existanceTestFile - file to test whether the application had been started
      by the user.
    name and description should be in English language
    icon - not the full path, just the name of the icon
  -->
  <xsd:complexType name="ApplicationType">
    <xsd:sequence>
      <xsd:element name="resource" type="ResourceType" minOccurs="1" maxOccurs="unbounded" />
    </xsd:sequence>
    <xsd:attribute name="id"                type="xsd:string" use="required" />
    <xsd:attribute name="name"              type="xsd:string" use="required" />
    <xsd:attribute name="icon"              type="xsd:string" use="required" />
    <xsd:attribute name="description"       type="xsd:string" use="required" />
    <xsd:attribute name="existanceTestFile" type="xsd:string" use="required" />
    <xsd:attribute name="version"           type="ApplicationVersionType" use="required" />
  </xsd:complexType>
  
  <!--- Data for each application resource
    id - unique id for the resource - recommended to be in 
      <application id>.<resource id> format
    prefix - the path to the parent directory of all files in this resource
      (the files in a resource don't need to be in the same folder - prefix
      is the prefix of all folders in which the files of this specific resource
      reside)
    name and description in English language
  -->
  <xsd:complexType name="ResourceType">
    <xsd:sequence>
      <xsd:element name="file" type="xsd:string" minOccurs="1" maxOccurs="unbounded" />
    </xsd:sequence>
    <xsd:attribute name="id"                type="xsd:string" use="required" />
    <xsd:attribute name="name"              type="xsd:string" use="required" />
    <xsd:attribute name="prefix"            type="xsd:string" use="required" />
    <xsd:attribute name="description"       type="xsd:string" use="required" />
  </xsd:complexType>

  <!--- Category
    List of application IDs in <application>...</application> tags
    id attribute - one of the following
      web.browser, web.messaging, web.email, ... (not yet decided)
  -->
  <xsd:complexType name="CategoryListType">
    <xsd:sequence>
      <xsd:element name="application" type="xsd:string" minOccurs="0" maxOccurs="unbounded" />
    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:string" use="required" />
  </xsd:complexType>
  
  <xsd:simpleType name="ApplicationVersionType">
    <xsd:restriction base="xsd:string">
      <xsd:pattern value="\d+\.\d+(\.\d+)?" />
    </xsd:restriction>
  </xsd:simpleType>
  

</xsd:schema>

--Boundary-00=_NNBCHDOZ7o8nyCr
Content-Type: text/xml;
  charset="iso-8859-2";
  name="kopete.xml"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="kopete.xml"

<?xml version="1.0" encoding="UTF-8"?>

<!--
    Document   : kopete.xml
    Created on : 2 March 2007, 21:14
    Author     : ivan
    Description:
        Kamion application data for Kopete
-->

<kamion version="1" xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
  xsi:noNamespaceSchemaLocation='file:/home/ivan/Projects/KamionXML/src/xml/appdata.xsd'>
  <applications>
    <application
      id="kopete"
      name="Kopete"
      icon="kopete"
      description="IM Program"
      existanceTestFile="$HOME/.kde/share/config/kopeterc"
      version="0.12.4"
    >
      <resource
        id="kopete.config"
        name="Configuration Files"
        prefix="$HOME/.kde/share/config/"
        description="Kate configuration files"
      >
        <file>kopeterc*</file>
      </resource>
      <resource
        id="kopete.data"
        name="Contacts, Themes, Images..."
        prefix="$HOME/.kde/share/apps/kopete/"
        description="Contacts, Themes, Images..."
      >
        <file>*</file>
      </resource>
      <resource
        id="kopete.history"
        name="Chat History"
        prefix="$HOME/.kde/share/apps/kopete_history/"
        description="Chat History"
      >
        <file>*</file>
      </resource>
      
    </application>
  </applications>
  <categories id="web.messaging">
    <application>kopete</application>
  </categories>
    
</kamion>

--Boundary-00=_NNBCHDOZ7o8nyCr
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Amarok-devel mailing list
Amarok-devel@kde.org
https://mail.kde.org/mailman/listinfo/amarok-devel

--Boundary-00=_NNBCHDOZ7o8nyCr--