Visual Studio for Mac enables developers to create applications using.NET and C# only. Visual Studio for Mac should also provide support for C++ development, using compilers available on the system (gcc, Clang, etc.).
Maybe I'm going out on a limb with this one, but it seems to me that rich text editors represented an important step forward in moving the World Wide Web from a broadcast-oriented, publisher/programmer-focused endeavor to an interactive, content-remixing medium where we can extend and build upon each other's expertise and inspiration. Think about it: At one time, content had to be built into a Web page by a programmer. Or at least a writer with some technical expertise in HTML markup. Later we got the ability to submit plain text back to the server, which might build a new page with the new content. The state of Web content editing changed significantly with the release of Internet Explorer 5.5, in 2000, which introduced the designMode and contentEditable attributes. DesignMode made the entire document editable, while contentEditable made a specific element (and its child elements) editable. Users could edit the text within an editable element or page, and the browser also provided API hooks for commands that enabled features like bold or italic styling, adding links, and so on (see Figure 1).
![Visual Studio For Mac Write Web Page Visual Studio For Mac Write Web Page](https://www.hanselman.com/blog/content/binary/Windows-Live-Writer/97b35c87376a_CF10/Screen%20Shot%202017-05-31%20at%202.06.25%20PM_7e844268-9dd2-49de-942a-966981568c06.png)
[Click on image for larger view.] Figure 1. Editing Text in a contentEditable Element Microsoft included this functionality in Internet Explorer with the intention that developers could use it to develop rich text editors, and they did. These features were popular enough, in fact, that they were rather quickly reverse-engineered and added to competing browsers. For some interesting background on this history, see Mark Pilgrim's ' post at The WHATWG Blog. There's brief-but-straightforward documentation for over at Mozilla Developer Network, and an interactive at HTML5 Demos. (If you're interested in more Internet Explorer history like this, I highly recommend listening to the ' episode of Brian McCullough's excellent Internet History Podcast.) With those historical notes out of the way, let's take a look at a few of the rich text editors available to you today. ProseMirror An interesting new project to create a conentEditable-based, collaborative rich text editor is, and I think it's a project worth keeping an eye on.
First, ProseMirror ( Figure 2) is the latest open source effort by Marijn Haverbeke, whose previous projects include the interactive online tutorial and print book, ' and the browser-based code editor, (which I discussed previously in the May 2014 column, '). [Click on image for larger view.] Figure 2. ProseMirror Collaborative Editing Demo Like most of the editors I'll discuss here, ProseMirror is a library for creating in-browser, HTML-based text editors. What's different about ProseMirror?
![Visual Studio For Mac Write Web Page Visual Studio For Mac Write Web Page](https://cdn2.macworld.co.uk/cmsdata/features/3640347/xamarin_studio_learn_c.jpg)
While it uses contentEditable, the underlying document model is not HTML. Instead, Haverbeke is creating an extensible, semantic document model based on the implementation of Markdown.
In addition, ProseMirror is being designed from the ground up as a collaborative online editor. The library has built-in hooks for storing local changes, sending document changes over the wire (using your transport of choice), handling conflicts, supporting multiple levels of undo and more. Check out the for a hands-on look at how it works, then read Haverbeke's ' overview essay and ' deep dive into the mechanics of coordinating changes between multiple users.
Aloha Editor After all that talk about contentEditable, it's important to point out that not all rich text editors use that approach today. In fact, does not use it at all! Instead, it provides a simple, lightweight (142KB), JavaScript library giving you a fast editor that you can integrate into your Web projects. The advantage of not using contentEditable is that you don't have to worry about the details of browser support and implementation. Just plug in Aloha Editor and go.
Another key feature of Aloha Editor is a focus on sophisticated handling of copy and paste from Microsoft Word, which can be a huge boost in productivity. Truly what you see is what you get. There's a beautiful on the Aloha Editor site so you can try it for yourself. The project is open source and distributed under GPL2 license. Commercial licenses are available, as well. DevExpress ASP.NET HTML Editor DevExpress offers an provided as both a Web Forms Control and an MVC Extension.