I much prefer the use of migrations, then the DataMapper approach, but using DataMapper made for an easier demo.

“Also create the files with the properly content !!!.

app/views/posts/index.html.erb
app/views/posts/edit.html.erb
app/views/posts/show.html.erb
app/views/posts/new.html.erb”

I think what you mean by that is why doesn’t Mack create all the form elements when you run scaffold like Rails does. Well, there’s two reasons for that.

One, is that Mack is an ORM agnostic framework. That means you should be able to use any ORM you wish with it. There are basic hooks for ActiveRecord and DataMapper, however.

Two, is that I’m still very much so working on the core components of the framework. The scaffold generator is really there to just ‘lay things out’ a bit for you. Down the line when I have more time, and a more of the core feature set implemented I plan on returning to this, and trying to improve upon the scaffold generator for both DataMapper and ActiveRecord. Of course, with that said, I’m looking for other contributors, so if you’re interested and want to write that part of the code, I’m happy to chat with you.

‘posts_index_url’ gives you ‘/posts’, so it effectively does with ‘posts_index_path’ does in Rails. It’s absolute, but does not give you the full domain path. This was done for a couple of reasons, the big one being that by not giving you the full domain path, you’re able to use the routing methods without a request. This makes it easy to use them in Rake tasks, emails, etc… something that Rails has a big problem with. If you really need the domain on there, then write a helper method to wrap the *_url methods, or just override the ‘link_to’ method.

Currently there is no support for nested resources. That doesn’t mean there won’t be support for them down the line, it’s just right now, I’m one guy, and I’m trying to write the core features, and the features that are different from Rails, before I write things like nested resources.

As far as skins/themes are concerned, that’s actually on my list of things to tackle. It’s a big need the company I am working for needs, and something that will be at the heart of Mack in a future release. Right now there is the standard layout support, similar to Rails.

I hope that answers your questions. Please feel free and hit me up with more. I’m always welcome to feedback, I think it makes for a better code base in the end.

Thanks Dinooz.

class Post This can create the properly migration file or update the app/models/post.rb file automatically.

class Post < DataMapper::Base
property :title, :string
property :email, :string
property :body, :text
property :created_at, :datetime
property :updated_at, :datetime

validates_presence_of :title
validates_presence_of :body
validates_presence_of :email
end

Also create the files with the properly content !!!.

app/views/posts/index.html.erb
app/views/posts/edit.html.erb
app/views/posts/show.html.erb
app/views/posts/new.html.erb

So what is left for you to do just update your routes file and start your web server. =)

Note
when you mention posts_index_url, does exist the post_index_path also ???
What about the comments, can you elaborate on how to add a comments relation in this framework ???
How can enable the usabe of nested resources ???
Any possible ideas on implement basic themes/skins ???

So far looks good , I think will give a try keep doing the good job.