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 11 years ago.
I have achieved a beginner skills in mvc3 and now want to try next level.
I want to create a super simple CMS that has following features:
Support extensible skinning, i.e. start with some default dynamic skin and when change database setting for skin name, it should work with the new skin / theme
Dynamic pages loaded from database
partial view I think that can show available pages from database
Can somebody point me on how to get started? I tried to look into source code of orchard, and couple of other popular cms in mvc3 but because of lots of code, I am not just getting it properly to get started with.
Thanks in advance.
Don't worry about what other people are doing at the moment..
If this is just a learning exercise then you should look at what you want to do and then look at how to achieve that...
So your reqs are:
Extensible skinning (like themes in say WP?)
Dynamic pages
An admin area to manage pages
I guess the first thing is to get your areas setup if you want to do it that way.. (add an area for the admin section).
see here -> http://msdn.microsoft.com/en-us/library/ee671793.aspx
or
here -> http://mvccoderouting.codeplex.com/ -> this way could mean no need to set up areas... more detail on the page.
For the dynamic pages you are probably going to do something with routing a default controller.
do you reference the pages by id in the url... or do you have a key that makes up part of the url? that's one design choice you will have to make.
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 10 years ago.
I want to develop a personal blogging website using ASP.NET MVC 4.
I know that I could be using WordPress/ Joomla/ Orchard/ Umbraco/ Funnelweb, etc., instead of reinventing the wheel but I really wish to try it out myself.
I do not want my website to look like some beatle-aged archaic remain. I see plugins like Akismet/ Prettify/ Markdown/ nrelate that add amazing functionalities to your blog. But I am not really sure if I would be able to use any of these in my custom application as most of them are PHP based. I want to stick under the Microsoft roof and implement technologies like HTML5, CSS3 Silverlight5 and WCF 4.0, along with ASP.NET MVC 4. (At least thats what I plan to do)
I understand that I need to develop a scalable database design that could accomodate newer functionalities in the future. Additionally, the exorbitant focus on SEO and cross-browser capabilities is overwhelming. Permanent links for individual blogs, internal navigation, video-embedding inside posts, etc., sound like building Rome in a day
Please if you could guide me personally or direct me to appropriate resources, it would be very helpful.
I am sort of doing it right now on my own. It's not done yet but it will give you an idea: MvcBloggy.
Also, have a look at FunnelWeb source code. It's written in C# and uses ASP.NET MVC 3 I believe but it's a really good resource and easy to follow.
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.
So I want to start working on specific pages on my website to have a mobile version. I was wondering how I should go about it? Do I create a new controller for each controller so that if it detects mobile then it redirects to that controller? or do i just use css to change how the page gets viewed?
If I need to create a new controlelr do I host it on a subdomain?
Comments are greatly appreciated.
Thanks!!
#TheRealKingK is right about picking up some books on the matter. There are always 1000 ways to solve a problem, so it really depends on the variables involved in your project. I read an article in the latest MSDN that touches on mobile/desktop strategies and it had some good insight.
CSS media queries are excellent for helping render things for different sized screen, but do not help with detecting hardware capabilities, or filtering out heavy media out of the site for faster downloads on say a 3G mobile network.
Having a seperate controller base could be a decent strategy. I would have ALL your controller inherit from a custom base controller that (among other things), would determine where the request is coming from, and route them to the right controller. This really depending on what the site is for and what your client needs on the desktop versus a mobile app (native or HTML5)
I am playing around with rolling an MVC4 blogging application with a custom content management on the backend. Thus far it is pretty lightweight, so CSS is working for me.
I dunno if this sounds like a nerd-rambling or not, but hopefully it gives you some insight.
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 11 years ago.
I am starting with web development. I looked at the URL design of a few websites, especially github and stack overflow.
A user page on github is of the form github.com/<username> (e.g. github.com/roma1n). This strikes me as requiring careful reservation of top-level identifiers, i.e. there cannot be a user explore in github, because github.com/explore shows a list of trending/interesting repositories. It also seems hard to extend once usernames that would make useful page names (e.g. latest, all) have been taken up by users.
Stackoverflow seems to go on the opposite route, where a user page is of the form stackoverflow.com/<numeric id>/<username>. This seems to add redundancy to the address, unless multiple users with the same nickname are allowed (e.g. to make life easier when identifying through other providers such as OpenId?).
What are the pros and cons of each solution, (and of the other obvious ones such as example.com/users/<numeric_id> or example.com/users/<nickname>)? Is there a current best practice or reasonable default?
I think your suggestion example.com/users/<nickname> is pretty reasonable. given a choice I'd pick this, becuase it's more memorable for users than an id, and it sidesteps the the users nickname problem. of course you're free to adopt any convention that fits your use case, so whatever works!
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 12 years ago.
I think there are not many people who don't think that ASP.NET MVC is one of the greatest technologies Microsoft gave us. It gives full control over the rendered HTML, provides separation of concerns and suits to stateless nature of web.
Next versions of framework gaves us new features and tools and it's great, but... what solutions should Microsoft include in new versions of framework? What are biggest gaps in comparison with another web frameworks like PHP or Ruby? What could improve developers productivity? What's missing in ASP.NET MVC?
I would love to see better server side validation support. Data Annotations doesn't really cut the mustard.
Also I need a way to properly personalize the validation error message when an invalid format of a nullable property (such as int?, float?, DateTime?, ...) has been entered by the user and the model binder tries to set the value. I am sick of string backing properties and manually parsing nullable types.
Also donut caching is a feature that every respected web framework must have built-in support for.
I would love some more shorthand helpers around routes, similar to what rails has with :resource or :resources routes for example.
Biggest issue for me are lack of some action result types like XmlActionResult or PdfActionResult.. they could be usefull...
Built in support for migrations and activerecord
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'm looking for a desktop application framework similar to Rails:
Good ORM
MVC
Default directory structure
View Helpers/DSL
Elegant
Open Source
Fun language
Decently mature
Check out Griffon, a Grails-like framework for Swing application development that fulfills all your needs.
Have you checked out Shoes?
There is also Bowline. It was mentioned in ruby inside blog recently. I haven't tried it. Tried Shoes though. It is very simple.
There is another one called Anvil. Anvil is a MVC framework that wants to be equivalent to rails for GUI development. It is based on wxruby. Which makes me want to try it.
try Rebol, it's got the simplest gui that is out there. an example of a window with one text field, one button "click me" and a label "hello" :-
view layout [ field label "hello" button "click me" ]
or if you want it in multi line
view layout [
field
label "hello"
button "click me"
]
I've personally ended up using Swing/SWT + JRuby. The Java cross-platform GUI libraries are just light-years ahead because they're used for IDEs, which are about the most demanding application you can have for a GUI toolkit. It's nowhere near as elegant as Rails is for the web (and I'm no fan of Rails), but in the long run, it's a much better choice than anything based on wxWidgets or GTK or QT. It also gives you the option to drop into Java if you have a particular piece that's running too slow. I wish there were better options, but that's what we've got.
Monkeybars is the main solution I'm aware of, but it's not ideal from the point of view of your bullet list. Its "MVC" isn't really like any other interpretation of MVC that I've come across; it's more a convenience wrapper around Swing. At least, that's the way I use it.