Cavortify is now powered by hobo.
15 views
Skip to first unread message
Tiago Franco
Feb 11, 2009, 8:51:34 PM2/11/09
to Hobo Users
Hi,
I'm happy to announce that the rework on Cavortify (http://
cavortify.com) was placed in production 5 minutes ago.
Comments are welcome :)
A few metrics:
- The full rework took 167 hours (from scratch!)
- The original estimate was 150
- 2 features were de-scoped (moved to an upcoming version)
- 16.5 hours spent updating hobo (e.g. changes in the permissions sub-
system, etc.)
- 17.2 hours spent developing a friendship system
- Lifecycles are not working as expected. Issue with WEBrick?
- The modeling of the friendship in hobo cookbook is hard to
implement. Symmetric associations are easy to manage if modeled with
two rows.
Main curiosity:
- 3 hours spent deploying on Heroku. 2 days after Heroku moves to
Heroku garden and I decided to use another hosting service!
Main issues:
- I found the behavior of some features in table-plus and the updates
of ajax views hard to manage.
- Table plus can not sort custom collections.
- In place edits can not refresh parts.
Overall feedback:
The final balance is quite positive, as the usability of the
application was enhanced with features out of the box.
PS: if Cavortify is slow, blame the hosting service. Need to find a
better one soon.
Hope this information is useful.
Regards,
Tiago Franco
I'm happy to announce that the rework on Cavortify (http://
cavortify.com) was placed in production 5 minutes ago.
Comments are welcome :)
A few metrics:
- The full rework took 167 hours (from scratch!)
- The original estimate was 150
- 2 features were de-scoped (moved to an upcoming version)
- 16.5 hours spent updating hobo (e.g. changes in the permissions sub-
system, etc.)
- 17.2 hours spent developing a friendship system
- Lifecycles are not working as expected. Issue with WEBrick?
- The modeling of the friendship in hobo cookbook is hard to
implement. Symmetric associations are easy to manage if modeled with
two rows.
Main curiosity:
- 3 hours spent deploying on Heroku. 2 days after Heroku moves to
Heroku garden and I decided to use another hosting service!
Main issues:
- I found the behavior of some features in table-plus and the updates
of ajax views hard to manage.
- Table plus can not sort custom collections.
- In place edits can not refresh parts.
Overall feedback:
The final balance is quite positive, as the usability of the
application was enhanced with features out of the box.
PS: if Cavortify is slow, blame the hosting service. Need to find a
better one soon.
Hope this information is useful.
Regards,
Tiago Franco
Brett Nelson
Feb 11, 2009, 11:09:50 PM2/11/09
to Hobo Users
Very nice look!
Tom Locke
Feb 12, 2009, 3:38:38 AM2/12/09
to hobo...@googlegroups.com
Congratulations Tiago : ) Looks great.
Thanks for the "powered by Hobo" link.
Tom
Thanks for the "powered by Hobo" link.
Tom
MartOn
Feb 12, 2009, 10:27:31 AM2/12/09
to Hobo Users
It would be nice if you could post how you got lifecycle to work on
the user model.
I then think of the e-mail activation and lost password stuff.
You could post it as a receipe on http://cookbook.hobocentral.net/
/MartOn
the user model.
I then think of the e-mail activation and lost password stuff.
You could post it as a receipe on http://cookbook.hobocentral.net/
/MartOn
Owen Dall
Feb 12, 2009, 5:33:13 PM2/12/09
to hobo...@googlegroups.com
Congratulations! Looks great. What hosting service are you now using?--
Owen Dall Barquin International
Owen Dall Barquin International
Scott Bronson
Feb 13, 2009, 2:49:22 AM2/13/09
to hobo...@googlegroups.com
Yes, the hobocentral link is a nice touch.
Alas, it actually links to http://cavortify.com/hobocentral.net :)
Alas, it actually links to http://cavortify.com/hobocentral.net :)
Scott Bronson
Feb 13, 2009, 2:58:16 AM2/13/09
to hobo...@googlegroups.com
Hi Tiago, Cavortify looks great.
I notice you don't mention anything about testing... Did you give
this any thought? Personally I'm using Shoulda in my app but my test
coverage is probably around 0.002%... need to spend some more time on
this!
I agree that table-plus can be tough to use. There are some gotchas
that aren't documented anywhere (like how to write the action for an
index method, it's a little different than the show example cookbook),
and I ran into the custom collection limitation too. I want to free
up the time to really dig into table-plus and understand it well
enough to improve it but there's always been more pressing stuff to
worry about. It's a really cool feature and will hopefully become a
real selling point for Hobo.
Nice work,
- Scott
I notice you don't mention anything about testing... Did you give
this any thought? Personally I'm using Shoulda in my app but my test
coverage is probably around 0.002%... need to spend some more time on
this!
I agree that table-plus can be tough to use. There are some gotchas
that aren't documented anywhere (like how to write the action for an
index method, it's a little different than the show example cookbook),
and I ran into the custom collection limitation too. I want to free
up the time to really dig into table-plus and understand it well
enough to improve it but there's always been more pressing stuff to
worry about. It's a really cool feature and will hopefully become a
real selling point for Hobo.
Nice work,
- Scott
Tiago Franco
Feb 13, 2009, 2:29:23 PM2/13/09
to Hobo Users
Thanks for the positive feedback and support :)
>> Thanks for the "powered by Hobo" link.
1 - We have to give something back :)
>> It would be nice if you could post how you got lifecycle to work on
>> the user model.
>> I then think of the e-mail activation and lost password stuff.
2 - It is in my TODO list. I'll probably be able to write the recipe
near the end of month.
>> Congratulations! Looks great. What hosting service are you now using?
3 - Dreamhost. I'll search for an alternative soon.
4 - Oooops. Fixed! :)
>> I notice you don't mention anything about testing...
5 - I'm doing a lot of unit testing (models). I didn't analyse the
test coverage, but I would like to get my hand on some figures. What
tools are out there?
6 - I'm not testing controllers. I've tried to authenticate the user
in a test but failed on the first attempt. I did't go for a second
try, but I'm sure it wouldn't take more than half an hour to find the
solution. I'll do some functional testing in the next iteration.
7 - I'm not using an additional test framework. I would like to spend
some time analyzing shoulda though.
>> (Table-plus) It's a really cool feature and will hopefully become a real selling point for Hobo.
8 - Yep! Table-plus was the decision factor that lead me to adopt
hobo. Unfortunately this feature has some problems in Cavortify and
was the reason of some headaches :|
Regards,
Tiago Franco
On Feb 13, 7:58 am, Scott Bronson <bron...@rinspin.com> wrote:
> Hi Tiago, Cavortify looks great.
>
> I notice you don't mention anything about testing... Did you give
> this any thought? Personally I'm using Shoulda in my app but my test
> coverage is probably around 0.002%... need to spend some more time on
> this!
>
> I agree that table-plus can be tough to use. There are some gotchas
> that aren't documented anywhere (like how to write the action for an
> index method, it's a little different than the show example cookbook),
> and I ran into the custom collection limitation too. I want to free
> up the time to really dig into table-plus and understand it well
> enough to improve it but there's always been more pressing stuff to
> worry about. It's a really cool feature and will hopefully become a
> real selling point for Hobo.
>
> Nice work,
>
> - Scott
>
>> Thanks for the "powered by Hobo" link.
>> It would be nice if you could post how you got lifecycle to work on
>> the user model.
>> I then think of the e-mail activation and lost password stuff.
near the end of month.
>> Congratulations! Looks great. What hosting service are you now using?
4 - Oooops. Fixed! :)
>> I notice you don't mention anything about testing...
test coverage, but I would like to get my hand on some figures. What
tools are out there?
6 - I'm not testing controllers. I've tried to authenticate the user
in a test but failed on the first attempt. I did't go for a second
try, but I'm sure it wouldn't take more than half an hour to find the
solution. I'll do some functional testing in the next iteration.
7 - I'm not using an additional test framework. I would like to spend
some time analyzing shoulda though.
>> (Table-plus) It's a really cool feature and will hopefully become a real selling point for Hobo.
8 - Yep! Table-plus was the decision factor that lead me to adopt
hobo. Unfortunately this feature has some problems in Cavortify and
was the reason of some headaches :|
Regards,
Tiago Franco
On Feb 13, 7:58 am, Scott Bronson <bron...@rinspin.com> wrote:
> Hi Tiago, Cavortify looks great.
>
> I notice you don't mention anything about testing... Did you give
> this any thought? Personally I'm using Shoulda in my app but my test
> coverage is probably around 0.002%... need to spend some more time on
> this!
>
> I agree that table-plus can be tough to use. There are some gotchas
> that aren't documented anywhere (like how to write the action for an
> index method, it's a little different than the show example cookbook),
> and I ran into the custom collection limitation too. I want to free
> up the time to really dig into table-plus and understand it well
> enough to improve it but there's always been more pressing stuff to
> worry about. It's a really cool feature and will hopefully become a
> real selling point for Hobo.
>
> Nice work,
>
> - Scott
>
solars
Feb 13, 2009, 2:36:48 PM2/13/09
to hobo...@googlegroups.com
Hey :)
> >> I notice you don't mention anything about testing...
> 5 - I'm doing a lot of unit testing (models). I didn't analyse the
> test coverage, but I would like to get my hand on some figures. What
> tools are out there?
I'm using rcov it's pretty cool and all I need
(rspec for testing)
> 6 - I'm not testing controllers. I've tried to authenticate the user
> in a test but failed on the first attempt. I did't go for a second
> try, but I'm sure it wouldn't take more than half an hour to find the
> solution. I'll do some functional testing in the next iteration.
I think I issued normal post request to login my users, that should
work. Somehow I couldn't find the right place to hook in, for
setting the session var or so.. iirc - but maybe I just didn't look
long enough :)
greetings,
Christoph
Tiago Franco
Feb 15, 2009, 2:49:30 PM2/15/09
to Hobo Users
Hey.
> I think I issued normal post request to login my users, that should
> work. Somehow I couldn't find the right place to hook in, for
> setting the session var or so.. iirc - but maybe I just didn't look
> long enough :)
Yep. This is my 2 minutes test: http://pastie.org/389936
It fails in the assert. I need to find the right name of the session
variable.
Nevertheless this wasn't a priority, so I only invested a couple of
minutes in this test.
TF
> I think I issued normal post request to login my users, that should
> work. Somehow I couldn't find the right place to hook in, for
> setting the session var or so.. iirc - but maybe I just didn't look
> long enough :)
It fails in the assert. I need to find the right name of the session
variable.
Nevertheless this wasn't a priority, so I only invested a couple of
minutes in this test.
TF
Reply all
Reply to author
Forward
0 new messages