On Fri, Apr 06, 2007 at 02:15:07PM -0400, Peter Silva wrote:
> Hello,
> 
> I just started lurking a few days ago.  I have a BB 8700R for the office.
> It is configured to work with the exchange server there.  I can play with
> berry using my Debian Etch laptop.  compiling from CVS is fine, everything
> that should work does.  the only thing is I made btool and bcharge setuid
> root for now, because nothing else seems to work.

Hello and welcome!

You've probably done this already, but depending on your system, take
a look at the udev/ or hotplug/ directories.  There is a README in the
CVS tree that explains some of the udev files.

If you've already tried this, are there any messages in the logs
that might be helpful for debugging?  On my system, /etc/udev/udev.conf
controls whether logging is on or not.



> I can read & futz with C++ (last time I used it was 10 years ago, as a minor
> contributor to kppp and konsole in KDE 1.x days.) but not a real developer
> (ie. design and such.)  so given a lack of access to USB snooping on
> windows, what would be useful to look at (hobby, spare time sort of work)?

That depends on your interest.

You can help out with record format parsing, if you enjoy low level work.
So far only Address Book, Calendar, and part of Email records are supported
in src/record.h and src/record.cc.  Do a "btool -t" and pick one of the
databases that interests you.  Then do btool -d "Database name here" -v
and start reverse engineering the data.  Often they will be variable
length records with a typecode/size/data, repeating until the end of the
record, but this may depend on the record.  Even just documenting the
formats you reverse engineer and posting to the mailing list is helpful
for others who may wish to pick up where you left off.



If you enjoy GUI programming, you could make the backup program more
functional.  The GUI uses gtkmm and libglade and friends.

One item in the TODO file:

- allow temporary overriding of backup destination by letting user
        type in the PIN field... as soon as the user types something,
        change the label to "Backup filename:" or something, and
        let user type in full path name.  If no '/' chars exist in user's
        filename, then assume config default path, and open a
        Save... file chooser box in that directory.  If there are '/'
        chars in the filename, attempt to chdir() there and open
        Save... file chooser there.

The idea was to make the destination file optional.  Right now, all
backup files are stored in ~/.barry, and the user can't change that.



Alternately, you could create special edit dialogs for records we know
the format of.  For example, it might be nice to display a list of
records from the device's Address Book, and allow the user to edit it
in place.

Adding this will really expose you to the Barry library API, which is great,
since I'm looking for feedback on that.  I'm sure the API could be made
better, but sometimes that's hard to discover until someone uses it.



If you prefer to write a command line utility, there has been interest
in a command line backup tool, that could be run in an automated fashion.
You could rework some of the code in the GUI to create this, if you like.
Preferrably, any common code should be shared between programs.


And of course, there is always a need for documentation.  Currently the
library documentation is in doxygen format, in the code.  Adding to that,
or fixing what is there would be great.  Also, you could look at the
src/protostructs.h file, and document the underlying Blackberry protocol.
This is something I should do really, since I wrote it, but I won't
stop you if you're interested. :-)

As you learn the API, writing clear, commented, code examples for the
examples/ directory is also welcome.


And finally, if you are a Debian user, cleaning up the .deb build process
would be fantastic.  Troy Engel has done great work on the RPM side,
and Debian support is lagging at the moment.


Happy Hacking, and please ask if you have questions along the way.

- Chris

Attachment: pgpE7VhFtkLsR.pgp
Description: PGP signature

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to