The main mew features are:

• Idle time is caught: In this version if you’re inactive during more than 5 minutes this inactivity time isn’t assigned to any and it’s stored as IDLE.
• GTK-Doc reference: Now source code it’s properly commented to generate the reference using GKT-Doc.

Furthermore we’ve recorded a demonstration video that you can download at MyTime homepage.

As you can guess I’m going to use this blog to post some comments about exercises, practices, examples or whatever interesting thing related with this master (you can take this post as the first example).

In the next paragraphs I’ll try to sum up my relation with free software from my first contact to nowadays trying to answer some question of the subject Introduction to Libre Software.

My first use of free software could be the use of Netscape as web browser before enter University (more or less between 1999 and 2001), however at that moment I only know that I didn’t have to pay and it worked better than Internet Explorer nothing related with free software.

When I started my degree on Computer Science at University (2001) I had my first contact with free software because there was Linux installed on University computers (it wasn’t the default OS but it was installed), the distribution was a Red Hat 6 and I installed it in my home with some problems: printer and modem internet connection didn’t work. This year I’ve also my first contact with Emacs without success.

During the years at University and after that I tested a few distributions:

• Red Hat: The first contact and a good first step.
• Fedora: The evolution of Red Hat and my distribution for some years.
• Ubuntu: My default distribution since 2005.
• Open Suse: Nothing special to highlight only a test.

From last years at University I’ve been a free software user but only as end user moreover I’ve tried to spread the use of free software applications, among other: Firefox, OpenOffice.org, Eclipse, …

After join Igalia I’ve started to collaborate in some free software projects mainly related with TYPO3 a content management system written in PHP.

Finally I can say that free software has evolved since my first contacts and today it’s more than ready to be used by anyone. Maybe in a few years the main applications in any field would be free software, we should push for it.

I decided to go to the next talks:

• Hitchhiker’s Guide to TYPO3 v5: This was a talk to summarize the work done during the last year on FLOW3 and TYPO3 v5 projects. There were some things repeated from the tutorial and he mainly talked about persistence and REST services, every operation that could be done in TYPO3 backend will use web services. A good presentation with videos and so on, I liked it.
• Continuous Integration for FLOW3: A good talk about Continuous Integration in TYPO3, it works really nice perfectly integrated on TYPO3 forge running all tests in 3 platforms (Mac, Linux and Windows). It uses Hudson, and he explained about how to use it for particular projects.
• Intelligent web forms: As a Formidable collaborator I can miss the only talk about forms in the conference. They talked about the extension FormMaker that allows to manage forms from backend. Something interesting is that it allows to define some steps in a form, dividing it in several pages defining a workflow; they manage it with sessions and it has a drawback because you couldn’t have two forms with different data in two browser tabs. It seems a very powerful extension, maybe quite complex in the beginning but I should test it to give my opinion about it.
• Transparent Object Persistence with FLOW3: Karsten started talking about DDD (Domain Driven Design) and explain the different concepts of that approach: repository, aggregate, entity and value. This is the base of FLOW3 persistence framework that defines a Content Repository in which objects are stored automatically. A good point of this repository is that you can mount a relation data base and use it as an object with the API of the repository. There is a tool called TYPO3 CR Admin quite useful to see the stored date.

Finally I didn’t attend to the Best paper award event because the “Spanish” people (Nivel Siete, ICTI and Igalia people) went for a walk to get an overview of Berlin. We took the underground till Alexander Platz and we returned walking to the hotel seeing a lot of monuments.

In this TYPO3 conference I tried to catch as much information as possible about FLOW3 and TYPO3 v5 and these talks refreshing my concepts about Software Engineering (AOP, DDD, TDD, …). Furthermore they recommend a lot of books about Software Engineering you can see the further reading section at FLOW3 website. My conclusion about these projects could be that there’re a lot of things to do and one of them is improve the performance, if they get it FLOW3 will be a great framework and TYPO3 will have a great source code.

Congratulations to the organization of this great conference and also to Igalia for let me live that great experience.

The day started with the Keynote by Kasper, it was shorter than I expected but quite amusing. The next year will be a TYPO3 Conference in Dallas (USA) but it should not replace to the conference in Europe, it means that TYPO3 community is growing and it’s good.

After the Keynote I went to the next talks:

• DEV3 - TYPO3 Enterprise Development: DEV3 is an Eclipse plugin to work with TYPO3 4, FLOW3 and TYPO3 5. It has a TeplateView that allows to users to modify TypoScript from Eclipse, users can edit constants and setup sections, moreover it has syntax highlighting, syntax checking, auto-completion, … for TYPO3, FLOW3 and TypoScript (mental note: “I have to test this plugin”).
• CSC2: Bringing CSS Styled Content to the next level: This was a talk about CSS, but it was very general and I don’t like it so much, maybe because I don’t usually have to fight with CSS or because I already knew the most of the things that she said.
• OpenEMM - Sending out Newsletters with TYPO3: An extension to send newsletters that integrates OpenEMM into TYPO3 backend. For that extension you need OpenEMM, an open source Java application, and it doesn’t provide anything special compared with TC Directmail (tc_directmail), so if tc_directmail doesn’t fits your requirements maybe this new extension could do it.
• Business Case - Marketing Open Source Software: Another quite general talk about marketing in open source companies, he recommended a book “The Cluetrain Manifesto” and talk about that in open source companies there’re 4 C’s, the common 3 C’s of marketing (Corporation, Customers and Competitors) and Community.
• Touchless Security with FLOW3: An explanation about how the security framework works in FLOW3. It uses AOP (Aspect Oriented Programming) to can intercept every method that is going to be executed and through ACLs (Access Control Lists) the framework allows or denies the execution of any method. The most important here is that you don’t have to take care about security in your code, only have to define a concrete ACL and never modify your code.
• Test Driven Development using FLOW3: He explained the concept of Test Driven Development in which you have to write tests for all your code and before write your code, in that way you define the APIs before write it. FLOW3 has a Testing package based on PHPUnit that make easy write unit tests. I think that it’s a very interesting idea about how to develop an application. Karsten also talked about Test Driven Design, because some time you are doing design while you write your tests.

That day was a long day because of the conference dinner and the party after that. Not a very good day talking about the talks but a good social day.

I’m in the TYPO3 Conference, today I’ve attended two tutorials: development with FLOW3 and a workshop for creating TYPO3 websites.

Robert Lemke was the author of the first tutorial, it showed a mixing of his podcasts about FLOW3. The great new was that there is already implemented a complete blog system like buzz.typo3.org with FLOW3 using the content repository as persistence mechanism (quite interesting see that actually some stuff works). However the main problem is still performance (Robert said that it shouldn’t be difficult to fix) but the development context is currently very slow. Some brief comments about this tutorial:

• Classes define actions, methods that are going to be called from outside.
• All objects are single instantiations (Singleton Pattern) if you don’t mark them as prototype.
• If you depends on another class you should use Dependency Injection defining a method that is going to be called automatically when the class is instantiated.
• He gave an overview about Domain Driven Design, in a roughly way we can talk about 3 concepts: entities (objects), values (immutable objects) and aggregates (entities that are going to be searched).
• Talking about persistence we need a repository for each aggregate, if we extend the basic repository we’ll have common methods to add, remove, find, … (other entities will be stored transparently). The content repository need that the type of class attributes is specified through comments.
• Finally he talked about REST services, and all repositories are going to be services that will be called automatically to the concrete method depending if there is or not some GET parameter or if there is some POST parameter.

The second tutorial was a workshop from jweiland.net, they gave some useful receipts that can be applied in any TYPO3 projects. They talked about a tool to clean TYPO3 installations, it seems very useful because in big projects usually you don’t know how file you need or not in your filesystem, they don’t say the name of the tool but I can guess that it’s the cli_dispatch.phpsh script (more info) I have to test it!. Other comments:

• Use UTF-8 for the database from the beginning (it’s always good to remember).
• For TypoScript they recommend to create a library in a system folder that could be used in other projects (exporting/importing), these TypoScript templates will be used with Basic Templates and defining constants.
• Moreover it’s possible to detect syntax errors in TypoScript using the Object Browser and the Template Analyzer.

I’ve enjoyed this first day so I’m going to rest to be prepared for tomorrow.

PS: I’ve met some people from Colombia (Nivel Siete) and we’ve been talking Spanish in Berlin .

If you want to use this new feature you’ll need an account at Box.net, a web service that allows users to store files online, and set this account at MyTime preferences.

Moreover MyTime 0.2 is integrated with Online Desktop because it’s using the Online Desktop account system to store the Box.net account. We’ve developed a library (libmytime-common) that has the responsibility to manage the account data depending on if there’s an Online Desktop session, when it uses the Online Desktop account system, or not, then it uses the GNOME Keyring.

Feel free to test this new release, we’ll be glad if you give us your feedback.

PS: MyTime is on Softpedia.

You can download the Debian packages to test it, any comment or suggestion will be welcomed.

In future releases we’re going to add support to store information recorded by MyTime on a Web Service, in order to can query this information from any computer. Moreover we’ll try to use Online Desktop to store the data needed to login at Web Service.

You can read more information about this project at MyTime home page and return your feedback using different resources (mailing lists, forums, tracker, …) at SourceForge.net page.

We hope you enjoy this application and find it useful .

PS: MyTime is now translated to Spanish and Galician.

This extension is very useful for multilanguage websites improving work efficiency in tasks related with internationalization and localization.

Last days I’ve been working on this extension, and I’ve done some changes to add new features that make this extension more powerful. The main modifications are:

• Added the possibility to create translations for more than one page or record at the same time.
• Support to translate records of any table.
• Use generic configuration variables.

You can download the last release 1.2.2 directly from TER or if you like you can download the source code from the SVN repository:
svn checkout https://forxa.mancomun.org/svn/gltransstat

Moreover in the following phases we’re going to try to integrate this project with Online Desktop trying to store information about application use remotely so that you can query information about your time everywhere.

The project is been developed by some people from Igalia engineering group: Antonio, Diego, Quique, Iván, Chema, Loren, Xavi and me.

Among other technologies MyTime uses:

• GTK+ and Glade for the graphical interface.
• GObject for data server and model logic implementation.
• D-Bus usage for communication between components.
• SQLite database system for local data management.

You can read more information about the project in its home page at Igalia community. Furthermore the project has its own page at SourceForge.net where you can find mailing lists, forums, and SVN repository of the project.

There’re a lot of things todo, however feel free to test MyTime and give us your feedback, we’ll be very happy.

We’ll keep you informed of news in this project.

If you develop TYPO3 extensions, specially frontend forms, you should test the extension called Ameos FORMidable (ameos_formidable), with this extension you can develop TYPO3 extensions very fast. After more than one year developing TYPO3 applications, I think that FORMidable is an essential TYPO3 extension; I’ve fallen in love with it.

Furthermore FORMidable actually is a free software project, at project’s homepage there’re links to documentation, SVN, a lot of examples, and mailing list. In this list you can ask, suggest, send patches, etc. and somebody from FORMidable community is going to try to help you, besides FORMidable authors accept patches to improve FORMidable or fix some bugs; I’ve sent several patches and they’ve added my modifications to project.

This post has only the purpose to announce that I’ve published my first article at FORMidable web page.

Finally I’d like to thank to FORMidable development team, specially to Jerome Schneider, for give me the opportunity to collaborate in this great project and for accept my ideas and patches trying to improve FORMidable.