Tweets by @Actipro
Please take some time to learn more about us and our product offerings.
We’re very happy to have reached the first major milestone for the SyntaxEditor for WPF product, the beginning of alpha testing! SyntaxEditor for WPF is a syntax-highlighting code editor control similar to the Visual Studio code editor.
Yesterday we began a closed alpha test for WPF Studio customers who plan on using SyntaxEditor once it is released.
If you are a WPF Studio customer and would like to apply to be an alpha tester, please e-mail us with your name, e-mail address, and the organization name under which you own WPF Studio licenses (same as your WPF Studio license’s Licensee). Only existing WPF Studio customers may apply. Additionally, provide a brief description of what you plan to do with SyntaxEditor, and how much time you’ll have to start working with the product.
A requirement of being an alpha tester is that you must provide feedback on the product. If you don’t think you’ll have the time to do so, then please don’t apply.
Again this is the first alpha test so while there is a huge amount of work already completed, there will be missing/incomplete features. As we progress towards a beta and later an RTM, we will be adding more and more features.
A lot of people have asked why it’s taking so long to complete the product. As mentioned in past blog posts, we are not just making something to get it out and selling. We are really trying to design a next generation editor that will be the definitive standard for this type of control, mostly on par with VS 2010’s editors capabilities.
We did a quick scan this morning and our current codebase size for the SyntaxEditor and Text assemblies (the two pieces of this product) are already a total of 70,000 lines in the C#, VB, and XAML code files. That should give you an idea of the scope of this product.
January 27, 2009 at 13:13
What about Windows Forms SyntaxEditor customers? We would like to look into using the WPF version to avoid the period of time it will take for you to bring the Windows Forms version up to speed with the new foundation, and we can use the WPF version with interop.
January 27, 2009 at 20:35
Hi Jesper, you may be able to interop the WPF version in. However keep in mind that right now, while SyntaxEditor for WPF has a lot of new features and enhanced features over the WinForms version, there are still a number of areas in which the WinForms version has features that haven't been implemented yet in the WPF version. We are working as fast as possible to get into those areas though.Also note that if you did interop the WPF version into a WinForms application, your base requirements would be .NET 3.0 instead of .NET 2.0.
Bill Henning (Actipro)
January 28, 2009 at 01:44
Our base requirement is already .NET 3.5, so this is not an issue.We don't use a lot of the SyntaxEditor control's more advanced capabilities that we know of, but we would like to have access to the small basic tweaks and improved language support as soon as possible.
February 3, 2009 at 03:23
I am worried that the WinForms version is already suffering. 3.0 language features are missing, and even generics require quite some polishing.Fancy WPF bits will not make this better, I would have preferred to see WinForm port for footprint and more. As well as one that will actually work on Mono. It makes sense, but your choice really..