I have something exactly the same but I build an XML editor - the widgets are determined by the data types from the schema (spinboxs for integers, text boxes for strings etc) and my code builds these widgets as required by the XML file You'll find yourself using closures a lot to handle the callbacks - most of my methods return subroutines that get assigned to callbacks (-command or -validatecommand params for the Tk widgets) - the closure part comes from those subs having references to data from the time of their creation, to be used at the time their actually called - sounds like a time-warp waiting to happen, but its actually pretty cool. And dont forget that things like Firefox are built out of their XUL description - the firefox code interprets the XUL and builds the browser...so its a pretty common, albeit advanced, technique
...reality must take precedence over public relations, for nature cannot be fooled. - R P Feynmann
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|