How does Agile Toolkit Work?

A life of a common web developer requires a deep knowledge of many different libraries, protocols, frameworks, concepts and paradigms. But what if development platform would be capable of managing all that. Developers then would be able to focus on UI logic and business logic and get things done much quicker.

Agile Toolkit is in control of things. While it remains flexible, it introduces a structure for both — business logic and user interface. Developing with Agile Toolkit is much faster. Are you wondering why?

Agile Toolkit is built to be effective!

Without further delay, I'd like to bring in the first example.




$f->addButton('Button Does nothing');

You don't even need the know programming to understand what this code does. That's the first major principle of Agile Toolkit — all the code is simple and very intuitive, yet it uses native PHP5 language.

Did you notice how good form looks? Everything in Agile Toolkit looks great by default. Generic look of all elements are described in "design theme" through HTML/CSS. One theme comes bundled with Agile Toolkit. Get started with development and change theme anytime later.

Simple and sufficient. Things just work out of the box. This applies to everything in Agile Toolkit: Views, Models, Addons. Focus on your goals and Agile Toolkit will take care of the rest.

Agile Toolkit controls the universe. You control Agile Toolkit

Forms, Lists, Menus, Grids and other Views you will encounter while developing already know how to work with the database. That is also true for more advanced Views and Add-ons — they all are capable of interacting with the database.

Agile Toolkit connects everything. Instead of keeping things separate, it integrates things. Components rely on each-other to work in the most efficient way.

Next is an example of a Grid which reads it's row contents from the database:


Name Surname
aa aa
aaaa abbbb
Nikhil Sharma
luizin luizinzin
bla blablabla



Just this small piece of code was sufficient to produce a nice looking table with the data from your database. What's also very important is that components have a built-in security. Data is properly encoded and validated as it is being exchanged.

Agile Toolkit connects everything. Your UI, database, Models, Cloud services. You tweak the details, but all the tough work is done in an efficient and secure way without a chance for developer to do introduce a mistake.

There are 10 ways to be flexible with Agile Toolkit. Here are three:

Countless products have tried to tie User Interface with the Database at the expense of flexibility. Driven by a real Web Projects concepts, Agile Toolkit have been refined since 1999. One of the biggest challenges for the toolkit is the flexibility. Form. How to change its look? How to rearrange fields? How to put text after the field? How to add new field type? How to add JavaScript or AJAX or make form without JavaScript at all? Agile Toolkit holds answer for all those questions. (The Perfect Form)

By this point you might think — database tie-in is very in-flexible. Not in Agile Toolkit. All the database operations are handled through Dynamic Queries. You can change any query in the system at any time by adding joins, clauses, limits, additional fields or sub-selects.

Flexibility (or agility) is extremely important and as you become more familiar you will be able to master new ways.

1. Templates — All Views come with default one. However you can specify different template to any View. Skin can hold many template variations same view and you can add your own too. 2. Spot — When you use $f=$p->add('Form', null, 'destination_spot'); the "destination_spot" defines the placement of your new object. This is placement within the template of parent View. Typically Views would have many spots to choose. 3. Configure — After you call add(); you can still configure your object. There are many things you can change about each copy of the View after it was created.

In this example, we are still adding the Form, but different form template is used. This can produce a significantly different HTML. This method is ideal when CSS change is not sufficient.


Gender Name Surname
F aa aa
F aaaa abbbb
M Nikhil Sharma
M luizin luizinzin
M bla blablabla



This example demonstrates how developer can decide where things appear. Every View can have many useful spots in it's template. Field have "before_field" and "after_field" spots. Example below uses them to put Icon and Button there.

Adding new spots is really easy. Define your own template, and put <?$myspot?> inside. You are done.




set('Try me');

Adding objects is quick and fast. It merely creates a new copy. By interacting with that object further you can "configure" it to behave like you want. Like everything else chaining is optional but it allow you to affect behaviour, appearance of the individual object.


Gender Name Surname Salary
F aa aa -399.60
F aaaa abbbb 200.80
M Nikhil Sharma 801.20
M luizin luizinzin 801.20
M bla blablabla -99.40
- - - 1,304.20


$g->dq->field('length(name)*300.20 - 1000 salary');

As a bonus — it really matters WHERE you add your View. You can add them into $api, $page or ever another View. You never have to worry about conflicts. Each View is designed to be completely self-sufficient and work anywhere. Even if you have 2 identical forms on your page, they will know, which one was submitted.

AJAX, jQuery w/plugins and a better way to write JavaScript

Are you getting excited? The best part is about to begin. Learn how Agile Toolkit finally binds JavaScript with your Views