Linde002::PHP

A small update to the IPv4 Entry widget and a specialized IPv6 Entry widget.

IPv4 has had some small cosmetic code changes and after some small behavioral  modifications (skipping fields has been resolved and stops at the last field) is ready for stable use.

Following a request / inquiry from Frédéric Marand I have also written an IPv6 Entry widget. I’m not familiar with IPv6 so the question of usability & quality must be answered by others. Please let me know what you think.

And now for the code:

IPv4Entry

IPv6Entry

I know, I know. Not strictly PHP-GTK related (although I am working on a GTK project that uses it) but I felt I should share this code with you.

For the people that use the ABC bittorrent client as their preferred way of downloading it shouldn’t come as a surprise that it features a network component that lets you control the client over a TCP/IP connection.

I wrote a class that does the low level interfacing for you using PHP5’s OOP capabilities (there is another class available on phpclasses but it’s written for PHP4) which you can use within your custom application.

It is advisable to create your own filter classes that use this class and processes it’s results in a meaningful way.

Code here.

While creating a wizard for my kiosk application I needed the user to enter an IP-Address. I could’ve just let them enter away and do extensive error checking but using an IPEntry widget just looks cool doesn’t it?

Well here you go for the code.

Drop me a line if you like it or have questions/comments

Whilst showing one of my colleagues the beauty that is PHP-GTK he brought up an interesting concept that I feel has some potential.

The ‘problem’ with many POS* systems is that when you use the software at different locations it becomes quite a challenge to update all the software. Questions like “Who performs the update? The people on site? A company Sys-admin?” arise.

You might solve this by building a framework that, on the client-side, only holds a ‘GUI-starter’ and a SOAPClient component. The rest of your application (including the glade file that defines your application) is downloaded (or directly opened) from the server and all your business logic can be contained within the SOAP Server that is called with a generic request.

I’ll try building a small sample app this weekend.

*Point Of Sale. For those of you who, like me, did not get this one in our daily dose of acronyms whilst growing up.

When I started using PHP-GTK I was at a loss trying to decide what kind of application I should build to learn its intricacies.

This was solved when I stumbled upon kksou’s website where he has placed some sample applications and templates. Among these examples he has created kiosk templates and this got the ball rolling.

My kiosk application has a server-client architecture which means you run the server application on one computer where you add the users and set their access time and clients connect to this server to verify the user.

This application is merely created as an example of the power of PHP-GTK and the way you can mash up several of PHP’s extensions together. At the moment you need to have PHP-GTK with the PDO / PDO-Sqlite extensions enabled in order to run it.

You need to manually edit the client code if you want it to connect to a different ip/port then 127.0.0.1:1987 but work is underway to make this editable in a configuration file.

The admin application features a nifty wizard to set it up (again with thanks to kksou) so enjoy.

Admin application

Kiosk Client

Another PHP-GTK oriented blog. But hey, I needed a place to post my code and insights so here we go.