Association Subscribers Manager and Open source stuffs

To content | To menu | To search

Tag - documentation

Entries feed - Comments feed

Wednesday 19 August 2009

New video tutorial and new YouTube group !

Hi !

Back from my holidays I resumed works on Association Subscribers Manager : 

  • Here is the new (English) video tutorial which covers the presentation of the Federation Editor (watch on You Tube).

  • And here is the new You Tube group that I created to promote Association Subscribers Manager (See on You Tube).

About the code, I have made some patches to fix little issues in the 3.0 version (like a re-translation bug for example), I need to backport them and hunt for some more bugs and I'll release a bugfix version (3.0.1) of Association Subscribers Manager.
See you later !
Arnaud Dupuis

Friday 6 March 2009

Association Subscribers Manager is on the road of being fully documented.

Hi,

in the development process one thing is very important : the documentation. And Assuma lakes one very important thing: documentation !

But fortunatly this problem is about to be solved ! Starting with the revision 119 I will change this and documents all public methods/slots of the Association Subscribers Manager API. At this point of the project, documentation is really importante since I plan on openning the source code to external contributions. Moreover the upcomming plugin system will also need an excellent documentation if I want people to develop plugins for Association Subscribers Manager ;-).

Arnaud Dupuis

PS: I am almost done with the super-ultra-absolute-comprehensive-howto-install-cutting-edge-Slackware-Linux-on-EeePC !

Sunday 7 September 2008

slack-get feature highlights #3 : add FTP credentials to your medias.xml configuration file.

Hi,
Today, I will highlights a brand new mechanism in slack-get : how to add your FTP credentials to the medias.xml confniguration file.
First let's remind how was the ftp authentification mechanism before.
In the old ages, you had to fill a section in the config.xml file. The section look like that :
<network-parameters>
     <ftp>
          <login><![CDATA[anonymous]]></login>
          <password><![CDATA[slack-get@infinityperl.org]]></password>
     </ftp>
</network-parameters>

This section (in the <common> configuration bloc) is (still) used by the sg_daemon to authenticate himself on FTP server (this is the global credentials).
But you may have to provide particular credentials for one ftp server, so I added the possibility to use the standard URL syntax in the medias.xml file.
So starting from the svn revision 198, you can use the ftp://<login>:<password>@<some ftp server> syntax in your medias.xml file.
The specific credentials, of course, prevails on the globals ones.

On a developper side now, this trick is done by the Slackware::Slackget::Network::Connection->parse_url() method. This is a specific case of the ftp so far but I can easily make it available for any protocols if there is a need to do so.
I plan on testing, in this parse_url() method, the availability of a __parse_url() method drivers' specific. This could help to develop specific drivers with specific url format.
I will think about that.

That's all for today ! Enjoy the end of the week end !

Arnaud Dupuis

Saturday 6 September 2008

slack-get Perl api available (again)

Hi,
The Slackware::Slackget api is available on CPAN, but the latest documenation is now available in the SVN tree (viewable on Sourceforge's viewsvn service) and on my own server.
The two last ones will be more up-to-date than the CPAN one.

I hope that it will helps contributors !

Arnaud Dupuis.

Saturday 2 February 2008

SGNCC - Slack-Get Naming Convention Compliant : the new slack-get's naming convention document

Document purpose :

The purpose of this document is to "standardize" slack-get development by imposing a naming convention for both (but not only) : slack-get clients, sg_daemon, all Perl modules and the C++ library.
This include of course, all plug-in which can be released in the futur.

Vocabulary :

In the future, we will refers to the slack-get naming convention as :
SGNC: for Slack-Get Naming Convention.

Additionally, we will refers to SGNC compliant code as SGNCC (SGNC Compliant).

Scope of the SGNC :

All the code released under the "slack-get development team" label must be SGNC compliant (SGNCC).
More generally, all code released and packaged with slack-get must be (and will be) SGNCC.
The SGNC apply to all API visible method names. Every methods in a class or bundle must be SGNCC. By extension to this principle all methods in the sg_daemon, slack-get and the upcoming slack-get GUI have to be SGNCC.
All script released and packaged with slack-get should be SGNCC too. But in order to not slow down some developments it is acceptable to keep not SGNCC code in the branch/ SVN tree. If released with slack-get, this code will be optional at building and installation time. It will also be released in a different package.

Rules of SGNC :

We refer to functions and methods as the same generic term of "method".
The SGNC consist in the following 3 simple programing rules :
  1. a method name consist of lower case, English words where space are replaced with underscores ;
  2. if the method name is conflicting with Perl or C++ built-in function or language syntax, change the case of the first letter to upper  case.
  3. if a conflict was solved according to rule 2), and if the name conflicts with only one of the supported languages (Perl and C++), add a wrapper method around the renamed one, in order to comply with the rule 1).


The slack-get development team