Assetic

Assetic is an asset management framework for PHP written by Kris Wallsmith. Although this library is available for every PHP project I’m focusing in Symfony2 integration.

For a complete overview of the usage of Assetic in Symfony context please refer to the following cookbook entries:

• Symfony2 – How to Use Assetic for Asset Management
• Symfony2 - How to Minify JavaScripts and Stylesheets with YUI Compressor

Usage in SmartyBundle

SmartyBundle provides the same javascripts, stylesheets and image functions supported in Twig and PHP engines. Usage is quite similar to Twig.

Javascripts

Stylesheets

To bring in CSS stylesheets, you can use the same methodologies seen in this entry, except with the stylesheets tag:

Combining Assets

You can also combine several files into one. This helps to reduce the number of HTTP requests, which is great for front end performance. It also allows you to maintain the files more easily by splitting them into manageable parts. This can help with re-usability as you can easily split project-specific files from those which can be used in other applications, but still serve them as a single file.

Using the same javascripts example as above. Note the usage of commas to separate assets.

In the dev environment, each file is still served individually, so that you can debug problems more easily. However, in the prod environment, this will be rendered as a single script tag.

Block attributes

Here is a list of the possible attributes to define in the block function.

• assets: A comma-separated list of files to include in the build (CSS, JS or image files)
• debug: If set to true, the plugin will not combine your assets to allow easier debug
• filter: A coma-separated list of filters to apply.
• combine: Combine all of your CSS and JS files (overrides `debug`)
• output: Defines the URLs that Assetic produces
• var_name: The variable name that will be used to pass the asset URL to the <link> tag

Full example

And now here goes an example using all available attributes:

This is work in progress

That’s right, Assetic support in SmartyBundle still requires some real world usage to get rid of its sharp edges and bring it to production level. If you are able to give it a try, test it for a bit and bring your complains over to SmartyBundle issue tracker. I’ll appreciate it!

SmartyBundle is Symfony2 a bundle that provides integration for the Smarty3 template engine. It will allow the usage of the Smarty template engine in Symfony2, instead of Twig or PHP templates. SmartyBundle is released under a LPGLv3 license. To download it you may:

Git-clone-it:

$ git clone https://github.com/noiselabs/SmartyBundle.git

or download the repository as a zip file:

https://github.com/noiselabs/SmartyBundle/zipball/master

Full documentation is available on GitHub and after download in the Resources/doc/ folder.

What is Symfony

Symfony is a Open Source PHP Web Development Framework. It is currently my PHP framework of choice that first grabbed my attention by its standalone components and got me back to PHP after digging into the, Python-based, TurboGears Web framework.

What is Smarty

Smarty is a template engine for PHP, facilitating the separation of presentation (HTML/CSS) from application logic. Version 3 brings some important improvements like the addition of template inheritance and a complete code rewrite to make use of new PHP5 capabilities.

Try it!

I welcome everyone interested to try it, test it and to improve its code by sending comments, suggestions and GitHub pull requests. Bugs and feature requests are tracked on GitHub.

Thanks and see you soon

After my last Xorg update I’ve lost the nice ability to log into my KDE. Well, this *sucks* because I spent a long time compiling kdelibs and friends so I really want to use it.

Symptoms

A blank screen on login. You can even see your mouse pointer but nothing else.

If you take a look at the Xorg log you’ll see X is mad about a “batch buffer thingie”.

Error in /var/log/Xorg.0.log:
(EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: No such device

The Solution

Pretty ease to solve this one. Either upgrade your kernel to something like 2.6.36 or better (recommended) or block xf86-video-intel>2.14.

Permanent solution
Upgrade your kernel. I was running an old 2.6.32-tuxonice-r7. Upgraded to 2.6.36 and… Welcome back, KDE.

# emerge --sync && emerge --update gentoo-sources

Workaround (if you’re in a hurry)
Add this to /etc/portage/package.mask

>=x11-drivers/xf86-video-intel-2.14.0

and recompile.

# emerge --update x11-drivers/xf86-video-intel

While working with the TableTools PDF generator included in the great DataTables jQuery plugin I’ve noticed that sometimes the script failed to generate the PDF file. The cause? Invalid characters in the filename.

Well, to solve this issue I’ve made a simple PHP function to return a safe version of the given filename.

How it works?

Reads a filename string and replace each “dangerous” character with an underscore. Of course you can use any other “safe” character instead of an underscore.

The Code

Download this and more…

This snippet and other useful [at least, I hope so] PHP methods are grouped on a git repo available via GitHub. This is also the best [and only] way to get the updated version of the code.

Go to the project’s web page on GitHub or download it right way with (you must have Git installed first):

$ git clone git://github.com/noiselabs/noiselabs-php-toolkit.git

Everyday morning was the same: updatedb came and took my Gentoo away. The symptoms were clear, X/KDE applications starting to become slow and unresponsive, and then the two inevitable choices: go for a coffee and wait or pkill the bastard.

Asking updatedb to be nice (the wrong way)

To fix this came to my mind the nice command. This is well known to Gentoo users because of the PORTAGE_NICENESS feature include in make.conf. Nice is a program that adjusts the process scheduling (aka niceness) of the desired programs so setting a value of 19 (the maximum) would make updatedb to be “nicer” to other applications and therefore being less bossy. So I’ve edited /etc/cron.daily/slocate, placed “nice -n 19″ before the updatedb command and waited. But, once again, updatedb came and owned my computer.

Asking updatedb to be I/O-nice (the right way)

So. what’s wrong here? Updatedb is not a CPU-intensive application so nice won’t change a thing. The bottleneck is disk access so what we need here is a nice for I/O. The solution? Ionice.

Ionice is able to set the I/O scheduling class and priority for a given program. To give updatedb a low priority we pick the class 3, the idle one.

Again, let’s go to crontab and edit the slocate entry.

# vim /etc/cron.daily/slocate

Put ionice -c 3 before the updatedb command.

#! /bin/sh

if [ -x /usr/bin/updatedb ]
then
        if [ -f /etc/updatedb.conf ]
        then
                ionice -c 3 /usr/bin/updatedb
        else
                ionice -c 3 /usr/bin/updatedb -f proc
        fi
fi

And if you’re asking where (in Gentoo) is this ionice program, the solution is sys-apps/util-linux, which I’m pretty sure is already installed. If not: emerge -a sys-apps/util-linux.

This is all good but… what’s this updatedb thing?

Updatedb is a tool ran daily by cron to update the slocate database. And Slocate (Secure Locate) is a security enhanced version of the GNU Locate, which is used to index all the files of your system allowing a (very) quick search of them. In Gentoo Linux the slocate is available in Portage through sys-apps/slocate.

For some time I’ve been using Wikipedia to translate expressions that a normal translator couldn’t give exact results, because they use literal translations. Now there is a faster way.

MemeMiner, brought to us by Fred Rocha, is a Web tool that does this work and gives us a easy and fast way to get this translations.

From the author own words:

For most of it’s articles, Wikipedia provides the equivalent expression of that concept in other languages.
With MemeMiner you can effortlessly find out how a certain idea is expressed across the language spectrum.

Now go ahead and try this tool at http://fredrocha.net/MemeMiner/

Meme Miner webpage

Thanks Fred!

Recently I decided to visit CoovaChilli website and check the latest version of the software. CoovaChilli is now at version 1.2.2. I’ve decided to dedicate some time to make this version available in Gentoo and started working on it. It’s also my intention to shorten the gap between new releases of CoovaChilli and their availability in the Overlay

OK, but.. what is CoovaChilli?

Here goes a description taken from the website:

CoovaChilli is an open-source software access controller, based on the popular (but now defunct) ChilliSpot project, and is actively maintained by an original ChilliSpot contributor. CoovaChilli is released under the GNU General Public License (GPL). CoovaChilli is a feature rich software access controller that provides a captive portal / walled-garden environment and uses RADIUS or a HTTP protocol for access provisioning and accounting. CoovaChilli is an integral part of the CoovaAP OpenWRT-based firmware which is specialized for hotspots.

So CoovaChilli is a Wireless LAN Access Point Controller. For those who used Chillispot this is the natural successor.

Follow the development process on GitHub

I’m storing the Ebuild on my GitHub account so for those wishing to check out the evolution of the Ebuild (not sure why would someone want to do this but …) just open this link.

Of course is always possible to checkout the git repo and retrieve my personal Gentoo overlay which includes the CoovaChilli ebuilds. To do this just execute:

$ git clone git://github.com/noisebleed/noisebleed-overlay.git

Make sure to keep the repo updated:

$ git pull remote origin

Try version 1.0.11 available on Sunrise overlay

The Sunrise overlay is the place I choose to provide the CoovaChilli ebuilds. To use the ebuild (coova-chilli-1.0.11) first bring the overlay into your system through Layman:

(Install layman)
# USE="subversion" emerge -va app-portage/layman
# layman -f -a sunrise
(since layman 1.2.3 use "/var/lib/" instead of "/usr/local/portage/")
# echo "source /var/lib/layman/make.conf" >> /etc/make.conf
(Update the overlay)
# layman -s sunrise

Then just emerge the normal way:

# emerge -av net-wireless/coova-chilli

More information about using overlays can be found on the Gentoo documentation. Specific Sunrise instructions are available on Sunrise’s wiki.

tar: file name is too long (max 99); not dumped
tar: Error exit delayed from previous errors

If you happen to see the same error message it is quite likely that you (and by you I mean Automake) are using the old V7 tar format.

Just want the solution? It’s here

V7 and other tar formats

By default Automake is pulling the historical V7 format to generate the tarball with make dist. This tar format supports file names only up to 99 characters and that’s why tar is refusing to build the tarball.

Since automake 1.9, th tar format can be chosen with the options tar-v7, tar-ustar, and tar-pax.

This is what the Automake manual says about each option:

• tar-v7

This is the historical default. This antiquated format is understood by all tar implementations and supports file names with up to 99 characters. When given longer file names some tar implementations will diagnose the problem while other will generate broken tarballs or use non-portable extensions. Furthermore, the V7 format cannot store empty directories.

• tar-ustar

(…) format defined by POSIX 1003.1-1988. This format is believed to be old enough to be portable. It fully supports empty directories. It can store file names with up to 256 characters, provided that the file name can be split at directory separator in two parts, first of them being at most 155 bytes long. So, in most cases the maximum file name length will be shorter than 256 characters. However you may run against broken tar implementations that incorrectly handle file names longer than 99 characters.

• tar-pax

(…) the new pax interchange format defined by POSIX 1003.1-2001. It does not limit the length of file names. However, this format is very young and should probably be restricted to packages that target only very modern platforms. There are moves to change the pax format in an upward-compatible way, so this option may refer to a more recent version in the future.

How to fix it?

The solution is to pick a newer and better tar implementation like tar-pax. Go to configure.ac or configure.in and change the AM_INIT_AUTOMAKE macro so it specifies the tar format and requires automake version to be 1.9 or better as tar-pax is only supported since 1.9.

configure.ac/configure.in:

AM_INIT_AUTOMAKE([1.9 tar-pax])

Now run `make dist` again and tar won’t bother you anymore (at least with this error ).

As of February 5, Google developer Ryan Cairns has made this statement on the Chromium OS dev mailing list:

As we’ve been growing and working with more partners, the need to support board specific builds and improve our tools has become more urgent. In order to get there more quickly we’ve been investigating several different build tools. We found that the Portage build tools suit our needs well and we will be transitioning 100% within the next week.

As a Gentoo user and supporter I’m happy to see Portage being picked by major projects like the Chromium OS. Hopefully it will bring more (positive) attention to Gentoo and maybe we will see the Google folks contributing with improvements and bug fixes back to Portage.

For those interested in checking out the Portage-based build environment and build a bootable Chromium OS image take a look at this Chromium OS documentation page.

If you are interested in Portage features and usage check the Gentoo Handbook page about Portage. And if you got curious about Portage history I recommend the this article by Daniel Robbins, the founder of Gentoo.

To know more about the Chromium OS project and Google Chrome OS check this.

• Step 1: Type “is:unread” in the search bar.

• Step 2: Then select “Unread” as seen in the picture below.

Type "is:unread" in the search bar and then select "Unread" from the selection bar

In the "More actions" dropdown select "Mark as read"

And that’s it. Your inbox shouldn’t be reporting any unread messages by now.