Re: Re: PDesk plugin

"Jeff Mikels" <[email protected]> Sat, 26 Aug 2006 00:18:08 -0400
Newsgroups gmane.comp.handhelds.palm.progect
Message-ID <[email protected]>
Here's some of my stuff...

OPML and LifeBalance plugins... the OPML works pretty well now. I can't
recall if I did an output too...



On 8/25/06, Rick Price <[email protected]> wrote:
>
> Yes, please do, it will take me a little while to look at them, but they
> sound useful.
>
> Rick
>
>
> On Fri, 25 Aug 2006, "Jeff Mikels" wrote:
>
> > I have a couple plugins I wrote myself to import from structured text
> files.
> > OPML and CSV if I recall. If you don't mind potentially broken code, I
> could
> > send them to you.
> >
> > On 8/25/06, mec1353 <mec1353-/[email protected]> wrote:
> >>
> >> Hi Rick,
> >>
> >> 2 topics: loading plugins and importing text.
> >>
> >> 1) Loading plugins:
> >> I have added more plugins to see if they would load or not. They seem
> >> to load well, I can see them in the "export" menu but none in
> >> the "import" menu. I am copying the text of the PDesk.log file (I
> >> cannot see how to attach a document to this mail), it says:
> >> "Error importing plugin CSVInOut
> >> Got Module use of python22.dll conflicts with this version of Python."
> >>
> >> 2) importing text:
> >> Since there seems to be no posibility to import a format other
> >> than 'text', is there a documentation on the format for the text file
> >> to be read and re-entered back into PDesk with the data in the right
> >> fields? I noticed that a project exported as 'text' is not retreived
> >> properly by PDesk, all the data for a task (name, priority, progress,
> >> note,...) is packed into the task name.
> >>
> >> thanks for your help
> >>
> >> ------------------ text of PDesk.log --------------------------
> >> New Session started on Fri Aug 25 20:59:09 2006
> >> platform  : win32
> >> byteorder : little
> >> ----------------------------------------------------------------------
> >> --------
> >> PluginManager started
> >> Start in C:\Program Files\PDesk
> >> Now in C:\Program Files\PDesk\plugins
> >> got plugs :
> >> ['CSVInOut.py', 'DocBookXMLInOut.py', 'HTMLInOut.py', 'MSProjectInOut.
> >> py', 'Report_HTMLInOut.py', 'TextInOut.py']
> >> Error importing plugin CSVInOut
> >> Got Module use of python22.dll conflicts with this version of Python.
> >> imported <module 'DocBookXMLInOut' from 'C:\Program
> >> Files\PDesk\plugins\DocBookXMLInOut.pyo'> successfully
> >> imported <module 'HTMLInOut' from 'C:\Program
> >> Files\PDesk\plugins\HTMLInOut.pyo'> successfully
> >> imported <module 'MSProjectInOut' from 'C:\Program
> >> Files\PDesk\plugins\MSProjectInOut.pyo'> successfully
> >> imported <module 'Report_HTMLInOut' from 'C:\Program
> >> Files\PDesk\plugins\Report_HTMLInOut.pyo'> successfully
> >> imported <module 'TextInOut' from 'C:\Program
> >> Files\PDesk\plugins\TextInOut.pyo'> successfully
> >> loaded plugins : [<class 'DocBookXMLInOut.DocBookXMLInOut'>,
> >> <class 'HTMLInOut.HTMLInOut'>,
> >> <class 'MSProjectInOut.MSProjectInOut'>,
> >> <class 'Report_HTMLInOut.Report_HTMLInOut'>,
> >> <class 'TextInOut.TextInOut'>]
> >> Trying <class 'DocBookXMLInOut.DocBookXMLInOut'>
> >> Trying <class 'HTMLInOut.HTMLInOut'>
> >> Trying <class 'MSProjectInOut.MSProjectInOut'>
> >> Trying <class 'Report_HTMLInOut.Report_HTMLInOut'>
> >> Trying <class 'TextInOut.TextInOut'>
> >> returning output plugins :
> >> [<class 'DocBookXMLInOut.DocBookXMLInOut'>,
> >> <class 'HTMLInOut.HTMLInOut'>,
> >> <class 'MSProjectInOut.MSProjectInOut'>,
> >> <class 'Report_HTMLInOut.Report_HTMLInOut'>,
> >> <class 'TextInOut.TextInOut'>]
> >> returning input plugins : [<class 'TextInOut.TextInOut'>]
> >> Listening on 127.0.0.1:9999
> >> Waiting for a request...
> >> Going to users Chris directory : C:\pilot\Chris
> >>
> >>
> >>
> >>
> >>
> >>
> >> --- In [email protected], Rick Price <rprice@...> wrote:
> >>>
> >>> The ultimate solution to your problem is really going to be the XML
> >>> conduit.
> >>>
> >>> However, the XML conduit will not involve PDesk, it will go
> >> directly from
> >>> XML to your Palm device when you hotsync. The point of the XML
> >> conduit
> >>> being to replace the existing conduit and PDesk making your
> >> favourite
> >>> editor compatible with Progect.
> >>>
> >>> Of course, the hotsync part is not written yet.
> >>>
> >>> The part that is written will go from XML to a Progect PDB file
> >> which
> >>> PDesk can read (A PDK file is really a PDB file with a different
> >> name).
> >>> You can also load the PDB file directly into your Palm device.
> >>>
> >>> Currently the conversion is one way, it does not merge the data.
> >>>
> >>> Finally, there is a small bug in the code (Python PalmDB) that
> >> ruins the
> >>> PDB file, that should not be that hard to fix, it was working
> >> shortly
> >>> before I broke it.
> >>>
> >>>
> >>> So, the biggest issue you should have, is getting Teamplay XML
> >> supported
> >>> by the Python PalmDB project. (We will assume that Teamplay can
> >> read/write
> >>> XML).
> >>>
> >>>
> >>> To support the Teamplay XML in Python PalmDB, a XSLT script has to
> >> be
> >>> written to go from the canonical Progect XML to the Teamplay XML,
> >> and then
> >>> another XSLT script has to be written to go from Teamplay XML to
> >> Progect
> >>> XML.
> >>>
> >>> That may be difficult, but should not be insurmountable.
> >>>
> >>> If you were able to write that XSLT, you would be in good shape,
> >> otherwise
> >>> you will have to wait until I have time to write it.
> >>>
> >>>
> >>>
> >>> As to why the PDesk plugins do not work, they are probably old and
> >> out of
> >>> date. If they do not show up in the list however, there may be a
> >> problem
> >>> loading them. If that is the case, the problem should be shown in a
> >> log
> >>> file.
> >>>
> >>> Rick
> >>>
> >>>
> >>> On Tue, 22 Aug 2006, "mec1353" wrote:
> >>>
> >>>>
> >>>> Hi Rick,
> >>>>
> >>>> first of all, thanks for answering my call.
> >>>>
> >>>> The main project management tool we have is Teamplay from
> >> Primavera. It
> >>>> is big, but also has several output formats. I am almost certain
> >> it
> >>>> supports XML and will double check tomorrow.
> >>>>
> >>>> If it has XML support and you plan to have such a conduit, this
> >> may
> >>>> really be the solution for me, thanks.
> >>>>
> >>>> I would also like to understand why my PDesk does not recognize
> >> CSV
> >>>> plugins as described in the csv doc becuase if the XML plugin
> >> does not
> >>>> showup either in the menu, this won't help.
> >>>>
> >>>> If you have time for a little bit of history, I will tell you
> >> that I
> >>>> have experimented several things around the import/export
> >> commands and
> >>>> the ".pdk" files of PDesk.
> >>>>
> >>>> Before calling for help,  I simply tried the "export as text" and
> >> back
> >>>> with the "import as text" to discover this was not reversible. I
> >> tried
> >>>> different text formats with no success. So, I wonder what sort
> >> of 'text'
> >>>> format does PDesk accept to load into a good looking project with
> >> tasks,
> >>>> priorities, notes, dates, progress,..... any information?
> >>>>
> >>>> Then I discovered that the HTML export does not epxort all the
> >>>> information (no date, no note) and there is no slector like there
> >> is for
> >>>> the text export. So, HTML was not an option for me.
> >>>>
> >>>> When I looked at the 'MS project MPX' export, I got a good view
> >> of the
> >>>> data. However, I realized that the only import capability
> >> is 'text' and
> >>>> since I do not know what text format works, I had to give up.
> >>>>
> >>>> My last attempt was to try to install the CSV plugins, in the
> >> hope that
> >>>> I could export 'csv' format to excel and work there or better, use
> >>>> Teamplay to export 'csv' and read it directly into PDesk.
> >>>>
> >>>> Unfortunately, I was not able to get PDesk recognize the plugins
> >> and I
> >>>> still only have 'text' export.
> >>>>
> >>>> That's when I decided to post a mail...
> >>>>
> >>>> thanks in advance for any information.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --- In [email protected], Rick Price <rprice@> wrote:
> >>>>>
> >>>>> What programs are you trying to interface with Progect?
> >>>>>
> >>>>> I am working on a XML<->Progect conduit.
> >>>>>
> >>>>> If your programs could work with XML, then there is a good chance
> >>>> that,
> >>>>> that would help you.
> >>>>>
> >>>>> Rick
> >>>>>
> >>>>>
> >>>>> On Sun, 20 Aug 2006, "mec1353" wrote:
> >>>>>
> >>>>>> Hi,
> >>>>>> I am new to the group, I have decided to join because I
> >> discovered
> >>>>>> Progect and PDesk, installed on my Z22 and was impressed with
> >> the
> >>>>>> pair.
> >>>>>> I find it easier to update the information on PDesk and hotsync
> >> to
> >>>>>> the palm. The problem I have is that the information I need to
> >>>> update
> >>>>>> comes from project management tools used in my company and I
> >> have
> >>>>>> been looking for ways to create status update files that I could
> >>>>>> directly import in PDesk, then hotsync.
> >>>>>> I tried the 'text' format but this did not work (actually, I
> >>>>>> discovered that PDesk cannot 'txt' import projects exported in
> >> text
> >>>>>> format!)
> >>>>>> I joined the group, then, to look for other plugins and found
> >> the
> >>>> CSV
> >>>>>> plugin which I think would be compatible with the applications
> >> used
> >>>>>> in the company.
> >>>>>> I downloaded the zip file and followed the intructions, copied
> >> both
> >>>>>> files into the plugin folder... no CSV option appeared in PDesk.
> >>>>>> I thought that this would work only with the latest released of
> >>>>>> PDesk. So, I got the 0.8.5 version, uninstalled my 0.8.4 and re-
> >>>>>> installed the new one. Recopied the two CSV files, and re-
> >> started my
> >>>>>> computer.
> >>>>>> Opening PDesk and creating a small project, I still do not see
> >> any
> >>>>>> CSV option in export or import.
> >>>>>>
> >>>>>> I am now out of ideas to try to make Progect-PDesk as better
> >> tool
> >>>> for
> >>>>>> my work. Can anyone tell me what I missed, what I did wrong?
> >>>>>>
> >>>>>> thanks in advance,
> >>>>>> Luke
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> Remember to visit Polls, Files and Bookmarks sections at
> >> http://groups.yahoo.com/group/progect. You are welcome to vote, upload
> >> your files and submit bookmarks.
> >> Yahoo! Groups Links
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Jeff Mikels
> > leading people one step closer to Jesus
> > http://jeff.mikels.cc
> > http://thesouthsidechurch.org
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
>
>
>
> Remember to visit Polls, Files and Bookmarks sections at
> http://groups.yahoo.com/group/progect. You are welcome to vote, upload
> your files and submit bookmarks.
> Yahoo! Groups Links
>
>
>
>
>
>
>


-- 
Jeff Mikels
leading people one step closer to Jesus
http://jeff.mikels.cc
http://thesouthsidechurch.org


[Non-text portions of this message have been removed]




Remember to visit Polls, Files and Bookmarks sections at http://groups.yahoo.com/group/progect. You are welcome to vote, upload your files and submit bookmarks. 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/progect/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/