[Thread Prev][Thread Next][Thread Index]
Re: GUI address tool
- To: pilotmgr@xxxxxxxxxxxxxxxxxxx
- Subject: Re: GUI address tool
- From: Gary.Foster@Corp (Gary D. Foster)
- Date: 08 Dec 1997 16:30:35 -0800
- In-reply-to: mindless@moshpit's message of "Mon, 8 Dec 1997 16:21:03 -0800"
- Mail-copies-to: never
- References: <199712090021.QAA05792@moshpit.Corp.Sun.COM>
- Sender: owner-pilotmgr
>>>>> "Alan" == Alan Harder <mindless@moshpit> writes:
Alan> Actually Gary, a program that reads/write the .pdb format
Alan> wouldn't be all that helpful in creating a pilotmgr conduit.
Alan> Pilotmgr receives the address book records in a perl hash,
Alan> and is completely unrelated to the .pdb format. I suppose
Alan> you COULD write a conduit which reads the records thru the
Alan> pilot conduit api and then converts it BACK to the .pdb
Alan> format for saving...
Hmm, I wasn't aware of that... however:
Alan> The advantange of .pdb format tool is you could use it as a
Alan> viewer of your current address book before a pilotmgr
Alan> conduit is developed.. If the pilotmgr conduit was
Alan> developed at the same time as the PIM tool, you could use
Alan> ANY format you wanted, and you just need to make the conduit
Alan> read and write that format...
How's this for an idea... a GUI that reads a _generic_ format that is
modular... if you wanted to read .pdb files, you'd plug in the pdb
format module, the same for VCARD format, or even PilotMgr format.
That way, the GUI would write to and read from a standard API and
there'd be hooks for connecting this to whatever input/output format
you wanted. Would that make it easier to interface with PilotMgr?
-- Gary F.
---------------------------------------------------------------------
********************************************
* This is a public mailing list! *
* Please do not publish Sun proprietary *
* information here! *
********************************************