Conference iosg::all-in-1_v30

    
    Hans,
    
    By attributes, do you mean such things as BOLD and UNDERLINE?  If so,
    you can include <&BOLD>, <&UNDERLINE>, <&CLEAR> as part of your 
    MERGE_LINE string.  See the section on MERGE in Vol 2 of the APR.
    
    Hope this helps,
    
    Jack

    Sorry, I should have mentioned that I meant other than the four
    video attributes. E.g. superscript or technical cahracters, or
    any WPS-PLUS function really.
    
    Hans

Hans,

As long as your boilerplate is store as an ASCII file you cannot have most of
the fancy WPS-PLUS type characters, i.e., line drawing, greek characters,
math symbols, super/subscript, etc.

You can store your boilerplate as a WPS-PLUS file and gain all these nifty
things.  The way I do it is:
1. Create a WPS-PLUS document
2. GOLD GET the template file
3. Edit it the way I like
4. Save it
5. Do a FULLDB to get the VMS filename of the document just created
6. Copy this VMS file to the development directory where the .BLP is
   with the name oldtemplatename.WPS
7. Modify CM$SITELOG to have new .WPS filename as disk location
   a. From menu enter CM$SITELOG
   b. Select appropriate element
   c. C
   d. GOLD 7
   e. GET DISK_LOCATION = "templatename.WPS"
   f. <RETURN><RETURN>
8. Test and delete the old boilerplate file from the development area.

Have fun,

Joe

Re: .-1

That disk location in 7.e. should include the directory name.  You will just
be changing it from whatever-it-is.BLP to whatever-it-is.WPS

    Thanks Joe,
    
    I've tried to follow your example, but maybe I missed something,
    cause I didn't get it to work....
    
    Just as an example, I created a doc, used GOLD G to pick up 
    MAILMEMO1.BLP and edited it. Used FULLDB and copied it to
    OA$SITE_DEV_LLV:MAILMEMO1.WPS.
    
    Called CM$SITELOG, and selected MAILMEMO1 (type BLP). Then I couldn't
    do Create, it said "the post has already been saved in a file", which
    seems logical, but I did an Edit, and changed location on disk to
    OA$SITE_DEV_SWEDISH:MAILMEMO1.WPS.
    
    But when printing a mail message, I still don't see my edited version
    of MAILMEMO1, just the same old one. If I from CM try to edit 
    MAILMEMO1, I get a lot of rubbish, which seems to indicate that I
    have changed the format of it from ASCII to WPSPLUS.
    
    Am I just doing something wrong in accessing the boilerplate?
    I tried Modifying search order to Development first, but no luck...
    
    Hans

Hans,

Humble appologies, and all that.

The ".WPS" should be ".WPL" of course.  (Don't know where my head was.)

You will need to modify search order in CM to access this element while
it is in development (until you move it to live).

You will also need to select WPS PLUS as your CM editor to edit this 
template.

If this doesn't fix your problem then make sure that the CM$SITELOG
record has the same name as the template you're calling in the merge
and that the filename in DISK_LOCATION for that CM$SITELOG record points
to the correct directory and file name.

If all is still not good, give us a call back.

May the ALL-IN-1 gods be with you,

Joe

Hi, 

The solution described in .-* is very unconventional, but then, CM is flexible
enough to do 'anything' ;-). 

To keep track of all changes, the list of actions need a little modification:

Under ALL-IN-1 V2.4:

As you are using standard ALL-IN-1 boilerplates:
    
1. From CM, copy the element which you want to replace from the ADE menu to the 
   Development area, e.g. MAILMEMO1 BLP ENGLISH
2. From CM, modify CM$SITELOG to have new .WPL filename as disk location:
   	<WRITE CHANGE CM$SITELOG %KEY = $CM_KEY,-
	  DISK_LOCATION = "OA$SITE_DEV_<whatever>:MAILMEMO1.WPL",-
	  LIVE_DISK_LOCATION = "OA$SITE_BLP_<whatever>:MAILMEMO1.WPL"
3. Set your CM editor to WPSPLUS
4. Edit the element the way you like
5. Save it
6. Mark the element to be moved to the Live area
7. Move the element to live via the Manager account.

Keep in mind that:

- When using MAIL*.BLP, they reside in the TXL and the CMTXL
  has to be compiled again to include the MAIL_*.WPL


From V3.0:

1. From CM, create a WPS-PLUS boilerplate, e.g. MAILMEMO3 BLPW ENGLISH
2. GOLD GET the template file, e.g. OA$BLP:MAILMEMO1.BLP
3. Edit it the way you like
4. Save it
5. Copy the element which you want to replace from the ABE menu to the 
   Development area, e.g. MAILMEMO1 BLP ENGLISH
6. Mark the element (old, i.s. MAILMEMO1) to be moved to the Live area
7. Move the element to live via a Maintainer account.
8. Copy the new element to the live directory, e.g.
   From the CM menu, select the old element (i.s. MAILMEMO1):
	<GET #A = CM$SITELOG.LIVE_DISK_LOCATION[$CM_KEY]
	<GET #OLD = -
	  FN$REVERSE(FN$RIGHT(FN$REVERSE(#A),FN$LOCATE(FN$REVERSE(#A),"."))) -
	  "WPL"
   Select new element (i.s. MAILMEMO3):
	<COPY CM$SITELOG.DISK_LOCATION[$CM_KEY] #OLD

Keep in mind that:

- When using MAIL*.BLP, they reside in the TXL and the CMTXL has to be 
  compiled again to include the MAIL_*.WPL
- You cannot change the LIVE_DISK_LOCATION of the old element (MAILMEMO1) as
  it is recalculated everytime you mark it to be moved to live
- You should edit the new element when making changes, as CM now assumes a 
  BLP to be an ASCII file


It's a shortcut which I don't like, but it serves your purpose.

Ciao,

	Simon
                         

    Thanks for all your input!
    
    I found out the easy way to test a boilerplate by using it as a
    template in a special FORMAT. But then to make it usable your
    suggestions are valuable. 
    
    Hans

Re: .7

>2. From CM, modify CM$SITELOG to have new .WPL filename as disk location:
>   	<WRITE CHANGE CM$SITELOG %KEY = $CM_KEY,-
>	  DISK_LOCATION = "OA$SITE_DEV_<whatever>:MAILMEMO1.WPL",-
>	  LIVE_DISK_LOCATION = "OA$SITE_BLP_<whatever>:MAILMEMO1.WPL"

Simon,

Thanks for clarifying (and correcting) my disheavled approach.  However,
I still prefer invoking the CM$SITELOG form and updating the location
fields with GOLD 7 over doing a WRITE CHANGE.  You can see that you are
in fact modifying the correct record before you make changes, you can 
see the affected changes before writing the record, and you don't have
to find a way to type in a 120 character statement in a 70 character
CHOICE field.

To each his own,

Joe