Site News :: DSL v4.3

The latest sqlite is huge in comparision to our current version. I don't think I can accomodate the latest sqlite into core. There has been much discussion on the merits of moving to the latest sqlite. Currently DSL only has one script that interfaces to sqlite and it is not a required script. It was something I was doing and using for my personal needs. Possibly a library can be built to support our current version of sqlite. Or perhaps someone can shed light on a compelling reason to require the latest sqlite.

Hi Robert!

That sounds very promising. I can hardly wait. Thanks for all your good work!

As always have fun,
meo

EDIT: I was referring to your post before this last one

Quote (mikshaw @ May 02 2008,19:00)

On the subject of flrun, you're attempting to set the value of a menu to a string, when it requires an integer. If you change input:value() to input:add(), it adds the command to the menu. Is that what you wanted?

Maybe. Gonna test. I remember when first using fl_input_browse widget I didn't know of any examples of its use (or even edible ones in C), so I didn't know how to deal with it: as fl_input_box or as fl_browse. It seemed to work as fl_input_box, so I went that way. Wrong on my part for not checking changelogs.

Quote

Also, the browse callback tries to work with fl_file_chooser directly.

I remember checking it to see if an intermediate variable was needed. I saw fl_input indulged happily being assigned a nil value so I dispensed the caution in the script. It worked, but you are again right that it is against best coding practices.

Quote

There's no need to edit the scripts when you can apply it to every murgaLua GUI in one shot:
http://damnsmalllinux.org/cgi-bin....t=19979

Extra-nice

Gonna play with that.

The LUA_INIT is used by all Lua scripts. With the new open lua fltk, not all Lua scripts are GUI, nor would you want such scripts to have to require the fltk widget set. Therefore LUA_INIT would not be such a good choice. One can still have themeable lua fltk by using, say, a dofile pointing to your .murgaLuarc.
Then only those lua scripts that need GUI, having the require('fltk") could also have a dofile("/home/dsl/.murgaLuarc"). Then editing the .murgaLuarc would cause all such lua fltk gui scripts to have the specified theme, fonts, etc.

I wonder if it might be easier to do a check for fltk in the LUA_INIT file before running any fltk commands. This assumes that -lfltk is being used as part of the interpreter as mentioned earlier, and that -lfltk loads fltk before LUA_INIT is read, neither of which I know at this point. In any case, if it works, I think either method could be used. I only mention sticking with LUA_INIT because it would allow you to skip running dofile in every fltk-enabled script.

On the previous subject of my hardware issue, I'm still not certain what the problem is, but it's looking like it might be CPU failure (swapping the ram out didn't help). My cousin just gave me his "old" mobo, which includes twice the ram i had before, and a comparable processor (1.6ghz Athlon compared to my previous 1.8ghz Pentium4). So after a few days without computing, I guess I can continue now =o)

The fans are really loud, though.

Next Page...
original here.