Again, so far so good. The first practical use of this will be to create a gnocl::pixMap command to handle off-screen rendering of images.
![Reblog this post [with Zemanta]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_vuD-AIWzifmJp9e9aJ7xZ7ti6N30wc_CLYYxsOlZ-tNt7FFxEdwJDF-2081s6sa44d2sKs6mkm0rfvXxYD6q9NltTtmrXZP6OWU2xyVonjikspGbab8f0-9OPaYxTEwUA0QrrwkiHqMLoBXGgLSVoQ=s0-d)
Sunday, January 17, 2010
Command module builder
After enjoying success with custom scripts to automate the creation of object and widget modules, I thought that I'd do the same for building new new Gnocl commands. Here there is no widget registration and so on but the familiar framework of commands, sub-commands and options needs to be there.
Again, so far so good. The first practical use of this will be to create a gnocl::pixMap command to handle off-screen rendering of images.
Again, so far so good. The first practical use of this will be to create a gnocl::pixMap command to handle off-screen rendering of images.
Subscribe to:
Post Comments (Atom)
-
Given this module some attention today. Added some of the more package wide options to the module and created customised handler for settin...
-
Over the past few programming sessions I've been working on producing a central point, a dashboard, around which it's possible to se... -
The contents of a GtkTextBuffer can be saved as serialized binary file. Whilst converting such a file to ascii may be problematic if the bu...
No comments:
Post a Comment