skn3 - I agree
13. Autodetect modules used (release mode only?) could take a bit more time to do the extra processing.
This will be one of the core features of my preprocessor, but its better implemented in the compiler. Maybe an ultra-release mode that even strips down all unused stuff from the modules used, placing these stripped down versions in the tmp directory for a very long compile. This is a possible feature of my preproc.
Russel: this has been discussed before.
1) Of course. This is best achieved by first creating an abstract class for each control, each inheriting from "gadget" or "control". Then, in each platform specific file, the abstract classes are implemented and
2) Yep
3) See 1. For GUI, personnaly, I'd prefer two methods, one my own and one from this python native gui thing. My own is that in the abstract classes there are fields (properties, actually - MARK - GUI MODULE WILL NEED THESE TO BE ELEGANT), that give info on sizing of conrols, dimensions, etc. This will allow you to position cross platform, but it requires quite a bit of coding on the user side. Other positioning methods can be built upon this. For instance, the python thing's gui system was to define a window like an html table, and place a control in each data area. Not html ofcourse but it was like html. It was reasonably easy. The editer for my method could be where you say, define all components as attaching to other components, with a certain pixel distance between them. this sounds limiting, but it is for the most part how the VS2005 gui editer works for the most part and it is VERY convenient because all your stuff is lined up and neat.
4) see 3
Anyway, it'd be nice to carry the gui discussion to another thread. This wasn't created for discussing a gui module, it was created forr getting a response from BRL, which seems impossible.
13. Autodetect modules used (release mode only?) could take a bit more time to do the extra processing.
This will be one of the core features of my preprocessor, but its better implemented in the compiler. Maybe an ultra-release mode that even strips down all unused stuff from the modules used, placing these stripped down versions in the tmp directory for a very long compile. This is a possible feature of my preproc.
Russel: this has been discussed before.
1) Of course. This is best achieved by first creating an abstract class for each control, each inheriting from "gadget" or "control". Then, in each platform specific file, the abstract classes are implemented and
2) Yep
3) See 1. For GUI, personnaly, I'd prefer two methods, one my own and one from this python native gui thing. My own is that in the abstract classes there are fields (properties, actually - MARK - GUI MODULE WILL NEED THESE TO BE ELEGANT), that give info on sizing of conrols, dimensions, etc. This will allow you to position cross platform, but it requires quite a bit of coding on the user side. Other positioning methods can be built upon this. For instance, the python thing's gui system was to define a window like an html table, and place a control in each data area. Not html ofcourse but it was like html. It was reasonably easy. The editer for my method could be where you say, define all components as attaching to other components, with a certain pixel distance between them. this sounds limiting, but it is for the most part how the VS2005 gui editer works for the most part and it is VERY convenient because all your stuff is lined up and neat.
4) see 3
Anyway, it'd be nice to carry the gui discussion to another thread. This wasn't created for discussing a gui module, it was created forr getting a response from BRL, which seems impossible.