Deskbar Style Changes and Refactoring

Description

This might be a small abuse of the trac system but I created this ticket so I'd have a place to put patches that relate to style changes and refactoring. None of these changes should have any effect on Deskbar from a user's perspective but they either make the code style nicer, or eliminate code duplication, or give a variable a better name.

Deskbar Style Super Mega Patch. Delete evil spaces at the beginning and end of lines. No your comments are not so special that they deserve and extra indent. No your comments are not so special that they get a tab after instead of a space. No you cannot use a tab instead of a space if the tab happens to indent by 1 space. Spaces around binary operators. Other stuff.

This patch is big vim style checker found even more style issues including that the Open Tracker license broke the 80 char limit in almost every file! yeah! Also more evil spaces deleted, more 80 char limit fixes, more spaces around binary operators. Single line comments get indented *after* the line they affect as per style guide.

While I think your changes looks ok from a quick view, I find there is no need for the silliness done in TBarApp using be_app to call BarView(). I can't really see why TBarApp can't call BarView() directly. If I'm not mistaken I think that call would be better than introducing a member for fBarView.

Thank you for reviewing my patch. I grabbed a pointer to the barView in the constructor because the code to grab the barView was being called many times. This way, the pointer to the barView is gotten just once, and is used several times rather than having to grab the pointer over and over again. DRY

I created this particular ticket strictly for style changes only. Any functional changes would go somewhere else. Since I really want the other style changes in the above patches committed (gets em' out of my patches) I'll just remove the controversial bits for now.

Deskbar Style Super Mega Patch. Delete evil spaces at the beginning and end of lines. No your comments are not so special that they deserve and extra indent. No your comments are not so special that they get a tab after instead of a space. No you cannot use a tab instead of a space if the tab happens to indent by 1 space. Spaces around binary operators. Other stuff.

This patch is big vim style checker found even more style issues including that the Open Tracker license broke the 80 char limit in almost every file! yeah! Also more evil spaces deleted, more 80 char limit fixes, more spaces around binary operators. Single line comments get indented *after* the line they affect as per style guide.

Nice. The patches is beginning to be large, so further changes should probably be divided in to several patches. This way one patch at a time can be reviewed and applied easily.

There is a branch for Deskbar/Tracker rewrite that might be affected if to big changes are done. I do not know what the state of that branch is, so I'm a bit worried of how to handle this. It probably need more devs though, as you have seen the code can be improved and refactored.

There is a branch for Deskbar/Tracker rewrite that might be affected if to big changes are done. I do not know what the state of that branch is, so I'm a bit worried of how to handle this. It probably need more devs though, as you have seen the code can be improved and refactored.

Don't worry, the tracker_layout branch only touches src/kits/Tracker. I'm taking a Haiku break at the moment but i'm still around :)

I really wish there was a way to upload multiple patches at once... anyway I split my patch into individual diff files so they can be reviewed and applied separately. Because they are style changes _only_ you should be able to apply each file separately without breaking anything. I also accidentally uploaded some unrelated patches so please ignore Deskbar Autoexpand Teams 1.diff, Deskbar Disable Expand Options 1.diff, and Deskbar Resize Team Icons 5.diff. Those are patches to other things, not style related. I marked them as obsolete to reduce the confusion. Sorry I have way too many patches floating around. Anyway, if you like patches you'll love this ticket. Please review my patches and apply them if they are good, fix them if they are not. Thanks!