Menu
▾
▴
bitpim-devel — For bitpim developers
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
(53) |
Apr
(48) |
May
(14) |
Jun
(3) |
Jul
(21) |
Aug
(11) |
Sep
(77) |
Oct
(67) |
Nov
(28) |
Dec
(163) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(112) |
Feb
(143) |
Mar
(114) |
Apr
(138) |
May
(173) |
Jun
(119) |
Jul
(119) |
Aug
(117) |
Sep
(187) |
Oct
(170) |
Nov
(254) |
Dec
(193) |
| 2005 |
Jan
(336) |
Feb
(284) |
Mar
(189) |
Apr
(100) |
May
(89) |
Jun
(52) |
Jul
(85) |
Aug
(138) |
Sep
(181) |
Oct
(137) |
Nov
(104) |
Dec
(98) |
| 2006 |
Jan
(76) |
Feb
(106) |
Mar
(224) |
Apr
(270) |
May
(103) |
Jun
(144) |
Jul
(77) |
Aug
(38) |
Sep
(37) |
Oct
(20) |
Nov
(14) |
Dec
(73) |
| 2007 |
Jan
(130) |
Feb
(68) |
Mar
(78) |
Apr
(60) |
May
(45) |
Jun
(63) |
Jul
(84) |
Aug
(45) |
Sep
(40) |
Oct
(12) |
Nov
(71) |
Dec
(56) |
| 2008 |
Jan
(44) |
Feb
(20) |
Mar
(25) |
Apr
(17) |
May
(33) |
Jun
(60) |
Jul
(97) |
Aug
(38) |
Sep
(10) |
Oct
(20) |
Nov
(13) |
Dec
(19) |
| 2009 |
Jan
(7) |
Feb
(5) |
Mar
(23) |
Apr
(10) |
May
(6) |
Jun
(5) |
Jul
(17) |
Aug
(7) |
Sep
(14) |
Oct
(27) |
Nov
(13) |
Dec
(12) |
| 2010 |
Jan
(37) |
Feb
(9) |
Mar
(13) |
Apr
(12) |
May
(8) |
Jun
(3) |
Jul
(1) |
Aug
(9) |
Sep
(3) |
Oct
(1) |
Nov
(1) |
Dec
(4) |
| 2011 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(4) |
May
|
Jun
(2) |
Jul
(8) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
(3) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
|
From: Roger B. <ro...@ro...> - 2004-03-07 20:42:50
|
> Wondering where I got the other impression, I see that it was the help > page you get from the Help menu in BitPim 0.62, which contains the > incorrect statement "Mac OS X has drivers builtin". > > That's obviously what had me going down the wrong path originally. Yup. If someone wants to update the 0.62 help I would be quite happy. I do all my work on 0.7 :-) Roger |
|
From: Michael C. <ma...@ca...> - 2004-03-07 20:29:30
|
On 3/7/04, Roger Binns posited: >The help does clearly state you need drivers: > >http://bitpim.sourceforge.net/testhelp/lg4400-cables.htm Good. Wondering where I got the other impression, I see that it was the help page you get from the Help menu in BitPim 0.62, which contains the incorrect statement "Mac OS X has drivers builtin". That's obviously what had me going down the wrong path originally. --=20 Mike Casteel ma...@ca... Seattle, WA |
|
From: Roger B. <ro...@ro...> - 2004-03-07 19:50:21
|
Michael Casteel wrote: > I think there's one thing that can be improved in the help for the 4400. > Reading all I could find in the help and online, I was left with the > distinct impression that Mac OS X 10.3 included suitable drivers for the > Radio Shack USB/Serial cable. I wasn't able to get BitPim working, until > a poster pointed me to the drivers to download for OS X. > > It seems that OS X 10.3 does *not* include suitable drivers, although > I'm quite sure that the help stated it did. The help does clearly state you need drivers: http://bitpim.sourceforge.net/testhelp/lg4400-cables.htm Roger |
|
From: Roger B. <ro...@ro...> - 2004-03-07 19:36:28
|
If anyone is a lawyer on this list, it would be interesting to know about this (quoted from a /. poster on inks and inkjet printers): The Magnuson-Moss Warranty Act (15 U.S.C. 2302(C)) states: "No warrantor of a consumer product may condition his written or implied warranty of such product on the consumers using, in connection with such product, any article or service (other than article or service provided without charge under the terms of the warranty) which is identified by brand, trade or corporate name ... ." Simply put, the warrantor can not void a warranty because of the use of an aftermarket part. Furthermore the warrantor must show that an aftermarket part caused the damage in question that they wish to void the warranty over. While this act was passed to protect automotive aftermarket part manufacturers I'm guessing it could be applied to this situation. Maybe someone with Westlaw access could check. I wonder if this also applies to using BitPim with a phone? Roger |
|
From: Michael C. <ma...@ca...> - 2004-03-07 19:35:33
|
I think there's one thing that can be improved in the help for the 4400. Reading all I could find in the help and online, I was left with the distinct impression that Mac OS X 10.3 included suitable drivers for the Radio Shack USB/Serial cable. I wasn't able to get BitPim working, until a poster pointed me to the drivers to download for OS X. It seems that OS X 10.3 does *not* include suitable drivers, although I'm quite sure that the help stated it did. --=20 Mike Casteel ma...@ca... Seattle, WA |
|
From: Roger B. <ro...@ro...> - 2004-03-07 18:59:59
|
> now; also, I had the impression that for the vx6000 (and I assume for > the later vx4500 as well) that straight USB cables are might now be > preferable. Yes, if you can use a straight USB cable then do so. The ONLY exception is the LG VX4400 where you should not use that kind of cable. I have also seen many reports that the VX6000 cables do work. I would suggest just ordering one from a place that claims they work. Roger |
|
From: Roger B. <ro...@ro...> - 2004-03-07 18:58:03
|
greg cunningham wrote: > I know your time is limited. I was wondering... If I > can get a phone distributor to donate a vx4500 (at > least for a short period) for the bitpim cause would > you have the time to work with this phone. Yes, if one is loaned to me then I will spend some time on it. Generally I need the phone for quite a long period as it takes a while to work through all the issues (3 months). Roger |
|
From: Tom P. <mlp...@ea...> - 2004-03-07 15:35:51
|
Hi, I am greatly looking forward to pitching in with bitpim and with improving its support for my recently purchased vx4500, but I still haven't picked up a cable. I've tried to ask on the bitpim-user list for recommendations of vx4500-compatible data cables that work for MacOS X users, but have received no response. (I contacted RPI Wireless, too.) I know there were a couple of early reports the vx6000 serial-USB cables worked, but I couldn't tell if those reports were made by MacOS X users; also, there are a couple of cables marketted as vx4500 cables now; also, I had the impression that for the vx6000 (and I assume for the later vx4500 as well) that straight USB cables are might now be preferable. TomP On Mar 7, 2004, at 2:37 AM, greg cunningham wrote: > I in now way meant to imply blame for this problem.... > I know that you have worked hard to make this program > as good as it is now.... (it works fine for me) I was > just trying to relay problems that other users have > had with the 4500 and bitpim so the developers would > be aware of the situation. I am hoping that I can get > several lgvx4500 group members to volenteer to work > with you in developing the software. |
|
From: greg c. <gre...@ya...> - 2004-03-07 15:16:41
|
I know your time is limited. I was wondering... If I can get a phone distributor to donate a vx4500 (at least for a short period) for the bitpim cause would you have the time to work with this phone. greg --- Roger Binns <ro...@ro...> wrote: > greg cunningham wrote: > > I in now way meant to imply blame for this > problem.... > > I wasn't taking it as blame. I am just trying to > point > out that the code is incomplete, and I have no idea > how incomplete. Telling us that there are issues > because > it is incomplete doesn't really get us anywhere, > since > we can't even try to help to tell you where it is > incomplete. > > > I am hoping that I can get > > several lgvx4500 group members to volenteer to > work > > with you in developing the software. > > Now they should be able to figure out where the > issue is. > Generally the course of action is to use a different > program or a GIN program to update something, and > then > compare before and after snapshots of the > filesystem. > Once there are several examples of what changes, it > becomes > easier to figure out how it changes, and then that > makes > actual code easy to write. The coding is not the > hard > part of BitPim - it is figuring out what should > happen > that is, and if you figure that out someone else can > code > it. > > Roger > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux > Tutorials > Free Linux tutorial presented by Daniel Robbins, > President and CEO of > GenToo technologies. Learn everything from > fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Bitpim-devel mailing list > Bit...@li... > https://lists.sourceforge.net/lists/listinfo/bitpim-devel __________________________________ Do you Yahoo!? Yahoo! Search - Find what youre looking for faster http://search.yahoo.com |
|
From: Roger B. <ro...@ro...> - 2004-03-07 08:20:19
|
Stephen, Can you email me pics of the RPI cables so that I can add them to the help? Everyone else, I would like to improve the help for the various phones, especially the cable options available. Start at http://bitpim.sourceforge.net/testhelp/phones.htm The page for the VX4400 cables is the template. Pages should show pictures of each cable, and then discussion about drivers, and I would like to tidy it all up. I would appreciate people letting me know of other cables that have been missed, particular ones that are sold publically such as at Radio Shack or by Verizon. For ones sold by random vendors on eBay, they need to follow the bottom of http://bitpim.sourceforge.net/testhelp/contributing.htm (We want to verify the cables are ok, and adequate/appropriate drivers are provided especially for Linux and Mac, as well as them actually working with the relevant phones). I now have 5 (yes five) USB hubs and 6 USB phone cables on my desk :-) Roger |
|
From: Roger B. <ro...@ro...> - 2004-03-07 07:59:44
|
greg cunningham wrote: > I in now way meant to imply blame for this problem.... I wasn't taking it as blame. I am just trying to point out that the code is incomplete, and I have no idea how incomplete. Telling us that there are issues because it is incomplete doesn't really get us anywhere, since we can't even try to help to tell you where it is incomplete. > I am hoping that I can get > several lgvx4500 group members to volenteer to work > with you in developing the software. Now they should be able to figure out where the issue is. Generally the course of action is to use a different program or a GIN program to update something, and then compare before and after snapshots of the filesystem. Once there are several examples of what changes, it becomes easier to figure out how it changes, and then that makes actual code easy to write. The coding is not the hard part of BitPim - it is figuring out what should happen that is, and if you figure that out someone else can code it. Roger |
|
From: greg c. <gre...@ya...> - 2004-03-07 07:45:25
|
I in now way meant to imply blame for this problem.... I know that you have worked hard to make this program as good as it is now.... (it works fine for me) I was just trying to relay problems that other users have had with the 4500 and bitpim so the developers would be aware of the situation. I am hoping that I can get several lgvx4500 group members to volenteer to work with you in developing the software. As far as talking to verizon or lg about bitpim... Im not that stupid... I suspect that they would just mark my file as voided warentee and tell me Im sol. thank you again for your work on this program. thanks greg --- Roger Binns <ro...@ro...> wrote: > greg cunningham wrote: > > Here is a problems that lgvx4500 users are > > experiencing with bitpim... > > The VX4500 code is incomplete. I have never even > seen one. > A reminder from the home page: > > This program is distributed in the hope that it > will be useful, but > WITHOUT ANY WARRANTY; without even the implied > warranty of > MERCHANTABILITY or FITNESS FOR A PARTICULAR > PURPOSE. See the GNU General > Public License for more details. > > There are no warranties as stated above (ie this > software may damage your > phone). This software is in no way associated with > Audiovox, LG Electronics, > Qualcomm, Sanyo, Sprint or Verizon Wireless. It has > not been certified or > endorsed by them, nor was it written using > information directly supplied > by them. > > The phones like to store variants of the same > information in multiple > locations. It is quite likely this could be the > cause with BitPim > only updating one of the locations. There is > however nothing I can do > about it. I have never seen one of these phones, > nor have access to one > so I can't try and troubleshoot what it going on. > > Roger > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux > Tutorials > Free Linux tutorial presented by Daniel Robbins, > President and CEO of > GenToo technologies. Learn everything from > fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Bitpim-devel mailing list > Bit...@li... > https://lists.sourceforge.net/lists/listinfo/bitpim-devel __________________________________ Do you Yahoo!? Yahoo! Search - Find what youre looking for faster http://search.yahoo.com |
|
From: Roger B. <ro...@ro...> - 2004-03-07 07:34:25
|
I neglected to point out that you can't report this as a bug to LG unless you can reproduce the problem on phones that have never been touched by BitPim. They do not run a general purpose operating system, more like a bunch of hacks stuck together, with seemingly random formats for files and data and methods for operating on them. There is no documentation either for the kind of thing BitPim does. Roger |
|
From: Roger B. <ro...@ro...> - 2004-03-07 07:32:28
|
Roger Binns wrote: > This weekend I will be changing the licensing of BitPim to the GPL > (with an exception allowing linking to OpenSSL). ... > I will also be obsoleting the code that deals with the LG TM520/VX10. Ok, that is all now done. If I have made any mistakes, please speak up ASAP. Roger |
|
From: Roger B. <ro...@ro...> - 2004-03-07 07:31:06
|
greg cunningham wrote: > Here is a problems that lgvx4500 users are > experiencing with bitpim... The VX4500 code is incomplete. I have never even seen one. A reminder from the home page: This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. There are no warranties as stated above (ie this software may damage your phone). This software is in no way associated with Audiovox, LG Electronics, Qualcomm, Sanyo, Sprint or Verizon Wireless. It has not been certified or endorsed by them, nor was it written using information directly supplied by them. The phones like to store variants of the same information in multiple locations. It is quite likely this could be the cause with BitPim only updating one of the locations. There is however nothing I can do about it. I have never seen one of these phones, nor have access to one so I can't try and troubleshoot what it going on. Roger |
|
From: greg c. <gre...@ya...> - 2004-03-07 05:47:41
|
Here is a problems that lgvx4500 users are experiencing with bitpim... thanks greg Yup got it too. Guess we need to report it to LG somehow via website or phone. Thanks, Peter --- Brusters <bru...@ad...> wrote: > I too have the same problem when cycling thru the > wallpapers, except that > each graphic does not show up on the phone display. > If I select the graphic > as the wallpaper to use, then it is displayed > properly when I exit the menu. > Does anyone else have the problem of not seeing the > graphic when scrolling > thru the list (hitting OK to view)? > > > Thanks, > > Bruce > > -----Original Message----- > From: Paul Barreto [mailto:pba...@al...] > Sent: Saturday, March 06, 2004 11:15 AM > To: LGV...@ya... > Subject: RE: [LGVX4500] Re: Wallpapers shutting > phone down after I cycle > thru them a few times. > > I have the same problem with only 1 wallpaper in my > Medias; it seems to > be a bug with the VX4500. I hope someone finds a > solution. > > -----Original Message----- > From: Peter [mailto:pcu...@ya...] > Sent: Saturday, March 06, 2004 1:30 PM > To: LGV...@ya... > Subject: [LGVX4500] Re: Wallpapers shutting phone > down after I cycle > thru them a few times. > > Author of above message... > > I deleted all my 8 wallpapers and then uploaded just > one. > I then kept displaying (clicking center button and > then clear) the > same one about 5 times. Eventually the phone did > show a white screen > and shut down. Tried another picture same thing. > > Did not have this problem before when I used a > previous version of > BITPIM with VX4400 specified and the FileSystem but > I serously doubt > it is the program. > > I also never cycled through them more than once > until last night as a > trial after I uploaded a few more pics. > > I even did a phone activation *228 update but this > did not help. > > At one time I thought the pictures must be in alpha > order but this is > not the case either. Tried that. > > The second time I uploaded them I used the > FileSystem as opposed to > the Wallpaper tab. Same result of shutting down > after a few showings > of same or cycling through pictures. > > I now have one pic in the phone and after a few > viewings I get white > screen and then a shut down if I try again. > > If someone can try this on their phone I would > appreciate it. > > Thanks, Peter > pcu...@ya... > > > --- In LGV...@ya..., "Peter" > <pcumming@y...> wrote: > > Wallpapers shutting phone down after I cycle thru > them a few > > > > I uploaded quite a few ringers and all worked > fine. (LG VX-4500). > > Even a few mp3's (renamed as MID). Today I > uploaded a few more for > a > > total of about 15. > > > > WALLPAPERS > > I added a few more bmp wallpapers with dimensions > no greater than > > 120x131. > > When I cycle thru them (press center button and > then right button) > I > > see them all. > > > > PROBLEM > > However if I continue to press the right button to > cycle a few more > > times (about 3), eventually I get a blank picture > (of the 4 I > > uploaded), then the phone shuts off. > > > > Ideas? > > > > > > Thanks, Peter > > pcumming@y... __________________________________ Do you Yahoo!? Yahoo! Search - Find what youre looking for faster http://search.yahoo.com |
|
From: Roger B. <ro...@ro...> - 2004-03-06 01:36:22
|
This weekend I will be changing the licensing of BitPim to the GPL (with an exception allowing linking to OpenSSL). It will effectively make a new revision of every source file that starts as GPL from that point on (ie the old code is still available under the old license if anyone cares). If I never have to hear about licensing again, I will be happy. If I have overlooked anything/anyone, please point it out ASAP. I will also be obsoleting the code that deals with the LG TM520/VX10. That code is incomplete, and has several contributors who are no longer active. If someone wants to own the tm520/vx10, speak up. You will need to start the files from scratch, but can use the existing code as documentation. Roger |
|
From: Roger B. <ro...@ro...> - 2004-03-05 08:24:24
|
This is just a reminder to people who do send email directly to me that it isn't a particularly good idea. For support stuff I refer you to http://bitpim.sourceforge.net/testhelp/support.htm Note the first item in the "Do not do" section. Most of the rest of the email should be posted to bitpim-devel or bitpim-user, even if it doesn't seem relevant to all. Often the answers are relevant or interesting to other people. The other reason is that a substantial amount of my responses to people get bounced back. If your address was @users.sf.net, it bounces back almost all email with stupid error messages. I have given up raising support issues at SF about this. For many other people, they have stupid ISPs that bounce stuff for arbitrary reasons (usually in the name of "Anti Spam"). At that point you have wasted my time in answering, and noone gets to see the answer. I will not do any form of clicking or vision tests to confirm I am human, nor deal with whatever ranges of ip addresses your ISP has decided to block today. (You mailed me remember). So in summary, just post to one of the lists, not directly to me. From now on I will ignore ALL email sent directly to me unless there is good reason for it to be private. Roger |
|
From: Roger B. <ro...@ro...> - 2004-03-05 01:45:08
|
> Actually I do see one problem with OpenSSL. The BitFling stuff I am > working on uses m2crypto which in turn produces a wrapper around > OpenSSL. http://www.gnu.org/licenses/license-list.html > shows OpenSSL as not GPL compatible, but not the circumstances that > apply. (In this case OpenSSL is being used through two layers > of indirection of runtime library loading.) It looks like one can place an exception in the COPYING file to solve this problem. For example, see 3rd paragraph of http://www.opensource.apple.com/darwinsource/10.1.2/fetchmail-4.1/fetchmail/COPYING Roger |
|
From: Roger B. <ro...@ro...> - 2004-03-05 01:20:51
|
> > decide to use the full GPL after making sure that all the other > > components are GPL compatible. > > I think I am sold on this now. I don't forsee any problems with the > components, but would appreciate other people checking. Start from > this link: > > http://bitpim.sourceforge.net/testhelp/3rdparty.htm Actually I do see one problem with OpenSSL. The BitFling stuff I am working on uses m2crypto which in turn produces a wrapper around OpenSSL. http://www.gnu.org/licenses/license-list.html shows OpenSSL as not GPL compatible, but not the circumstances that apply. (In this case OpenSSL is being used through two layers of indirection of runtime library loading.) Roger |
|
From: Roger B. <ro...@ro...> - 2004-03-05 00:31:25
|
> are. Not sure about pySerial since its license file seems to date back > to a time when python licenses were not GPL compatible. As far as I can tell, the pySerial license is identical to the Python Software Foundation license: http://www.opensource.org/licenses/PythonSoftFoundation.php > I don't think > the licenses of the installers and freezers are relevant to GPL > compatibility. They are :-) On both Linux and Windows, a stub binary supplied by the freezer (py2exe/cx_Freeze) is what is actually run. It arranges for the Python shared library to be loaded and locates the BitPim code (typically in a seperate zip file, or in a zip file appended to the end of the stub binary). I believe they are both ok anyway. I think the Mac is just running the Python binary directly. > I'm not sure that the LGPL really fits and the talk of Library could be > confusing in the context of BitPim. I agree, although based on how the freezers work you could argue it is a library :-) > I guess my preference is to either stick with the V2.0 perl license or I haven't had any response from the maintainer of that license or from the Perl6 licensing mailing list. Not a good thing. I don't quite see why all the various places kept saying to use that if it is dead (or not particularly lively anyway). > decide to use the full GPL after making sure that all the other > components are GPL compatible. I think I am sold on this now. I don't forsee any problems with the components, but would appreciate other people checking. Start from this link: http://bitpim.sourceforge.net/testhelp/3rdparty.htm > The latter still leaves options for > proprietary software developers that would like to use BitPim in some > way. They can try to negotiate a separate license with us, or they can > use the "facts" (i.e. sync protocols for various phones) documented by > BitPim in applications that don't use any BitPim code. This also serves as a reminder to anyone who contributes code to ensure that they appropriately mark their copyrights. That means that you have to be consulted for any use of your work outside the scope of the license (which is a good thing). You are also welcome to assign your copyright to me (for example if you no longer intend to be active with BitPim, or you really just don't care). Roger |
|
From: Stephen W. <sa...@us...> - 2004-03-04 19:30:35
|
On Thu, 2004-03-04 at 01:11, Roger Binns wrote: > The problem with the GPL is that it is "freedom or nothing". Technically > anything you link in (such as BitPim does with wxWidgets, DSV, libusb, > Python, pySerial, win32all, cx_Freeze) must also be under the GPL. > I don't like the idea of linking to other peoples components and then > effectively relicensing them, although maybe I am misreading the GPL. I think it OK to combine GPL and non-GPL parts as long as the non-GPL parts are GPL-Compatible. (More permissive?) This: http://www.gnu.org/philosophy/license-list.html#GPLCompatibleLicenses lists licenses that the FSF believes to be GPL compatible. I think a big part of what makes it GPL compatible is that whoever receives the software is free to modify it and redistribute it. But it is not entirely trivial. For example, a seemingly minor change in the XFree86 license has apparently made the latest XFree86 incompatible with the GPL. A lot of the 3rd party components look to be GPL compatible according to the gnu.org page. Python, wxWidgets, Python-DSV, libusb all clearly are. Not sure about pySerial since its license file seems to date back to a time when python licenses were not GPL compatible. I don't think the licenses of the installers and freezers are relevant to GPL compatibility. > However the GPL does seem to be more attractive every day since > it is rigidly "freedom or nothing". That means no loopholes > or other vagaries. > > Ok, as a last shot, how about the LGPL. It doesn't appear to "infect" > other libraries and components that share the same executable. Section > 5 of the LGPL does make my head spin though. Section 6 does bring > in the "advertising" which is nice. I'm not sure that the LGPL really fits and the talk of Library could be confusing in the context of BitPim. I guess my preference is to either stick with the V2.0 perl license or decide to use the full GPL after making sure that all the other components are GPL compatible. The latter still leaves options for proprietary software developers that would like to use BitPim in some way. They can try to negotiate a separate license with us, or they can use the "facts" (i.e. sync protocols for various phones) documented by BitPim in applications that don't use any BitPim code. Stephen |
|
From: Chris F. <cf...@za...> - 2004-03-04 16:46:50
|
> CDM-8900 and writing the data back without setting some of the fields > results in the handset getting rebooting. At least this is the unfortunate > experience of a number of users on HoFo. I mean to say getting -stuck- rebooting. My proof reading skills are diminishing it would seem. Chris... |
|
From: Chris F. <cf...@za...> - 2004-03-04 16:14:02
|
Comments inline - Chris... On Wed, 3 Mar 2004, Roger Binns wrote: > The main thing I need is pointers to research people have already > done, and especially any sync protocols. There do appear to be > various threads on Howard Forums, but they wonder all over the place. > I do have the Curitel PC Sync app so I will have a look at that. The only thing I can say about the PC Sync App is to caution you about writing any data back to the handset from it. It would appear that the phonebook data is -slightly- different on the TX-95C than the CDM-8900 and writing the data back without setting some of the fields results in the handset getting rebooting. At least this is the unfortunate experience of a number of users on HoFo. > > Roger |
|
From: Roger B. <ro...@ro...> - 2004-03-04 06:17:19
|
Stephen Wood wrote: > V2.0 looks basically OK, but what is the point of section 8. I have just posted to the Perl licensing list asking about that using your precise example. Dunno if I will get an answer. > happy with this. I would prefer someone embedding my code to either > acknowledge my code (the dreaded BSD advertising clause), or make their > source code open (the viral GPL). I do very much agree with your sentiments. The Artistic license is very strong on distinguishing standard from modified versions, which is my biggest concern. The problem with the GPL is that it is "freedom or nothing". Technically anything you link in (such as BitPim does with wxWidgets, DSV, libusb, Python, pySerial, win32all, cx_Freeze) must also be under the GPL. I don't like the idea of linking to other peoples components and then effectively relicensing them, although maybe I am misreading the GPL. However the GPL does seem to be more attractive every day since it is rigidly "freedom or nothing". That means no loopholes or other vagaries. Ok, as a last shot, how about the LGPL. It doesn't appear to "infect" other libraries and components that share the same executable. Section 5 of the LGPL does make my head spin though. Section 6 does bring in the "advertising" which is nice. Roger |
107 messages has been excluded from this view by a project administrator.
