![]() ![]() That DSL file is likely to be quite compact (less than 100 lines), and will be the part of the application that is visible to users. If this technique works as well for you as it has worked for me on my projects, then you will end up with your translation application being an "engine" whose behaviour is driven entirely by a configuration file that, in effect, is a DSL (domain-specific language). For example, you might use one table to provide a source URL -> destination URL mapping, and a different table to provide instructions for translating fields within messages. Also, don't feel you have to shoehorn all of your translation-based configuration into a single table. If you decide to use this technique, then obviously you will need to invent instructions to specify runtime translations rather than instructions to generate code. I have used the above technique in several projects, and each time I have invented instructions specific to the needs of the particular project. This is the last but one action in the action. The first thing you will want to do is to create a Draft with the Taskpaper format. #Taskpaper stylesheets codeThe instruction specified that code should be generated to assign I have created an any action group for Drafts 5 which is meant to help you create Taskpaper formatted projects or tasks and then send it all along to OmniFocus afterwards.The instruction specified that no code should be generated to. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |