Now on stock: RSpactor 0.9.16
RSpactor 0.9.16 is ready for download. Grab your copy from here. Please report any problems or feature requests at Lighthouse.
So what’s new?
.. not very much. I’ve completely rewritten the app, so there was no time and space for new features, but RSpactor should be a lot more stable and responsive now. New features are coming within the next releases. So stay tuned..
Comments
Mikel Lindsaar said on Monday, August 04, 2008:
Hey, looks like a great tool, but I also have a G5 that I use for other development, any chance of a universal binary?
I tried downloading it and building it on the G5, but it wasn't that easy :)
Happy to provide any help or do it myself with some direction.
Mikel
rubyphunk said on Monday, August 04, 2008:
Oh. I didn't thought about a universal binary yet, but I will have a look on it.
Thanks for the idea :)
Mark Wilden said on Monday, August 04, 2008:
Nothing changed? :)
RSpactor looks very different from the gem I installed. I don't really want a GUI app, so I think I'll stick with the commandline version. Any chance that will get updated? About the only problem I have with it is that it eats keystrokes when you're debugging. Otherwise, I love it!
///ark
rubyphunk said on Monday, August 04, 2008:
You may have missed RSpactor 0.9.10.. I stopped maintaining the gem version a few month ago. However there is a fork of the gem on Github by pelle.. http://github.com/pelle/rspactor.
I for myself had problems with the gui version too. But by the time I cannot imagine working without the .app anymore..
Mark Wilden said on Tuesday, August 05, 2008:
OK, I gave the GUI RSpactor a try, but I don't think it will work for me, as it is. Some of the problems I found were cosmetic; but others were functional.
1. (Minor) When the app first opens, the only text is "Welcome :)". Now, I know that you've spent a lot of time working on RSpactor (applause!), but for the rest of us, it's a tool. We don't need to be welcomed (with or without a smiley). It's unprofessional.
2. There is no indication of how to actually use the program. The time it took to welcome us could better be spent in adding a line about what to do. I finally figured out that you should type the path to the root level of your app in the input line at the top. First I tried "~/twistage" and clicked Run. The button throbbed, but nothing else happened. If you don't like the contents of the input line, say so! When I typed the full path to the root, it worked.
3) It looks like I'll have to type the full path to the root each time I start the program.
4) (Minor) The status Growl at the end of testing shows the time taken to seven decimal places. Again, I think that looks unprofessional.
5) It would be great if RSpactor could support other editors than TextMate.
6) After running all my specs, I got a Growl saying "Error loading spec environment!". First, exclamation points in messages are so 1980. Don't shout at your users. Second, there were in fact no errors - just warnings. Some apps just have warnings (particularly redefined constant warnings). In our case, at least one of the warnings comes from Rails - we can't do anything about it. If I have to click away a big Growl every time, that's going to be pretty irritating. Finally, there were warnings that do not appear when running rake spec, autotest, or the RSpactor gem. That's kind of scary - implying that the GUI RSpactor is loading things differently than those programs.
7) When an exception is raised during a test (e.g. NoMethodError), the GUI lists the file as having failed, but has nothing else to say. There's no way (that I can see) to determine the problem. The filename isn't clickable.
8) The spec that raised the error was videos_controller_spec.rb. When I made a change to videos_controller.rb and saved it, nothing happened in RSpactor - the spec was not rerun. This is pretty much a deal-killer, as you can imagine.
I have none of these problems with the gem, so I'll continue to use that, since I really like how RSpactor responds to FS events, instead of polling.
There are some really nice things about the GUI version, but I would suggest that it needs a wider beta-test.
I've taken the time to post these things not to give you a hard time, but in hopes that these issues might be addressed, because I think RSpactor has great potential to supplant autotest in the Mac world.
///ark
rubyphunk said on Wednesday, August 06, 2008:
You're right. The current release is a first beta version and there are lot of things to do. I keep your list of things in mind for the next release..
Thanks for your comment.