Re: [AD] New BeOS patch + problem with multi-line strings in config

[Angelo Mottola <a.mottola@xxxxxxxxxx>]

> But you don't call it on "Yes" and "No" button names.

Wops! I'll fix this.

> What about adding of
> something like converting "escape" sequences ('\n', '\r', ... or even '\'
> on end-of-line ('\<eol>')). Is it wanted feature? It could be good,
> especially with '\<eol>' sequence, but it would break backward
> compatibility. There could be also some problems if anyone is finding
> lines by brutal search for new line character, but I did not find it in
> config.c. destroy_config() should be rewritten to store values with
> escaping those characters. What do you think?

Hummm... Using escape sequences may be a solution, but IMHO I think it's 
better to fall back on the single line implementation and convert the window 
close message into a single line statement. This is not only because it saves 
time, but because as you say adding multi line support to the config routines 
may break compatibility, and adds more overhead.

> And I almost forgot: Would not it be good to have language.dat and
> keyboard.dat unpacked in some CVS directory like resources/language and
> resources/keyboard (to be able to diff them like any other file) and have
> some script to update theirs *.dat after each commit (or before
> releasing a WIP)?

That would be really useful to keep translations up to date! The .dat 
creation could be added into zipup.sh. Can someone do this please?

Talking about the window close issue, I think we can add the popup message 
even in X: the problem was that X has no default widgets set, but what if we 
use directly Xlib to draw the popup alert window? In the end this is what 
GTK, QT and others do, so why not to go the same way? The only problem for 
this is that it could be longer to code... At least for me, as I'm a beginner 
on Xlib programming.
What do you think?

-- 
Angelo Mottola
a.mottola@xxxxxxxxxx
ICQ UIN #66972680