What you have missed, Alain, is that Habarixenu must be installed into the profile's chrome directory, NOT into K-Meleon's chrome directory (like Aggeg8).
What you could try: Install Habarixenu into Firefox or Mozilla and whatch what is written into your profile's chrome\chrome.rdf. Then take over these changes to your K-Meleon profile and hope the best...
Have you tried my way to have automaticly individual rssfeeds.rdf ?
LOL. Your are joking! The aggreg8 version you are using is always storing your subscribed feeds in K-Meleon's chrome directory (chrome\aggreg8\content\rssfeeds.rdf). You cannot change this behaviour by just copying rssfeeds.rdf to your profile directory. Make the trial! Open aggreg8, create a new feed or category, close aggreg8 and now look in which of your rssfeeds.rdf the new feed or category is stored.
I haven't found what to put in $xul ...
I guess you misunderstood me. Don't mind. It's easier to do than to explain it. I will have a look on it some time...
>LOL. Your are joking! The aggreg8 version you are using is always storing your >subscribed feeds in K-Meleon's chrome directory >(chrome\aggreg8\content\rssfeeds.rdf). You cannot change this behaviour by just >copying rssfeeds.rdf to your profile directory. Make the trial! Open aggreg8, create a >new feed or category, close aggreg8 and now look in which of your rssfeeds.rdf the >new feed or category is stored.
No, it's not a joke ...
Yes the version is always the all-profiles one. But In onStartup and OnQuit, I copy the rssfeeds.rdf in one sens and in the other, and it works fine ...
You must use utils kplugins (0.0.4) , that's all ..., and there's now no need to put the end in chrome.rdf ...
Ah. I apologize, Alain. I've overseen that. There was no documentation or explanation on that (or I have overseen it, too).
However, your way of doing things won't work in a multi-user setup. It will only work, as long as you (your windows account) have write permission to the K-Meleon program directory. It won't work when you are logged on as a non-privileged user. And of course, you will loose your changes, when K-Meleon crashes, although your changes were already saved to disk. My rdf-hack will work under these circumstances...
However, your way of doing things won't work in a multi-user setup. It will only work, as long as you (your windows account) have write permission to the K-Meleon program directory. It won't work when you are logged on as a non-privileged user. And of course, you will loose your changes, when K-Meleon crashes, although your changes were already saved to disk. My rdf-hack will work under these circumstances...
kko, I think you are jocking now.
If, as you said, a non-privileged user can't write to k-meleon folder (chrome and profile folder), he also can't use K-Meleon and uses probably IE.
My solution writes in k-meleon\chrome\aggreg8\content and in k-meleon\profiles\profilename\*.slt\
The only difference with your solution is you don't write in chrome...
- Only administrators (privileged users) have write permission for the K-Meleon directory.
- User profiles are stored in user's %AppData% directory.
--> Non-privileged users can't write to K-Meleon directory (and thus to \chrome\aggreg8\content\rssfeeds.rdf) but of course all users can write to their profile directory.
1) there's no kmeleon build which works like that (and I agree it would be better)
2) in this case, aggreg8 no more works, because it naturally saves under chrome.
So, before we have this config (I don't think Dorian or Hao builds work like that), my solution works great, and, in the case the privileges users are limited, aggreg8 can't work without rdf modifications which are, in my thought, a little hard to do by basic users .