Tweets by @Actipro
Please take some time to learn more about us and our product offerings.
A week or so ago in our newsletter we officially announced the development of Actipro Docking for WPF and Actipro SyntaxEditor for WPF. These two products when completed will be added to our WPF Studio control bundle.
Also note that we have some other special controls in development as well, but we'll keep those under wraps for now.
A WPF window showing tool windows that are docked and in auto-hide mode, along with a SyntaxEditor control in the content area of the DockSite
The Docking product is progressing very nicely and is expected to be the next major product added to WPF Studio. Its design harnesses our themes framework, thereby making it easy for us to provide alternate themes such as Aero, or Office themes with minimal effort.
Docking includes many of the extremely flexible behavior options that have made our UIStudio Dock for Windows Forms product very popular. We also have some surprises in store. We'll get into some of these options and new features in future posts.
We're approaching the SyntaxEditor product as an opportunity to do a lot of neat new things and make improvements to the SyntaxEditor for Windows Forms product that is recognized as the industry leader in syntax highlighting editor controls.
One design goal of ours is to try and separate out the document/parsing model to a .NET 2.0-based assembly that could be used by both SyntaxEditor for WPF, SyntaxEditor 5.0 for Windows Forms, and a future CodeHighlighter.
We are working on doing some big language design enhancements too. Even though what we have now is great, we have a lot more ideas that we want to integrate, making it easier for you to develop both simple and complex language parsers for your editor.
Stay tuned to the blog for more information on Docking, SyntaxEditor and other new controls. We'll continue to post new information as development progresses.
August 5, 2008 at 06:49
As long as the WPF Syntax Editor isn't available, we considering to use de Forms Syntax Editor. We will implement a non-dynamic language (Blaise), probably using Antler for generating parsers etc. Will the transformation to the WPF version be possible and be straighforward?
Martin de Jong
August 5, 2008 at 18:38
Hi Martin,We haven't gotten into the coding of the parsing part of the WPF SyntaxEditor yet so it's hard to say. However one thing we are looking at is making it easy to convert an ANTLR grammar definition over to our grammar.
Bill Henning (Actipro)
January 10, 2009 at 20:15
I have written a custom test system runtime and test system language compiler in C# using the GOLD Parser Builder and Morozov Engine. See http://www.devincook.com/goldparser/(The grammar is defined using BNF/regular expression syntax and the parsing engine calls my code when keywords and grammar rules are encountered)I am interested in using your WPF Syntax Editor.When do you expect it to be done?Can I use my parser or do I have to rewrite it using your parsing system?Does your grammar definition and parsing system work in a similar fashion to the GOLD Parser Builder?
January 11, 2009 at 01:23
Hi Dave,We are getting very close to having a closed alpha for some initial beta testers. The first release of the control will not likely have any semantic parsing features but that will be worked on following initial public release. In SyntaxEditor 4.0 (WinForms) we have mechanisms for you to tie in custom semantic parsers. We'll have something similar in the WPF version as well.