Home Forums DITA and XMetaL Discussion Searching .dita files using the "Find in Files" feature Reply To: Searching .dita files using the "Find in Files" feature

Derek Read

Reply to: Searching .dita files using the "Find in Files" feature

The following file extensions are included in all “cross file” operations (including Find in Files) by default:


The settings for this can be safely altered in a (well hidden*) dialog:

1. Enable the Macros toolbar.
2. Run the macro named “XMetaL Configuration: About Services”
3. In the dialog that appears select “Multiple-File Operation Service”.
4. On the right side of the same dialog click the button labelled “Extended Info”.
5. In the dialog that appears add or remove file extensions, separating each with a semicolon.

*The reason for hiding this is that the “cross files” feature is new and it was assumed during the design that few people would need to add or remove values from this list. We didn't want to make it impossible to change the values though, so they are exposed here. We don't expect to get a lot of feedback from people saying they need to add other file types, but if we do we might consider moving this setting to a more accessible location.

Note that this whole “XMetaL Services” feature is undocumented because there is good chance we will be changing the way it functions (and we don't want people to start using a feature and then break backward compatibility — this probably applies more to people/partners that might choose to build their own “service”). Ultimately, we might repackage most features in the product as “services” that you can install/uninstall/enable/disable. Currently we have “application level” and “document level” customizations, such as the Journalist and DocBook demos, the CMS integrations, and the DITA authoring functionality, as well as customizations that many clients (and partners) build for their own use, but they are not always easy to separate from the core product. A services model might allow end users to more easily unclutter their UI by removing things they don't use, it might provide a nicer way for developers/partners/us to package and deploy features (customizations). Sort of the same way “plug-ins” for FireFox and other web browsers function. This is not nearly complete, but I thought I would try to preempt any questions about the feature. As it stands today it is best to not mess around with it. Wait until it is fully documented as being something end users or developers (or partners) should be touching.