would like to use fckeditor or similar for building/editing webpages on the fly
but there are a few other old questions where there are issues
am looking for any recent experiences/alternatives ?
thanks
http://tinymce.moxiecode.com is not bad
I had a pretty easy time integrating fckeditor in my asp.net mvc app. The fact that mvc and regular webforms co-exist seamlessly made including the free fckupload utility a snap. I highly reccomend it.
Depends on the functionality you need. If it's a simple one like the one used here at StackOverflow, there's a Markdown Editor.
Related
Is it possible to take advantage of a polymorphic viewmodel when using the grid from MVC Extensions? Google wasn't very helpful :(
I know that ASP.NET MVC supports it via display templates. But how would I do something similar using the telerik grid?
Turns out it does.
http://www.telerik.com/help/aspnet-mvc/telerik-ui-components-grid-display-and-editor-templates.html
Hope this helps someone google it a bit easier :)
I'm converting a asp.net application over to asp.net mvc that uses a lot of listboxes, specifically the RadListBox from Telerik. The ListBox that comes with mvc is very basic and I'm wondering if anyone has come across a better alternative. I'm really looking for the ability to reorder, add, and delete from the client. Thanks
It seems at the moment there is no special tool (with professional features like Telerik tools) for MVC. However I suggest you using extension methods as it was my problem already:
And also you can replace it with a [Telerik MVC dropdownlist][2]
[2]: http://demos.telerik.com/aspnet-mvc/razor/combobox which is Free!
Telerik claims their controls work with ASP.NET MVC now. Has anyone already used the controls in a MVC project?
My company uses the Telerik ASP.NET controls in a large application and it works out quite well. That's why we think about using them in a MVC project.
EDIT 1:
telerik has a new go at ASP.NET MVC this looks much better then their first go at it. But it was to late for my project. http://www.telerik.com/products/aspnet-mvc.aspx
You could check out the demo application (a forums application) they built using ASP.NET MVC, announced here. Source code is available.
The demo is a simple- and stylish -
forums application. It uses 9 of the
RadControls, including RadGrid,
RadEditor, RadChart, RadTreeView and
RadUpload, to build a forum site that
has basic thread/post navigation,
formatted forum posting, user
authentication (with support for
custom avatars), and a site activity
"Statistics" view. Everything you need
to have a fully functional MVC forums
app. The source is available for
immediate download, so I encourage
anyone interested in learning more
about MVC or the RadControls in MVC to
grab the bites and study the example.
You may have already seen it, but Telerik has a blog post about how to use their controls with MVC and some of the limitations. I don't actually use their controls so I can't speak to whether the limitations are really a problem. It does appear that there is a a little more "manual lifting", so to speak, when using the controls with MVC but that there are workarounds to get most of them to work properly.
I'm hoping that they will eventually release MVC versions of their controls. I'm holding off evaluating them until that happens, but if you're already using them I'd certainly look to see how easy they would be to use with MVC. Perhaps you could update your question with an answer if you give it a try and let the rest of us know how it went.
I have been using the Telerik controls for about 6 months. I have been using the Grid and Window controls on MVC 2. Like most commercial products there are issues we have been fortunate to work them out. Once you get past the initial learning curve the controls are time savers. You can't beat the price for the amount of functionality you get.
My biggest issue is that they seem a bit sluggish responding on their forums. Maybe I'm just asking lame questions. I've been lobbying management to pay the $ for the supported version. Considering the amount of time we spend digging around to solve some of the more complicated problems I think it would be worth it.
I've just had a look at their grid and wrote a small POC project with it and must say I'm quite impressed. I'm not sure about their previous MVC controls iterations, but the current one can be a real time saver. It also fits very nicely into ASP.NET MVC ajax applications since there is a rich client-side API. Having jquery DataTables on the client side results in an even better user experience (because it is much faster), but also requires more error-prone javascript code.
As an alternative, you can check for MDBootstrap (it´s a front-end framework built on top of Bootstrap). There you will find an article with free ASP.NET MVC templates.
What would be best practice to localize your ASP.NET MVC application?
I would like to cover two situations:
one application deployment in IIS which would handle multiple languages
one language/application deployment.
In first situation should you go with some kind of view based thing like, ~/View/EN, ~/View/FI, ~/View/SWE or something different?
What about second case, just application based config via Web.config and point these different languages to different URLs?
You can also take a look here ASP.NET MVC 2 Localization complete guide and ASP.NET MVC 2 Model Validation With Localization these entires will help you if you working with ASP.NET MVC 2.
You would localize your ASP.NET MVC application very much in the same way you would a classic ASP.NET Web Form application.
You wouldn't use different pages/views for each language, but each page would support multiple languages using satellite assemblies.
You can look at Matt Hawley's blog entry for more explanation and examples.
Unfortunately, Matt Hawley's original code doesn't work in the release version of ASP.NET MVC. Check out an updated post: http://blog.eworldui.net/post/2008/10/ASPNET-MVC-Localization-via-View-Engines.aspx
In general, the localization process isn't as smooth in the VS 2008 / ASP.NET MVC world as it is with traditional web forms. http://www.guysmithferrier.com/post/2009/05/Localizing-ASPNET-MVC.aspx
Have a look at Rob Connery's MvcStore project. He does a screencast showing one way to solve the globalization problem.
http://wekeroad.com/2008/04/24/mvcstore-part-5
I've never been convinced of handling localization within a form as Elijah suggests - the different lengths and directions can lead to very complex or vary naff looking forms.
I'm only just starting with MVC but taking the decoupling method you would wan to use the same controller regardless of the language (treating language just as a view) - this would then give you /Controller/Action/language/form
There is good tutorial with recent update on How to localize asp.net mvc application covering all aspects including DisplayName localization, Validation, using Routing (storing culture name in URL), issues with output cache and so on... Alex Adamyan Blog - While my keyboard gently weeps
We actually went a complete different with overriding the
DataAnnotationsMetadaDataProvider.
In there you can make sure that the DisplayNameAttribute values are resolved into the correct language.
Actually you could even get rid of that attribute and resolve by field names only if that would be any help.
I wrote this article a while ago. It uses a custom view engine.
http://blog.oimae.com/2011/02/20/cultured-view-engine-for-mvc/
And another tutorial for different solution
Tutorial: Create ASP.NET MVC localization with language detection
Should I learn NHaml?
What does it provide me over a classic ASP.NET MVC view? What are the pros and cons?
Are you using it via the MVC Contrib project?
I have been seeing more and more about it. For example... I saw a blog post by Matthew Podwysocki using ASP.NET MVC, NHaml, and F#!
It should only take a few hours if you're familiar with the MVC framework, so I'd say yes, learn it. NHaml is a compact way to write HTML code. It is pretty easy to read and write once you get used to it. The downsides are that you lose the ASP.NET controls, so server-side processing is more difficult. Your team may be resistant, too.
Absolutely, learning NHAML is really easy and it is much easier to write than the web forms syntax.