Prepping for ZDLSharp 3.0.5.3

I’ve made great headway on a couple of the bugs. Unfortunately there’s one that will take some time, so now I’m faced with the decision to either fix it or leave it for another time. I really want to get this version out the door, as it’s taken a long time. Part of the changes I want to implement to fix it are slated for 3.0.6.0. I planning a better configuration backend and doing away with the old ReadINI support. Of course, since a substantial amount of the program is built on this old code, it will take quite a few hours of coding. The current bug is pretty isolated I think.

As for my plans in the wiki for 3.0.6.0, this is what I’m planning:

1. New Update System
• I’ve chosen to do a hybrid between self updating and leaving it alone. I don’t want people to have to open their browser every time just to update
2. Community Functionality
• This feature won’t be in 3.0.6.0 at all. Perhaps in subsequent versions, but it’s not in the pipeline yet.
3. Config File Trampling
• Currently with the readINI() functions, any unknown lines are completely removed. I’m going to change this, plus also keep track of what version wrote the last config file. I recommend that all ZDL ports use this functionality, and warn users if they’re using an old config file. If the user agree’s it’s cool, overwrite it if a better system isn’t implemented. If the user isn’t cool with it, read the config, but do not write it back at the end.