Name: close_button Function: end
background_color: red
Name: textbox
function: {
display,
read_in
}
access:
{
add_button,
subtract_button,
multiply_button,
divide_button
operator (+, -, /, *)
}
name: add_button
function: add{int, double, float}
operator: +
name: subtract_button
function: subtract {
int, double, float}
operator: -
name: multiply_button
function: multiply {
int, double, float}
name: divide_button
function: multiply{
int, float, double}
operator: *
Say that's a calculator with a gui, is it too verbose?
Programming method (what do you think?)
Personally, I think it looks sparse.
There is not enough information provided to allow any decent amount of customization.
Also, the event handling looks much to rigid.. do buttons only ever fire off a single type of event? The textbox has two event? or does a single event fire two functions? If it has two events, which event does the first function map to and which the second? Is the order important?
I think you'd have trouble maintaining the code... if you dropped the project for two months and came back, would you really be able to remember exactly what everything actually meant?
I don't mean to be hard on the code... I just think that this might be a case where Verbosity is a necessary nuisance, otherwise you'll end up with too much indecipherable information.
After searching for something similar in Qt, i think it's good but needs improvement.
@paragon: order won't matter and the textbox won't have just two events. I just used as an example.
Until you know what you are doing, and why things work ( and don't ) the way they do, you can't even begin to improve on them.
Until you know what you are doing, and why things work ( and don't ) the way they do, you can't even begin to improve on them.
aka "You are not god's gift to binary."