Comments for Zwabel's Weblog

Comment on Portable Meta-Information by TagFS, tracking progress in the field of semantic file systems | Zen of Linux

Sun, 04 Oct 2009 12:38:42 +0000

[...] Thoughts on portable metadata (why a central tag repository/db is flawed), also here Portable Meta-Information continued and here [...]

Comment on Pushing Immature Technology onto the User by devsk

devsk — Sun, 06 Sep 2009 01:58:30 +0000

Can someone please help me get my invisible theme in gkrellm working again? Is there anyway I can tell KDE to allow gkrellm to show my desktop wallpaper in its background? I don’t have anything against compositing or clean architecture without hacks but I do need a nice system monitor with transparent look. With or without compositing. And no, ksysguard or its kde4 incarnation is not good enough. gkrellm has a place in top left corner of my desktop. If anything similar to gkrellm exists which does this without any fuss, I would like to know about that too.

Comment on Portable Meta-Information by On Hierarchical File Systems and Storage Location « Thorwil’s

On Hierarchical File Systems and Storage Location « Thorwil’s — Sun, 23 Aug 2009 09:46:53 +0000

[...] topic is old enough to be discussed in the FLOSS [...]

Comment on KDevelop4 UI: Areas, Working Sets, etc. by lost

lost — Sun, 09 Aug 2009 02:24:58 +0000

same problem as the other guy wanting to start learning on kdevelop and c++. I have spent 2 days trying figure out how compile and run hello world. other ide’s are intuitive and straight forward. I can find no where or way to write even my most simple source files to begin using kdevelop to build upon as a new programmer. using codeblocks now.. but I rather be using kdevelop.

Comment on KDevelop4 UI: Areas, Working Sets, etc. by Alex

Alex — Thu, 02 Jul 2009 12:33:01 +0000

Could you please describe what exactly these Areas do? Especially maybe post a screenshot of a Debug area?

Because if they are even remotely associated with Eclipse Perspectives, I smell disaster. Eclipse Perspectives completely change your working area, and are the worst thing anyone could do in an IDE. Give me a good code view area with an ability to debug on the spot – I’ll take it over Perspectives any time.
Actually, Perspectives are one of the reasons I hate Eclipse (the others are it being sloooow and having a worst possible UI on the planet. For example, the right-click menu is 700 pixels high and contains ~40 entries, half of them submenus, copy/paste being somewhere in the middle, with even “Preferences” being there, wth?).

P.S. It seems I’m not the only one who thinks like this. Here’s a (slightly ranting) writeup from a long-time programmer: http://www.informit.com/blogs/blog.aspx?uk=Thinking-About-Upgreading-to-Firefox-30-Think-Again

Comment on KDevelop4 UI: Areas, Working Sets, etc. by Staffan Palmroos

Staffan Palmroos — Tue, 30 Jun 2009 21:25:16 +0000

KDevelop4 is such a step up from KDevelop3, it’s amazing to see all the new features. I just hope the project management bits gets worked out soon, so I can start using it for real.

I really like the working set idea. I have a little problem with the tooltip dialog though.

I think that the “hover to get a dialog” mechanism breaks the GUI consistency with the rest of KDE. Hovering over a component usually only gives a small informative text, which goes away when the mouse leaves the GUI component. Redefining how tooltips works is a bad idea, consistency-wise. The relatively complex code view tooltips when hovering over the syntax elements are a stretch, but I think they are ok given that they are _mostly_ informative.

I’m not sure you actually need to ‘manage’ the working sets very much. When a file is opened its view is automatically added to the current working set. When the view is closed it is removed from the current ws. All you really need are buttons to add and remove working sets.

The working set icon besides the document tab bar could be a drop-down button instead, similar to the forward and back buttons in konqueror, i.e. when you hold it down for a second a small menu appears that allows you to create a new working set or delete the current. There is no need to show what files are part of the working set, you see that in the document tab bar anyway. I don’t think the “Add all” and “Subtract all” are needed either, just open or close the files you want in a ws.

Comment on C++ IDE Evolution: From Syntax Highlighting to Semantic Highlighting by vasaka

vasaka — Tue, 30 Jun 2009 08:34:40 +0000

Hello, I want to make style coding style checker for C++ and your highlighter seems to be a good base for it.

can you briefly tell me what parts of your project are needed to create a standalone tool for code checking?

Comment on KDevelop4 UI: Areas, Working Sets, etc. by manudwarf

manudwarf — Mon, 29 Jun 2009 09:03:49 +0000

Great !!!

I hope it will integrated in the major distribution including KDE4.3, it seems to become really amesome !

Comment on KDevelop4 UI: Areas, Working Sets, etc. by zwabel

zwabel — Sun, 28 Jun 2009 21:06:28 +0000

@Kombat: Either find some tutorial how to create a hello-word Makefile or cmake project. cmake is not complicated, a hello-world project would just look something like “TARGET(helloworld, main.cpp)” and not much more. Actually KDevelop has a “No GUI (Cmake)” template, that probably is exactly what you want, a hello-world command line application.

@JabberWokky: The working sets are automatically defined by the files you have open. Every set of open files automatically is a working set.

Comment on KDevelop4 UI: Areas, Working Sets, etc. by Evan 'JabberWokky' Edwards

Evan 'JabberWokky' Edwards — Sun, 28 Jun 2009 19:46:11 +0000

Very nice. Are the Working Sets fixed categories? I tend to edit in sets more like lib, cli, gui for some of my applications, and yet other categories for other applications. It’s not clear if I can define my own sets with this new interface. Heck, I’d toss in a scratch documentation and website set as well so as I’m working I can note certain changes.

Well done, either way!