From kde-edu  Wed Oct 31 21:19:06 2007
From: Ljubomir Simin <ljubomir.simin () gmail ! com>
Date: Wed, 31 Oct 2007 21:19:06 +0000
To: kde-edu
Subject: Re: [kde-edu]: kamion migration and backup tool
Message-Id: <200710312219.06420.ljubomir.simin () gmail ! com>
X-MARC-Message: https://marc.info/?l=kde-edu&m=119386782518342
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--Boundary-00=_KFPKHJpvaKUl3J6"

--Boundary-00=_KFPKHJpvaKUl3J6
Content-Type: text/plain;
  charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 31 October 2007 22:09, Ljubomir Simin wrote:
> Hi KDE Edu developers,
>
>
> I'm Ljubomir Simin, from the Kamion project [1]. Kamion ("Truck" in
> Serbian language) is the (user friendly) migration tool, which allows to
> move and backup application data and settings. It was started by Ivan
> =C8uki=E6, the author of yet to be released Lancelot launcher, and now has
> gathered the new development team.
>
> Our tool is in functioning shape, and we are looking for application
> developers willing to try us out.
>
> The idea is simple: the 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 dat=
a.
> Nothing more besides recipe is required from application developers.
> Users uses Kamion GUI tool to easily backup and restore their settings.
>
> In case of KDE Edu, it could migrate settings, data files (vocabularies,
> logo files, maps, downloaded hotnewstuff), etc.
>
> Kamion is written in Qt4 with KDE4 in mind, but
> there are some efforts aiming for desktop independence in the future.
>
> If you think the idea behind our project is valuable, please try it out a=
nd
> tell us your needs, comments and propositions. We would like to implement
> any feature needed to satisfy the application developers. In case you're
> wondering, our future plans include:
>
> * 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 impo=
rt
> 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.
>
>
> As our website is a bit sparse in details, I'm attaching a sample recipe
> for Kopete, and a XSD of the recipe format.
>
> Hope to hear you soon,
>
>
> Ljubomir Simin
>
>
> [1] http://kamion2.sourceforge.net/
>
>
> PS. I'm not subscribed to this mailing list, so please CC any replies to
> me. Thanks.

=46orgot to actually attach the files, sorry :(

=2D-=20
Ljubomir Simin=20
Registered Linux User #351181

--Boundary-00=_KFPKHJpvaKUl3J6
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=_KFPKHJpvaKUl3J6
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=_KFPKHJpvaKUl3J6
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kde-edu mailing list
kde-edu@mail.kde.org
https://mail.kde.org/mailman/listinfo/kde-edu

--Boundary-00=_KFPKHJpvaKUl3J6--