I'm not against implementing this, but I see the wxVariant as a fairly complex piece. If wxVariant isn't done correctly, then we might as well have not done this. But it's somewhat difficult to see how to wrap this stuff, while keeping it wxEuphoria-like. Automatic creation by the library of the wxVariants would be very difficult, while making the user manage too much detail would be nearly as bad.
I think that once v0.10 is released, I'll come back to this. In the mean time, suggestions on how to make the wxVariant system work within wxEuphoria would be much appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=61059
Originator: NO
I'm not against implementing this, but I see the wxVariant as a fairly complex piece. If wxVariant isn't done correctly, then we might as well have not done this. But it's somewhat difficult to see how to wrap this stuff, while keeping it wxEuphoria-like. Automatic creation by the library of the wxVariants would be very difficult, while making the user manage too much detail would be nearly as bad.
I think that once v0.10 is released, I'll come back to this. In the mean time, suggestions on how to make the wxVariant system work within wxEuphoria would be much appreciated.