We all know we need to clean up, so to get some specifics up, here's a few tasks I belive we can split up. Please pick tasks.
* Cleaning up the event handeling I volounteer for this, heck, I even want to do it. And I belive it is quite important. * Error handeling This would involve creating a log-system of sorts that would be easy to use, and allow us to use the --verbose options. It shouldn't be much work, to create it, but we need to get it in there so we can start outputing stuff that might be important. Consider the "could not bind 0xXXXXX to pixmap" messages, they normaly aren't important, but we want to be able to EASILY enable them without a rebuild. The usage, the way I see it, would be something like: pCritical(char *fmt, ...) pWarn(char *fmt, ...) pInfo(char *fmt, ...) pDebug(char *fmt, ...) pVDebug(char *fmt, ...) and it would be exposed to plugins. VDebug beeing verbose, and mostly only used by developers, but there is no reason not to expose this to a user through stacking of -v's if there is a problem. * Settings overhaul See the diffrent thread, does anyone volounteer? * General plugin cleanup. Specificly: CUBE. Cube/rotate should either be completly rewritten, or significantly cleaned up. Does anyone feel up to the task? * Build cleanup We have a lot of strange and empty files laying around, some plugins are optional, others are not. Some build deps are unknown to the build system, etc... This might actually be a job for someone mostly involved with the packaging? * Documenting This needs to be a priority. I don't expect people to write documentation files, but folks, document your code. I expect all new functions going in to core to have at least a one line comment describing what it does. Preferably 2-3 lines. If we get this done, I belive we'll have a hell of a lot of fun afterwards. It WILL pay off to do this dirty job. -- Kristian _______________________________________________ beryl-dev mailing list beryl-dev@lists.beryl-project.org http://lists.beryl-project.org/mailman/listinfo/beryl-dev
