KDE Blogs 

ok... so as the recent thread on kde-core-devel re: kcfg showed, people FEAR usability efforts. that's right, people FEAR it. that word was actually used in relation to the topic. they are afraid some people will screw it up, that KDE can't cope with a drive towards being more usable without becoming pure shit. i really feel like ranting about thickheads, but that would just be adrenaline speaking. as much as that would feel good ;-) , i'm going to try to be constructive instead: what can be done to gain the trust of people in KDE? or is that a pipedream? Read More

ah... finally in my new house and it's feeling good... now to start putting the wraps on various bits of code i have laying around ... committed small things to kjots and kcm_kicker the last two days, and have bigger chunks of kscd, kicker, TOM and systray patches awaiting my attentions. i also have that bookmark code lypie's been patiently waiting for me to commit. =) Read More

ok.. so, i'm sick of waiting several seconds for kwrite to pop up whenever i do a View Source in konqueror. yes, one might be correct in saying kwrite should open faster. but i've got a different idea: why not have a simple viewer window that runs IN the konqi process ala Mozilla? i've had this on my slower box at home for some time now and BOY does it make a nice difference speed-wise. i need to add some basic viewer functionality to it like Search and Print. perhaps just a nice little toolbar with a couple of buttons on it (and an incremental search line? hrm...) anyways... i'm pondering whether it's worth polishing up and attempting to convince the Konqi maintainers that this is a better approach than launching an external editor. here's my benefit/cost summary: Read More

Being on holidays certainly gives you time to reflect on what new features you'd like in your text editor :) I've come up with something which I hope will help make using a text editor a better experience by providing more assistance to the user... input filtering. It came to me when I was thinking of cleaner ways to do code templates. At the moment, I think you have to use a keyboard shortcut to insert code templates? Anyway, this will make it easier for the 3rd party app developer to e.g. respond to "for " and insert a template. It will also make immutable text a possibility, something requested in a comment to my last blog. In fact it will make it possible to enforce valid structure on a document, though I personally think that would be too restrictive. Immutable text could be appropriately highlighted, and the cursor could move around it in a logical manner, so that the for ( ; ; ) { } template could be navigated more easily. Other ideas on the go are improved text navigation eg. easier use of code folding (previews of folded code? auto-expand modes?) and the ability to add a custom widget to the top and/or bottom right-hand corners. I've also decided to improve the idea I had for syntax highlighting by giving each text range a "state" variable, and associate a specific highlighting style to a state, then the developer just has to change the state of a range to make it look different. I'm also taking requests for whatever text decorations you'd like to see available in the next kate - I'm thinking of borrowing some ideas from css, just let me know which ones you think would be useful. Furthermore, I'm planning to extend on code completion by adding syntax highlighting to the dropdown, expanding the info presented, allowing several different filtering and sorting rules (eg. by inheritance; by access (public/protected etc); alphanumerical; and hiding / disabling completions which don't fit the current context), and integrating (somehow - ideas?) summary documentation for the highlighted method. My flight calls, gotta go... someone should sponsor KDE developers going on long-haul international flights so they can hack from business class! Economy is way too cramped... Read More

My ISP confirmed last night that my ADSL should be working from tomorrow, so I'll be getting back to work on XPath and KJSEmbed. Hurray!

I've committed Qt bindings for libusb - see http://sourceforge.net/projects/libusb/ This includes API docs and unit tests. This isn't released yet, so you'll need to suck down the CVS version. I'm a bit worried that the bindings aren't really Qt-ish enough, because I'm not very experienced with class design. So I'm taking advice (and patches!). You'll need to provide fairly specific advice though - at least the interface needs to be specific. Read More

I've been working on something pretty big for katepart for a while now, but it's just struck home how widely applicable this new idea will be for apps utilising the KTextEditor api. The whole thing started when I was looking for a way to enable custom programmatic syntax highlighting. I first implemented a smart cursor which retained its relative location while the text around it was edited; then extended this into a pair of smart cursors to define a "range" of text. These objects give forth plenty of useful, convenient signals, such as changed(), moved(), etc. This looked like a promising way of implementing custom HL. Yesterday, it struck me how these smart cursors could replace most of the clumsy mechanisms used today to interface with text editors. As it stands, most 3rd party apps like KDevelop, Quanta etc. all maintain an externally parsed version of the document's buffer. This is not only inefficient, but the hooks to enable on-the-fly parsing (rather than delayed / background parsing) are not there, so there is always some lag time with the parsed versions. Here's how I envisage this new interface would work: Read More

The following post is mostly a response to Aaron's comments in his latest blog entry. It's basically about the reason why I like KDE and why I do the contributions I do, so it might be an interesting albeit highly theoretical read. Read More

I just moved house (like aseigo) and I second his thought on how much it sucks. My ISP was due to reconnect me to my ADSL today, but this morning I got a call saying it could be another week. Arghhhhhh! Read More

"One little feature that would make Kexi a next step to be a killerapp", said Lucijan to me today. Yes, I hope so. What do you think about following feature that works database-transparently?: [image:358,middle] Read More