As you probably noticed, until now we did not get into any way to actually operate on the l10n objects outside of memory. At this point you should know how to create an Entity, Comment, how to create an EntityList, L10nObject and L10nPackage, traverse, join and search and bundle it all together.
Now we'll focus on the ways you can use to load/save those objects to actually be able to use the system in the real life.
There are two levels of this operations. First one is an actual loading entities from somewhere to internal structure like EntityList, L10nObject or L10nPackage and saving it to some place. This is covered by silme.io family.
silme.io is a package that contains everything needed to read and write from different sources including - file system, databases and revision control systems.
Each separate class that manages reading and writing is called a Client. There are several abstract clients bundled in silme.io.clients that are bases for all other clients. For example there is IOClient, DBCLient and RCSClient which are bases for FileClient, MysqlClient, SVNClient respectively.
The clients are managed by silme.io.Manager which can register and select best client for us.
IOClient is an abstract class that is a base for every I/O client that can read and write objects. For example a FileClient can read a file into memory and write it back to the hard drive. Or it can load directory as L10nPackage. SvnClient can load L10nPackage from the directory in SVN repository, JarClient can load a *.jar file as L10nPackage and SQLiteClient can read tables as L10nObjects.
silme.io.Manager has 3 important methods:
- register() - allows you to register clients in a form: silme.io.Manager.register('file', 'jar', 'mysql')
- register_all() - registers all clients it will find in its path
- get(name=) - allows you to get client (if it's not loaded and Manager will find it, it'll load it automatically)
- get(path=) - will test each registered client to check if it supports this kind of path and return first that does
In the simple case you just use IOManager to load a proper IOClient and then interact with selected type of IO. For example:
ioclient = silme.io.Manager.get('file') # you can you other types here like: jar, sqlite, mysql, svn
l10npackage = ioclient.get_l10npackage(path='./test/')
l10nobject = ioclient.get_l10nobject(path='./test/example.dtd')
- Manager fires client.matches_path(path) on each client and returns the one which will return True first
ioclient2 = silme.io.Manager.get(path='./data/test.jar')
l10npackage2 = ioclient2.get_l10npackage(path='./test.jar')
In result we have two L10nPackages, one from the directory on the hard drive, and another extracted from the .jar file. Also, we have an L10nObject from the hard drive.
To write down an L10nObject or L10nPackage you simply use the same IOClient:
ioclient = IOManager.get('file')
IOClient lets you read and write between the objects in the memory of the program and an actual storage of the data. It may be a database, hard drive, zip package or an RCS.
It's getting exciting!
Thanks to what we already know we can now (almost) load an L10nObject, modify it an save back to the file:
file = './test/example.dtd'
ioclient = silme.io.Manager.get('file')
l10nobject = ioclient.get_l10nobject(path=file)
l10nobject.modify_entity('entity.id', u'new value')
This is a very convenient way to work with L10nObjects. You can of course easily operate on all elements of nested L10nPackage structure, modify entities inside, move them around and then save the whole package somewhere.
It's important to remember that different kinds of IOClient will give different results. For example SQLClients will not be able to produce full L10nObject and they will serve EntityLists instead.
The reason is that L10nObject is in fact EntityList with a textual context, while SQL does not have any context beside of table rows that represent data.
In most situations you will want to extend the generic SQLClient to suite it to your database structure. You may want to store each locale as a separate column in one table or as a separate table.
In case of RCSCLients their nature requires a user to slightly change the way he operates with the data.
First, while loading L10nObject or L10nPackage, you can select revision from which you want the data to be.
Second, when you save the data, you have to decide how you want the changes to be saves. Should there be a commit on every single change or would you like to offer a user a dynamic sandbox with his changes that are commited once in a while.
In the next chapter we will get a better understanding on what actually happens during read and write of the object and how silme knows which format to use.