[Coco] e-mail app???

Sat Jul 4 15:51:12 EDT 2015

I am not good at documentation.  here's info on the printers including the
flush command:

In config.xml you'll find a printer section like this:

<Printer category="printing">
   <Driver list="TEXT,FX80" type="list">FX80</Driver>
   <OutputDir type="directory"/>
   <OutputFile type="file"/>
   <FlushCommand type="string"/>
   <CharacterFile type="file">default.chars</CharacterFile>
   <Columns max="132" min="1" type="int">80</Columns>
   <Lines max="132" min="1" type="int">66</Lines>
   <DPI max="1200" min="50" type="int">300</DPI>
   <ImageFormat list="JPG,GIF,PNG,BMP" type="list">PNG</ImageFormat>
</Printer>

Driver can be TEXT or FX80.  If TEXT, Drivewire just writes whatever
the CoCo sends to a file.  If FX80, DW sends it to an emulated epson
fx80, which then outputs image files.

OutputDir and OutputFile specify where the output is created.  If
OutputFile is set, all output is written (appended) to the same
specified file.  Probably not what you want unless it sounds like
exactly what you want.  Most folks will not want to set it, and
instead will set OutputDir which tells DW to create new files for each
print job (or page, in FX80 mode) in the specified directory.  If both
are set, OutputFile wins.

FlushCommand is any command you'd like executed after DW writes a new
file or appends to the OutputFile.  If the string '$file' is in this
command, it will be replaced with the full path of the file DW just
created.

The remaining settings only apply to FX80 mode:

CharacterFile is the font definition for the FX80.  The default
setting specifies an included file that matches the default font the
FX80 used.  Its a very simple human readable format.

Columns and Lines define the dimensions of an FX80 text page.  You
could for instance change Columns to 132 to emulate one of those
really wide variants in the epson fx family, or change Lines to
simulate different paper length.  The defaults match what a regular
FX80 used on 8.5x11 paper.

DPI and ImageFormat control the image files that the FX80 emulator produces.

On Sat, Jul 4, 2015 at 3:45 PM, K. Pruitt <pruittk at roadrunner.com> wrote:

> Wow, the possibilities that spring to mind are endless.
>
> Very jazzed to find out about the arbitrary command or script being
> optionally ran. That was the only clumsy part of my process. I didn't know
> drivewire was willing to do it for me if I had just had the sense to ask it.
>
> Thanks Aaron.
>
> ----- Original Message ----- From: "Aaron Wolfe" <aawolfe at gmail.com>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Saturday, July 04, 2015 12:17 PM
>
> Subject: Re: [Coco] e-mail app???
>
>
>  You might be able to save some steps using URIs with the list command.
>> Anywhere you can use a file path im a dw command you can also use URIs
>> like
>> http://something/whatever.  So if there was a web to SMS gateway that let
>> you submit texts using an http get, you could do something like "dw server
>> list http://smsgateway.com/send?number=5551212&text=howdy".. Something
>> like
>> that.
>> There is also a parameter you can specify in a printer definition to
>> execute an arbitrary command or script when a job is flushed, and you can
>> define lots of printers and switch between them with dw commands... So
>> that
>> might provide a nice way to submit data to various scripts on the server
>> side.
>>
>> Just some thoughts.
>>
>> On Sat, Jul 4, 2015, 3:01 PM K. Pruitt <pruittk at roadrunner.com> wrote:
>>
>>  Yeah, it is totally on the PC at this point. Drivewire can deliver our
>>> outgoing message to the PC right now, as is. And grabbing an incoming
>>> message for the CoCo from the PC is already there in Drivewire in the
>>> form
>>> of the list command. I often use it to list a file from my PC to a file
>>> on
>>> my CoCo. So we have two-way communication already implemented via
>>> Drivewire.
>>>
>>> On the PC end we just pick up the file that the CoCo has sent it via
>>> drivewire and process it in to email or SMS. Using pre-existing software
>>> and
>>> a few batch files, I think this can be implemented without even writing a
>>> line of code.
>>>
>>> I'm still waiting for Aaron to speak up and tell us to just use the dw
>>> sms
>>> command. Hehe.
>>>
>>> ----- Original Message -----
>>> From: "Bill Pierce via Coco"
>>> Sent: Saturday, July 04, 2015 8:47 AM
>>> Subject: Re: [Coco] e-mail app???
>>>
>>>
>>> > David, NitrOS9 already has all that's needed if the work is being done
>>> > on
>>> > the PC Drivewire server. There are several types of DW4 "virtual ports"
>>> > already on the nitros9 ditribution disk and in the boot.
>>> > What would have to be done, is to implement (in dw4 itself) a command
>>> code
>>> > that lets DW4 know what it supposed to do. DW4 has a host of cmd codes
>>> > already that allow many things that are not being used by software, so
>>> > there may be something the you can use already.
>>> >
>>> > DW4 already supports listing a text (or binary, dw4 doesn't care) file
>>> > to
>>> > the PC (virtual print to file through "/p"), and some have even set up
>>> > Linux to intercept these files and forward them to the server's >
>>> printer.
>>> > This listing can actuall be renamed and directed to anywhere you need
>>> > it
>>> > to go with a few simplke dw4 commands (already implemented). It would
>>> > be
>>> > easier to just use this DW4 feature and then deal with the file that is
>>> > sent.
>>> >
>>> > I actually use this feature to write OS9 files from OS9 to the DW4 >
>>> server
>>> > in my MShell project.
>>> >
>>> > Most of the work for the OS9 end was already forseen (and done), it's
>>> > the
>>> > PC end that needs work.
>>> >
>>> >
>>> > Bill Pierce
>>> > "Charlie stole the handle, and the train it won't stop going, no way to
>>> > slow down!" - Ian Anderson - Jethro Tull
>>> >
>>> >
>>> >
>>> > My Music from the Tandy/Radio Shack Color Computer 2 & 3
>>> > https://sites.google.com/site/dabarnstudio/
>>> > Co-Contributor, Co-Editor for CocoPedia
>>> > http://www.cocopedia.com/wiki/index.php/Main_Page
>>> > Global Moderator for TRS-80/Tandy Color Computer Forums
>>> > http://www.tandycoco.com/forum/
>>> >
>>> > E-Mail: ooogalapasooo at aol.com
>>> >
>>> > -----Original Message-----
>>> > From: David Gettle
>>> > Sent: Sat, Jul 4, 2015 11:26 am
>>> > Subject: Re: [Coco] e-mail app???
>>> >
>>> >
>>> > So it sounds like all that is needed is just add adding a virtual >
>>> device
>>> > to
>>> > drivewire and a routine in drivewire to convert text sent to it to a
>>> > batch
>>> > file for the host machine, and execute it. and a Nitros9 device
>>> > descriptor,
>>> > sounds simple enough, just wish I had time enough to work on
>>> > it.....
>>> >
>>> > On Sat, Jul 4, 2015 at 12:05 AM, K. Pruitt wrote:
>>> >
>>> >> ----- Original Message ----- From: "K. Pruitt"
>>> >> Sent: Friday, July
>>> > 03, 2015 7:43 PM
>>> >> Subject: Re: [Coco] e-mail app???
>>> >>
>>> >>
>>> >>  I think the solution
>>> > would be to run everything SMS-related from the PC,
>>> >>> and just configure the
>>> > software to accept  the text from the Coco via
>>> >>> drivewire.
>>> >>>
>>> >>> Of course I
>>> > don't have the details for this software I speak of, but it
>>> >>> seems logical to
>>> > throw all the work-load on to the PC.
>>> >>>
>>> >>> --
>>> >>>
>>> >>
>>> >> For example, I wanted my
>>> > CoCo to be able to tell my PC to do things. I
>>> >> came up with this Rube-Goldberg
>>> > style method of having the CoCo send a txt
>>> >> file to /p and then I used a cron
>>> > utility on my PC to check the printer
>>> >> directory every minute and convert the
>>> > text file to a .BAT file and run it.
>>> >> It was clumsy and inconvenient but it
>>> > worked.
>>> >>
>>> >> So what I am saying it the CoCo only has to treat the text message
>>> > it
>>> >> wants to send as any other string of characters. The CoCo never needs
>>> >> to
>>> >>
>>> > know anything about SMS. All that can be handled on the PC with
>>> >> pre-existing
>>> > open source software, with all that is needed to be added is a
>>> >> software
>>> > interface to pick up that simple string of characters from the
>>> >> CoCo and pass
>>> > it along to the SMS software.
>>> >>
>>> >> --
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> https://pairlist5.pair.net/mailman/listinfo/coco
>>>
>>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> https://pairlist5.pair.net/mailman/listinfo/coco
>>
>>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>