Hi guys,
I'm working on getting Remarkable working with Rails 3 / Rspec 2. I don't know how many users care about it, but I figured I'd give users a chance to tell me. The way it looks now, it won't be backwards compatible (primarily because Rspec2 has a lot of refactoring, starting from changing the namespace from Spec to Rspec).
If you need Remarkable for your project, now is the time to speak up.
Ho-Sheng Hsiao http://hosheng.blogspot.com
+1 we definitely use it for our project 
Cool, glad I'm not out in the cold on this one 
I've been making updates on this thread as I go along with the port:
http://groups.google.com/group/remarkable-core/browse_thread/thread/393f086488b1317b
When I get a preview release out, I would definitely appreciate it if you test it in your project.
Ho-Sheng Hsiao http://hosheng.blogspot.com
I care about it
+1
+1
Thanks all. Can you tell me which of the following are more important for your project:
- Remarkable (core) - Remarkable ActiveRecord - Remarkable Datamapper - Remarkable Rails
For my own project, it will be Core and AR. And while I like DM, I'm less likely to use it anytime soon before I use Remarkable-Rails.
The other thing is that there are other projects such as remarkable- paperclip that will break with the new port. Do any of you guys use this?
Ho-Sheng Hsiao http://hosheng.blogspot.com
I care most about:
Remarkable ActiveRecord Remarkable Rails
Do you have anything working yet? I bundled your fork and could not get it working this past weekend. Any status info would be appreciated.
Also, if you need some help please let me know. I am willing to contribute. I am midas on Github.
Thanks,
Jason
I'm still banging my head against Remarkable AR. Here's the current problem:
Rspec2 dynamically generated nested classes under example groups. So for example, when I do
describe "foo" do end
That block actually goes under Rspec::Core::ExampleGroup::Nested_1
Remarkable::AR overrides describe, however, that's not actually getting called or inherited.
Well, let's talk over at http://groups.google.com/group/remarkable-core/browse_thread/thread/393f086488b1317b ... I write a note on what I've done and the current issues as I push up code to the rspec2 branch. Until I get the specs passing, I won't try to run it bundled, so there's lots of things under flux.
Ho-Sheng Hsiao http://hosheng.blogspot.com
Another quick poll
How many folks care about these features:
describe Post do subject_attributes { valid_attributes } def valid_attributes { :name => "my post" } end
it "should give me a post with valid attributes" do # ... end
describe :name => "blah" do it "should give me a shorthand for :name => blah" do # ... end end
For some reason, describe is not being properly overridden. But more importantly, the hash syntax conflicts with the built-in metadata functionality in Rspec 2
I never knew this functionality existed in Remarkable 3.3, and frankly, I don't really use it.
subject_attribute {} is neat but you can just as easily use subject { Post.new(:attributes ... ) }
If there are enough people that care about this, I may give it another crack. At this point though, I'm culling it from the feature set and push for a bundle-able-prerelease.
Ho-Sheng Hsiao http://hosheng.blogspot.com
Ho-Sheng Hsiao wrote:
Hi guys,
I'm working on getting Remarkable working with Rails 3 / Rspec 2. I don't know how many users care about it, but I figured I'd give users a chance to tell me. The way it looks now, it won't be backwards compatible (primarily because Rspec2 has a lot of refactoring, starting from changing the namespace from Spec to Rspec).
If you need Remarkable for your project, now is the time to speak up.
Ho-Sheng Hsiao http://hosheng.blogspot.com
+1 from me I have loads of pending specs for validations and associations!
AR and Rails are the most important ones imo.
Released gems:
remarkable remarkable_activemodel remarkable_activerecord
How to use it in your Rails 3 project:
Issue tracker: http://github.com/remarkable/remarkable/issues
I figure it is better to release some core features early and let people kick the tires.
Remarkable::Rails will need some rethinking, and I'll want to talk to people who actually use it. My needs are for testing a web-service with most of the resource controllers dynamically generated from inherited_resources, so I won't have an active project in which I test any UIs. In particular, please upvote or comment on this issue: http://github.com/remarkable/remarkable/issues#issue/9
For those keeping track, I have Remarkable 4.0.0.alpha2 released:
remarkable remarkable_activemodel remarkable_activerecord
How to use the simplified loading: lambda { }: Remarkable 4.0.0.alpha2
Issue tracker: http://github.com/remarkable/remarkable/issues
Ho-Sheng Hsiao http://hosheng.blogspot.com/