Feemo

I have recently checked in a new project into code google. The project name came out of a play on words File Mover but since fimo would make the i sound kind of strange in my opinion. I changed the spelling to two e's instead so that the i could only be pronounced one way. Anyway, the concept behind Feemo is simple - to allow me to perform tedious repeatable folder manipulation tasks quickly and easily.

I was recently inspired by Martin Fowler's talk on Domain Specific Languages(DSL) and therefore I decided to create it in a way that the DSL can specify the instructions and then the FeemoRunner can take over and process them. If you are interested in something like this, take a look at the project. Currently it is not ready for delivery it still has quite a way to go before it can be used but I project that I can get enough going to perform some of the basic operations like processing the clean folder commands and move folder commands in the very near future.

I am also enrolled in an XML class and have a research project to write on an XML topic so I decided to tie Feemo into it. That is why Feemo will support both FeemoScript and FeemoXml.

You can find more information about Feemo here.

Comments

Ricardo said…
I like the name and the idea. I am downloading this now - thanks for sharing!
April 9, 2010 at 7:15 PM
Fernando Zamora said…
This is just the start of the project. I am excited about it and hopefully it can grow. This is based off of an idea that has been simmering for a long time.
April 10, 2010 at 2:34 PM
Post a Comment

Popular posts from this blog

Putting Files on the Rackspace File Cloud

Recently, I’ve been playing around with Asp.Net MVC and I (along with some friends) am creating an Asp.Net MVC application that can access files from our website. This means that files must display on the site as well as provide a way to download/upload them. I won’t give away all the details of the project but I will say this: Sharing photos is one of the driving forces for our project.  The files are only image type files( jpg, etc) The files must be uploaded by the users and stored somewhere within our system.  We don’t necessarily know at this time how much storage space we need but we think that we will need a little at first but possibly a lot more down the road. This means that the storage of these files must be scalable. The uploading of files must be controlled by our system.  Right off the bat we started our application and were uploading files to the web server with no problem.  We only did it this way to kind of prove our system model. We wer...
Read more

Setting Up XnaMobileUnit to run unit tests in Windows Phone 7 XNA Games

Image
Introducing XnaMobileUnit I decided to roll my own unit test framework for Windows Phone 7 XNA games.   I have a couple of reasons why I decided to roll my own.  Among them was the fact that you cannot reference regular .Net assemblies from Windows Mobile Framework.  That means that referencing NUnit was out of the question.  Also using some of the other libraries that can be used for Silverlight Applications didn't quite feel right for me. The framework that I have created, XnaMobileUnit, is very simple to use and provides all the necessary functionality to run unit tests.  I am still working on the framework to provide a few more capabilities and features, but for the most part it is ready to use out of the box.  XnaMobileUnit is open source licensed under the Apache 2.0 License and can be downloaded from http://code.google.com/p/xna-mobile-unit/ .  I recommend downloading the latest source and compiling it then referencing the new DLL. Othe...
Read more

Reasons to Stay Away from CSLA

We've been using CSLA - Component-based Scalable Logical Architecture in a product for approximately one year and while it solves quite a few problems it violates some major good practices. No Clear Separation of Layers While at the time that we chose CSLA we knew very little about domain driven design, it is no excuse for the framework to possess the data access layer within the business object. This makes it extremely difficult to separate the concerns. As a result, it is difficult to mock the data-access layer creating many problems when attempting to perform unit tests. This also puts the additional responsibility of data access on the business object class, violating the Single Responsibility Principle( SRP ). Data access layer should be totally separated from the business object period. Having the data access within the within the BO class is not the only additional responsibility placed on the class but is the most significant one I can think of. No Context Validation...
Read more