On Thu, Jun 20, 2013 at 10:36:08AM -0700, emc_lab wrote: > > Thanks for the long answer. Well there are a lots of information there and > we probably need to spend sometime time to understand it inside and out. > > I am an average programmer (maybe a little better than average) and has > spent last week or two opening up > http://ruote.rubyforge.org/documentation.html everyday (3-4 hours a day) > and comb through the document trying to learn ruote. It is a good place to > start with. But I don't feel I am good enough after reading all the > document (at least 2 times) to start coding comfortably knowing what I am > doing exactly. Probably it is like that when learning new tricks in > programming and we learned rails pretty much the same way. For rails there > are large number of programmers and help/document are easy to come by on > stackoverflow.com or online. For ruote, the community is much smaller and > the document other than yours is hard to come by. It seems that most of > time you are the person answering the questions and it certainly wouldn't > be easy for you or anyone else. There is another member on our team who has > integrated ruote-kit within a rails engine a year ago. He like ruote and > said it was very stable. But about why and how he did this not that, he > could not have the answer easily as he did it a year ago with a test > project.This time we are looking into integrating ruote directly into rails > without going through ruote-kit which is an extra layer and uses haml and > sinatra (we use erb and rails (rails engines)).
Hello, yes, ruote is much smaller than Rails. And yes, I'm mostly the only one to answer, although Danny Northox and Doug are helping these days (many thanks guys, it's much much appreciated :-) ) Somehow, ruote is a Ruby library. I don't want to focus on writing documentation on how to integrate it in Rails, there are many ways to build/deploy a Rails application. I trust integrators to know their tools, their requirements, their deployments. I cannot feed with a spoon every one and write docs about their specific deployments. I strive to answer quickly on this mailing list to fill the gap between the generic doc and the specific requirements people may have. I am a programmer mostly because I can tinker with stuff and make mistakes, lots of small mistakes. When people ask about how to integrate X with Y, I am thinking: "hey, why don't you just try?". I wrote lots of documentation, it's never enough, it's never enough hand-holding, I can't cover everything. I don't want to write documentation about Rails, I just want to write documentation about ruote, the Ruby library. Too many facets to the Rails integration. Somehow who can do 2 * 2 = 4 can figure it out, or at least make mistakes that'll make him better. > If you don't mind, I would like to post the question and your answer to > stackoverflow so the answer will be available for others who want to know > more about ruote. It is a quality piece information from the author of > ruote and is worth to keep. I don't think it's a good idea. It's merely duplication of the info found / created in the mailing list. Maybe I could switch and say "let's stop using the mailing list and let's do all the support via StackOverflow", but it then makes it impossible to announce stuff... Well, I could use my blog to make such annoucements, but I'm not the only one to make announcements... Conversation... Ruote is a tiny project, not used by many people, it's not worth StackOverflow. Best regards, John, very tired -- -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
