Examples are great, but scaffolding some templates for your existing odata model entities would be a way better start and would reduce waste time for repetitive work a lot!
Perhaps you'd like to contribute such templates? We would welcome them ... or at least an example as we're not clear on what template would be most valuable for this purpose. I know this sounds snarky but it's a genuine request for help.
Related
I am building an Umbraco site, and there is a need for a really simple forum (e.g. one level of topics, a simple subject/body form for new entries and replies, that's about it)
What is the easiest way to implement this? I think nForum is an overkill. Should I go with Umbraco API for member management and content creation, of should I use my own prefixed db tables and custom backend implementation?
Thanks in advance
Themos
For small and limited requirements you can surely look at the UFORUM, it is time tested and pretty decent.
It supports membership out of the box...
http://our.umbraco.org/projects/collaboration/uforum-basics
Check it out Hope it helps.
I have a best practice question. I have two classes, company and category. They have a many-to-many relationship. When clicking a category I shall go to a page showing all companies with the chosen category. Pretty straight forward.
My question is:
Should I list all the companies on the companies/index.html.erb after filtering the companies in the controller?
or
Should I list all the companies on the categories/show.html.erb page?
or
Should I do a completely new page, since it doesn't really fit into any of the two above?
Do you generally make a new page when your goal doesn't fit the scaffold made pages or do you use them quite freely?
I am working/learning alone with rails, so there are a lot of best practice questions popping up all the time.
Cheers Carl
A scaffold is a starting point, so you should always consider what you need in your web application.
In you case, I think all examples are fine, but again, it's really up to you.
If you are just learning Rails, stick to as many conventions as possible. Scaffolding is one of the ways Rails can help you get things started when you don't know how all of the pieces work together.
But like Oscar said, ultimately you must decide what your application will need.
The Ruby on Rails platform comes with many principles such as DRY etc.
The main part is the MVC architecture, the thing scaffolding does is let you see how this MVC is used correctly by a Model, View and Controller generation.
When you learn how this works you will be able to answer your own question, I could write my thoughts down but it is key for a Rails developer to understand the MVC structure so my suggestion is to read:
http://betterexplained.com/articles/intermediate-rails-understanding-models-views-and-controllers/
have fun
Just looking into vote_fu for a public page where people can vote on content. I am interested in implementing this, but there will be no model to act_as_voter, only a model to act_as_votable. Is this doable? Anyone have experience with this?
Many thanks as always.
Ben
I'd not recommend doing that. The gem/plugin is built around the idea of a voter model. You might be able to tweak your implementation by creating your own migrations and overriding included methods to be still able to use vote_fu, but IMO that would be hardly worth it.
Thinking about an anonymous voting process in its simplest form you should be a lot faster by rolling your own custom version.
I need a Rails plugin that gives you the chance to purely separate HTML and any logic in your views. Views should be classes reading the separate markup and replacing it with dynamic content where needed.
Basically Effigy from github does this.
I am looking for something like Wicket, but on the Rails base.
I can remember seeing a plugin from a Rails enterprise that does this. In my memory, it was better and seemed more mature than Effigy. But I forgot its name. It was something like "luxurious" or "delicious"; does anyone know what I am talking about? The plugin was created in a US Rails enterprise.
Any other alternatives would be much appreciated.
I feel that Effigy is almost OK, but it's hard to find tutorials or people using it properly, so I question its the maturity.
Well, if nothing comes up, I will go ahead with Effigy for now.
All right guys, I think I finally found what I was talking about.
The plugin is called "Erector"
The thing that I like about it, is that views are finally plain ruby objects and you can do everything you can usually do in ruby. I found couple of blogposts:
https://github.com/erector/erector
Why I always liked this idea you can easily see in this blogpost
I want to thank the creators for this.
I have to add Wufoo-like WYSIWYG form-builder functionality to a Rails webapp.
Does anyone know of good resources (gems/engines/plugins/example code) that would help?
this is not really an answer to your question, but I still can't add comments unfortunately, due to my reputation level, sorry :)
There is exact equivalent of such functionality in Drupal(php)
http://drupal.org/project/webform especially useful for contact forms, i.e. clients happy and don't bug me every time they want to adjust or even to add new inquiry form :)
Would be nice to have such gem/plugin if any? :P
Thanks.
I don't think creating such a app in rails would be a great idea.
Using AR, such an app would be creating migrations on the fly - which doesn't sound like a great thing to do.
AFAIK, wufoo uses php.