[JJR]

Just so you all know, my tentative plans are to update the svn trunk this weekend (I'm kind of busy throughout the week). For the next few days, I'll just let some of the fixes and testing accumulate in git.

okibi, if your next pre-release package contains most of these recent additions and fixes (updated dsss.conf as well), I may use it to apply the changes to svn this weekend.

One other item I notice is that all versions of gtkd STILL seem contain sporadic occurrences of import statements in classes. This is ugly and completely unnecessary. I'm not sure if this is a side-effect of the wrapper logic or not. Nonetheless, in the next release, I'm hoping we can make sure that all such occurrences are removed.

I'm hoping that we can clean up the code a fair bit too over the next while... maybe follow Tango project's example in clean well-documented code.

-JJR

[okibi]

JJR, I intend to revise some of the code myself, as well as apply whatever is in the git repo on Friday and post a new pre-release. Pre7 should be available Friday afternoon, complete with both compd and dsss build scripts (sorry, I just love compd!).

Also, I'm sorry that the link to the gtkD-pre6.zip (as well as the old pre-releases) have been up and down lately. I've had issues with my router, but they should be fine now.

[JJR]

Thanks, okibi. I'll look forward to the pre-release, then.

compd is a bit of an enigma to me (other than that it's used in the shell scripts to build the library and examples): I confess that during the process of cleaning up gtkd I've been tempted to discontinue support for it (no, don't gasp! ); but if you feel it's an important part of gtkd, I guess it should stay. I was starting to feel that it more properly belonged in its own project or within the leds project (since that seems to be the project it was designed for).

Is there any documentation on how to use it? I don't see anything other than the examples of its use in the shell scripts. Nor does it display a list of commands on the command-line when you run it with no arguments. That to me is a pretty serious shortcoming of any important tool. Would it be possible to document it? I think any tool that stays in gtkd needs to be thoroughly documented. If I missed the docs somewhere... oops, my mistake.

Anyway, thanks for all your great work on gtkd.

-JJR

[jcc7]