[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

1695.0. "Supported or unsupported?" by CDROM::DUPREZ () Wed Nov 08 1989 09:01

    This relates to an earlier note I put in (1685).  I now know how
    to add additional verbs to "Applications" under the Session Manager
    by adding text to the sm defaults - my question is, is doing this
    as part of a product installation something that is/will be supported?
    
    Here's the bigger picture.  We are looking at having an application
    be available under Session Manager, FileView, or both.  I already
    know the supported way for providing a new verb as the product is
    installed under FileView so that ALL users may add it.
    
    I would like to do the same under the Applications menu in Session
    Manager.  I was able to do it by modifying (as suggested in a reply)
    the appropriate .DAT file in DECW$SYSTEM_DEFAULTS, but I'm not quite
    sure this is what I should be doing.
    
    Is there any way I can augment what is in this file by putting an
    addition to it in SYS$COMMON:[DECW$DEFAULTS.USER]?  And is this
    something I should even be attempting, or am I going against the
    laws of DECwindows nature?
    
    Any info would be helpful, and a pointer to the appropriate
    documentation would be even more helpful.
    
    						Thanks,
    						Roland
                                                      
T.RTitleUserPersonal
Name
DateLines
1695.1look at 1685.21SHOT::HOULESteve, NM is the future!Thu Nov 09 1989 10:161
    
1695.2No supported waySTAR::BROUILLETTEMon Nov 13 1989 13:5725
    
    Adding a command to the session manager at product installation time is
    not supported for V2.   The best you can do for V2 is to 'unofficially'
    change decw$system_defaults:decw$session.dat.  The commands in this
    file are considered "system commands", and cannot be modified in the
    Customize Application Definition dialog box.  But they will appear in
    the listbox and can be moved to the users Applications menu.  The
    commands you add will work like the commands to start the OOTB
    applications.  
    
    A new version of decw$session.dat is NEVER written out by the session
    manager.  So, unless a user edits this file, your change will not be 
    overwritten.   It is only used at application startup time.   Of 
    course the user could have manually created a decw$session.dat in
    either [decw$defaults.user] or in sys$login, and this file would
    override the one in [decw$defaults.system].  But users who do this may
    not have all of the OOTB commands either.  
    
    You could also put a version in [decw$defaults.user]. That file would be 
    read at the session manager application startup time INSTEAD of the one 
    in [decw$defaults.system].  The two are not merged by the toolkit.
    
    Application startup is being improved in V3 of DECwindows and this
    problem will go away.