<< Prev
 Table of Contents

Contribute

Report Bugssss
 

There are bugss ??? really ??? I'm amaze !!! send mail to j.a.l@free.fr describing what's wrong ( don't say "everything", I already aware of that... ), when it was happened, always or sometimes...
You could also provides dump of what was happened by providing strace and ltrace log. There softs report all calls to library and files operations ( ~ 80kb each ). Use strace and ltrace only with shot session, i.e. when you can create the bug quickly, log of 1 hours and 3Mb no thanks for me....
 
> cd Gsfdm-0.1
> ./configure --enable-debug
> make clean
> make 
> make install
> mkfifo fifo ; ltrace -C -o fifo gsfdm --disable-crash-dialog | sed -f ed.script < fifo | bzip2 -K > ltrace_gsfdm_log.bz2 ; rm fifo
> mkfifo fifo ; strace -C -o fifo gsfdm --disable-crash-dialog | sed -f ed.script < fifo | bzip2 -K > strace_gsfdm_log.bz2 ; rm fifo

In case end with ctrl^\c...



Internationalization
 
Your work is welcomed...
I recommend you the use of poedit... link to it from every good site.




Create you own plugin
 
Creating a plug-in is easy. A plug in is a shared library loaded at run time. You can write in language you want but it would be easier to use C, primary because this is the language of Gnome, and the one I use. In the directory "plugin/Doc" there are files that simplify life : headers, main.c skeleton and files for autoconf.
 


What's autoconf ? : If you don't know you are really newbie and perhaps you may start with somethings less tough.... Autoconf is the way any coders / hackers must use. it takes care about making all make files according of soft spec and your system...

A good way is to have a look at current plug-in...

An other way is to request me....


If you know spec of other streamed files ( perhaps for *.rm files... ), mail me. Same with soft like wget.


 << Prev
 Table of Contents