Generation should be improved to work more general and reduce the number of config files (use convention instead of configuration)
1. Class names to be generated may be extracted from the GIR file automatically (currently in use: global_conf.json)
2. Class names to be exchanged may be generated based on general pattern (most of the GLib libs even do have prefixes) so there should be no need to manually provide src/Config/swap_types.json (depends on 4.)
3. extra_methods.json is hard to read and maintain. It could easily be replaced by some ObjC Categories in BaseClasses
4. Determine class dependencies to get rid of extra_imports.json. For this to succeed I need to detect circular dependencies and enable the generator to write forward declarations
Generation should be improved to work more general and reduce the number of config files (use convention instead of configuration)
- [x] 1. Class names to be generated may be extracted from the GIR file automatically (currently in use: global_conf.json)
- [x] 2. Class names to be exchanged may be generated based on general pattern (most of the GLib libs even do have prefixes) so there should be no need to manually provide src/Config/swap_types.json (depends on 4.)
- [x] 3. `extra_methods.json` is hard to read and maintain. It could easily be replaced by some ObjC Categories in `BaseClasses`
- [x] 4. Determine class dependencies to get rid of extra_imports.json. For this to succeed I need to detect circular dependencies and enable the generator to write forward declarations
Letterus
added this to the First release of ObjGTK(0.3) milestone 9 months ago
Generation should be improved to work more general and reduce the number of config files (use convention instead of configuration)
extra_methods.json
is hard to read and maintain. It could easily be replaced by some ObjC Categories inBaseClasses
First part done with
c664e26787
.Second part could get a little bit more complicated because not all relations are 1-to-1,but some (Widget, Window, …?) are 1-to-n.