We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. (Last updated on : Nov 16th 2018).
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

How hard to configure for a new language?

Thread ID:

Created:

Updated:

Platform:

Replies:

10501 Feb 4,2004 05:49 AM UTC Feb 4,2004 11:08 AM UTC WinForms 1
loading
Tags: EditControl
Jay Ayliff
Asked On February 4, 2004 05:49 AM UTC

I just found out about the SyncFusion Edit control. Before I invest major time & effort, has anyone created a complete config for a language? How hard is it? I''m thinking of Caché ObjectScript/MUMPS. Has anyone done that?

Administrator [Syncfusion]
Replied On February 4, 2004 11:08 AM UTC

Hi Jay, Creating a configuration file for Essential Edit is a relatively simple task. Please refer to the sample configuration files in the directory ...\Syncfusion\Essential Suite\Edit\Samples\Ini Files. This contains configuration files for several languages such as C, C++, C#, VB.NET, Java, SQL etc. Each language has a specific configuration file associated with it, which contains its syntax coloring information like the ColorGroups, Tags, Keywords, DataTypes etc. You can easily use our syntax configuration model to create a configuration file for any desired language. Once the configuration file is ready, you could simply plug this into the EditControl using the following code : editControl.SettingFile = ConfigurationFileName; Please let me know if you need any other information. Thanks for considering Syncfusion products. Regards, Guru Patwal Syncfusion, Inc.

CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

Warning Icon You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.Close Icon

;