We are getting ready to launch the new homepage for Agile Toolkit. That’s why I haven’t been doing much posts lately.
Things are going to be very exciting soon, so get ready to put your evangelist cap on.
Tags: newsWith some up-coming changes in trunk, we have created a stable 3.9 branch. It is not an official release yet, but if you are using trunk, I recommend you to switch.
Tags: grid, newsWhile we are still debating, most probably Agile Toolkit 4 will be available under the General Public License. It will be dual-licensed under commercial license if you wish to use it in commercial applications. The same principle will apply on all the code, plugins, modules.
Tags: supportHi. Few people have had difficulties understanding which approach is better to choose, since so many things can be done in different ways. This post will clarify you regardless where you should put your code.
Tags: add-ons, javascript, mvcI 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)
Tags: news, path, urlSeveral of current components are relying on their own implementation for file searching:
PathFinder is designed to be a system-wide controller which will take all those searches under control. It introduces concepts of Locations and resource types (such as ‘js’, ‘html’ for templates, ‘php’ etc)
Tags: pathFor 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.
Tags: url
