P4A 3 rendering layer discussion

This post will not be easy to write… I’ll try to explain you what kept us really busy in the past 2 weeks. ok a screenshot could help me :-)

In the P4A 3 roadmap post, I told you about a new widget rendering system… I didn’t post more technical info intentionally, I wanted to create a bit of suspense :) but I also wanted to do some tests before publishing news.

For P4A 3 we’d like to have a killer graphic with killer features (resizable widgets, border layouts, beautiful and powerful menu and so on) thus we looked to the biggest javascript frameworks out there: extjs and dojo. Both have great features and both have issues.

Extjs as really a killer graphic layout, and it’s released under LGPL3 (developers wrote some licensing notes that I can’t really understand… actually I think that those notes could conflict with LGPL3 itself) but it has not an open SVN and development is quite closed. Another note: only community support is for free.

Dojo is more polite with licensing and it’s released under BSD, but I don’t like the graphic layout too much and the way you’ve to code your applications writing a non-standard HTML with dojo-only attributes. It has some accessibility features.

Some considerations:

  • In my tests I found bugs in both frameworks
  • porting P4A to one of these tools is a “1 way road”
  • relying the rendering layer to a 3rd party project means we’ve to 1000% trust this project
  • these tools do not have a good print CSS support

We would have a 3rd option: continue on our road with quite standard HTML but rewrite our CSS from scratch with a CSS reset and a modular design which will give us better control.

I wrote extjs developers to know if they’re interested in a collaboration with P4A, I’m waiting for an answer but I’m looking for your considerations too, community it’s important to me, please let me know what you think and what are your experiences with those tools (or suggest others).

What about gnomescan?

The new beautiful interface for scanning media? Think gnome should add it by default and hemmmm… ubuntu? can someone please drop xscan? ok xscan works but it’s 2007, think we deserve a better interface…

just a thought

P4A 2.2.1, first maintenance release for 2.2 serie

Changelog:

– multicheckbox field and multiselect field now support saving in single table field
- P4A_Field::setMultivalueSeparator method was added
- a bug with images on p4a_table wal solved
- rich_textarea “Full” theme was added
- jQuery::form was updated to 2.01
- a bug with empty “file” fields submitted with an ajax call was solved

Download P4A 2.2.1 here

10 thousand!

10 thousand visitors hit my blog, I thought a celebratory post was due :-)

next goal is one more zero at the end ;-)

Remastering an “Ubuntu alternate” ISO with Ubuntu Customization Kit – the complete guide

You have an Ubuntu alternate ISO and you want to customize it, to do things with ease you choose to do that with Ubuntu Customization Kit which will handle most of the tasks for you.

Preamble

This guide is written with the SVN version of Ubuntu Customization Kit, thus somethings (actually only minor things such as log messages) could be different from the ones you’ll get with your copy of UCK.

Prerequisites

To remaster an Ubuntu alternate ISO you need to:

  • be running an Ubuntu based distro on your host system in order to install and run UCK successfully
  • have UCK installed in your Ubuntu box. In order to install it go to the UCK’s website, click download and select the debian package. After downloading the package install it with the usual tools (dpkg or gdebi or whatever).
  • have an Ubuntu alternate ISO downloaded somewhere in your hard disks.

First step: extract the ISO

An ISO image is a single file, you can’t modify it in any way keeping it “as is”, thus you’ll use UCK to extract its contents to a directory with this command:

fabrizio@fabrizio-laptop:~$ sudo uck-remaster-unpack-iso ubuntu-7.10-server-i386.iso
Mounting ISO image…
Unpacking ISO image…
Unmounting ISO image…

Ok all went perfectly, now you’ll find the contents of your ISO in the “~/tmp/remaster-iso” directory

Second step: prepare the remastering environment

This step creates a new package repository inside your remastering directory (~/tmp/remaster-iso/pool/extras), in that repository you can now put all the packages you want to be added to the new ISO.

fabrizio@fabrizio-laptop:~$ sudo uck-remaster-prepare-alternate
now you can copy your packages in /home/fabrizio/tmp/remaster-iso/pool/extras, customize preseed files or do other customizations

Third step: adding new software

Alternate ISO system only manages deb packages thus you need to have deb packages for all the software you need to add to your new ISO.
There’s only one thing you have to do, copy the deb packages to the ~/tmp/remaster-iso/pool/extras directory, that’s all.

IMPORTANT: Added packages are not automatically installed by the Ubuntu installer on my target system

If you add software to the extras pool you can have two reasons:

  • you want those packages to be automatically installed into your target system
  • you want those packages to be available on cd/dvd to be optionally installed into your target system after a choice of the user (Ubuntu text installer handle this within “tasksel”)

If your option is the first then adding the deb packages to the extras directory won’t be enough, you’ll have to modify the preesed file, what is a preseed file? It’s a file which tells the Ubuntu installer what to do, it’s a way to script it.

Preseed files have their own syntax but for the purpose of this small guide I suggest you to take a deep read of the “modify installer behaviour using a preseed file” guide.

The “install cd customization” guide is really big but you don’t need to study it all, you can read only the “modify installer behaviour using a preseed file” section just because UCK covers all other sections for you.

Forth step: modify software that already was in the original ISO

Sometimes you could want to modify default configurations of software which is bundled with the default ISO, in order to do that you’ve to:

  • locate the original deb package within the remaster-iso/pool tree
  • delete it
  • create a new deb package for the software, with all your customizations inside it
  • copy your new deb package to the position where the original one was (eg: ~/tmp/remaster-iso/pool/main/a/apache2)

You need to delete the original package to avoid possible conflicts.

Fifth step: finalize the remastering environment

Ubuntu alternate ISO system works with signed Ubuntu repository thus you’ll have to regenerate all the metadata files for your updated/new repositories and than sign it with GPG. If one of these conditions are not met the installer will hang telling that your ISO is corrupted.

When I was writing alternate support for UCK this was one of the most difficult part to code and this would be difficult for you too if you were not using UCK :)

If you don’t have it, create a personal GPG key before going ahead. Remember also to write down the ID of GPG key, it should be printed by the key generation process or you can read it with the gpg --list-keys command.

Now simply let UCK do the work for you with:

fabrizio@fabrizio-laptop:~$ sudo uck-remaster-finalize-alternate 691D19E1

UCK will then do a lot of things, download files from the Internet and do all the tasks we were talking before, the operation could last a few minutes and you’ll see a lot of log lines. You’ll be asked to type the password for your GPG key, this should happed 3 times.

When the process will be finished you’ll be ready to repack your ISO.

Sixth step: pack your new ISO

fabrizio@fabrizio-laptop:~$ sudo uck-remaster-pack-iso

A lot of log lines will be printed in this phase too, don’t worry about those if you don’t see any strange error message.
Ok that’s all, finally you did it, where’s your new ISO file? Here:

fabrizio@fabrizio-laptop:~$ ls -lah ~/tmp/remaster-new-files/
totale 501M
drwxr-xr-x 2 root root 4,0K 2007-11-27 11:49 .
drwxr-xr-x 5 root root 4,0K 2007-11-27 11:49 ..
-rw-r–r– 1 root root 500M 2007-11-27 11:49 livecd.iso

Now you’re free to burn it, test it with qemu/virtualbox/vmware or whatever ;-)

Closing notes

This guide should be pretty exhaustive, if you encounter errors, misspellings or have any suggestion, please feel free to drop a comment!

And… remember to DIGG this guide using the button here below :-)

Ubuntu Customization Kit 2.0.1

A small maintenance release to fix a few bugs, mainly focused on the “alternate” ISO remastering.
Here you have the complete changelog:

GUI:

  • version number shown in uck-gui was fixed

Backend:

  • when unpacking an “alternate” ISO now we don’t try to parse the filesystem manifest
    because it doesn’t exist
  • uck-remaster-finalize-alternate now can handle new releases of ubuntu-keyring package

Package:

  • fakeroot dependency was added

Links:
Download UCK 2.0.1
UCK’s official website

Minibuntu – the base for your distro, now add your ingredients

A few days ago a guy on UCK forum told me that he would need a clean Ubuntu livecd without all the bells and whistles, without gnome and all the graphic releated software, a sort of minimum system to build on his new Ubuntu derivate, starting from a clean base.

I thought it was a really good idea to publish the minimal Ubuntu package set packed in a small bootable livecd ISO image.

This is minibuntu, the base Ubuntu system, ready for your ingredients to cook your own Ubuntu derivative.

Hope you like the idea, please let me know what you think about that.
Read more on minibuntu page.

P4A 3.0 roadmap

ok here you have:

  • brand new widget rendering system, it will provide a new experience from the users point of view, a richer set of widgets and the best browser support (we’re doing deep tests right now, more info will follow)
  • PHP5 only
  • add Zend Framework
  • replace adodb with Zend_DB
  • define which database engine will be supported (I think MySQL, PostgreSQL, Oracle, SQLite) and drop support for all the others
  • solve definitively all the problems with all supported databases
  • replace our date parsing/formatting library with Zend_Date
  • drop all localization formats and use Zend_Locale’s (which uses unicode.org formats)
  • replace our numbers/currency formatting library with Zend_Locale
  • replace our translation library with Zend_Translate
  • make every output string to be translated and make the translation system work the way gettext work (making possible to include partial translations)
  • create a tiny php5 optimized library to replace phpThumb
  • completely remove PEAR

Yes, it will be a huge, massive and killer release, I promise it will rock!

The theme quest…

Will ever be over? I don’t know… wordpress.com hasn’t the perfect theme for me, sorry guys!!

P4A 2.2 is finally out

This is the month of the big releases :-) first was UCK 2.0 a few days ago, now it’s time for P4A – PHP For Applications 2.2!

Highlights of this release:

  • Prototype/scriptaculous were dropped and jQuery was added. Thanks to jQuery and some wonderful plugins we added a new color picker field type, the ajax file upload feature, some great improvements to the popup system also with the ability to block the underlying interface and a beautiful audio/video preview system.
  • Answering to many request the tooltip system was implemented, $field->setTooltip() and you’ve done the work of providing information about fields on your mask.
  • Another requested feature: field autocomplete, similar to the google suggest one, enjoy it
  • A smooth “helpers system” was introduced, now everyone can really write plugins for P4A, overriding core mothods without having to patch framework’s file (this only works with PHP5)
  • The getid3 library was added, its work is to read all data from multimedia files and pass them to P4A that will use them and store them. Now we have a better width/height/mime-type detection for many and many multimedia file formats.
  • …and many many improvements and bugfixes, check the changelog for the complete list

Upgrade:
You should have no problems directly upgrading from 2.0.6 to 2.2.0, otherwise write us on the help forum!

Download:
Can’t you wait? Here you have:
P4A 2.2.0 download

Future:
You already know that we can’t stop, things are already moving… we’ll publish more info very soon, also because I’m going to commit some preliminary tests for the next big step: P4A 3.0. Don’t miss it, I swear you’ll like it.

Technical note:
If you use P4A SVN, please switch to the 2.2 branch and don’t use the main trunk anymore!!! That’s because we’re working on it for P4A 3.0!

see you :)