After reading a good number of posts regarding Git as an SCM I had the chance to experience it and use it myself. With the help and guidance of Rein Henrichs, an extremely helpful member of the DataMapper (among others, I'm sure) project.
In working to create new features for DataMapper we are collaborating on a new conditions parser. To do our work, Rein has created an account on GitHub and branched from the existing Git repository for DataMapper. GitHub is a fantastic web application similar to other such web front-ends for SCM tools (such as Warehouse for Subversion). GitHub is currently in closed beta but, I would recommend signing up to join.
Back to Git itself. Like most SCM tools, it is a repository for whatever purpose you may see fit. However, unlike most SCM tools, Git is decentralized, the users are encouraged to branch and merge (with proper workflow), and it is being used by the largest and many, many small software projects, alike. Aside from DataMapper, other small projects include Merb, Mephisto, and the people at Viget Labs.
Rein is currently working on a presentation of Git, and its usage. I'm hoping he will post it up on his blog so that I, and anyone else may share in his extensive knowledge.
Showing posts with label DataMapper. Show all posts
Showing posts with label DataMapper. Show all posts
Monday, February 11, 2008
Friday, February 1, 2008
Merb + DataMapper, I'm Lovin' It
No, this isn't a post about McDonalds. This is a post about Merb (and DataMapper).
As the story goes, I was working on a project involving creating a new web application to match the features of a legacy java application, while maintaining the use of the same exact database. ActiveRecord was worthless in this endeavor. Even with excessive work I could not break it from its conventions.
Since Rails is utterly dependent upon AR I was forced to find an alternative. My saving grace was found with a reference to Merb (Mongrel+erb) by my cousin. Merb is agnostic in many ways. Most importantly with regard to the ORM (object-relational mapping) used. ActiveRecord is supported, as well as, DataMapper and Sequel. In making the switch, I also switched to using jQuery instead of prototype.
All in all, I'm loving it. The only downfall I have experienced is having to dump and restore my database whenever applying a change in my models to the database as the DM migrations are destructive.
Aside from this Merb (and DataMapper) are faster, lighter, and easier to contribute to (if I find a bug, or wish to add features).
As for the project that started this all: it is coming along far better than I could have hoped with Ruby on Rails.
As the story goes, I was working on a project involving creating a new web application to match the features of a legacy java application, while maintaining the use of the same exact database. ActiveRecord was worthless in this endeavor. Even with excessive work I could not break it from its conventions.
Since Rails is utterly dependent upon AR I was forced to find an alternative. My saving grace was found with a reference to Merb (Mongrel+erb) by my cousin. Merb is agnostic in many ways. Most importantly with regard to the ORM (object-relational mapping) used. ActiveRecord is supported, as well as, DataMapper and Sequel. In making the switch, I also switched to using jQuery instead of prototype.
All in all, I'm loving it. The only downfall I have experienced is having to dump and restore my database whenever applying a change in my models to the database as the DM migrations are destructive.
Aside from this Merb (and DataMapper) are faster, lighter, and easier to contribute to (if I find a bug, or wish to add features).
As for the project that started this all: it is coming along far better than I could have hoped with Ruby on Rails.
Subscribe to:
Posts (Atom)
