Re: [Beaver-devel] Next release

[Tobias Heinzen]

Double 12 wrote:
> 1) I think we better write real new code (like in conf.c/conf.h) after 
> we migrate everything to GtkUiManager. Otherwise, we will have to 
> change the code before, after and during the migration. The idea of 
> using the key parser is very good, by the way. In my opinion, one 
> config file is enough.
well changing to the key-file-parser of glib would be real code. I never 
write imaginary code ^^ I do not really understand your statement. The 
configuration stuff isn't really part of the migration and the interface 
does not change (only the implementation will be easier). I wanted only 
to change the implementation of the six functions (get_*_conf, 
set_*_conf) to the newer implementation (as part of the refactoring).
> 2) old_editor.c and old_editor.h are the only  old files, to my 
> knowledge. I guess we can remove them. They aren't compiled in the 
> Makefile, are they?
no. so they will be gone. if we still want to use part of the code they 
would be still in the older branches, so no real harm done.
> 3) Personally, I think we can get rid of the .bl-function. Of course, 
> it's a very innovative function for Beaver, as a small editor that 
> tends to just have conservative functions. But if we really want to 
> have it working, we have to spend time on it, and removing it will 
> probably make Beaver faster and a little bit less memory-consuming. 
> Plus the fact that the function is three years old and may be using 
> outdated technologies.
well if the need arises this feature could be readded with the (perhaps) 
new language xml-files (which are still to come). so it will be gone too^^

greets
Tobias