You might have noticed I didn't write much here recently (to tell the truth, last post was really long ago).
What happened back then? I entered and left another university, felt in love and broke up with another girlfriend, decided to rent an appartment alone, changed job twice and been to LVEE. I tried limiting my Kolibri-related activity to get real life going. One time I've even been depressed with all the world being a huge peace of shit. And believe it or not, I still love this OS.
Most of things I were interested in are now supervised by other community members whom I thankful for that. diamond is currently working on common libraries (libs-dev), hidnplayr and CleverMouse do great job on network stack improvements.
This year started with kernel diving. Seriously, I had too much free time and too less things to do so I couldn't stand it and got back to Kolibri. I've been there all this time, but sweared myself not to code for it anymore. What a pity.
Anyway, what I did is tried to prettify, comment and simplify GUI code. I wanted to do that before but were always failing to start properly. As a side-effect, I not only made code more readable but implemented functionality wanted so long: from now on (and I'm talking about trunk revision #1391), user is able to resize windows in five different directions by grabbing appropriate border or corner: west, south-west, south, south-east and east. Minimal width is restricted to 127px and minimal height the one windows would have in rolled-up state.
Codebase is huge and no one really wants to make global modifications leading to possible overall stability decrease. What we have now is mostly a mess of undocumented code with small time-to-time modifications made by different people with different coding styles and different professional level. Don't get me wrong: this is very, very good and that's probably one of things we all love about Kolibri, but it has to stop. Not in a way of me being the one to refactor all the kernel (moreover, I just can't do that because of lack of knowledge and time) but in a well-thought coding guidelines document all should follow. If you're interested, take part in discussion.
Sunday, February 7, 2010
Back to life
Posted by
mike.dld
at
5:12 PM
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment