From: Arndt Roger Schneider <arndt.roger@...>
Date: 2009-12-12T19:20:31+09:00
Subject: Re: [ANN] Design tool Jeszra 0.1 for Ruby Tk

Hidetoshi NAGAI schrieb:

>Hi, 
>
>From: Arndt Roger Schneider <arndt.roger@web.de>
>Subject: [ANN] Design tool Jeszra 0.1 for Ruby Tk
>Date: Thu, 10 Dec 2009 20:05:06 +0900
>Message-ID: <hfqkds$pdg$1@aioe.org>
>  
>
>>Hi all Ruby-Tk Users and Developers.
>>
>>I am pleased to announce the first
>>public release of Jeszra (0.1).
>>    
>>
>
>I'm a develper of Ruby/Tk.
>Can I help you? Do you have any request to Ruby/Tk?
>  
>
Yes, there is a huge pile of work to push ahead for Jeszra.
I myself still have to do some admin homework to do the sourceforge projects
to ... setting up the repositories and updating the gestaltitems online 
documentation as
well as the libraries themselve.

In relation with Ruby:
The immediate thing is the lack of ruby examples inside the documentation,
I did include lots of tcl examples, but only one for ruby sofar --the 
goolbar add command--

Providing these examples and reviewing them is a lot of work.

The entire documentation for the libraries and Jeszra is written
in DocBook and all the DocBook manual pages are being generated
by Jeszra.

There are two DocBook related chapters inside the Jesra book
explaining how the documentation is being created, the abridged
chapter explains how to modify the generation process itself.

That is: Everyone with a DocBook 4.5 toolchain is able to
generate all the included manual pages, independently from me.

For the current time I will collect those examples sent to me
by email and publish them inside a newly created review section
online for public review.

I think the best way for this is to publish the email address of
the original example-author within the example, so
that each reviewer can directly communicate with the
original authors.

I also appriciate an example how to create a rubygem
(I think there tutorial out there).

rubygem, starpack, Asd ... should be generated by Jeszra
as-well. So this has to be done in Tcl not Ruby.

Most other things are related with future versions.
This is actual software design work

I want to: Integrate Jeszra within every ruby-Tk, Lisp-Tk, Tcl/Tk, 
Python-Tk ...
application. I think I will have to work colsely with
at least 3 projects from small to large, in order to define these 
integration
procedure. Jeszra itself uses this for itself: The little red button 
allows full
access to Jeszra's internals--something akin to a live vivisection of 
Jeszra ;-)

I want to: Allow editing Ruby-Tk, Tcl//Tk ... Designs side-by-side
to switch and transgress these projects freely. I have no glue yet how
to accomplish that with Ruby-Tk.

There is some very important code inside of Tkinter (Python)
related to the Tix package.

The package allows the subclassing of existing Tk windows,
such an mechanism is also needed inside the wrapper classes,
since in many cases may the need arise to access internal windows
of a composite window. This is for example necessary for the
bwidget tabset, were a frame is generated by the tabset and
returned to the caller, in which then the dialog is being put.

Runtime Library and GestaltItems do not generally need
this, since I always prefer explicit creation rules over implicit ones.


I like the way how Ruby-Tk casts the return values and
properties when passing them from and to Tcl/Tk.
The generated wrapper classes lack these ability --of course
Jeszra has to generate those either.
In the meantime this should be done by inheritance, lot of work.


Thanks for asking

-roger