RE: [Phpgroupware-developers] phpgroupware and coldsync

[Brian Johnson]

groovy

I think it will adapt fairly well, really just point the HASHES from the
results of the SQL statements to the new imported data

> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden Behalf Of Alex Borges
> Sent: Wednesday, July 17, 2002 11:56 AM
> To: address@hidden
> Subject: RE: [Phpgroupware-developers] phpgroupware and coldsync
>
>
> El mié, 17-07-2002 a las 10:21, Brian Johnson escribió:
> > I still need a table for each conduit to map phpgw records to
> palm records
> > for each user
> >
> > So, I'd still need access to a database (but it needn't be the
> phpgroupware
> > one) or to a flat file (I think the database table would be faster)
> >
> > Although this sounds like a plausible solution for the interaction with
> > phpgw (instead of direct SQL queries) I don't think I have time to
> > implement/figure it out right now
> >
> > I could provide explanation and assistance for anyone looking
> to modify the
> > conduits to this type of system - I am particularly interested
> in accessing
> > the ACL to provide multi-user record sharing on the Palms
> No worries....keep at it how youre doing it, ill pick it up in the
> future and make it so as to be mantainable this other way.
>
> Just keep that in mind as you code so its easy to port to this other way
> (just use a lot of functions).....
>
>
> Alex
>
>
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: address@hidden
> > > [mailto:address@hidden Behalf Of
> > > Brian Johnson
> > > Sent: Tuesday, July 16, 2002 4:18 PM
> > > To: address@hidden
> > > Subject: RE: [Phpgroupware-developers] phpgroupware and coldsync
> > >
> > >
> > > I guess my original reply went straight to you, not the group
> > >
> > > As our private dialog has progressed, this concept seems very
> > > plausible,
> > > especially if a 'wrapper' php file can be made to run from
> > > the command line
> > > and include the phpgw functions - is anyone able to do this?
> > > We'd start
> > > with the memo app first since it includes the least fields
> > > (from a sync
> > > standpoint, it is the easiest).  And we'd need access to the
> > > categories as
> > > well
> > >
> > > Basically, I need a way to access the phpgw functions from
> > > perl - I don't
> > > know how to do this but it must be possible.  If we can
> > > 'include' the native
> > > phpgw files instead of copying and modifying them, upgrades
> > > will be easier
> > >
> > > Could someone confirm that this concept will access the
> > > phpgw_acl and list
> > > all of the memos (for instance) that is readable by the user
> > >
> > > Can I trap a write error if the user is unauthorized to write
> > > to a category
> > > so that I can reroute it to another category (so that records
> > > aren't lost)?
> > >
> > >
> > > > -----Original Message-----
> > > > From: Alex Borges [mailto:address@hidden
> > > > Sent: Monday, July 15, 2002 10:33 AM
> > > > To: address@hidden
> > > > Cc: address@hidden; address@hidden
> > > > Subject: RE: [Phpgroupware-developers] phpgroupware and coldsync
> > > >
> > > >
> > > >
> > > > About data sync problems.....
> > > >
> > > >
> > > >
> > > > Kay, my phpgw deployment has been thoroughly tweaked so as to
> > > > sycnronize
> > > > certain aspects of the whole thing (such as addressbook+users+email
> > > > servers+virtualhosts+mailinglists+true global preferences).  This is
> > > > done in a command line (thats important for me), and so, traditional
> > > > phpgwapi programming is out of the question (as is in your
> > > > problem -palm
> > > > sync)
> > > >
> > > > I was reading the whole thread on this and, at seeing the kinds of
> > > > troubles you can get for directly manipulating tables, i decided to
> > > > share with u guys the way i did it for thease other things,
> > > so then u
> > > > guys can decide if this is relevant to the particular
> > > > technique you are
> > > > using for palm-sync.
> > > >
> > > > 1.- General rule.
> > > >         Since we are modifying stuff in the addressbook, one
> > > > can get nervous
> > > > about directly manipulating the tables (on by oneself
> > > modifying the db
> > > > schema, or a thourough change the next release will kill your
> > > > work). So
> > > > what i did was the next 'better' thing.... i copied
> > > > class.contacts_sql.inc.php to a directory (call it
> > > > stepone-sync-tool/inc) and modified it so it could be used on the
> > > > command line. Same goes for class.preferences.inc.php ....
> > > >
> > > >         Course, if the api changes or the table layout or
> > > > schema changes, ill
> > > > end up re-porting class.contacts.inc.php...etc...but one
> > > thing is just
> > > > getting the next version to work under the command line
> > > (php cgi) and
> > > > another to go through all sql statements  to reflect changes.
> > > >
> > > > 2.- um....same as 1 but with the preferences..... so, couldnt
> > > > calendar/notes/todo be done the same way?
> > > >
> > > > Or wouldnt it help?
> > > >
> > > >
> > > > Alex
> > > >
> > > >
> > >
> > >
> > > _______________________________________________
> > > Phpgroupware-developers mailing list
> > > address@hidden
> > > http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
> >
> >
> > _______________________________________________
> > Phpgroupware-developers mailing list
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
> >
>
>
>
> _______________________________________________
> Phpgroupware-developers mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/phpgroupware-developers