Steps to "de-pod" workspaces in FM 9

Report · Aug 27, 2010

In a current thread

http://forums.adobe.com/thread/707908?tstart=0

a user is having problems working with a large file in FM9. I suggested he try "de-podding" the FM workspace to see whether that saved enough RAM and whether that might help to successfully create the print file without graphics dropping out.

Info about the workspaces is here:

Workspaces in FrameMaker 9

The pods are where FM enumerates variables, markers, cross-refs, conditional text, fonts, and all the other goodies it creates / uses. Even if your particular docs don't use any of these features, my understanding is that FM still has to scan the doc to populate these panels, adding processing time and overhead.

In my own experience, being able to use a "de-podded" workspace is essential to being able to open and work with "large" files. System has 4gigs of RAM, WInXP. In an extreme example, a single chapter of 1800 pages of tables, approx 1.4 million cells total. The symptoms of the problem are that the files either won't open, or they're excruciatingly slow to open, or there is display and system instability to the point where FM has to be closed in Task Manager and the system rebooted. In a typical example, a de-podded workspace opens the file in approx 6 seconds. With the FM workspace called "Authoring" it brings FM to a complete halt. A smaller subset file of this, 83 pages, takes 4 seconds to open de-podded, 1.55 minutes with Authoring workspace.

Following the instructions in the above Workspaces explanation it's possible to create your own workspace files; I will post my own versions of these files in a reply to this message, if anybody would like to test them.

Regarding the "de-podding" process, though, I found that the following was ** essential ** in order to have the pods correctly suppressed.

Two steps are needed in order to get FM to be correctly de-podded for a given user:

1. put the nopods.fws and .cfws into the user’s Documents and Settings location (location varies according to Windows version)

2. have the user open FM, open a new blank FM document, select the "NoPods" workspace, close the new document, and use File > Exit to close FM.

If #2 isn’t done, then the symptom is that FM won’t open existing files (either double-clicking in Explorer or doing File Open in FM’s menu) with nopods active, even though nopods files exist in the correct Documents and Settings location and even though FM will, however, open a new blank document and have the nopods correctly activated.

Sheila

Report · Aug 27, 2010

I don't know whether the forum software will mangle the following content or not, but here's a test.

Save the lines after the two ==== lines as "NoPods.cfws" in %APPDATA%\Adobe\FrameMaker\9\WorkSpaces\Unstructured

where %APPDATA% is something like c:\documents and settings\<username>\Application Data

The location varies depending on your Windows version.

==================

NoPods.cfws

==================

<FrameUI version="1">
    <data type="all"/>
    <fm-workspace>
        <workspace version="1">
            <dock anchor="left" content="palette toolbar" is-closed="false"/>
            <dock anchor="right" content="palette toolbar" is-closed="false"/>
            <dock anchor="top" content="multi-control-bar" is-closed="false">
                <control-bar-pane >
                    <control-bar id="00F109AC" origin="0 0" size="551 26" is-closed="false" app-data="#lt;control-bar cb-data=#quot;tb_txt_fmt#quot; minimum-size=#quot;438 26#quot; maximum-size=#quot;1680 26#quot; preferred-size=#quot;551 26#quot;/>"/>
                    <control-bar id="003F0A02" origin="569 0" size="266 26" is-closed="false" app-data="#lt;control-bar cb-data=#quot;tb_tr_ch#quot; minimum-size=#quot;266 26#quot; maximum-size=#quot;266 26#quot; preferred-size=#quot;266 26#quot;/>"/>
                </control-bar-pane>
                <control-bar-pane >
                    <control-bar id="004C0A20" origin="0 0" size="608 26" is-closed="false" app-data="#lt;control-bar cb-data=#quot;tb_qck#quot; minimum-size=#quot;608 26#quot; maximum-size=#quot;608 26#quot; preferred-size=#quot;608 26#quot;/>"/>
                    <control-bar id="002D09F2" origin="626 0" size="460 26" is-closed="false" app-data="#lt;control-bar cb-data=#quot;tb_para_fmt#quot; minimum-size=#quot;445 26#quot; maximum-size=#quot;1400 26#quot; preferred-size=#quot;460 26#quot;/>"/>
                </control-bar-pane>
            </dock>
            <dock anchor="bottom" content="palette" is-closed="false">
                <tab-pane mode="expanded" preferred-iconic-length="0" layout-mode="auto-flow">
                    <tab-group active-palette="014A0A96" is-closed="false">
                        <palette id="00150A32" is-closed="true" preferred-unconstrained-size="998 179" preferred-constrained-size="998 179" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 24 0;1;2;3;4;292;175;175;87;243;0;0#quot; minimum-size=#quot;562 179#quot; pref-unc-size=#quot;998 179#quot; pref-c-size=#quot;998 179#quot; maximum-size=#quot;1920 600#quot;/>" host-cached-sizes="false"/>
                        <palette id="014A0A96" is-closed="true" preferred-unconstrained-size="998 179" preferred-constrained-size="998 179" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 43 0;1;2;292;438;243;0;0#quot; minimum-size=#quot;592 179#quot; pref-unc-size=#quot;998 179#quot; pref-c-size=#quot;998 179#quot; maximum-size=#quot;1920 600#quot;/>" host-cached-sizes="false"/>
                    </tab-group>
                </tab-pane>
            </dock>
            <dock anchor="none" content="palette toolbar" origin="1567 181" is-closed="true">
                <tab-pane mode="icon" preferred-iconic-length="173" layout-mode="manual">
                    <tab-group active-palette="000D0AE8" is-closed="false">
                        <palette id="000D0988" is-closed="false" preferred-unconstrained-size="350 315" preferred-constrained-size="135 240" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 42 #quot; minimum-size=#quot;80 80#quot; pref-unc-size=#quot;350 315#quot; pref-c-size=#quot;135 240#quot; maximum-size=#quot;960 1200#quot;/>" host-cached-sizes="false"/>
                        <palette id="009D0976" is-closed="false" preferred-unconstrained-size="204 143" preferred-constrained-size="135 1039" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 17 #quot; minimum-size=#quot;80 80#quot; pref-unc-size=#quot;204 143#quot; pref-c-size=#quot;135 1039#quot; maximum-size=#quot;960 1200#quot;/>" host-cached-sizes="false"/>
                        <palette id="009B0960" is-closed="false" preferred-unconstrained-size="260 117" preferred-constrained-size="260 117" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 56 #quot;/>" host-cached-sizes="false"/>
                        <palette id="003D0A42" is-closed="false" preferred-unconstrained-size="299 159" preferred-constrained-size="299 159" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 52 #quot;/>" host-cached-sizes="false"/>
                        <palette id="000D0AE8" is-closed="false" preferred-unconstrained-size="204 143" preferred-constrained-size="204 143" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 51 #quot;/>" host-cached-sizes="false"/>
                    </tab-group>
                </tab-pane>
            </dock>
            <dock anchor="none" content="palette toolbar" origin="1163 503" is-closed="true">
                <tab-pane mode="expanded" preferred-iconic-length="173" layout-mode="manual">
                    <tab-group active-palette="00150AD6" is-closed="false">
                        <palette id="00600BE2" is-closed="false" preferred-unconstrained-size="315 393" preferred-constrained-size="315 393" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 54 #quot;/>" host-cached-sizes="false"/>
                        <palette id="00150AD6" is-closed="false" preferred-unconstrained-size="212 241" preferred-constrained-size="212 241" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 50 #quot;/>" host-cached-sizes="false"/>
                        <palette id="000F0B2E" is-closed="false" preferred-unconstrained-size="249 208" preferred-constrained-size="249 208" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 49 #quot;/>" host-cached-sizes="false"/>
                    </tab-group>
                </tab-pane>
            </dock>
            <dock anchor="none" content="palette toolbar" origin="1100 238" is-closed="true">
                <tab-pane mode="icon" preferred-iconic-length="173" layout-mode="manual">
                    <tab-group active-palette="00190D32" is-closed="false">
                        <palette id="000D0C9E" is-closed="false" preferred-unconstrained-size="327 294" preferred-constrained-size="327 294" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 26 #quot;/>" host-cached-sizes="false"/>
                        <palette id="000A0C80" is-closed="false" preferred-unconstrained-size="426 361" preferred-constrained-size="426 361" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 25 0;1;2;3;100;100;100;100;0;0#quot; minimum-size=#quot;423 361#quot; pref-unc-size=#quot;426 361#quot; pref-c-size=#quot;426 361#quot; maximum-size=#quot;960 1200#quot;/>" host-cached-sizes="false"/>
                        <palette id="000A0CDC" is-closed="false" preferred-unconstrained-size="414 358" preferred-constrained-size="414 358" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 48 #quot;/>" host-cached-sizes="false"/>
                        <palette id="00190D32" is-closed="false" preferred-unconstrained-size="426 387" preferred-constrained-size="426 436" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 45 0;1;2;104;148;148;0;0#quot; minimum-size=#quot;426 387#quot; pref-unc-size=#quot;426 387#quot; pref-c-size=#quot;426 436#quot; maximum-size=#quot;960 1200#quot;/>" host-cached-sizes="false"/>
                    </tab-group>
                </tab-pane>
            </dock>
            <dock anchor="none" content="palette toolbar" origin="859 212" is-closed="true">
                <tab-pane mode="icon" preferred-iconic-length="173" layout-mode="manual">
                    <tab-group active-palette="001E0C76" is-closed="false">
                        <palette id="001E0C76" is-closed="false" preferred-unconstrained-size="350 315" preferred-constrained-size="350 315" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 29 #quot;/>" host-cached-sizes="false"/>
                    </tab-group>
                </tab-pane>
                <tab-pane mode="icon" preferred-iconic-length="173" layout-mode="manual">
                    <tab-group active-palette="000A0D82" is-closed="false">
                        <palette id="000A0D82" is-closed="false" preferred-unconstrained-size="279 242" preferred-constrained-size="279 242" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 28 #quot;/>" host-cached-sizes="false"/>
                    </tab-group>
                </tab-pane>
            </dock>
            <dock anchor="none" content="palette toolbar" origin="1372 46" is-closed="true">
                <tab-pane mode="icon" preferred-iconic-length="111" layout-mode="manual">
                    <tab-group active-palette="000D0D62" is-closed="false">
                        <palette id="000D0D62" is-closed="false" preferred-unconstrained-size="350 315" preferred-constrained-size="350 315" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 20 #quot;/>" host-cached-sizes="false"/>
                        <palette id="000A0DA6" is-closed="false" preferred-unconstrained-size="366 164" preferred-constrained-size="366 164" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 15 #quot;/>" host-cached-sizes="false"/>
                    </tab-group>
                </tab-pane>
            </dock>
            <dock anchor="none" content="palette toolbar" origin="848 342" is-closed="false">
                <toolbar id="000B0F4E" origin="2 25" size-variant="vertical-wide" is-closed="false" app-data="#lt;tool-bar tb-data=#quot;ToolBar_0#quot; vertical-wide-size=#quot;53 380#quot; horizontal-size=#quot;0 0#quot;/>"/>
            </dock>
            <dock anchor="none" content="palette toolbar" origin="1524 77" is-closed="false">
                <tab-pane mode="expanded" preferred-iconic-length="173" layout-mode="manual">
                    <tab-group active-palette="00400F20" is-closed="false">
                        <palette id="00400F20" is-closed="false" preferred-unconstrained-size="350 315" preferred-constrained-size="350 315" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 19 #quot;/>" host-cached-sizes="false"/>
                    </tab-group>
                </tab-pane>
            </dock>
            <dock anchor="none" content="palette toolbar" origin="1476 542" is-closed="false">
                <tab-pane mode="expanded" preferred-iconic-length="173" layout-mode="manual">
                    <tab-group active-palette="000A0FBC" is-closed="false">
                        <palette id="000A0FBC" is-closed="false" preferred-unconstrained-size="266 124" preferred-constrained-size="266 124" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 14 #quot;/>" host-cached-sizes="false"/>
                    </tab-group>
                </tab-pane>
            </dock>
            <dock anchor="none" content="palette toolbar" origin="1060 104" is-closed="true">
                <tab-pane mode="expanded" preferred-iconic-length="0" layout-mode="manual">
                    <tab-group active-palette="000F10DC" is-closed="false">
                        <palette id="000F10DC" is-closed="false" preferred-unconstrained-size="359 245" preferred-constrained-size="359 245" current-state="1" is-minimized="false" app-data="#lt;palette kit-data=#quot;3 13 #quot;/>" host-cached-sizes="false"/>
                    </tab-group>
                </tab-pane>
            </dock>
        </workspace>
    </fm-workspace>
</FrameUI>

Report · Aug 27, 2010

This is the SECOND file, not that it's named ".fws" rather than ".cfws".

Save the lines after the two ==== lines as "NoPods.fws" in %APPDATA%\Adobe\FrameMaker\9\WorkSpaces\Unstructured

where %APPDATA% is something like c:\documents and settings\<username>\Application Data

The location varies depending on your Windows version.

==================

NoPods.fws

==================

Report · Aug 28, 2010

Some additional info you might find helpful in managing workspaces and pods at a deeper level.

The storage location depends on whether you use FrameMaker in Structured or Unstructured mode:

%APPDATA%\Adobe\FrameMaker\9\WorkSpaces\Structured

%APPDATA%\Adobe\FrameMaker\9\WorkSpaces\Unstructured

The files are XML files internally and the file name extensions most probably have the following meaning:

*.fws - FrameMaker WorkSpace

* cfws - Current FrameMaker WorkSpace

Why this? If you save a workspace a *.fws file is created. If you reset a workspace, the data from the *.fws is used.

If you change anything in a workspace those changes are saved in the *.cfws, therefore they persist even if you change workspaces or quit FrameMaker. If you select another workspace, the *.cfws data is used if such a file exists otherwise the *.fws is used. If you want to update the *.fws after you made changes to it, just save it again under the same name.

If you want to distribute workspace settings to others it is sufficient to give them the *.fws.

Theoretically it is possible to create a minimal workspace file looking like this:

<fm-workspace>

</fm-workspace>

</FrameUI>

But you will notice that a "real" workspace file contains information about preferred location and also pixel dimensions. I have not tested it, but I guess workspace files should only be shared between users with similar monitor setups. Also, to create an empty workspace it is easier to just close all pods and toolbars and save it. This resulted for me in a file that is basically identical to Sheila’s NoPods.fws – and you save yourself the possible problems with XML text copied from this forum.

And if new to the FrameMaker 9 UI you should always listen to RJ Jacquez’ presentation at

http://rjacquez.com/elearning_session_on_the_new_u/

- Michael

Report · Aug 30, 2010

Thank you for adding the clarification, Michael. Agreed that creating an "original, from scratch" workspace is the best of all solution.

It seems to me that there are some tricky distinctions between how FM's other .ini and config files work vs. the way the workspaces are "activated" -- specifically, having to have a file open in order to change or save workspaces -- can make getting up to speed with them daunting. This is especially true in configuring server systems that are used for automated FM processing, or for users who regularly work with "large" files (either large in content or large in numbers of markers/variables etc and who might not realize that the pods could be the culprits in FM doc opening delays.

Not to beat a tired horse as I know you're already aware of the issue, but for other forum readers this is the reason I mentioned the "symptom" of FM not being able to open (or taking an extraordinary long time to open) existing files -- even when the .cfws and .fws files exist in the correct directory locations.

Sheila

Report · Aug 30, 2010

AxialInfo wrote:
Thank you for adding the clarification, Michael. Agreed that creating an "original, from scratch" workspace is the best of all solution.
It seems to me that there are some tricky distinctions between how FM's other .ini and config files work vs. the way the workspaces are "activated" -- specifically, having to have a file open in order to change or save workspaces -- can make getting up to speed with them daunting. This is especially true in configuring server systems that are used for automated FM processing, or for users who regularly work with "large" files (either large in content or large in numbers of markers/variables etc and who might not realize that the pods could be the culprits in FM doc opening delays.
Not to beat a tired horse as I know you're already aware of the issue, but for other forum readers this is the reason I mentioned the "symptom" of FM not being able to open (or taking an extraordinary long time to open) existing files -- even when the .cfws and .fws files exist in the correct directory locations.
Sheila

InDesign can create, reset, and choose among workspaces and perform a number of UI settings and set a number of defaults, without any open documents. If the current workspace is not able to display and set these items through the Control panel, Application Bar, or Application Frame, almost every panel can be opened from the Window menu.

Preferences and settings made with no document open become application defaults; preferences and settings made within a document but with no active selection, become document defaults; preferences and settings made with a selected object, paragraph, table, or tool, become the default for that item.

It's very flexible, but totally crazy-making if you have poor short-term memory, or if you step into someone else's workstation environment, because there are no indicators that, say, a paragraph style (aka FrameMaker format) is the document or application's or document's default.

It's possible to dream that some scripting ace will set about extracting these settings from wherever they're kept - if the information is exposed in the scripting model - and either donate the script to the community, or perhaps will commercialize it.

FrameMaker's approach of storing these settings in accessible text files may be old-school, but it's helpful to some folks to have this kind of open access to the settings.

Regards,

Peter

_______________________

Peter Gold

KnowHow ProServices

Report · Oct 14, 2010

Sheila,

Many thanks for your very helpful post. I was looking for a solution with FM 9 Server where it would crash at about the 692/693 file when batch converting documents. I have noticed the pods but had not thought to close them. Creating a minimal workspace with all pods closed resolved the problem.

BTW I found this comment in the link Workspaces in FrameMaker 9 in your post very noteworthy!

'While using Workspaces it might help to have the option Hide Panels On Close ‘unchecked’ (File->Preferences->Interface). Otherwise it might happen that many panels remain open in the hidden state.'

Jon