• Netmail/wcWEB

    From CHRIS CRANFORD@1:124/5013 to All on Thu Jan 31 19:10:38 2019
    Date: Tue, 12 Nov 2002 10:35:45 -0400
    From: CHRIS CRANFORD
    To: HECTOR SANTOS
    Subject: Netmail/wcWEB
    Newsgroups: win.server.wish.list
    Message-ID: <1037115345.33.0@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 37

    Hector -

    Do you think it would be possible to incorporate creating of netmail
    messages via the WEB interface as a core piece of functionality to
    Wildcat!?

    If not I understand, but what I had visioned would be the current
    template checks the mailarea type. If it's a netmail area, the
    template would display two text boxes (each next to the to/from user
    names) in the form.

    Since the ansi side looks for fidomsg.wcx to run when creating netmail,
    I would think there could be a variable that represents whether
    html-fidomsg.wcx existed. If so, then the template would also show
    a button with like "..." as the caption that spawns a popup window
    which runs the html-fidomsg.wcx hook.

    The html-fidomsg.wcx hook would be a custom module that we'd need to
    write ourselves that parses or reads a nodelist data file and gives
    the user the option to select a nodelist entry to send to/from.
    When the selections are made, the data is set in the calling form and
    the popup window is closed.

    Since the fields for the node numbers are text boxes, the user could
    also just type in a FTN-address in 3D/4D/5D format that the create
    message code parses and sets in the message header.

    If you want me to modify the code for the hooks and submit it to you,
    I'll be welcome to in order to try to push this into the core package. I
    know you want to keep things consistent regardless of connectivity type,
    and I think it's a step in that direction. I also realize that this is
    a very LOW LOW item on the list of things to change/add to WINSERVER
    which is why I'm willing to put it together and submit it to ya if that
    is what works the best for you.

    Thoughts?
    Chris
    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From TODD COCHRANE@1:124/5013 to All on Thu Jan 31 19:10:38 2019
    Date: Tue, 12 Nov 2002 10:43:45 -0400
    From: TODD COCHRANE
    To: CHRIS CRANFORD
    Subject: Netmail/wcWEB
    Newsgroups: win.server.wish.list
    Message-ID: <1037115825.33.1037115345@winserver.com>
    References: <1037115345.33.0@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 41

    If someone could make the fidomsg.wcx a little more robust I would be
    happy..


    Hector -

    Do you think it would be possible to incorporate creating of netmail
    messages via the WEB interface as a core piece of functionality to
    Wildcat!?

    If not I understand, but what I had visioned would be the current
    template checks the mailarea type. If it's a netmail area, the
    template would display two text boxes (each next to the to/from user
    names) in the form.

    Since the ansi side looks for fidomsg.wcx to run when creating netmail,
    I would think there could be a variable that represents whether
    html-fidomsg.wcx existed. If so, then the template would also show
    a button with like "..." as the caption that spawns a popup window
    which runs the html-fidomsg.wcx hook.

    The html-fidomsg.wcx hook would be a custom module that we'd need to
    write ourselves that parses or reads a nodelist data file and gives
    the user the option to select a nodelist entry to send to/from.
    When the selections are made, the data is set in the calling form and
    the popup window is closed.

    Since the fields for the node numbers are text boxes, the user could
    also just type in a FTN-address in 3D/4D/5D format that the create
    message code parses and sets in the message header.

    If you want me to modify the code for the hooks and submit it to you,
    I'll be welcome to in order to try to push this into the core package. I
    know you want to keep things consistent regardless of connectivity type,
    and I think it's a step in that direction. I also realize that this is
    a very LOW LOW item on the list of things to change/add to WINSERVER
    which is why I'm willing to put it together and submit it to ya if that
    is what works the best for you.

    Thoughts?
    Chris
    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From CHRIS CRANFORD@1:124/5013 to All on Thu Jan 31 19:10:38 2019
    Date: Tue, 12 Nov 2002 10:49:39 -0400
    From: CHRIS CRANFORD
    To: TODD COCHRANE
    Subject: RE: Netmail/wcWEB
    Newsgroups: win.server.wish.list
    Message-ID: <1037116179.33.1037115825@winserver.com>
    References: <1037115825.33.1037115345@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 53

    On 11/12/02 10:47 AM, TODD COCHRANE wrote to CHRIS CRANFORD:

    Fidomsg.wcx is a program written by Santronics for Platinum Xpress. I
    have written my own fidomsg.wcx; however it interfaces with other
    software products I use here instead of PX :o)...

    Chris

    If someone could make the fidomsg.wcx a little more robust I would be happy..


    Hector -

    Do you think it would be possible to incorporate creating of netmail
    messages via the WEB interface as a core piece of functionality to
    Wildcat!?

    If not I understand, but what I had visioned would be the current
    template checks the mailarea type. If it's a netmail area, the
    template would display two text boxes (each next to the to/from user
    names) in the form.

    Since the ansi side looks for fidomsg.wcx to run when creating netmail,
    I would think there could be a variable that represents whether
    html-fidomsg.wcx existed. If so, then the template would also show
    a button with like "..." as the caption that spawns a popup window
    which runs the html-fidomsg.wcx hook.

    The html-fidomsg.wcx hook would be a custom module that we'd need to
    write ourselves that parses or reads a nodelist data file and gives
    the user the option to select a nodelist entry to send to/from.
    When the selections are made, the data is set in the calling form and
    the popup window is closed.

    Since the fields for the node numbers are text boxes, the user could
    also just type in a FTN-address in 3D/4D/5D format that the create
    message code parses and sets in the message header.

    If you want me to modify the code for the hooks and submit it to you,
    I'll be welcome to in order to try to push this into the core
    package. I
    know you want to keep things consistent regardless of connectivity
    type,
    and I think it's a step in that direction. I also realize that this is
    a very LOW LOW item on the list of things to change/add to WINSERVER
    which is why I'm willing to put it together and submit it to ya if that
    is what works the best for you.

    Thoughts?
    Chris


    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)