Getting Drupal’s Access Control Module to Work Properly
After setting up some content types — some public, some internal. I installed the Access Control module, set up internal content not to be visible to anonymous users — but without any effect.
After some research, but without success, I realized the *Advanced* section at the bottom of the Access Control tab for each content type. And now the magic trick: Increase the weight and you are done. So I guess the build in access management was fighting the Access Control module, so it is up to you to make your favorite module stronger by giving it more weight. — I doubt this is intuitive. Additionally, it is for sure difficult to simply find the tiny little select box down there in a section, which is by default folded.
KDE vs. Gnome
Now, my decision is final: KDE rules (though I actually prefer the look of Gnome
).
Simple reason: Gnome does not support drag-and-drop in combination with alt+tab (see bug tracker), but there might be hope with the upcoming Gnome 3.
[Edit 2011-06-14: Indeed, drag-and-drop + alt-tab works since since Ubuntu 11.04 (did not try with 10.10). One major difference remains: Do you need a lot of configuration and customization options? And are you will to accept complex, maybe not that self-explaining menu structures for that? If yes, KDE is your choice, otherwise Gnome might make your life easier. See also this page for more details and screenshots.]
In more detail: using drag-and-drop together with alt+tab key combination allows to work very efficiently. For example, while ordering my photos, I want to work on one of them — as I do this regularly, Gimp is opened already, but in the background — so what I do using KDE or MS Windows is, I grab the picture, switch to Gimp by using alt+tab and immediately drop the picture without moving the mouse at all — I am quite confident that this is the fastest way of opening a picture for editing. Some people advice to set Gimp as default application to open JPEGs, but I am not always editing pictures, most of the times I just want to view them.
Using “Open With” on a JPEG file for sure is the common approach — but let’s compare it:
- Drag-and-drop & alt+tab
- Actions to be performed: mouse down + key down + key up + mouse up
- In total: four fast steps
- “Open With” solution (holding mouse down as improvement)
- Actions to be performed:mouse down + moving to “Open With” + wait for sub-menu to open + move to sub-menu + mouse up
- In total: two fast, three slow steps
How to Make Jquerymenu for Drupal Keep its State on Page Reload
While setting up the website for my new project “Glocal” www.glocal-project.eu), I came across the problem of finding a proper menu module. Something easy to use, stable and efficient in the same time for the complex intranet structure (therefore, sorry, but you will not be able to see my solution there unless you are a project member). Something with a high usability in the end. Activemenu is still quite buggy and DHTML Menue requires a double click to actually open a page — unbearable in a non-doulbe-click environment like the Internet — who is supposed to guess, that this menu requires a double click?? Leaving me with JQuerymenu.
First impression: perfect! Open and close branches by clicking (+) or (-) — view page by clicking menu item label. Even the few styling issues could be fixed easily by using CSS. But as soon, as someone clicks a label, the menu collapses to its default status. It does not remember its last status after loading a different page with the same menu.
Is this it? All module have critical downsides like this? I was quite disappointed!
But I taught JQuerymenu to remember!
As it is quite some code, I will not post it here directly, but added it to the tracker page for this “feature request” or you can download the two updated files (jquerymenu.js and jquerymenu.module) here and replace the once in your /sites/all/modules/jquerymenu folder.
But please be careful, it should be considered an alpha version, there are quite some weaknesses (see tracker page). Any feedback or suggestions are very welcome!
good & bad usablity
the tap example
Everyone interested in HCI and Usability saw the cover picture of The Design of Everyday Things by Donald Norman. But there are examples about good and bad usability all around us, every day and I want to share one of mine.
I realized how much more comfortable the shower tap at my parents place is, compared to the one in my shared flat.

Don’t move! If you touch it and you are lucky, the water gets only turned off… otherwise you get frozen or boiled.

A good example of a water-tap for a shower.
The example to the left is a typical one — most probably following an assumption like “this tap is working for the washbowl, so it will do for a shower as well”. As it is mounted waist-high, it is easy to reach, also by mistake, which can be quite dangerous as it can easily be turned towards hot water by a slight touch. The re-engineered example on the right shows a functional and easy-to-use solution, in addition, the water temperature can be set up very precisely, but most important, there is no way to change the water temperature by accident as it is selected with a knob. Additionally, due to the knob, its almost impossible to reach the handle, which is used to set up the water amount, by accident.