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 howtips, url
I have been working on a refactoring in a separate branch. Right now it looks stable, so I’m putting more details in here:
(you can try new branch by using svn switch)news, path, url
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.
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.url