Are there any plans to incorporate Razor syntax into the Rich Text Editor?
Since Silverlight will be used primarily for LOB type applications in preference to using HTML5/JQuery type technologies I expect the desired usage for a WYSIWG editor will be different for SL app than for a generic web app.
In my opinion the most common type of activities that would be required for a Rich Text Editor in LOB application incorporate both Merge functionality and various syntax highlighting. The very real requirements being for various exporting / printing / letter generation/ document template type activities, over actually editing content for say a website (for this you would stick to a HTML/JS based WYSIWYG).
I understand MailMerge type functionality already exists, but rather than stopping there I would like to see the ability for a user to pick/drop properties of a source object onto a document/artefact (the thing you are editing). With this thought in mind, why stop there and actually bring in RAZOR syntax. The key element would all be in the UX, proving a UI which shows both the static text/images etc. alongside the more dynamic elements such as merge fields, Razor snippets
Since Silverlight will be used primarily for LOB type applications in preference to using HTML5/JQuery type technologies I expect the desired usage for a WYSIWG editor will be different for SL app than for a generic web app.
In my opinion the most common type of activities that would be required for a Rich Text Editor in LOB application incorporate both Merge functionality and various syntax highlighting. The very real requirements being for various exporting / printing / letter generation/ document template type activities, over actually editing content for say a website (for this you would stick to a HTML/JS based WYSIWYG).
I understand MailMerge type functionality already exists, but rather than stopping there I would like to see the ability for a user to pick/drop properties of a source object onto a document/artefact (the thing you are editing). With this thought in mind, why stop there and actually bring in RAZOR syntax. The key element would all be in the UX, proving a UI which shows both the static text/images etc. alongside the more dynamic elements such as merge fields, Razor snippets