Back to Helsinki. GUADEC was great but you already know that. Also, in no specific order:

• Actually my preferred topic of discussion was freedesktop.org and how to help the critical projects there.
• GTK+ 3.0 will come and break. Finally. I liked how the GNOME Release Team was there shoulder by shoulder.
• Chris presenting Gecko/Firefox and Alp presenting WebKit for GTK+: spectacular. Watch and see how this (r)evolves in the web runtime side of things.
• Federico exposed brilliantly the problems of user Oralia finding files. He dismissed the relevance of the mobile ("who has a touchscreen anyway?") but somehow I feel that mobile platforms for devices sharing content with local and online computers will push the solution of Oralia's problem. Not a desktop doing local searches.
• Gitorious, Transifex, Bazaar shirts and Mark Shuttleworth - something intense is going on in the crescent world of collaboration tools.
• Interesting to see the most used applications in the Online Desktop.
• Some speakers seemed to have fun joking about Python. Some other seemed to have fun showing cool stuff developed with Python. Computer Science is such a science.
• Sorry guys but this time the GUADEC organizers beat everybody with the best shirt.
• Glady surprised of seeing ARM in the list of sponsors.
• Stormy Peters is not just great. She is also born in Barcelona and speaks fluent Spanish. We started talking business.
• Offered to the board hosting a GNOME hackfest in the Maemo Summit.

And because not everything is free software in this life:

• Istanbul Modern is cool. I was surprised.
• Büyükada is beautiful. I was delighted.
• Fener has an interesting history. I was touched.
• Mosques and bridges fit together.
• Pide, artichokes and aubergines forever - I expected more from fish though.
• Still intrigued about women covered with black veil, specially those walking with other women or husbands dressing jeans.

Last but not least, Katja was impressed about the people and the ways of working and sharing in GUADEC. But I had been telling her about GNOME the project, the people and the events during 3 years at least. There is a marketing & communication problem here, since we cannot send the World to GUADEC to let them see with their own eyes. Should GNOME produce good video marketing?

عند برمجتك ال AIR عن طريق HTML/CSS/Javascript فإن المترجم لكل هذه التقنيات هو WebKit المترجم الموجود فى المتصفح safari على الكمبيوتر و ال iphone و قد إختارته شركه ADOBE بعد البحث لأسباب كثيره أهمها انه مفتوح المصدر و مجتمع المطورين فيه يزداد و التطوير فيه مستمر و دائما يقوم بطرح توصيات منظمه W3C للعمل عليها و دمجها فى المترجم مثل DOM specifications و CSS level specification و HTML و توصيات مجموعه WHATWG بالإضافه إلى ماتضيفه WebKit على غيره من المتصفحات فعلى سبيل المثال فى ال CSS يمكنك عمل حواف دائريه للعناصر بدون إستخدام الهاكات او المكاتب التى أعدت لذلك مثل rounded corners كل ماعليك هو إستخدام الخواص الجديده و الحصريه فى WebKit و المثال التالى يوضح ذلك

-webkit-border-bottom-left-radius:20px;
-webkit-border-bottom-right-radius:20px;
-webkit-border-top-right-radius:20px;
-webkit-border-top-left-radius:20px;

و الصوره توضح العنصر ذو الحواف الدائريه عن طريق أربع أسطر من الكود فقط بدون تعقيدات المكاتب و الهاكات

و لذلك عليك معرفه خواص المترجم عن ظهر قلب و هذه الروابط ستفيدك

ال CSS فى بيئه ال AIR و المرجع الشامل لكل خواص ال CSS فى WebKit

ال javascript فى بيئه AIR

ال HTML فى ال AIR

و أخيرا موقع webkit

و إذا كان لديك إستفسار إترك تعليق او راسلنى :)

If you would like to get your hands on the Webkit powered version of Epiphany, you need to actually have the Webkit engine installed first then install Epiphany. And that involves a lot of dependencies headache. But, luckily, I found two ways of running Epiphany/Webkit: the Soft way from Michele Costantino and the Hard way :) . If you just want that thing running immediately , just go for the soft way but if you're like me and you want a little bit of challenge, well, you know which one to pick.

Soft Way

Add the following two repositories to your /etc/apt/sources.list:

deb http://ppa.launchpad.net/stemp/ubuntu hardy main #WebKit & Midori
deb http://ppa.launchpad.net/michelinux/ubuntu hardy main #Epiphany-WebKit

Then reload your sources

sudo apt-get update

Now Install epiphany/webkit

sudo apt-get install epiphany-webkit

To run epiphany/webkit

epiphany-webkit

Hard Way

Install WebKit/GTK+

Download a nightly tarball source (small download)
You can head over and start installing but it generate a lot of dependencies errors if you don't the right packages installed. To help you a little bit in your adventure based on my adventure, make sure you have the following installed:

sudo apt-get install libtool bison flex gperf libicu-dev libglib2.0-dev libgstreamer-plugins-base0.10-dev libgstreamer0.10-dev libxslt-dev libcurl4-openssl-dev libsqlite3-dev libjpeg62-dev libpng12-dev libcairo2-dev libpango1.0-dev libgtk2.0-dev gstreamer-0.10 gstreamer-base-0.10 gstreamer-plugins-base-0.10 gnome-vfs-2.0 libgstreamer0.10-dev libgstreamer-plugins-base0.10-dev gstreamer0.10-gnomevfs libxt-dev

Extract the tarball and from the resulted folder, Run the following commands to configure and build WebKit (choosing an appropriate prefix):

sudo ./autogen.sh --prefix=/usr/local
sudo make
sudo make install

Install Epiphany/Webkit

Make sure you have the following installed:

sudo apt-get install libstartup-notification0-dev libgnome-desktop-dev libdbus-glib-1-dev libwebkitgtk-dev

-Download the source tarball from here, extract it and from the resulted folder

sudo ./configure –with-engine=webkit
sudo make
sudo make install

To run epiphany/webkit

epiphany

La prochaine version du navigateur Epiphany de Gnome utilisera WebKit à la place de Gecko.

Ça serait quand même sympa de pouvoir tester l'avancement du projet.

Hé bien Michele Costantino Soccio a pensé à nous et a préparé les paquets nécessaires dans son PPA.

Il suffit donc de rajouter (en plus de mon PPA pour Webkit) la ligne suivante dans votre sources.list :

deb http://ppa.launchpad.net/michelinux/ubuntu hardy main

Ensuite il faut installer le paquet epiphany-webkit (à noter que cela mettra aussi à jour globalement epiphany).

Grazie mille Michelinux ;)

Install was very clean with much improved interface. Installed to dual-boot alongside Windows XP on one of my older desktops - is an AMD 64 3500 processor with 2GB Ram and an Nividia 6800 128MB Graphics card... had a 160GB disk which I partitioned in 2 - giving the linux install a nice clean 80GB to work with... is not bad for a mess about machine to experiment with.

Two of my biggest bug-bears with OpenSuse Linux have been solved in respect of the USB wireless dongle being picked up and working straight away, as well as much improved ease of install of Nvidia graphics driver.

I still find it annoying that you have to download Nvidia drivers separately for OpenSuse linux... as has always been the case... but they have made the install very very easy these days and was impressed that Nvidia were bang up to date with OpenSuse 11 drivers pretty much on the day of distro release.

The Wireless LAN pickup was a dream come true. It took me ages to get this same Wireless USB dongle working on OpenSuse 10.3... at least 2 evenings... so I was glad to see that OpenSuse 11 just recognised it straight away.

Was a bit dissappointed with Compiz-Fusion experience on this machine. Was able to get it working OK using nice new graphical UI configuration tools and the fx are pretty sweet... however I haven't been able to spot  anything on the GUIs provided to enable this to be switched on by default whenever the OS reboots... so I guess I'm gonna have to hack some configuration file in the background somewhere...just a slight annoyance - but still it would have been nice to put something so simple on one of the config screens! Secondly... I admit the graphics card I'm running this on only has 128MB Ram... but I have noticed that, when I have compiz-fusion switched on, the window buttons for maximise, minimise, close etc keep on disappearing... windows won't close sometimes even when you repeatedly press the close button... is a bit annoying... never the less is all still a big improvement over the previous configuration experience and certainly all-in-all makes linux just the sexiest looking rich eye-candy desktop experience out there when compared to Vista or OS X... especially like the Apple cover-flow-style alt-tab window swapping experience they've built in... that's just sweet...although obviously Apple did it first.

Was impressed with the fact that a lot of packages they have in this distro were so up to date including KDE 4.0, Firefox 3 (which was only released the day before!), and Wine 1.0 (just released the week before) were all in the box... very nice!

Was out at concert this evening but had left it installing all the usual development stuff including Apache, MySQL, php, Mono, Eclipse, SubVersion, webkit etc etc... will get messing with those in due course to evaluate...

All in all... good solid distro so far although I think I'm probably going to leave compiz-fusion switched off on my test machine... will try it on another machine with a better graphics card to see if experience improves... I still think OpenSuse is the best linux distro out there and makes for a great free download!

Go get it!

Other options might be a persistent web IM application, web form for
logging info, etc., that you don't want to tie to a full web browser
and other uses that might happen in it. I removed most of the menu
functions, but preferences work to change the url and window size is
remembered. The default page is my blog site, but I would recommend
checking out http://player.play.it/player/aolPlayer.html as well. If
you've never used Airfoil, I would recommend it too.
http://rogueamoeba.com/airfoil/

Grab it here

B

Con GWT ho già realizzato un prototipo d'interfaccia da usare come base di un progetto di prossima realizzazione. Ho usato la 1.4 e mi appresto a provare la 1.5.

Le socket mi servono per un'idea che dei miei amici mi hanno suggerito. Visto che i progetti di prova li sto scrivendo in C++, ne approfitto anche per rinfrescarmi la memoria su questo linguaggio. Più in la mi toccherà rivedere anche le QT, visto che intendo usarle per la GUI del "coso" a cui sto lavorando.

Mockito, che mi ha fatto conoscere il mio collega maeste, è un oggettino utile per fare mock object java, quindi per i test di unità.

Virtools è una tecnologia per lo sviluppo di ambienti virtuali 3D. Mi sta creando indirettamente qualche problema. Per installarlo sulla mia macchina mi serve una copia di Windows perfettamente funzionante, possibilmente non virtualizzata. Dato che non vorrei partizionare il disco del mio MacBook Pro, sto tentando di installarlo su un disco USB esterno, senza successo. Cioè, dopo vari giri sono riuscito a mettere una installazione di XP sul disco esterno, ma non riesco a fare il boot. In compenso però ho conosciuto rEFIt, un boot manager per mac che tra le sue funzioni comprende l'apertura della shell EFI.

Nella lista non ho citato JBoss ESB, che per il momento ho tralasciato, ma che dovrò affrontare quanto prima approfonditamente.

Continuo a prestare attenzione alle novità che riguardano WebKit. Oggi ho letto un articolo su Meta, un porting di WebKit pensato per essere integrato nei videogame. Ne avevo parlato qualche post fa.

Um dos melhores browsers, local de inúmeras inovações que mais tarde ou mais cedo acabam por ser copiadas por outros, está de volta. O Opera lançou a versão 9.50 para mac e a primeira impressão é que é rápida. Muito rápida mesma, tanto que o Opera recuperou o seu lugar na minha Dock juntamente com o Webkit e Firefox.

Por falar em Firefox ontem foi dia de Release Candidate 3 e entretanto foi anunciada a data de lançamento do FF3: Dia 17 de Junho, terça feira da semana que se aproxima.

Veja também:
Safari e Firefox e Windows

I discovered that Torch Mobile has built a browser called Iris Browser that uses the open source WebKit rendering engine (the technology that Apple adopted to create Safari both on the desktop and the iPhone.)

The Iris Browser leverages the WebKit rendering engine, providing a powerful, standards-based and Web experience that is consistent across mobile Web devices. Harnessing our extensive WebKit expertise, we made the Iris Browser small, fast and adaptable.

[From Torch Mobile » Products]

While the Iris Browser is definitely not as polished as Mobile Safari on the iPhone and is clearly still Beta software (the bookmark manager often fails to store your bookmarks when you quit the application. It runs out of memory pretty frequently, etc) It has great javascript support... it does such a good job emulating the iPhone that you can run tons of iPhone webapp (I love the iPhone version of Google Reader for example.) It can zoom in/out visually, supports basic scrolling gestures, supports having multiple pages open at once (using page thumbnails rather than tabs) and generally provides a much more organic browsing experience for Windows Mobile than anything else I've tried... And it's all done on the phone, so you don't have the weird behaviors you see with things like Opera Mini where pages are zoomed, formatted in the cloud.

La notizia odierna riguarda però il JavaScript engine che dalle ultime revision integra un nuovo interprete: SquirrelFish. I guadagni in termini di velocità sembrano essere straordinari e sono stati stimati in media nell’ordine di 1.6 volte rispetto al predecessore.

Difficile spiegare in breve il funzionamento di SquirrelFish; per maggiori informazioni sul suddetto componente potete però consultare l’esaustiva pagina dedicatagli sul sito ufficiale.

[via: osnews.com || ossblog.it]

This post was originally a rant about Apple's web browser, Safari, but seeing how the launch of Firefox 3 is gaining massive global attention, I thought I'd mention Download Day first.

Mozilla is attempting to set a world record for the most downloaded software in 24 hours on the launch of Firefox 3 and this can only be done with your help. If you're a fan of Firefox, pledge to download their latest version once it is out by visiting their website. There are already 191 pledges from Kuwait so far. :)

As for the Safari rant, I think Apple really needs to fix their WebKit engine; these high CPU cycles are outrageous and unacceptable by any means. Web browsers are one of the most commonly-used type of software on any platform; visiting a few websites should definitely not cause severe battery drainage!

Safari (3.1.1) using both CPU cores

Update: Reports are saying that Apple is improving JavaScript for its Webkit engine. Meh, we'll see.

De acordo com o site, a previsão da empresa é de que ele seja colocado no mercado já em janeiro de 2009, apenas 15 meses desde o lançamento do Mac OS X 10.5 Leopard, em outubro de 2007. Já existem possibilidades de que ele passará a ser compatível apenas com Macs com processadores Intel — apesar de que eu acho um pouco cedo demais.

Por fim, o site afirma que o 10.6 não trará grandes novos recursos para o sistema, mas será bastante focado em “estabilidade e segurança”. Mais uma informação um tanto estranha, na minha opinião: a Apple foca-se em estabilidade e segurança em updates menores (tais como o Mac OS X 10.5.1, 10.5.2, 10.5.3 etc.), tradicionalmente.

E o nome do novo felino, qual será? Segundo macmaníacos de plantão, Lion é um forte candidato.

for(var i = 0; i < array.length; i++)

An invariant loop would be

var len = array.length;
for(var i = 0; i < len; i++)

and a for each loop would look like

for (var i in array)

While the original tests were looking for percent speed improvements within a browser achievable by selecting the different types of loops I thought it would be interesting to modify the test to report raw speeds in milliseconds and then compare various browsers.
The speeds reported here are for the fast invariant for loop over a series of runs.
Safari 3.0 - 98 milliseconds
WebKit 3.1.1 - 37 milliseconds
Firefox 2.0.0.14 - 200 milliseconds
Firefox 3.0 RC1 - 28 milliseconds

The new WebKit shows a dramatic increase over the older Safari as does the new Firefox. WebKit appears to be nearly 3 times faster in this test than its' older version used in Safari. This may be due to the changing of the JavaScript interpreter to SquirrelFish in the place of the older one. A discussion of SquirrelFish and why it is faster can be found at WebKit'sblog.
It will be interesting to see if this new version makes it into the upcoming iPhone OS 2.0. It would be fantastic if it was stable enough and did. Every bit of speed you can get on a handheld device is precious.

There are 2 ways of doing this for free. (That is, if you value your time at $0 an hour)

First: khtml2png

http://khtml2png.sourceforge.net

khtml2png2 can be installed via a debian package, and runs on any variant of linux, as long as you have KDE installed. I didn't, and thus spent a long time downloading KDE. It uses Konquerer to render the webpages, and Konquerer will often prompt for user input when something is wrong (i.e. -- a plugin is missing (FLASH), or the web site wants access to your cookies.) It also was incredibly slow on my relatively fast desktop machine. However, it does the job -- alright, and fits the price -- free.

Second: webkit2png

Unfortunately, I was determined to make this process a little bit faster, and spent about 4 hours trying to get http://www.paulhammond.org/webkit2png/ to work. Webkit2png will run on OSX and takes screenshots using WebKit. It is fast, and a pain in the ass to install if you are unlucky. You'll need Python, and the PyObjC wrappers. It was trivial for me to setup the wrappers from http://pyobjc.sourceforge.net/. The whole process should be pretty straightforward, install PyObj, and grab the Python code from the above website, no problem. Of course on my computer WebKit the header files the PyObjC setup.py wanted could not be found, and because of this the PyObj was not generating some of the files that PyObjC needed to run, "_WebKit_Str.inc" in particular. I tried a few tricks to make the setup.py find these header files, and managed to completely screw up my webkit install. Long story short, the script that generates stub files for PYOBJC ONLY looks in /System/Library/Frameworks/ no matter what you specify in the setup.py, and doesn't even look in /Library/Frameworks even though it is listed in the default setup.py.

For PYOBJC to install correctly, you must have a directory called WebKit.framework in /System/Library/Frameworks, and it MUST have a Headers directory inside of it. And these headers must match the binary version of the WebKit library. I.e. you should have a directory structure that looks like:

bcx-mbp:/System/Library/Frameworks/WebKit.framework root# ls -l
total 24
lrwxr-xr-x    1 root  wheel    27 Jun  3 23:29 Frameworks -> Versions/Current/Frameworks
drwxr-xr-x   42 root  wheel  1428 Jun  3 23:40 Headers
lrwxr-xr-x    1 root  wheel    26 Jun  3 23:29 Resources -> Versions/Current/Resources
drwxr-xr-x    4 root  wheel   136 Jun  3 23:21 Versions
lrwxr-xr-x    1 root  wheel    23 Jun  3 23:29 WebKit -> Versions/Current/WebKit
bcx-mbp:/System/Library/Frameworks/WebKit.framework root#

The problem that I faced, and caused me to waste so much time was that I was missing the Headers directory inside of /System/Library/Frameworks/WebKit.framework. To solve this problem you can try doing a find -name WebKit.h and copying the Headers directory containing this file into your WebKit.framework directory. In my case I had another copy of the WebKit headers at: /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/WebKit.framework . Copying the headers directory from the above directory did the trick.

Now I left out a lot of the indirection that I faced in solving this problem. At some point in this process I broke WebKit and had to installed the 3.1.1 Safari upgrade from apple, (As described by: http://soakedandsoaped.com/articles/read/how-to-fix-broken-webkit-framework-after-safari-3-1-upgrade ) which updated my WebKit binary, but did not give me header files. Luckily the header files from the above /Developer/SDKs/ worked with this new WebKit binary. However the WebKit binary located in /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/WebKit.framework did not work with my version of Safari, and still gave me errors when I tried to load it using import WebKit in the python code I was testing. In short, I managed to get everything working, and I believe the root of my problem was a missing Headers directory, but I might have also needed to install Safari to fix issues with my existing WebKit install so that I could install and compile PYOBJC with WebKit bindings.

It is likely that all of these problems are fixed on Leopard, so it's unlikely anyone else will run into these problems. I believe Leopard comes with PYOBJC preinstalled, so no worries linking the two.

So anyway I got it all working and it was worth it, webkit2png.py is far superior to the konquerer based khtml2png2 even though it was a real pain to configure on Tiger.

I guess this is a little off topic.

A pasta, por enquanto, é apenas um atalho que aponta para a pasta 10.5, logo acima. Sua presença, porém, indica que a Apple já trabalha na nova versão do Mac OS X e que o time do WebKit estaria envolvido em seu desenvolvimento, é claro.

A ausência de conteúdo mostra que os trabalhos estão só começando ou, quem sabe, que informações sobre as novidades do WebKit no Mac OS X 10.6 ainda não podem ser reveladas nos nightly builds.

“Hello, Internet!”

WebKit’s core JavaScript engine just got a new interpreter, code-named SquirrelFish.

SquirrelFish is fast—much faster than WebKit’s previous interpreter. Check out the numbers. On the SunSpider JavaScript benchmark, SquirrelFish is 1.6 times faster than WebKit’s previous interpreter.

What Is SquirrelFish?

SquirrelFish is a register-based, direct-threaded, high-level bytecode engine, with a sliding register window calling convention. It lazily generates bytecodes from a syntax tree, using a simple one-pass compiler with built-in copy propagation.

SquirrelFish owes a lot of its design to some of the latest research in the field of efficient virtual machines, including research done by Professor M. Anton Ertl, et al, Professor David Gregg, et al, and the developers of the Lua programming language.

Some great introductory reading on these topics includes:

• The Structure and Performance of Efficient Interpreters (Introduces the fundamentals of virtual machine design and explains the importance of direct threading)
• Virtual Machine Showdown: Stack Versus Registers (Details the benefits of register machines, and the importance of copy propagation)
• The Implementation of Lua 5.0 (Outlines the implementation of a real-world register-based bytecode engine, with a sliding register window calling convention)

I’ve also pored over stacks of terrible books and papers on these topics. I’ll spare you those.

Why It’s Fast

Like the interpreters for many scripting languages, WebKit’s previous JavaScript interpreter was a simple syntax tree walker. To execute a program, it would first parse the program into a tree of statements and expressions. For example, the expression “x + y” might parse to

        +
      /   \
     x     y

Having created a syntax tree, the interpreter would recursively visit the nodes in the tree, performing their operations and propagating execution state. This execution model incurred a few types of run-time cost.

First, a syntax tree describes a program’s grammatical structure, not the operations needed to execute it. Therefore, during execution, the interpreter would repeatedly visit nodes that did no useful work. For example, for the block “{ x++; }”, the interpreter would first visit the block node “{…}”, which did nothing, and then visit its first child, the increment node “x++”, which incremented x.

Second, even nodes that did useful work were expensive to visit. Each visit required a virtual function call and return, which meant a couple of indirect memory reads to retrieve the function being called, and two indirect branches—one for the call, and one for the return. On modern hardware, “indirect” is a synonym for “slow”, since indirection tends to defeat caching and branch prediction.

Third, to propagate execution state between nodes, the interpreter had to pass around a bunch of data. For example, when processing a subtree involving a local variable, the interpreter would copy the variable’s value between all the nodes in the subtree. So, starting at the “x” part of the expression “f((x) + 1)”, a variable node “x” would return x to a parentheses node “(x)”, which would return x to a plus node “(x) + 1”. Then, the plus node would return (x) + 1 to an argument list node “((x) + 1)”, which would copy that value into an argument list object, which, in turn, it would pass to the function node for f. Sheesh!

In our first rounds of optimization, we squeezed out as much performance as we could without changing this underlying architecture. Doing so allowed us to regression test each optimization we wrote. It also set a very high bar for any replacement technology. Finally, having realized the full potential of the syntax tree architecture, we switched to bytecode.

SquirrelFish’s bytecode engine elegantly eliminates almost all of the overhead of a tree-walking interpreter. First, a bytecode stream exactly describes the operations needed to execute a program. Compiling to bytecode implicitly strips away irrelevant grammatical structure. Second, a bytecode dispatch is a single direct memory read, followed by a single indirect branch. Therefore, executing a bytecode instruction is much faster than visiting a syntax tree node. Third, with the syntax tree gone, the interpreter no longer needs to propagate execution state between syntax tree nodes.

The bytecode’s register representation and calling convention work together to produce other speedups, as well. For example, jumping to the first instruction in a JavaScript function, which used to require two C++ function calls, one of them virtual, now requires just a single bytecode dispatch. At the same time, the bytecode compiler, which knows how to strip away many forms of intermediate copying, can often arrange to pass arguments to a JavaScript function without any copying.

Just the Beginning

In a typical compiler, conversion to bytecode is just a means to an end, not an end in itself. The purpose of the conversion is to “lower” an abstract tree of grammatical constructs to a concrete vector of execution primitives, the latter form being more amenable to well-known optimization techniques.

Therefore, though we’re very happy with SquirrelFish’s current performance, we also believe that it’s just the beginning. Some of the compile-time optimizations we’re looking at, now that we have a bytecode representation, include:

• constant folding
• more aggressive copy propagation
• type inference—both exact and speculative
• specialization based on expression context—especially void and boolean context
• peephole optimization
• escape analysis

This is an interesting problem space. Since many scripts on the web are executed once and then thrown away, we need to invent versions of these optimizations that are simple and efficient. Moreover, since JavaScript is such a dynamic language, we also need to invent versions of these optimizations that are resilient in the context of an unknown environment.

We’re also looking at further optimizing the virtual machine, including:

• constant pool instructions
• superinstructions
• instructions with implicit register operands
• advanced dispatch techniques, like instruction duplication and context threading
• getting computed goto working on Windows

Performance on Windows has extra room to grow because the interpreter on Windows is not direct-threaded yet. In place of computed goto, it uses a switch statement inside a loop.

Getting Involved

If you’re interested in compilers or virtual machines, this is a great project to join. We’re moving quickly, so the best way to come up to speed is to log on to our IRC channel.

As always, testing out nightly builds and reporting bugs is also a great help.

Extra Bonus Updates

We’ve got some extra bonus info: very early draft documentation of the SquirrelFish VM’s opcodes. For those of you who know about VMs, you may find this enlightening, for those who don’t, you may find it is simpler than you expect.

In addition, we have a detailed comparison of Safari 3.1 vs. SquirrelFish, looking at the individual tests, it is interesting to see which sped up the most. If you look at this comparison to Safari 3.0, you can see that we’ve sped up 4.34x overall since Safari 3, and have improved some kinds of code by over an order of magnitude.

SquirrelFish around the web: There’s lots of interesting discussion in the reddit article about this post. And posts from key SquirrelFish developer Cameron Zwarich has performance data and other info, as does occasional WebKit contributor Charles Ying.

(Via Surfin' Safari.)

Ieri è stato rilasciato GNOME 2.22.2, il penultimo aggiornamento del ramo 2.22 del famoso Desktop Environment. L'uscita di GNOME 2.22.3 è attesa per il 30 giugno 2008, mentre in settembre uscirà la versione 2.24, che promette tante interessanti novità come il passaggio del web browser Epiphany al WebKit engine (lo stesso usato da Safari). Per quanto riguarda GNOME 2.22.2, non ci sono grossi cambiamenti. Il team si è concentrato sopratutto sulla documentazione e sulle varie traduzioni. Il secondo aggiornamento alla versione 2.22, che tra l'altro è stata dedicata a Raphael Higino, un membro dello GNOME translation team e di GNOME Brazil, morto a 24 anni in un incidente motociclistico, è servito a rendere ancor più solido il ramo stabile del DE. Anche questa volta Foresight ha seguito, con puntualità impressionante, il ciclo di rilascio di GNOME, e a poche ore dall'uscita di GNOME 2.22.2, era già disponibile Foresight 2.0.2 GNOME Edition che lo integra.

Per installare la nuova versione di GNOME dai sorgenti, gli sviluppatori, consigliano di utilizzare uno strumento di compilazione. GARNOME, basato sul "GAR ports system" creato da Nick Moffitt, scarica, compila e installa GNOME, dall'ultima tar ball rilasciata (questo è il manuale). Altrimenti si può scegliere di usare jhbuild, che è stato progettato per compilare GNOME direttamente da SVN.

Articoli correlati:

QGtkStyle: integrazione perfetta delle applicazione KDE in GNOME. Installazione ed uso

Foresight Linux, la distro ultra-aggiornata, che integra GNOME 2.22

Mettiamo un po’ di ordine nel menù di GNOME

You can see performance benchmarks that show a significant increase across the board of tests.

On average the tests show a 4 times improvement (compared to Safari 3.1), with spikes of 12.6x improvements on some access tests, and with the lowest grade of 1.63x for String unpacking.

This is great news. We are now seeing all of the major browsers improving their JavaScript stacks significantly, which means we will be able to do a lot more. If you are building heavy Ajax applications, this is what you dream off, and at the same time you hope that you can stop worrying about older browsers ;)

(Via Ajaxian.)

Vediamo insieme alcuni aggiornamenti che caratterizzano questa importante release:

• Phonon un framework multimediale per riprodurre filmati e suoni
• Webkit Qt API. Esso permette a sviluppatori terzi di includere con facilità nelle loro applicazioni molte delle funzioni proprie di Safari. WebKit è un progetto open source che nasce dalla combinazioni di componenti del sistema grafico KDE e di tecnologie Apple. (dalla Wikipedia)
• Il supporto a Windows CE

ed altri aggiornamenti che vi lascio scoprire rimandandovi alla pagina http://doc.trolltech.com/4.4/qt4-4-intro.html

inoltre http://www.riverbankcomputing.co.uk/software/pyqt/download per scaricare PyQt4.4
http://www.riverbankcomputing.co.uk/news/sip-475 per scaricare l'ultima versione di SIP

trovate questo articolo pubblicato sempre da me sull'home page di python-it.org

So also mal flugs die URL von Gmail oder Google Reader eingegeben, das Programm erzeugen und voilà: Fertig ist die eigene Client-Software. Genial. Mit einem richtig schönen schmucken Icon ist das ganze noch besser. Die Icons sollten als .ICNS-Ressource vorliegen. Dann einfach appl.icns benennen und in den Resources Ordner des Programm-Packages hineinlegen (die alte Datei dort überschreiben). Einfach cool.

First off, let me set the record straight and tell you that I am an unqualified supporter of Microsoft technologies such as SQL Server, BizTalk Server, Commerce Server and the .NET Framework. I'm also a Microsoft MVP for Commerce Server and an avid C#, ASP.NET and BizTalk developer. In my day job, I use these Microsoft technologies to create business-to-business e-commerce applications for the company that I work for.

But at night and on the weekends, I moonlight as a freelance web developer using mostly non-Microsoft technologies such as Ajax, PHP & mySQL. In both areas I strive to create "standards" based web sites and applications and my overriding goal is always to "create the best user experience requiring the least bandwidth" and this is where WebKit comes in.

When you think about how ASP.NET developers create great user experiences today, two things come to mind; ASP.NET AJAX and Silverlight. Both technologies allow developers to create really great user experiences on the web but only at the cost of bandwidth (download time, initial or otherwise). The same rule holds true for Flash and any Ajax library such as Prototype, script.aculo.us or jQuery (all of which are excellent Javascript frameworks).

Now think about the potential to create great user experiences using nothing more than the new HTML5 and CSS3 capabilities found in the latest WebKit builds. Gradients, shadows and rounded-corners without images, transforms and animation without Javascript, client-side data that goes way beyond cookies and support for highly compressible vector graphics (SVG). All in a fully "standards" based HTML/XHTML/CSS framework that (hopefully) renders the same in all browsers, both desktop and mobile.

Now we're talking about actually having the tools to "create the best possible user experience requiring the least bandwidth". This may be a pipe dream but it looks like the WebKit folks and I are drinking the same Kool-Aid at the moment!

Currently listening to: "Still Feels Good" by Rascal Flatts

What you may not be aware of is some of the very "advanced" features Safari (WebKit actually) has in the works which may well change the way we think about developing Web 2.0 applications.

1. Web Fonts
2. Client-Side Database Storage
3. CSS3 Transforms
4. CSS3 Animation
5. SVG Support
6. CSS Gradients
7. CSS Box Shadow
8. And Many, Many More...

If you look at any one of these new features individually, they are very cool! If you look at integrating these new features together, you begin to see the potential for replacing today's Javascript (Ajax) "eye-candy" with native browser rendering support!

And why you ask, is WebKit (and Safari) pushing these advanced features out the door so quickly?

Safari on iPhone!

Starts you thinking, doesn't it!

Currently listening to: Eric Merienthal's "Just Around the Corner"