: Assigning the return value of new by reference is deprecated in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/modules/system.module on line 306.
: Function call_user_method_array() is deprecated in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/theme.inc on line 216.
Project Status Update - Progect and PDesk
logo
home | books | Installing On Linux/Unix | Introduction | NewDB | NewDB | search | my account
: Function call_user_method_array() is deprecated in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/theme.inc on line 216.
: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/common.inc on line 836.
: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/common.inc on line 836.
: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/common.inc on line 836.
: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/common.inc on line 836.
: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/common.inc on line 833.
: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/common.inc on line 833.
Project Status Update
Submitted by rprice on Friday, July 21, 2006 - 17:42FAQ

> Hi,
>
> It been a while since a new release of Pdesk or Progect? Is there a
> plan to update either of these in the near future? Last thing I
> remember was a complete rewrite. Any news?


PROGECT:

I'm thinking of adding someone's patches for Progect and rebuilding a beta of it.

I also need to make sure it can handle opaque data from other desktop applications (explanation further on).

So, I will probably try and do that within two weeks.


PDESK:

PDesk is not likely to have much activity for a while, unless someone gives me patches, in which case I will certainly build another
version.

I have started on a rewrite of it called the "Outliner Framework" it's on SourceForge, but not ready for prime time. I have put it on
hold because I think we need to deal with the conduit first.


CONDUIT:

The current conduit is dangerous to your data, but only sometimes, perhaps only when you really, really care.

The current conduit isn't a perfect solution anyway, because the data stays in a binary format. Not everyone wants to use PDesk, some
people use Progect for things that are better handled by other applications on the desktop.

So

I'm writing a conversion library (and program) that will convert basically any Palm database to XML, plugins need to be written, so I'm
going to support Progect first before other programs, and to be honest, I would expect others to write the plugins for other programs
in general.

The program will go from the Progect Palm Database to the XML of the program we are supporting, so we would support things like
OmniOutliner directly.

Once I have the conversion library working, and a command line application available, I will start working on the conduit which will
utilize the library for it's functions.

Once all that is done, I will start working on merging the data between the desktop and the Palm.

This is a gigantic amount of work, and I expect it will take 6 months to complete the conduit.

Once that is in place however, people will be able to use the desktop application of their choice to edit their data. Their data will
no longer be locked in a binary format cage as well. I think the benefit for this will be huge.

The conduit needs to support opaque data from other applications, this way their settings will not be lost when we have it on the Palm. I am calling this data area the "attic".

So, that's what is currently happening.

Progect is definitely not dead, but the current conduit has to be replaced, and PDesk will be either replaced or repaired some time,
kind of far into the future. Probably a good year to year and a half out, easily two years. But that shouldn't matter so much, because
you will probably be able to use your favourite desktop editor(s) instead.

Of course if someone steps up to the plate, there are many things that can be done for Progect or the new PDesk and even for the
conduit, I need XSLT people currently to help with the conversions.

I hope to have a exe available with limited conversions within two weeks.

I will at the same time make the Python module available as an Alpha or Beta, and so people on other platforms will also be able to use
it.

Rick

[ login or register to post comments ]

: Function call_user_method_array() is deprecated in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/theme.inc on line 216.
: Function call_user_method_array() is deprecated in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/theme.inc on line 216.
SourceForge.net Logo

: Function call_user_method_array() is deprecated in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/theme.inc on line 216.
Downloads

Progect and PDesk are hosted at sourceforge. You will find install bundles at each program's project web site:

You might also read about Project and PDesk in the documentation under 'books' on the navigation bar.


: Function call_user_method_array() is deprecated in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/theme.inc on line 216.
Bugs

Project Bugs

PDesk bugs


: Function call_user_method_array() is deprecated in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/theme.inc on line 216.
Top nodes

: Function call_user_method_array() is deprecated in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/theme.inc on line 216.
Enhancements

If there is a feature you think would make your life easier, or just be cool, please add a new Feature Request

Project Feature Requests

PDesk

We use SourceForge to track these so everyone can see them.


: Function call_user_method_array() is deprecated in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/theme.inc on line 216.
User login

: Function call_user_method_array() is deprecated in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/theme.inc on line 216.
Who's new

home | books | Installing On Linux/Unix | Introduction | NewDB | NewDB | search | my account