Community

in textpad 5 it was sufficient to provide the following:
- a syntax definition file (*.syn) to be copied into the textpad installation directory ("Samples" subdirectory)
- a *.reg file to be imported by the user

the *.reg file contained all relevant preferences for the custom document class:
[HKEY_CURRENT_USER\Software\Helios\TextPad 5\Document Classes\MyCustomDocumentType]
- Members (file extensions)
- SyntaxFile (the name of the custom *.syn)
- Colors (keyword colouring)
- TabStops
- etc.


i'm now trying with textpad 7 and noticed the registry approach got replaced with an xml approach:
FOLDERID_RoamingAppData\Helios\TextPad\<version>\ConfigState.xml

for example see the following section the product's online help:
How To ... -> Customize Settings -> Transferring Between PC's


hence it's no longer possible to "share" a custom document class that can easily be "imported" by another user.

are there any solutions to this scenario?
any such features on the roadmap?

for example see notepad++ where we can import and export specific UDL as *.xml