Creating beautiful URLs with Agile Toolkit

Tuesday, July 20th, 2010|Beginner tips, Version 3|by Romans|2 Comments

By default pages created with Agile Toolkit end with .html. I myself believe that this is a good extension because HTML is being passed over. However it is easy to use different URLs in Agile Toolkit, here is how

Read more

Tags: ,

Symfony 2.0 vs Agile Toolkit 3.8 – part 2 – The View

Wednesday, May 19th, 2010|Misc|by Romans|

This post continues comparison of Agile Toolkit and Symfony 2.0. This post is based on features described in Quick tour – page 2
Read more

Tags: , , , , , ,

Agile Toolkit is branched for refactoring

Wednesday, April 28th, 2010|Core changes|by Romans|2 Comments

I have been working on a refactoring in a separate branch. Right now it looks stable, so I’m putting more details in here:

https://agiletech.ie/svn/amodules3/branches/romans/pathfinder/

(you can try new branch by using svn switch)

Read more

Tags: , ,

Introduction to dialog() integration.

Wednesday, April 21st, 2010|Beginner tips, Version 3|by Romans|2 Comments

jQuery UI have a good support for dialogs and windows. Agile Toolkit 4 takes it to the next level. Most importantly it manages to create contents of the boxes on the fly. Let’s review what we have.
Read more

Tags: ,

New class URL and API::getDestinationURL()

Saturday, April 17th, 2010|Core changes, Version 3|by Romans|3 Comments

For a while now, many parts of library relied on function API::getDestinationURL($page). This function returns the valid URL which will point to specified page. However the implementation of this function was only working for absolute page names, and was built-in into API.

I am adding implementation which relies on a new class called URL. This class instance will be returned by getDestinationURL(). If you happen to pass this object to getDestinationURL again, it will not going to mess up the URL anymore.

Read more

Tags: