The FED (Front End Development) Process framework takes advantage of the object oriented design approach from MooTools and applies it to the entire scope of front end development.
NEW (2011/AUG/15) - 1.3.1 supports MooTools 1.3, has a bunch of fixes and bundled with new LazyLoader.
With MooTools' object oriented approach however, the framework empowers code separation. That means you can easily break classes into its own files for a much better decoupling of functionality/widget. By applying a good code design, a loosely coupled MooTools class allows your code to be a lot more re-usable. Furthermore, you can package them easier and release them onto the Forge. The only problem is that including each of these classes in its own script tag could cause some performance issues on the front end. Primarily, there would be unnecessary http request for files.
Using a build process, we can keep our code separated while at the same time, packaging all these files into a single script.js would remedy the issue of having the page to make too many http requests. With the FED Process's approach, we've been able to achieve a high re-usability rate of our widgets and a great compression scheme using a minifier such as the YUI Compressor in conjunction of a server-side compressor such as GZIP.
Following such a process would make your life much easier in the long run when your site starts to get heavy on functionality. Another advantage is that it will allow for a friendly and painless multi-collaborator environment. When using SVN or GIT, we almost never run into code conflicts because all the files are so clearly separated. Since the code is built into the /b (build) folder, the build process actually cleans out the /b folder every time. So any conflict in the b/ folder can be ignored.
In some of our test cases and actual production work, we have more than 9000 lines of code without a single conflict when using this process. We believe that releasing our FED Process will help MooTools developers to take advantage of the object oriented nature of MooTools while adding Forge plug-ins into their own projects would be effortless. This is a tried and true development process that is stable and used everyday within our team. If you have any suggestions, then please feel free to let us know at firstname.lastname@example.org
This will seem like overkill at first, but contributes to the maintainability of the process.
A website is being build for this front end framework. Look for it in the coming months.
We will soon add in more demo test cases to better illustrate the process.
Even though the current version is stable, we strive for continuous improvements to our standards and processes. If you have any suggestions, please feel free to let us know at email@example.com
A note on comments here: These comments are moderated. No comments will show up until they are approved. Comments that are not productive (i.e. inflammatory, rude, etc) will not be approved.
Found a bug in this plugin? Please report it this repository's Github Issues.blog comments powered by Disqus