Tweets by @Actipro
Please take some time to learn more about us and our product offerings.
A couple months ago we make a post on our blog asking if anyone would be interested in a port of our SyntaxEditor for WPF control over to Silverlight. We’ve had some tremendous feedback, both via comments on that posting and via e-mail, so we’ve moved forward with development on the product.
As many of you know, SyntaxEditor for WPF is the premier syntax-highlighting code editor control for the WPF platform. It is being constructed with a new next-generation object model based on our years of experience with SyntaxEditor for WinForms, the market leader in the WinForms platform. We’ve made a lot of posts about SyntaxEditor for WPF’s features in this blog.
The Silverlight version of SyntaxEditor is essentially a large subset of SyntaxEditor for WPF’s object model. For those who have used SyntaxEditor for WPF, the entire text/parsing library is completely converted to Silverlight. This means all the document, syntax language, parsing, etc. code works in Silverlight exactly the same as in WPF. The UI layer is mostly the same as well. Many of the UI features found in the WPF version are already implemented where possible in the Silverlight version.
The possibilities are endless. Want to have a web-based source code browser where you can edit your code from anywhere right in the browser? Want to build a web-based IDE? Want to just use the editor in read-only mode to provide rich visualization of code?
SyntaxEditor for Silverlight would fit right into any of those conceptualizations.
Without further ado, let’s take a look at the first video of SyntaxEditor for Silverlight. In this video, I fire up the editor in an Internet Explorer page and do some typing and selection. Note that syntax highlighting is being driven from a syntax language that was created with our WPF Language Designer application.
I also have the smoke text effect enabled, which shows off the new adornment layers feature we’re currently working on. The smoke text effect is not something you’d normally have enabled in a production application, but it is a neat example of what you can do with our adornment layer framework.
There still is a lot of work to do on the Silverlight version before it would be production-ready. However we are trying to make some progress on it each day. And as we add any new features to the WPF version going forward, we are adding them to the Silverlight version at the same time.
We don’t have any target release dates at this point, but keep your comments coming and we’ll continue posting more details on the control.
October 30, 2009 at 22:32
October 31, 2009 at 06:53
really nice! Would use it today if available...
November 7, 2009 at 05:02
The hardest part is waiting until this is released! ;)
November 16, 2009 at 06:07
Are you still working on the WinForms versions? Sounds like more effort is going to alternate platforms than a defacto standard in .NET development.
November 16, 2009 at 13:23
Yes we are still working on WinForms. In fact we just added C# 4.0 and VB 10.0 support to the .NET Languages Add-on.
Also our long term plan is to migrate WinForms to the next gen framework we're making with WPF/Silverlight right now. We made our text/parsing library there based on .NET 2.0 so that it will be WinForms compatible. However we can't move WinForms to it until all the WinForms feature areas are fully implemented in the new framework. That is why we're really pushing on new features in the WPF SyntaxEditor.
Bill Henning (Actipro)
November 18, 2009 at 14:40
Could I get a notification when the component with intellisense is available? We most likely would purchase a license as soon as it is available.
November 18, 2009 at 14:44
Thanks for writing. Keep an eye on our blog (you can attach to the RSS feed) since we are very active about posting info on SyntaxEditor updates here.
November 20, 2009 at 01:47
That's exactly the component I'm looking for! Looks really great, do you have a view on the release date or a beta program?
November 20, 2009 at 03:40
We don't have a target date yet but are actively working on getting it out since there is a lot of interest in it. Please attach to the RSS feed of our blog since we'll be posting news on the Silverlight version there.
November 22, 2009 at 10:24
SilverLight 4.0 (Beta) has built in support for Rich Text Editor.
Hence would builing Syntax Editor on top of that alleviate some of the functionality to build from scratch?
November 22, 2009 at 18:13
Thanks for the note Mohan. It's not a problem though as we already have text rendering and editing working fine in SL 3.0 with our prototype. Also we can provide a lot more customization if we use our own rendering, with things like adornments, margins, etc. that wouldn't be possible with a vanilla RichTextBox-based control.
November 26, 2009 at 10:50
Are you looking at this working on Silverlight 3 only or a Silverlight 4 version also?Are you guys looking to .Net 4 for the Winforms version yet? What is your strategy there? A .Net 4 native version or .Net 2 that loads in the new runtime?
November 26, 2009 at 14:18
Right now we're working with Silverlight 3, but will likely switch to Silverlight 4 when it RTMs since it does overcome limitations in certain key areas (clipboard, etc.).
For WinForms, we'll likely stay with .NET 2.0 for now but will consider moving to a newer framework at some point in the future.
January 1, 2010 at 10:48
Actipro Blog 2009 Q4 posting summary
Actipro Blog 2009 Q4 posting summary
The Actipro Blog - WPF and WinForms Development
May 30, 2010 at 05:04
Your WPF SyntaxEditor control looks awesome. If you released something comparable for Silverlight, I would buy it immediately. Can I replace the IntelliPrompt UI with my own? The adorners are key for me, and the Oslo add-in is a huge bonus since all my grammars are defined in M.
May 30, 2010 at 06:49
I replied to your email already but for the benefit of others, here is a reply here:
The first closed beta just has quick info (no completion list yet). All IntelliPrompt controls have default styles so you can override them however you want.
Adornments are fully supported in the Silverlight version, however I'm not sure Oslo will. The Microsoft Oslo assemblies may or may not work in Silverlight. We haven't tried loading their assemblies there yet. We have not ported over our Oslo add-on for the Silverlight version at this time. If you do try loading Oslo's Xaml, System.Dataflow, etc. assemblies in Silverlight, please let us know what you find.