What is the preferred method of implementing the OpenSocial platform? I'm aware of Apache Shindig but can't really find any useful information on it. Also, is it possible to use an existing solution like the Rails-based lovdbyless and add OpenSocial features to it?
I've ported shindig over to .NET at http://code.google.com/p/pesta/ and a sample site using it from partuza at http://www.codeplex.com/raya
There seems to be a plugin that someone started, Ruby on Rails, OpenSocial Container plugin 0.1.0, the comments have someone from Apache Shindig suggesting it get rolled into there as the Ruby server implementation.
I also found an article on rolling your own, Google's OpenSocial with Ruby on Rails.
I haven't tried, either, yet.
Even some of the guys on the Shindig team admit that the documentation is very sparse, to the extent that they say the source code is the documentation - and, believe me, there's quite a bit of source code to look at.
The most helpful links I've found are these:
http://mail-archives.apache.org/mod_mbox/incubator-shindig-dev/200805.mbox/raw/%3CF60DD781-F361-4865-AEC6-284644D0DFF3#xs4all.nl%3E/
http://cwiki.apache.org/confluence/display/SHINDIG/The+rough+guide+to+deploying+shindig
http://mail-archives.apache.org/mod_mbox/incubator-shindig-dev/200905.mbox/%3c4CC1540B3EC8D54AA01CC6BC40F71030E0991E#EXCHANGE.corp.shop.com%3e
and for an example of how to replace the default classes so as to interact with a database:
http://cwiki.apache.org/confluence/display/SHINDIG/Providing+your+own+data+service+implementation
Related
My first question here.
I searched thoroughly, and unfortunately, I am unable to find an explanation I can understand.
I am interested in understanding how PJAX works (link below), so that I can consider implementing it. It seems simple enough, but the requirement to configure the server to recognize PJAX requests has me stumped. I am a front-end developer that is completely unfamiliar with back-end development.
For example, how do I configure the server? The PJAX author gives an example in RAILS, so it is a matter of placing that code wherever it goes?
I build custom and implement Wordpress, and I use a Wordpress hosting solution. Does that affect where I would configure the server?
I know these are general questions, which demonstrate how little I know. I would appreciate if someone could explain the concept of configuring the server and perhaps provide an example of what that would look like.
I appreciate your help.
https://github.com/defunkt/jquery-pjax
I am trying to use Photobucket(API) as a image uploading option in my website.
Is there any available gem to do this? or should i use things like REST to achieve this?
Please suggest.
Thanks,
Balan
The only thing I really found was this https://bitbucket.org/photobucket/api-ruby/src/7b69e473fb9fd5b4d37e2ad7f266500e45ef524b/example.rb?at=default. They are using the oauth rubygem to talk to photobucket, still a lot of manual process involved. It is also still using REST.
I would say the easiest way it going ahead and using REST following http://pic.photobucket.com/dev_help/WebHelpPublic/PhotobucketPublicHelp.htm and http://pic.photobucket.com/dev_help/WebHelpPublic/Content/FAQ/FAQOverview.htm to get you started.
I haven't done a REST client in ruby but this gem looks pretty good https://github.com/rest-client/rest-client.
I would recommend, assuming you have the time, making a photobucket ruby gem and wrapping the REST calls in useful class abstractions. It is great for the community, forces you to follow good practices(to a certain extent) and will provide great experience to put on a resume/talk about in an interview.
I'm introducing comments into a Rails application, and, being exceptionally lazy, I'm looking for a plugin to do it for me. I came across acts-as-commentable, but I didn't find much else. Acts-as-commentable seems fine, but it doesn't have support for threading.
Of course, it wouldn't be too hard just to home-brew the entire thing, but I think that surely commenting is such a common feature that there should be a canonical plugin to handle it. Can somebody with perhaps more Google Fu than me point me in the right direction?
This is acts_as_commentable_with_threading plugin which help you for threaded comment.
Link::
http://github.com/elight/acts_as_commentable_with_threading
The most lazy approach would be to use third-party commenting system like DISQUS : just copypaste a couple of javascripts and you're done.
Surely, it can't be used if your app has an authentication system of its own.
If you do not want to integrate a third-party service like Disqus, you have Juvia The Comments and Commontator. Also you can count with opinio as alternative. but only with Rails 3 and at the moment and as notice the development seems stalled.
with symfony using doctrine is very easy cause its fully integrated into the framework.
i wonder if there is a possibility to integrate solr with symfony too (eg, via plugin?)
thanks
There are at least 2: tjSolrDoctrineBehaviorPlugin and sfSolrPlugin. The second is a fork of the excellent sfLucenePlugin which works with sf1.0 and sf1.1, and although it doesn't have much exposure, it is stable. Check the full README for details of its use.
I wrote an article here to explain how to easyly make a powerfull search engine with symfony : http://leny-bernard.com/en/show/article/un-moteur-de-recherche-ultra-performant, you can ask me some questions on my website with the comment form
I'm looking for a Rails plugin that eases the development of a "friends" system or social networking system for the latest versions of Ruby on Rails.
Before anyone says it...I know, I should probably create it myself, from scratch. And I am fully capable of this (I think). I'm just looking for a good plugin that can a.) make life a bit easier for me and b.) give me some ideas for reference.
I tried to make my own authentication system, and did what I thought was okay, but then I switched to restful_authentication and realized how poor my system was in comparison.
Thanks in advance...
U might wanna try Community Engine
from the website
CommunityEngine is a free, open-source
social network plugin for Ruby on
Rails applications. Drop it into your
new or existing application, and
you’ll instantly have all the features
of a basic community site.
it uses engines, easy to change layouts or do modifications
real world example - http://www.weebabystuff.com/
another option I know is Insoshi as Chuck posted
updated : look at this blogpost http://jimneath.org/2008/04/25/building-a-social-network-site-in-rails/
-- Ed :) --
You could look into http://lovdbyless.com/
This is a free open-source Rails social networking app which should give you plenty of ideas and pointers.
Ronald
You HAVE to see this railscasts video.
try acts_as_network plugin
The only one I know of is Insoshi. I haven't used it myself, but it sounds like that's what you're looking for.
I would recommend using OpenID library for rails to handle authentication.
On top of what others have said, there's also acts_as_network. The bonus of this one is that it's a pure plugin (doesn't require engines). Not having to worry about engines is a huge plus. The downside, of course, is that it's not a full fledged social network. It's just a friending plugin for models.
You might want to checkout the Amistad gem. It looks pretty simple and it supports both Mongoid and Active Record.
For avatars i would use avatar and try will-paginate for pagination. other then that i love can_serach to make it alot easier to search in the database.
You should also look at the other gems by technoweenie. There is alot of great stuff there that can help you
I've just been researching this myself and chosen to go with Bort & CommunityEngine
Bort because I am familiar with it already and it provides all you need in user authentication and basic application functionality. Community Engine because it is an Engines based plugin and some aspects of Engines are being merged into Rails 2.3 so I know what I learn will continue to be useful and because CommunityEngine seems more modular while lovedbyess and Insoshi seem more like complete applications and I suspect it would likely be more work to disentangle the features I want from the ones I don't. However, take that with a huge grain of salt since it is just based on high-level quick browse initial impressions.
If you just want an activity feed then there is the activity streams plugin