DataMuseum.dk

top - download

    Length: 2943 (0xb7f)
    Types: TextFile
    Names: »DTIA_C«

└─⟦a7d1ea751⟧ Bits:30000550 8mm tape, Rational 1000, !users!projects 94_04_11
    └─ ⟦129cab021⟧ »DATA« 
        └─⟦this⟧ 
└─⟦f64eaa120⟧ Bits:30000752 8mm tape, Rational 1000, !projects 93 02 16
    └─ ⟦6f12a12be⟧ »DATA« 
        └─⟦this⟧ 
└─⟦2f6cfab89⟧ Bits:30000547 8mm tape, Rational 1000, !projects 94-01-04
    └─ ⟦d65440be7⟧ »DATA« 
        └─⟦this⟧ 

TextFile

Date:           Wed, 29 Aug 90 21:32:58 PST
Date-Delivered: Thu, 30 Aug 90 06:31:51 +0200
From:           yves
To:             cbh
Cc:             rjs, yves
Subject:        Re: DTIA Instantiation For C
In-Reply-To:    Your message of "Wed, 29 Aug 90 10:12:45 +0200"

Salut Chuck,

    Comment se passe ton integration en France? No problem for getting
the code of the small prototype I did for C manipulation. The places
to go are:
    A) !!Ranger!Commands.Internal.Dtia.Remote_File.Rev1_Working
    B) !!Ranger!Machine.Gateway_Classes.Remote_File
    This prototype is not officially packaged but the structuration is
reasonable enough and you should not have any problems using it. Everything
hereafter presupposes the installation on the R1000 and on the workstation
of Dtia_Mechanisms and Dtia_Rpc_Mechanisms (don't forget to run
Remote_Passwords.Add with the workstation name and the couple
[remote_user_name, remote_password]).

    The Remote_File subsystem in !Commands (A) includes the sources of the
gateway_driver (using Dtia_Rpc_Mechanisms & Dtia_Mechanisms); the
procedure Release creates a Load_Proc of the server to the Remote_File
directory in !Machine (B).

    The Remote_File directory in !Machine (B) includes the specification
of the Gateway-Clas, the Text files to be copied to the workstation and the
gateway server (Load_Proc created by Release in B).

    The things to do are basically:

    1) Modify the Gateway_Definition: Data.Host should contain the name
    of the workstation and Data.Context should contain the pathname of
    the remote directory where the remote file will be living.

    2) Copy Hello_C (resp. Beautiful) to the workstation in the remote
    context to hello.c (resp. beautiful).

    3) Build the Gateway_Class by running Gateway_Class.Build.

    4) Activate the Gateway_Class by running Gateway_Class.Activate.

    5) Create a Gateway object by running Gateway.Create.

    6) Hit "Definition" of "Edit" on the created gateway object.

    A window is supposed to appear with the content of the remote file.
The implemented features are only:
    Promot=> If the image is read_only Then
                Execute the C file (hello)
             Else
                Put to workstation (if necessary)
                Compile the C file (make hello)
             End
    Format=> Put to workstation (if necessary)
             Call the shell script beautiful which calls cb
             Get the formatted image back
    Semanticize=> Put to workstation (if necessary)
            Call lint
    Enter=>  Put to workstation (if necessary)
    Common.Revert=> Get from workstation.

    The three first features (Promot, Semanticize and Format) are
customizable thanks to attributes stored in the object. Its is possible
to modify these attributes on the fly by running Gateway.Property_Edit,
the atrributes will be re-read at the next key hit.

    Bonne chance, Amities a Knut.
    Yves.