Ah - neat, I might also do some hacking on it today.

There’s already a Ferret-based search branch on mind (which I plan on working on).

I personally think JS ought to be fine but A) I’m not Peter :P and B) it should be unobtrusive (e.g. if not using it, it shouldn’t change anything). Please though, avoid Prototype :P jQuery is so much nicer.

The only thing to note with edits is that if someone edits a feed it should probably remove it from the feed - I haven’t checked yet but from a quick look at the recent edit commit you made it doesn’t look like that change was made yet.

I pulled most of the changes and added a slight change of my own the the starring stuff (so it’s a smaller link now). Will add more as I go along.

One feature which would be awesome is something like Reddit’s inbox. So you can star the items your interested in and when someone comments on it, it’ll appear on the main page (or just another page). And of course RSS-support :-)

@judofyr consider the first part done - just need to improve and to add RSS for it. I’ll push it to github later this evening (not guarantee peter’s going to want to deploy the changes though).

It’s great to see that people are having fun with it. I will certainly consider any changes or new versions for RubyFlow.com.

That said, the reason there’s no JavaScript whatsoever on RubyFlow is for speed reasons. That’s also why there are no images (except for the Engine Yard one). RubyFlow’s pages are extremely light and very fast to load. Adding 50K or more in JavaScript will have an effect, even once it’s been cached. RubyFlow has received compliments on its speed, so there must be something in it.

If any JavaScript related work is truly unobtrusive, I could still use any updates, but just remove the JavaScript.

Oh, and one thing that would totally rock would be if someone who loves writing tests could write some more tests (I think the authentication system is currently covered, but that’s all) ;-)

Even better than removing it completely, I’ve made it possible to enable it on a per site basis and then rewrote the existing javascript to be unobtrusive.

Changes just got pushed to to my repo on github.

I also rewrote the star controller + changed the URL’s it used.

So, for a summary of changes to date: 1) Edit links for users (thanks to Soleone) 2) Starring items (bulk of work done by bdude, some changes by myself after) 3) “recently” page - kind of similar to reddits inbox, basically activity on starred posts since you last viewed the page. 4) per-site javascript options. 5) Search (in a branch of mine, not yet merged back in and I don’t think I plan on it yet. Using ferret but would prefer to use something ala sphinx).

I still need to finish the recently page and I plan on adding a page listing your starred items some time later today / tomorrow.

If you add JS from now on, it must be unobtrusive (see application.js) for details and you shouldn’t have to change the page html at all for it.

Most (all) of the changes discussed here should be available from my repo if anyone wants to look at / fork / pull the changes.

And for those who don’t want to clone / fork / muck around - there is also diff with all changes from Peter’s original upload at http://gist.github.com/3834

Mmmm. The taste of Open-Sauce!

Hi,

Pl. make the procedure of creating links a bit easier. I am not to happy to create the links on this site.

Many times i have just failed to create a perfect link, as i wanted it to be.

Thanks

After seeing how people use the site, I second softmind’s suggestion. I’m not entirely sure what technique is best, but I suspect getting the user to supply the URL to the content they’re posting, along with the link text, so that the site can put together the initial link of the post would be good. Then append whatever’s in the main box to that.

Hi,

I have been following RubyFlow for a while. My recommendations would be:

1) Include tags for each posting. 2) Also have broad categories so that content can be filtered for beginner, intermediate and advanced level developers at first glance.

These would be good features to add which would make the site even more helpful that it already is.

Thanks again for all the hard work people have done in putting the site up and maintaining it.

Another thing you might want to do (if it hasn’t been done already) is remove the RubyFlow specific stuff, and perhaps go to using a “default” config file so that all new sites aren’t called RubyFlow ;-)

Ah yes, the spam issue.. :)