bkmd-devel Mailing List for Bookmark Daemon
Status: Pre-Alpha
Brought to you by:
patricech
Menu
▾
▴
bkmd-devel — This is the list for bkmd developers
You can subscribe to this list here.
| 2002 |
Jan
(10) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: Patrice N. <mai...@pa...> - 2002-04-14 14:04:51
|
Hi there,
Bj=F6rn sent me some coding example for CommonC++ quite a while
ago. Finally I had the time (and motivation) to have a second look at
it. I have now introduced it into the source of bkmd. So the network
support should be quite solid now. At the moment the code is very
nasty, though and I will definitely have to correct this. But it's a
start, quite a good one.
Additionally the perl client works quite well by now. At least it's
possible to connect to a server, get the whole bookmark list and then
get the details when clicking on bookmark or folder.
And last but not least, a third tip. With the current galeon release
the bookmarks are stored as an xbel file. It's possible to use this
file for bkmd. A small change is necessary though. You must replace
the first element ("bookmarks") to "xbel" - and don't forget to change
the closing tag, too.
bye,
patrice
|
|
From: <sp...@pa...> - 2002-01-31 10:57:24
|
Hi, I realised I hadn't commited the additions to the CodingStyle document yet. I have done that now. I added something about classes and some smaller remarks. I also moved the file to the documentation directory. After all it is documentation. Björn |
|
From: Patrice N. <mai...@pa...> - 2002-01-20 20:11:38
|
Bj=F6rn Olievier <bjo...@ad...> writes: > I've read the CodingStyle document. Seems ok, but there are some gaps. > I'll add some things. I'll try to stick to suggestions made in the C++ > FAQ lite, which refers to news:comp.lang.c++ quite often. > The FAQ is at http://www.parashift.com/c++-faq-lite/. I'm looking forward to the changes. ;-)) p=E4t --=20 GPG ID: A5F15976 Key fingerprint: 201D 12D1 F629 1E9B 0BB0 EAF5 3009 AF60 A5F1 5976 |
|
From: Patrice N. <mai...@pa...> - 2002-01-20 20:10:55
|
Hey, Today I have implemented a source documentation system using doxygen. <http://www.doxygen.org/>. The commenting is pretty intuitive IMO, and I like the output very much. I'll put the documentation output online to <http://bkmd.sf.net>, so that people can have a look at it, see how awful this is implemented and jump here to help out. :-) Bye, patrice -- GPG ID: A5F15976 Key fingerprint: 201D 12D1 F629 1E9B 0BB0 EAF5 3009 AF60 A5F1 5976 |
|
From: Patrice N. <mai...@pa...> - 2002-01-16 01:19:57
|
Hi there, The new class diagram is online at <http://bkmd.sf.net/en/devel/server/server.html>. I have already used the CommonC++ classes for the two sockets. To separate them from the rest of the code they have a great background at the moment. I'm not sure if this is the official way to do this or if I should even highlight them at all. Kudos go to Bj=F6rn he has pointed out some errors in the previous diagram. He has also put his thumb on the fact that the source and the class diagram could be from different projects - they don't even resemble each other. I promise to fixe the source where it is different from the new diagram. Ok? :-) Ah well, please tell me if you like the new class diagram. And I know you won't so please tell me what you don't like. Thank you, patrice --=20 GPG ID: A5F15976 Key fingerprint: 201D 12D1 F629 1E9B 0BB0 EAF5 3009 AF60 A5F1 5976 |
|
From: <sp...@pa...> - 2002-01-14 22:08:54
|
On Mon, Jan 14, 2002 at 07:47:40PM +0100, Patrice Neff wrote: > Björn Olievier <sp...@pa...> writes: > > Thank you very much for your research! The results are very simular if > not equal to mines. Then you probably also found the more useless libraries like SimpleSocket or tcp++ and some more :) > > However, I found some very interesting frameworks: CommonC++ and ACE. > > They're more than just C++ wrappers for sockets. They have provide > > classes for networking, threading, dates, string manipulation, ... And > > they have extensive documantation and are still active (the last > > CommonC++ release was last month). > > I also ecountered these two libraries. I'm not sure if it's the right > thing to use a 1632 KB library for such a simple thing like sockets. Indeed, the size of the frameworks is a valid argument for not using them. Maybe if we could use the framework for others things too, it would be more interesting. > > I'd recommend we use CommonC++. ACE is designed for distributed and > > parallel applications, which is total overkill for bkmd :) > > Also, CommonC++ is a GNU project, something a Debian user might > > appreciate ;) There also seems to be some kind of XML stream parser > > present. > > Oh yes, I didn't see the XMLStream class before. So if this class is > usable we can drop the xerces library. I'll definitely check it out. I looks like an interface, an abstract base class. And I also saw a reference to Sax somewhere. But I don't know the details (yet). > Thank you very much again! No need to thank me, I signed up for the job :) Björn P.S. I seem to have some problems with incoming and outgoing mail. My ISP is probably messing around again. Some mails get stuck for a while and then get sent or arrive in batch. I hope I don't have to re-send them all. |
|
From: Patrice N. <mai...@pa...> - 2002-01-14 20:58:58
|
Hi there, This weekend I have developed a lot on the bkmd client. Well the result looks pretty small but I think it's a nice achievement though it cost me a lot of sleep and it is certainely not one of the nicest pieces of code ever written on this planet. I have uploaded it into the module `perl_client' so check it out with $ cvs -d "$USE...@cv...:/cvsroot/bmkd" co perl_client or if you want anonymous CVS access use: (untested) $ cvs -d:pserver:ano...@cv...:/cvsroot/bkmd login $ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/bkmd co perl_client It is far from being usable, but at least it is there. Ain't it nice? :-) bye, patrice -- GPG ID: A5F15976 Key fingerprint: 201D 12D1 F629 1E9B 0BB0 EAF5 3009 AF60 A5F1 5976 |
|
From: <bjo...@ad...> - 2002-01-14 20:07:44
|
Hi, I've done some research on the subject of C++ socket libraries. There are quite a few wrappers, but most of them are terrible. I've found 5 libraries to handle sockets. They are all incomplete: they only handle basic operations, have virtually no error handling or other issues. One tarball didn't even contain a decent Makefile. Also they are all 2 years old, at least, which means they're no longer maintained. However, I found some very interesting frameworks: CommonC++ and ACE. They're more than just C++ wrappers for sockets. They have provide classes for networking, threading, dates, string manipulation, ... And they have extensive documantation and are still active (the last CommonC++ release was last month). I'd recommend we use CommonC++. ACE is designed for distributed and parallel applications, which is total overkill for bkmd :) Also, CommonC++ is a GNU project, something a Debian user might appreciate ;) There also seems to be some kind of XML stream parser present. The URL's for CommonC++ and ACE, so you can check it out yourself: CommonC++: http://www.gnu.org/software/commonc++ http://sf.net/projects/cplusplus ACE: http://www.cs.wustl.edu/~schmidt/ACE.html Björn |
|
From: Patrice N. <mai...@pa...> - 2002-01-14 18:48:31
|
Bj=F6rn Olievier <sp...@pa...> writes: Thank you very much for your research! The results are very simular if not equal to mines. > However, I found some very interesting frameworks: CommonC++ and ACE. > They're more than just C++ wrappers for sockets. They have provide > classes for networking, threading, dates, string manipulation, ... And > they have extensive documantation and are still active (the last > CommonC++ release was last month). I also ecountered these two libraries. I'm not sure if it's the right thing to use a 1632 KB library for such a simple thing like sockets. > I'd recommend we use CommonC++. ACE is designed for distributed and > parallel applications, which is total overkill for bkmd :) > Also, CommonC++ is a GNU project, something a Debian user might > appreciate ;) There also seems to be some kind of XML stream parser > present. Oh yes, I didn't see the XMLStream class before. So if this class is usable we can drop the xerces library. I'll definitely check it out. Thank you very much again! patrice --=20 GPG ID: A5F15976 Key fingerprint: 201D 12D1 F629 1E9B 0BB0 EAF5 3009 AF60 A5F1 5976 |
|
From: <sp...@pa...> - 2002-01-14 09:18:24
|
Hi, I've done some research on the subject of C++ socket libraries. There are quite a few wrappers, but most of them are terrible. I've found 5 libraries to handle sockets. They are all incomplete: they only handle basic operations, have virtually no error handling or other issues. One tarball didn't even contain a decent Makefile. Also they are all 2 years old, at least, which means they're no longer maintained. However, I found some very interesting frameworks: CommonC++ and ACE. They're more than just C++ wrappers for sockets. They have provide classes for networking, threading, dates, string manipulation, ... And they have extensive documantation and are still active (the last CommonC++ release was last month). I'd recommend we use CommonC++. ACE is designed for distributed and parallel applications, which is total overkill for bkmd :) Also, CommonC++ is a GNU project, something a Debian user might appreciate ;) There also seems to be some kind of XML stream parser present. The URL's for CommonC++ and ACE, so you can check it out yourself: CommonC++: http://www.gnu.org/software/commonc++ http://sf.net/projects/cplusplus ACE: http://www.cs.wustl.edu/~schmidt/ACE.html Björn |
|
From: <bjo...@ad...> - 2002-01-11 16:16:18
|
Hi, I'm using the mailing list this time :) I've read the CodingStyle document. Seems ok, but there are some gaps. I'll add some things. I'll try to stick to suggestions made in the C++ FAQ lite, which refers to news:comp.lang.c++ quite often. The FAQ is at http://www.parashift.com/c++-faq-lite/. Björn |