>> 1) Shouldn't I be able to use Styler on a local machine with a local
>> of the stylesheet/FOSI and test my changes?
>> When I do this (with the doctype and stylesheet NO longer in PE custom
>> directory) I get an error that the stylesheet is not there.
> I'm not totally sure I understand the distinction you're making here. I do
> development with a local copy of my stylersheet. I maintain a different
> screen FOSI, so I flip back and forth renaming whichever stylesheet I'm
> working with at the time to application.fos.current or something like that
> so Editor/Styler will ignore it. When I'm testing locally, I have to issue
> set peservices=no at the start of each Styler session in order to use the
> local composition process.
<drv>I think the issue is the peservices variable, I think that will fix
my Styler issues.
>> 2) What's the best way to setup a sandbox area for making stylesheet
>> changes so I don't affect the production system?
> If you truly want to isolate yourself from the prod system ... it means
> having another PE license (your accountant will love you for that) and a
<drv>No PTC will love me, the accountant will run me out of the company
😉 I missed the relationship of the peservices setting and what that
would cause Styler to do, I would have expected it to switch off PE as its
a development tool.
> separate server (or VM image or whatever your virtualization strategy is).
> What I have done, however, which doesn't isolate me system-wise, isolates
> development, test/qa, and production stylesheets.
> I always distribute three stylesheets when releasing an application for
> first time:
> application.style (could be .fos, depends on the app)
> (The z-naming ensures that the "correct" stylesheet is the default
> in the compose dialog. Recent versions of Editor may be able to
> programmatically specify the default voiding this naming scheme.)
> One PE restart and all of those are available. Then I develop locally. I
> post a "draft" to PE as z_dev.style. (No PE restart required for this to
> picked up.) When I'm satisfied, I "advance" z_dev.style to z_test.style
> my lead authors do test and qa against z_test.style. Now I can move on to
> the next feature set in z_dev.style. Once z_test.style is approved, I
> advance it to application.style, my lead authors do a quick smoke test,
> then announce it to the rest of the authors.
So this sounds like you keep your development efforts all in the same
directory. Or do you develop and test elsewhere and switch peservices off
and on? Is there an advantage to leaving everything in the PE
environment/directories? I'm leaning towards keeping the pure development
and sandbox area in a different location. I can see using your convention
for testing by others.
This switching between stylesheets at compose time is related to the next
question. When PE comes up and shows me the sytlesheet its going to use,
there is only one in the list. I do have the association PI in my
document, maybe that is limiting my choices rather than just specifying
the default selection.
>> 3) What controls the association of a FOSI/Stylesheet to a given DTD?
> It seems like there is some link that is making only one FOSI/Stylesheet
>> avaiable for my test document. In the Editor I'm allowed to go out and
>> select any stylesheet to try and format with, PE seems to be limited to
>> the one sitting with the DTD.
>> Note that I have a DTD that exists in several variations, I have
>> FOSI's for these DTDs, what I wanted to do was to test the various FOSIs
>> with the same document and DTD. If nothing else to get away from the one
>> with errors and use one of the other FOSIs. I don't expect perfect
>> results, but I would like to see what happens. Ultimately these are all
>> variations on the CALS DTD, so I would like to just run my document with
>> the Arbortext CALS FOSI if nothing else.
> There is a whole series of "rules" and priority and whatnot for making
> choice. Normally if your doctype and stylesheet have the same name, they
> associated. There is also a processing instruction you can use to force an
> association. Our doctype/stylesheet associations are static, so I don't do
> lot here ... take what I said with a grain of salt. Hopefully someone who
> changes things around more will reply with more authority/detail. Or at
> least good pointers for what to search for in Help.
<drv>What I was expecting was the flexibility that the Editor option of
Format - Select Stylesheets allows me when it came time to print.
thanks for the ideas
> Paul Nagai