
Hi Syd, oXygen has a default page per type of editor (XML, XSL, XSD, etc.) in Options->Preferences -- Editor -- Pages. Then each Document Type (aka framework) can specify an initial page. When an document is closed oXygen remembers the page if that is different than the default, let's call it document-page association. Now, when a file is opened oXygen tries to determine the page to use as follows: 1. it looks for a document-page association and if it finds it then it uses that 2. it looks if there is a document type matching the file and uses the page specified for the document type 3. it uses the default page for the editor A framework configuration can be stored either externally, in a .framework file or internally in the oXygen options file. All the frameworks provided by oXygen by default are stored in external .framework following the pattern: [oxygen]/frameworks/[framewokFolder]/[frameworkName].framework When you edit an external framework from Options->Preferences -- Document Type Associations the changes are stored in the corresponding .framework file. For example for TEI P5 that file is [oxygen]/frameworks/tei/teip5.framework So you can basically change all the oXygen frameworks as you like and then you can distribute the updated frameworks folder on a different machine, either by replacing the [oxygen]/frameworks folder in the oXygen installation on that machine or by directing the users to set a custom frameworks folder pointing to the one you supply. They can set a custom frameworks folder from Options->Global by enabling "Use custom frameworks directory" option and then specify the frameworks folder in the "Frameworks directory" field. (Please note that after setting a custom frameworks folder oXygen needs to be restarted to have the new frameworks loaded) Another possibility is to take advantage of the Project level options that oXygen provides. You need to duplicate the external frameworks (using the Duplicate button on the Document Type Association page), they will be duplicated as internal frameworks, that is stored in the oXygen options, then disable the external frameworks by un-checking the checkboxes from the "Enabled" column to avoid conflicts with their duplicates. Edit the duplicate frameworks to specify the desired initial page and then select the "Project Options" radio option on the Document Type Association page to direct these options to be stored in the current project .xpr file. If the students will open that project then they will automatically get those options for the Document Type Association page, that is all the internal duplicated and updated frameworks and all the external frameworks disabled. If you have difficulties with any of these approaches let me know. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Syd Bauman wrote:
oXygen has four potential "modes" with which to view a file: Text, Grid, Author, and Design. I *always* want files ot open in Text mode initially. I realize that for any given document type, I can change the ihitial opening mode to Text mode in the "Document Type Association" preferences pane, as long as I tell it I'm a developer. But is there a way to do them all at once?
That's just for me. But the problem is bigger than that. I'm about to teach a TEI workshop using oXygen. They've bought a license and are busy installing oXygen 11 on a bunch of machines. It could be pedagogically counter-productive if when the students open their first template file, they get Author mode instead of Text mode. Is there a way I can change this behavior globally? Or at least a way to get this behavior without asking those doing the installation to manually adjust the preferences each time? (It takes roughly a dozen clicks/actions.) E.g., would it work to set the preferences the way I want them once, and then copy that instllilation to other machines? Can we just copy over a single preferences or framework file?
Thanks. _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user