As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'd like to build a control panel (let's call it "dashboard") for several applications. Each application has a REST-API which will be used by the dashboard. The dashboard should have a module for every managed application.
In Rails I could use Controller Namespaces to achieve something like this. The models and the views could be separated in a similar way. This would lead to the following directory structure:
controllers/app1/
models/app1/
views/app1/
controllers/app2/
models/app2/
views/app2/
But I don't like that. I would rather have something like this, to have the modules better separated:
modules/app1/controllers
modules/app1/models
modules/app1/views
modules/app2/controllers
modules/app2/models
modules/app2/views
Is something like this possible with Rails 3?
If you want that kind of separation you should investigate using Rails Engines to organize the components of your application. An engine is a sort of sub-application that's mostly self-contained.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I want to handle closer to 100% of my client side code with angularjs, I'm using twitter-bootstrap also, so the thing is twitter-bootstrap make me do so much html code to create forms, i like solutions like simple-form, but they consist in a model instance to do the form_for thing, and create an instance just for that doesn't sounds cool to me.
Does anyone knows any gem or something of those libraries that I'm missing?
thanks
There is a library full of directives for angularjs and bootstrap: http://angular-ui.github.io/
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I have spent some time familiarizing myself with
rails (ruby),
django...and other things like zope and pylons/pyramid (python),
catalyst (perl)
but often find myself wanting to use
sinatra (ruby)
bottle...or flask...(python)
dancer...(perl)
I'm not entirely sure...when I'm about to start a new project, which I should use.
What should be the deciding factor that makes me switch from a micro framework to something more substantial. Is it just when I would otherwise have too much SQL to write? I think not, because if that were the case I could just use an ORM library/module.
My main issue is a fear of choosing something that other developers would not understand if someone else needed to fix the site at a later point in time. Still I am still not sure what should inform my opinion.
With miсro frameworks you have more freedom in the use of libraries, you can add what you think is right. In large frameworks such as Django and etc already much that is "screwed" and there are certain rules and best practices how best to write certain things.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I recently came across this posting where Darin Dimitrov suggested that you never refer to HttpContext.Current in your ASP.NET MVC application.
We have NDepend, a tool for doing static code analysis, what are some other rules that you believe would be good to model with something like NDepend?
Much appreciated!
In our code base (which should reuse existing infrastructure and also uses Autofac for DI) I've currently written some rules along the lines:
To ensure we are not going to tightly couple ourselves to existing infrastructure
That we are not using ViewBags in our Views, but instead using ViewModels
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have a question about organizing a ASP.NET MVC project.
I have 3 different main area. Front and back-end, and I have a Web API.
I want to know what is best practice for organizing such a project?
What I have done so far is to make 3 different projects so I could separate the area of which they worked on, but I have a problem with the Web API with CORS (Cross-Origin Resource Sharing).
So my question would be, is it possible to have 3 projects, or should I have to use areas? I still want to be able to separate the "concerns" (Web API, fronted, back-end).
why dont you run it all under one default virtual directory.. your structure would be localhost => virtual root, localhost/Web1. localhost/Web2, localhost/Web3 and run them all under IIS and not IIS express
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I've started learning RoR and I really like it - but it feels like it's oriented in one specific way - a very basic MVC model.
Which type of web application might not benefit from using RoR? Are there any signs I can find while planning the architecture?
I don't think there's a specific technical reason not to use RoR - it's fast, clean and can probably do anything PHP does.
The only reasons I can think of are the same consideration as to any other technology : Do you have the right people, is the legacy code (if any) compatible, are you in a market that makes it easy to find RoR people to support the code, and so forth.
There's also a nice Quora thread about this question :
If you have to install your website on a client machine that does not support rails/ruby.
If your code needs to be maintained afterwards by people that do not have rails knowledge.