Hector ---- Platinum Xpress/Win/WINServer v3.1
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
If someone could make the fidomsg.wcx a little more robust I would be happy..
package. IHector -
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
type,know you want to keep things consistent regardless of connectivity
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
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,037 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 11:58:31 |
| Calls: | 832 |
| Files: | 95,177 |
| D/L today: |
15 files (15,401K bytes) |
| Messages: | 464,628 |