Antares is a project, which was born from a development department for a
magazine publishing firm. The development staff was broken down into three
people; two developers, and a single designer. From this scenerio, it was
realized that something had to be done in order to provide worthy, expandable,
and diverse code quickly.
The birth of the project was from a few simple classes which where re-used
in numerous of projects. This lead us to see how we could package these classes
and make a quick core layout for each project that was assigned. As time
progressed, it was noticed that more indepth functionality would be required
in order to fully accomplish what was desired by Antares.
Slowly, Antares grew into a project which was realized it had some potential
to assist the general populace. From there, the project took a new turn, and
the 'Code Graduation Process' was designed. Now here Antares stands, ready
to build a community of developers who desire for clean and worthy code.
Antares is a different project from all of the other Framework's which are taking light these days. How is it different you might ask? Some of these differences are listed below:
If you have ever worked in a multi-person development enviroment, you may understand the importance of this. If you have not, the main reason this is needed, is to limit the amount of time that each department must rely on each other to complete their task. For example, you have a department which does nothing but the design aspect of the project, they can complete their side of the project without having to worry about their developer being ready with the business logic.
This is a new approach to creating a full fledge framework, which caters to the basis of necessity. It also helps the project in finding worthy developers who have the same mentality in how suitable programming should be done. The jist of this, is functionality is first introduced into the project as a module. Once it becomes apparent that the functionality is suitable for the API, the code will be refined by a core developer and graduated into the API. If the functionality is still found to be even more crucial to over all functionality, it will then again be refined by a core developer to be graduated into the Framework of the project.