Currently, we use our own passive notification bar to show a recovery bar when a swap file was found:
Since version 4.7 we have a class called KMessageWidget (api documentation). Using KMessageWidget, the notification could also look like this:
Imo, the new one looks nicer, as it much better distinguishes the notification popup from the rest of the ui. However, it several drawbacks:
- the minimum width is now 800 pixel due to the label (too large, might break layout in apps)
- the title “Data Recovery” was omitted
- the “Help” link, showing a tool tip with further information, can not be added anymore (the api does not allow it)
- put the buttons under the label, as it was in the old version (currently, the api does not allow it, so we’d need something like setButtonsUnderText(bool))
- wrap the text in the label (looks aweful, since the buttons appear then between two lines of text)
- to get the “Help” label back, the api would need to forward the QLabel’s signal linkActivated(const QString&)
I’m not sure whether the API can be extended in the 4.x line, though…
just yesterday I got asked by one long time contributor, if he can at all join the KDE e.V. or if he needs to do something special for that. He thought it would be more an invitation only club.
It’s not Anybody who does contribute to KDE can join us.
KDE e.V. definition from its homepage:
“KDE e.V. is a registered non-profit organization that represents the KDE Community in legal and financial matters.”
If you want to have a vote on such stuff and are ok with the rules and goals of the e.V. like you can read on the e.V. homepage, please join.
You just need to fill out the questionaire on the e.V. page and send it to some e.V. member you know and that will support your application.
Even if you are no contributor, but want to support us with money to make our conferences & sprints possible (and our infrastructure), please take a look at our “Join The Game” campaign.
With KDE SC 4.9 around the corner and according to tradition, it’s time to have a look at what’s new in Kate.
Improved Support for Custom Color Schemas
- improved “Colors” tab in the “Fonts & Colors” config page
- configurable colors: search & replace, code folding, indentation line,
- schema export and import honor background colors (bug #291868) and font
- “highlight selection” plugin and “search and replace” plugin now use search & replace colors from Kate’s color schema
Line Modification System
- new option to disable in the editor settings: Appearance > Borders > [ ] Show line modification markers
- colors of the line modification system are configurable
- reworked config page (including advanced settings for remote debugging)
- support for remote debugging
- new option in Open/Save config page: [ ] Add newline at end of file on save
- all fixes in the bug tracker
Like last summer I am mentoring a student working on Kate’s Vi mode this summer. This year’s student is Vegard Øye from Oslo, Norway. I’ll let him introduce himself:
My name is Vegard Øye. I am a computer science student at the University of Oslo, Norway. I also have a bachelor’s degree in electrical engineering from Sør-Trøndelag University College in Trondheim, where I programmed for integrated circuits. It was a lot of fun, so I decided to embark on a grade with an even larger emphasis on programming.
My goal is to make modal editing more widespread outside of Vim. There is a Zen-like benefit to using a tool that does just what you tell it to – slicing and dicing text with surgical precision. My focus is not on adding new features to Kate (although I have implemented a few), but on sharpening existing functionality. In particular, I want to improve the integration between Kate’s vi mode and its extension system, as well as sort out various bugs pertaining to the vi mode.
Vegard has already done some really great work, and his changes should be trickling in to Kate’s git repository the next weeks. You can follow his work at http://quickgit.kde.org/index.php?p=clones%2Fkate%2Fvegardoye%2Fvegard_gsoc_2012.git.