If you don’t know what the awards are about:

“The .net Awards celebrate the best in web design and development, and are brought to you by the world’s best-selling magazine for web builders - .net. The 17 categories for 2009 range from Design Agency of the Year and Mobile Site of the Year through to the Infamy Award, and once you’ve voted you can use our Twitter widget - over there on the left - to tell your friends about the Awards! This year we have a fantastic group of judges including the likes of Jeffrey Zeldman, Paul Boag, Andy Budd, Christian Heilmann, Jason Santa Maria, Jon Hicks, Ryan Carson and Jonathan Snook!”

The magazine itself is no less than the .net. You can find my article in the ‘technique’ section of issue 191. You can find out what’s in issue 191 here

The article itself is a tutorial on how to put together an Ajax Chat for your website and I’m very proud of it. I will post a PDF version soon.

Stay tuned.

Download Mac OS X Mouse Cursors Easy Installer

Thanks to Shinde for uploading the cursors to Winmatrix.com

When talking to a SOAP interface the first thing you want to do is obviously connect to the endpoint:

This looks correct and innocent, however it produces this nasty error:

Changing SOAPClient parameters doesn’t help and disabling wsdl cache in php.ini doesn’t do much either.

After googling a bit I found a couple of bug reports. It turns out PHP has issues talking to endpoints over SSL. *Sigh*.

Here’s a workaround I came up with to force PHP to connect:

As you can see the idea is simple. Just turn off error reporting before instantiating soapclient and restore it afterwards.

I hope this helps some of you frustrated by this bug.

Things you need before you start:

• A SSH server between you and the shares you want to connect to. It may be running on the same machine as the shares you want to access.
• File Sharing (Windows) or Samba (Linux) configured correctly on the machine you want to access. Make sure your firewall lets the SSH server connect to your Samba or Windows shares.

1st Step: Create a local loopback interface

We need to create a loopback interface on your local computer first. There is a lot of HOWTOs on the web describing this. I suggest you read this one. As soon as you have the loopback working and putting properly forwarding ports to the local loopback interface, go to step 2.

2nd Step: Set up the tunnelling app

So you have the forwarding working now. Technically, that’s all you need. However, if you plan to use shares on a daily basis, there are a few things you will notice:

• It’s annoying to have the putty window open all the time,
• If you close it, your shares will become unavailable,
• If your network goes down for a while, putty won’t be able to reconnect your ssh session.

There’s a solution to these problems: a tunnelling tray application. Personally, I like myentunnel. It’s a simple wrapper for plink.exe from the putty package. Sitting quietly in the task-bar’s tray, it’s unobtrusive and reconnects automatically after a network failure.

Install and run myentunnel. Then set your hostname, username and password stuff in the Settings tab and go to the Tunnels tab. Add the Samba port and IPs in the Local box, press Save and then Connect. If putty connected and forwarded the ports properly, myentunnel should work without a hitch too.

If you have multiple servers to connect to, you can create server profiles. Read the myentunnel documentation for details.

That’s all, enjoy.

Features:

• Small, free and easy to install and use
• Automatically finds any images in the folder specified and scales them down if they are too big
• Zips the folder, opens your email application (Outlook Express by default) and creates an attachment for you.
• Warns you if the compressed folder is too big to send by email
• It’s localised. Currently it speaks English and Polish
• No administrator privileges required to install and run
• No additional software required to work properly

Download Paczkator 0.8 now!

Paczkator is distributed under the GPL2 license, which means the program is FREE for both private and commercial use. You can also redistribute and modify it. If you do so, I would be grateful if you notified me.

Feel free to contact me if you have questions or suggestions concerning Paczkator.

Version History:

• 0.8 - current release: added localisation, installer and fixed a few bugs
• 0.6 - improved image recognition and scaling procedures, a bug-fix release
• 0.5 - initial release

  Chcesz iKlasę? Kliknij dodaj do strony domowej

Już niedługo iKlasa będzie dostępna także jako kanał RSS.

Jeśli masz jakies sugestie co do gadżetu - zapraszam do komentowania.

English: iKlasa is an iGoogle gadget which displays a feed of latest friends photos from a Polish social-networking website nasza-klasa.pl

Here’s what I was looking for:

• as many windows-like (CUA) key bindings as possible. At least Ctrl-C, Ctrl-V.
• syntax coloring
• basic editing functions like search&replace
• needs to work on a VT as well as a console without rebinding keys
• minimum configuration

These features are not particularly demanding, are they? Well, I tried at least a dozen various editors and couldn’t find any that would meet these requirements. Not until I stumbled upon Diakonos.

Diakonos is a simple programmer’s editor for the Linux console that I find almost ideal. It’s open-source, it has all I need and it works out of the box. I’m not going into details (you can read about its features on the homepage), just a screenshot and a list of pros and cons.

Pros:

• very windows-like key bindings (all that I use, I didn’t rebind a single key!)
• no configuration needed (although you can configure it pretty extensively if you want to)
• works on a VT as well as console without reconfiguring putty, .inputrc or anything
• has all the features you would expect in a basic programmers editor (regexps, etc)

Cons:

• It’s slow. It is really slow when compared to any other editor (even Emacs). It’s written in Ruby, which is an interpreted language. I’m not sure if it is for Ruby or the author’s laziness but I don’t really care. It works sufficiently fast on my hardware. It saves a lot of my time which is more valuable to me than cpu cycles.
• Syntax coloring has some problems. I think it has something to do with switching contexts. When editing a PHP file with HTML in it, the coloring sometimes gets funny. Well that’s not a major drawback for me too.

To summarise. If you’re frustrated with complexity of Vim and Emacs, try Diakonos.

• It had to be pure a XHTML/CSS site. No PHP or any other server-side scripting used on the production server. That of course implied I couldn’t use a database.
• I had to transfer all the texts, product descriptions and images from MS Word documents I received from the client.
• The site had to be multilingual, so even more data to insert from *.docs.

The prospect of manually cutting and pasting those things from Word to XHTML sources didn’t sound exciting so I decided to use some scripting to do the tedious job for me. Here’s what I did:

• Firstly, I made XHTML layouts from images I received from my friend who took care of designing the whole thing. I included a bit of JavaScript eye-candy to to make the site more attractive.
• Then I developed a minimalistic CMS using PHP for automatic generation of product entries and pages from CSV input. It could also export the whole site to separate XHTML and CSS files.
• Then I made a couple of Perl scripts to convert *.docs to HTML, extract all the data from them (images and tabular data) and create CSV files.
• Finally I fed my minicms script with the CSV data and rendered everything to pure XHTML pages.

Of course not everything went OK automagically. Scripts needed quite a bit of tweaking because *.doc files didn’t have a regular structure and some things just were faster to import manually. However, the site was ready in half the time I would have needed to create it by hand and I saved myself from some serious headaches.

Screenshots of the result (you can take a look at the live site here):

Note: Decowood logo is a property of Decowood company. Both logos and pictures of products are used only for the purpose of presentation. Currently the site is maintained by a third-party contractor so it may look different.

I decided to give some of the generally available frameworks a try. After some time of playing with open-source solutions I chose CakePHP. I liked CakePHP the most because of its conventions, model relationships and the fact it worked with both PHP4 and PHP5.

PlastiCMS was my first commercial project created with CakePHP. It’s a custom-built CMS for managing a company website with an integrated E-commerce application.

Features of PlastiCMS include:

• Page management. You can organise pages in a classical tree structure, which is not trendy but suitable for a company site. Navigational elements are automatically generated using the page tree.
• TinyMCE rich text editor. You can edit pages the way you edit MS Word documents.
• An Image Gallery with a fancy Web2.0-like presentation using JavaScript.
• A Catalogue of Products with unlimited number of categories and subcategories. Products can be assigned to multiple categories. Each product can have many variants (colour, size, length). Each variant may influence price of the product.
• Internationalisation. You can run several language versions of a site.
• A simple Client Relationship Manager is included
• It’s Google-friendly
• It works with any shared hosting provider
• It’s simple to use for non-technical people.

Screenshots of a live site using PlastiCMS:

Plastiflora’s site design was created by a friend of mine, Marcin from K13 Graphic Design. I made the XHTML/CSS version of his idea.

Note: Plastiflora logo is a property of Plastiflora company. Both logos and pictures of products are used only for the purpose of presentation. Currently the site of Plastiflora is maintained by a third-party contractor so it may look different.