On Tue, Sep 15, 2009 at 11:12:59AM -0400, Ellen Oler wrote:
> OK, I fixed it I think (the Blackberry and the computer are not in the same
> place right now.)
> I found the "sample" Device line in the config file and removed it, which
> indeed had the PIN 3009efe3 as noted in the debug output.

Hi Ellen,

Glad to hear you got it working.


> SUGGESTION:
> 
> The developers probably are working in an environment where they have plenty
> of screen real estate, and what happened to me was I was installing on a
> tiny netbook and the troublesome lines were in the second screen of the file
> which I never scrolled down to and never saw.
> 
> Probably a lot more users over time will be using little netbooks, they are
> quite popular, especially running Linux.
> 
> Maybe help us tiny newbies out and comment out the troublesome device line
> from the example config file?

At first thought, that sounds like a good idea, but I have 3 concerns:

        1) If it is commented out, it may be confusing in a different way,
                looking like a comment.  It is meant to be an example
                of what the config file should look like.

        2) If it is commented out, the device will default to -1, which
                will give a similar error, but the pin number will look
                like ffffffff or similar.  I'm not sure that is any more
                helpful, since the user wouldn't have anything to search
                for in the existing config files.

        3) I could change the plugin to just sync with the device it finds
                on the bus.  If there is only one device connected, it
                might make sense to automatically connect to it.  But!
                I don't want the user to accidentally sync against a different
                device and possibly lose data.  I think the plugin should
                be a safeguard in such a case, and look for the PIN that it
                already knows about.

Also, The config format is changing for the upcoming opensync 0.4x to an XML
format.

In the end, I don't think either of these formats are very user friendly.
So ultimately, a GUI to configure all this, automatically detect devices,
etc, should be written.  And that is indeed on my higher priority todo list.


> QUESTION:
> 
> Is barry named after the well-known, Washington-based Blackberry enthusiast
> Barry O?

No. :-)  The original idea was to call it SyncBerry, but we thought that was
too close to RIM's trademark.


> -j (Ellen Oler's husband and official IT guy, new to Barry and barry-devel.)

Welcome! :-)

- Chris


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to