On Tue, Jun 14, 2005 at 02:36:19PM +0200, Wim De Smet wrote:
Hi,
Hi Wim!
[...] I was thinking about doing some simple kind of plugin to get started (are there any you want to work on?), but I'm fascinated with parsers and how they work, though I might not be very good at writing them, I'd be interested in working on that later on. Unfortunately my C skills aren't very good but I've got the basics and I also know lots of java (pretty useless here I guess :), some C++, and have experience scripting in shells and python.
cheers, Wim
OK. I think the easiest one is BUG#343 (parser related). On the side of dpis, I think a man-page-to-html filter can be interesting. This is something that lets you view man pages as html in the browser. It can be evolved to also handle "info" files and then become a good help browser, making an easy&quick interface to local information (in the harddisk). These days, GNU/Linux, BSD*, etc. distributions come with lots if information in different formats that is seldom used. This is man pages, info files, html files etc. if a dillo dpi can provide for an easy interface for accesing it, I think it would be very handy. Think of a single text entry that searches in the local HD for information ao a keyword[s] providing some local links as answer.
[Drasko wrote:] Thanks for your replies and warm welcome. I have experience in C, C++ and Java, and I am learning GTK+ and Python at the moment. I would like something simle to start on gently, as my skills are not qute high. I have no special preferencies, so I'll agree with anything that you consider appropriate for beginer. It would be nice to have some point-outs about the subject given (how to start and where to look for the docs).
Well, I meant something more specific about expertise. For instance: libc, pthreads, sockets, network programming, parsing, RFC implementations, protocols, widgets sets (as GTK/FLTK/Dw), non blocking IO, distributed programming, daemons, QA, testing, etc. :-) As with Wim, an easy one is BUG#343. On the cookies field, you can investigate/test BUG#364 and/or BUG#370 (got to coordinate with Diego S.). Another good one to start is BUG#674. A quick solution is trivial, but a good one requires a bit more of thinking and investigation to choose a good "cutting threshold" for the protection scheme. HTH. -- Cheers Jorge.-