LMX-Editor Addin for SharpDevelop
Create a SecondaryDisplayBinding addin for SharpDevelop IDE ([url removed, login to view]), to extend the original XmlEditor Addin([url removed, login to view]) that comes with SharpDevelop, with the features found in LMX-Editor ([url removed, login to view]).
LMX-Editor is a small open source project written in c#, that uses an alternative notation for representing XML files (Less Markap XML). SharpDevelop is well documented open source project also written in C#. There are a lot of papers, videos (see - HTML preview - Creating a custom secondary display binding.) ([url removed, login to view]) and a free e-book([url removed, login to view]) about how to write an addin for SharpDevelop.
Features to be Implemented:
All features found in LMX-Editor(syntax highlighting, folding, element, attribute and namespace auto-completion for configured schemas, well formed document check, validation against a schema(XSD). and so on...) must be implemented. In addition the following features also must be implemented: intelligent intellisense and one special new markap notation (LMX-Editor has five markap notation option) that allows end-users to "Edit as Table", similar to "Display as Table" in "Enhanced Grid View in Altova XMLSpy Editor"([url removed, login to view])
The addin you will create must work binded to a .xsd (W3C Schema) file, and offer all intelligent editing features such as context-sensitive choices, It must also work without binding any schema. In this case, of course, without all Intelligent editing features. LMX-Editor project uses CodeEditor/ColorTectBox controls. You can not use these control to implement the Addin. You have to use the original SharpDevelopTextEditor ([url removed, login to view]) instead. The SecondaryDisplayBinding LMXEditor must perform "round-trip" with SD Xml Editor. As the end-user changes the content in one view, the other one must be updated. 'Element Outline', 'Markap Configuration' and 'Editor Log' windows must be implemented as SharpDevelop Pads. All options (Markap Notation, Markap Configurations, Conversion Options and Editor Appearance) must be implemented as Sharpdevelop Options Panels
The code must be documented, written following the Best Practices, and using as much as possible the classes that already exists in SharpDevelop. The addin must be developed using C# and .NET Framework Class Library. Deliverables include fully-tested, bug-free final addin, source files, and copyright as always. All communications via e-mails. Must check in at least tree times a week during the project, with project status and/or questions. Payment via escrow account.
Please, do not bid if you are not a very experienced coder in C#, .NET, XML and XSD or you are not sure that you can finish this project.