tag:blogger.com,1999:blog-89449241117093833182026-02-11T05:35:03.477-08:00erosbhttp://www.blogger.com/profile/08287601607321533837noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-8944924111709383318.post-66489169177125769452012-08-20T13:00:00.000-07:002012-08-22T01:31:10.205-07:00

In this blog post I'm announcing the CyclonePHP project for the PHP developer community. In short, CyclonePHP is (will be) an application development framework for PHP 5.3 consisting of some loosely coupled libraries. The aim of the project is to provide a reliable RAD solution for web developers willing to create medium-sized business applications with fairly long maintenance interval.

erosbhttp://www.blogger.com/profile/08287601607321533837noreply@blogger.com0tag:blogger.com,1999:blog-8944924111709383318.post-14749111099601895892011-09-02T09:15:00.000-07:002011-09-02T09:31:01.724-07:00

All web developers know that any kind of text which comes from user input, should be sanitized before rendering. You must remove all dangerous HTML tags to avoid HTML and Javascript injections, XSS attacks - good old well-known issues, I'm not going to bore you with their concept. When you sanitize the input, in most of the cases you don't want to remove all HTML tags, you want to give your user

erosbhttp://www.blogger.com/profile/08287601607321533837noreply@blogger.com2tag:blogger.com,1999:blog-8944924111709383318.post-56194821263218263622011-07-11T05:07:00.000-07:002011-07-11T06:18:27.678-07:00

The usage of getter and setter methods instead of public attributes became very popular in the PHP community, and it's going to become the standard coding convention of so many PHP libraries and frameworks. On the other hand many developers - including me too - strongly unrecommend such convention, because of its performance overhead. I wanted to make some performance comparison for years, and

erosbhttp://www.blogger.com/profile/08287601607321533837noreply@blogger.com40tag:blogger.com,1999:blog-8944924111709383318.post-6523037095181248002011-05-27T15:05:00.000-07:002011-05-27T15:05:22.746-07:00

In PHP 5.3 one of the new magic methods was __invoke(). PHP 5.3.0 is not really a new stuff but I have seen nobody using __invoke() yet. In this post I will try to find some use cases when it can be useful. So first of all let's overview how this method works: if you have an object thats class implements the __invoke() method, then the object it becomes a callable. Example: class MyClass {

erosbhttp://www.blogger.com/profile/08287601607321533837noreply@blogger.com5tag:blogger.com,1999:blog-8944924111709383318.post-70111923770078609692011-05-17T04:28:00.000-07:002011-05-17T04:28:44.563-07:00

Inspired by the review published by Gábor Török I bought the book Dive Into HTML5 by Mark Pilgrim. I finished reading it yesterday, and in short I'm a bit disappointed. First of all I should mention that I'm not the primarily targeted reader of the book since I'm mainly a PHP developer and I'm not really a HTML guy. Since HTML5 is not only HTML but also CSS and JS I was interested in the new

erosbhttp://www.blogger.com/profile/08287601607321533837noreply@blogger.com1tag:blogger.com,1999:blog-8944924111709383318.post-42126633299643442212011-01-24T12:16:00.000-08:002011-01-24T12:25:12.496-08:00

Last night I created a prototype for an interactive debugger for PHP without the need of any IDE-plugin. In this post I'm going to show what I found. Unfortunately you will need some time to put the environment together, but I think it's worth doing it. My target was to create a way how you can view and modify your variables manually at runtime, only by inserting one line code. So let's overview

erosbhttp://www.blogger.com/profile/08287601607321533837noreply@blogger.com1tag:blogger.com,1999:blog-8944924111709383318.post-8982227979627599922011-01-02T10:42:00.000-08:002011-01-02T12:22:45.663-08:00

Yesterday Kohana 3.1 RC1 has been announced and tagged. I think now it's time to get familiar it. In this post I'm going to examine the refactored request execution workflow. Let's start with the bootstrap mechanism. The procedural bootstrap code is in the index.php and application/bootstrap.php since Kohana 3.0. In KO3.1 I can only see a very little difference: the main request execution is

erosbhttp://www.blogger.com/profile/08287601607321533837noreply@blogger.com0tag:blogger.com,1999:blog-8944924111709383318.post-49183527257066283672010-12-20T05:12:00.000-08:002010-12-20T05:13:36.606-08:00

The problem with static members in PHP is the poor initialisation capabilities. The initial value of a static property can only be a literal or a named constant: class MyClass { static $prop1 = 'hello'; //correct static $prop2 = PHP_VERSION; //correct static $prop3 = 1 + 2; //incorrect static $prop4 = my_func(); //incorrect static $prop5 = new AnotherClass(); //incorrect }

erosbhttp://www.blogger.com/profile/08287601607321533837noreply@blogger.com2tag:blogger.com,1999:blog-8944924111709383318.post-29657212581895725522010-11-30T15:00:00.000-08:002010-11-30T15:05:57.509-08:00

Using inheritance for coupling classes is very often used by php developers. At the first glance it seems to be great choice. Subclasses can refer to the members of their parent class as if it were defined in the body of the subclass. The protected keyword is explicitly designed for this kind of usage. Abstract classes are fancy and the abstract keyword is also introduced to enforce the usage of

erosbhttp://www.blogger.com/profile/08287601607321533837noreply@blogger.com3tag:blogger.com,1999:blog-8944924111709383318.post-26006320501687135632010-10-16T17:34:00.000-07:002010-10-16T17:34:43.858-07:00

When I started working with php frameworks, I began it with Code Igniter. Not so later I switched to Kohana, and I still actively use it in my everyday work. In the first post of my new blog I want to give a brief summary about the framework. What it is, what makes it unique and how does it basically work. Kohana is a pretty minimalistic and lightweight framework. It is not (and it does not

erosbhttp://www.blogger.com/profile/08287601607321533837noreply@blogger.com0