Site News :: DSL v4.3



Quote

Which version of fltk is there?

This is version 1.1.9, which the latest "stable" release of fltk.

As per my understanding, 1.1.9 might be the end of the 1.1.x line. Current development is 1.3.x and 2.x.
1.3 is adding unicode, printing, and a few new widget. And 2.x is refactoring the API (ie, no backward compatibility) to support C++ namespace, themable ui skins, and other stuff.
Quote

Note: libhistory was not used in murgaLua and is therefore not in core DSL. I had to mydsl-load compile-3.3.5.uci to get the missing library. After that it was smooth sailing. libhistory provides command history within the Lua interpreter.

Good catch. I haven't noticed the dependence as I had the compile extension loaded all along. Tonight, I'll check if it's possible to compile the lua interpreter without libhistory.

Quote

1. Fltk menu as already noted. Only concerns two programs, editor.lua and iconView.lua. For the second a work-around is possible. If we have to for go editor.lua for now, then that is OK.

I don't know why fltk menus aren't working as I have only compiled the murga's bindings, not made any change to code. Maybe some C++ name mangling or other obscure linkage issues are causing this? I'll give a try at recompiling the bindings with different settings, but I'm not sure it'll work better.

Quote

3. We do use Lua sockets. There is no work-around for sockets. So we need to have a lua sockets be able to be "require"d or loadlib'ed.

Ok, I will also give a shot at compiling the LuaSockets extension
(either from murgaLua distro or directly from there: http://www.tecgraf.puc-rio.br/~diego/professional/luasocket/).
Quote
I don't know why fltk menus aren't working as I have only compiled the murga's bindings, not made any change to code.
As far as I know, Murga did some custom coding in order to use menu item callbacks...apparently using the native FLTK methods was either causing trouble for him or it was just too much of a complication to use them directly...I'm just speculating.  I don't know if this helps or hurts you.

On the subject of 4.3 as it is, I seem to be having an issue with Bon Echo, which is a bit more serious than that cookie thing I mentioned earlier.  Every time I use it for a while, even if it just stays open doing nothing, eventually my entire system becomes flakey.  Bon Echo RAM use goes up steadily until it is no longer responsive around about 40mb. At this point any applications that are opened fail to respond.  X will close, but the linux console will not echo anything. I can force a login prompt, but it is not useable. Ctrl+Alt+Delete begins to shut down, but hangs. Alt+SysRq+b will successfully reboot.  This happens every time I have Bon Echo open for more than a brief session, and hasn't happened since I stopped using it.

My system has 512mb ram, so i'm not running low there.
[quote=mikshaw,May 10 2008,16:51]
Quote
snip...
On the subject of 4.3 as it is, I seem to be having an issue with Bon Echo, which is a bit more serious than that cookie thing I mentioned earlier.  Every time I use it for a while, even if it just stays open doing nothing, eventually my entire system becomes flakey.  Bon Echo RAM use goes up steadily until it is no longer responsive around about 40mb. At this point any applications that are opened fail to respond.  X will close, but the linux console will not echo anything. I can force a login prompt, but it is not useable. Ctrl+Alt+Delete begins to shut down, but hangs. Alt+SysRq+b will successfully reboot.  This happens every time I have Bon Echo open for more than a brief session, and hasn't happened since I stopped using it.

My system has 512mb ram, so i'm not running low there.

Interesting. Mine has been up for 34 hours and counting with 4 tabs always open. 512MB noswap running from a frugal pendrive. What else might be in the mix, plugins, flash, etc?
no flash...I'm currently morally opposed to it =o)  No other multimedia plugins either.

But maybe there's an issue with extensions.  I had been using NoScript and Save Text Area in DSL 3.2 without trouble.  When using Bon Echo, Save Text Area became a firefox killer, so I disabled it.  Perhaps there is an issue with NoScript as well.
Next Page...
original here.