This question is often asked, but is never answered properly. So how to measure framework speed? Let me also explain why “scalability” is more important than general “performance”.
Read more
Have you seen some potential in Agile Toolkit? If you are still unsure if you should adopt it in your critical product, read the following introduction to Agile Toolkit. This introduction is oriented at senior software engineers and describe some of the problems Agile Toolkit will help you solve in the long run.
Or
I’m pleased to announce the update of the “codepad”, which has been transformed into much more powerful Example browser and Object inspector.
http://codepad.agiletoolkit.org/
One awesome tool I’ve created in the process is the right-side “inspector”. Inspector examines the current page and objects on that page looping through them and finding objects which were added by the example. You can then mouse-over the objects to highlight the objects on the page or click to see source code of that class.
Enjoy all the examples and I plan to add more examples (from http://demo.atk4.com/) soon.
Would you like to look further into how codepad works? You can get it from github:
git clone git://github.com/atk4/atk4-codepad.git git submodule init git submodule update
Add your own examples into page/* to share them with your friends. You can also “fork” codepad and push back some of your own examples if you would like to see them in the Codepad.
I am working on a project, which features numerous places where it’s possible to select a client from a drop-down. I thought about creating a single class, which will work as a button, but would also contain the logic of actually adding the client through a form in jQuery UI Frame.
As a result, I’ve created a universal “NewEntry” button, which can be added anywhere like this.
[php]
$client=$form->addField(‘autocomplete’,'client_id’);
$client->setModel(‘Client’);
$client->add(‘Button_NewEntry’,null,’after_field’)
->setLabel(‘New Client’)->setModel(‘Client’,array(‘name’));
[/php]
This produces the following:
Agile Toolkit is awesome because it’s simple. Sometimes it lacks a feature, but it’s simple to add this feature. Having all those features in the core would be an over-kill, so many features are not in there on purpose.
An example is this controller, which will make items in your Grid order-able. Here is the screenshot of how it performs:
This sexy interface is implemented as a stand-alone controller in Agile Toolkit in about 70 lines of code and small bit of HTML, no JS or CSS. But more importantly, it can be added to any Grid out there with just this:
[php]
$grid->add(‘Controller_GridOrder’);
[/php]
Why is it important / cool?
When you develop your software, your goal is to get it done. This controller took me about 30 minutes to implement. To properly document it and share, it would take some more time.
I’m pretty sure it’s same for you. If you are developing with Agile Toolkit, you might have a few interesting bits out there. My plan is to make it super-easy for you to throw a link to your Github repository and then let others convert your code into the properly documented add-on. Instead of re-inventing it, they could clean it up and document.
This way we don’t have to re-implement every bit and we’ll have a great library of add-ons growing!
First – put your code into github and make it public. Even if it’s your personal project, it won’t hurt.
I’ll be working on the section on www.agiletoolkit.org where you will be able to “share” some goodies you have in your code. Leave it to other devs to extract it from your code, clean it up and improve. Your contribution to Agile Toolkit community would be highly appreciated.
OpenSource is an amazing phenomena, but how safe open-source projects are? Would commercial project be safer over the community-supported project?
Frameworks can’t exist without their core team and In this article I look at how different PHP frameworks are supporting their core developers.
We listen to your feedback and are cleaning code, adding PHPDOC support and more stuff. The “master” branch in github was switched to a version in preparation of 4.1 release.
If you were using 4.0 and are not quite ready to update then checkout “4.0″ branch from git. If you were on 4.1-beta1 then you are welcome to try “master”. If it produces errors, you can fall back to “4.1″ branch.
Of course we would love if you use “master” and gave us feedback on the errors you encounter. There are few minor thing to consider if you are switching from 4.1b1 though. Official upgrade guide is not out yet, hence the blog post:
I wanted to tell thanks to those few, who have offered to translate Agile Toolkit into different languages. Verison 4.1 is coming with multi-lingual support and we will also work with volunteers to translate documentation on this website.
If you are willing to help us out with translations as we prepare documentation, you need just the knowledge of Git. www.agiletoolkit.org is built on the framework itself, so it separates content from the logic. Here are the steps for you to get startedt:
Follow on the files as they are being changed. We are doing severe improvements on our front page and introduction. Look into lib/Sitemap.php to see how documentation is going to be laid out.
Huge thanks to those helping us out and making Agile Toolkit more accessible to more people!
