schwarzerkaffee-develop Mailing List for Schwarzer Kaffee
Status: Pre-Alpha
Brought to you by:
martinkalbfuss
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
|---|
|
From: Martin K. <ma....@we...> - 2009-12-20 13:53:35
|
Hi, The new version is out. It would be nice if someone could read the NEWS file and correct my misspellings. Also the used names in the library should be similar to the SDL names. If you see something please inform me. Thanks -- Martin Kalbfuß <ma....@we...> |
|
From: Radoslaw M. <rad...@gm...> - 2009-12-14 20:42:00
|
Hi, Yea, I just took a look - way too much chaff in those module files when we include documentation. Whenever I get a chance, I'll move the doc strings to a separate texinfo-based file (or collection of files). Probably also add a section to the makefile to give users the possibility of generating HTML/PDF from the texinfo source. Cheers- -Radek -----Original Message----- From: Martin Kalbfuß [mailto:ma....@we...] Sent: Monday, December 14, 2009 5:57 PM To: sch...@li... Subject: [sk-develop] Compiler bugs are fixed The compiler bugs are fixed now. The project is compilable again. I started to add docstrings to the SKVideo module. But I'm not really happy with the result. Maybe this was a bad idea. The docstrings are equal to the SDL documentation entries. Except some changed names and parts which looked unnecessary. The problem is, that some docstrings are so big, that they make the definition module unreadable. Maybe it's better to keep the documentation separate from the code. But you can use this docstrings as basis for the documentation. Maybe you have an idea. ---------------------------------------------------------------------------- -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Schwarzerkaffee-develop mailing list Sch...@li... https://lists.sourceforge.net/lists/listinfo/schwarzerkaffee-develop |
|
From: Radoslaw M. <rad...@gm...> - 2009-12-14 20:35:59
|
Can you maybe treat config.h as a plain text file, search for the PACKAGE_VERSION line and cut up the string to return only the version number? In INSTALL I only changed a couple really minor typos and re-justified the lines to make them a little bit longer an readable. Cheers- -Radek -----Original Message----- From: Martin Kalbfuß [mailto:ma....@we...] Sent: Monday, December 14, 2009 6:51 PM To: sch...@li... Subject: [sk-develop] Problems with config.h Hi, I try to get the version information from the build system, to implement a function, returning the library version. The problem is, that the config.h is a C header file. Not a Modula-2 definition module. Why is it always so difficult. :-( Maybe I will find a solution. Ah, yes. Your changes in the README are good. I have no idea what you've changed in the INSTALL file. ---------------------------------------------------------------------------- -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Schwarzerkaffee-develop mailing list Sch...@li... https://lists.sourceforge.net/lists/listinfo/schwarzerkaffee-develop |
|
From: Martin K. <ma....@we...> - 2009-12-14 16:58:41
|
Hi, I try to get the version information from the build system, to implement a function, returning the library version. The problem is, that the config.h is a C header file. Not a Modula-2 definition module. Why is it always so difficult. :-( Maybe I will find a solution. Ah, yes. Your changes in the README are good. I have no idea what you've changed in the INSTALL file. |
|
From: Martin K. <ma....@we...> - 2009-12-14 16:04:51
|
The compiler bugs are fixed now. The project is compilable again. I started to add docstrings to the SKVideo module. But I'm not really happy with the result. Maybe this was a bad idea. The docstrings are equal to the SDL documentation entries. Except some changed names and parts which looked unnecessary. The problem is, that some docstrings are so big, that they make the definition module unreadable. Maybe it's better to keep the documentation separate from the code. But you can use this docstrings as basis for the documentation. Maybe you have an idea. |
|
From: Martin K. <ma....@we...> - 2009-12-13 03:16:32
|
Hi, You should have SVN access now. Please edit the ChangeLog everytime you change something. If it's a bigger change please give an explanation on the list. I started to add doc-strings in the definition modules. Haven't uploaded the changes yet. But this will happen tomorrow. Currently I write them only for the Video module. If you like you could can do this for the other modules. Maybe we could write a shell script reading the doc-strings from the definition modules and create the API doc out of them. Do you have any experience with shell scripts? Do as much as you like and can. I'm happy about every help I can get. Even if it's only correcting some misspellings. If you have any questions, please ask on the list. Yeah, I know we are the only persons. But maybe(hopefully) this will change. -- Martin Kalbfuß <ma....@we...> |