On 04/28/2014 09:50 AM, Raymond Wooninck wrote:
On Monday 28 April 2014 09:21:45 Anton Aylward wrote:
The real problem is that the specific search engine is HARD CODED into various other applications and I have no choice about it.
Then I am afraid that you have to write your own desktop system to make sure that it only uses what you want it to.
Now you seem to be trying to make this into a personal issue rather than addressing technical merits and shortcoming and design preferences.
There are a lot more libraries, etc installed on each system that are required by the desktop environment of our choice. Maybe I want to remove Qt, because I don't need it. But Qt is HARD CODED in KDE without any choice. And there are a lot more of these HARD CODED dependencies.
As I said, you are being ridiculous. Its not an analogous situation as you well know. I do on to give some examples of how systemsettings makes it clear that some utilities KDE uses which are external programs are optional, we can chose, for example, to use Evolution or Thunderbird instead of Kmail. I try to bring to the attention of readers that these things are not HARD CODED into KDE. Neither are they UI infrastructure libraries like Qt.
But I can't chose what indexer to use.
Yes you can. Removing baloo-file and baloo-pim will remove the active indexing programs and baloo will stop to work. Nothing will be indexed, nor any activity will be done with baloo. Exactly the same way as that you can remove konqueror, but you can't remove libkonq.
No, its not analagous. Systemsettings lets me chose which file manager I want. If I want to use Thunar I can. Its not about what I have to delete in order to disable. And I can use so other external program. While I can fiddle with the rc file to disable baloo (as opposed to disabling it in systemsettings) I can, for example, write a nifty one in Perl and use the options in systemsetting to use that external program instead (or the one offered by Gnome whatever that is). I can't tell kmail to use the indexing available via Dovecot or some other external program. Its HARD CODED and its all or nothing. I can't tell dolphin/konqueror to use one indexer and kmail another, no matter how good the indexer in Dovecot is, not matter how well integrated that indexer is with the mail store and how much better suited it is that that very specific task than a general purpose file indexer. In fact its running on a remote machine, my mail hub, so the "desktop indexer" can't see the files... All this is just an example of how determining options at run time rather than compile time gives more flexibility.
Perhaps I think the one from Gnome is more to my linking. I'm stuck,
You are not stuck. As indicated you can completely disable baloo by removing 4 packages and baloo will no longer bother you. If you want to go further than this, then I guess you have to start building KDE by yourself from the source code so that you can omit whatever you do not want to have.
You are so missing the point. In fact you are missing very many points. There are dozens of editors I can select as my editor of choice using systemsettings. Similarly there are many other external program options I can select there since they are not hard coded into KDE. But when it comes to indexing you are telling me I can either use baloo or nothing. Superficially baloo is an external program (otherwise one couldn't remove it) but the reality is the interface to it is hard coded into KDE applications.
We are building here packages that are used by a lot of people with all different requirements. This would mean that we have additional library requirements that are pulled in during the build phase of KDE. This delivers a KDE environment with a big amount of functionality that can be utilised depending on additional packages that are being installed by the user.
Obviously not. Read the above. What I describe, what is previously in KDE to address editor, mailer, file manager and others is determined at run time according to the settings in systemsettings and make use of additional packages. This is not the case with the indexer. It is baloo or nothing.
Please understand the difference.
Well, I hope that you understand that there is a difference between HARD CODED and HARD CODED. As stated above KDE pulls in a lot of libraries to satisfy HARD CODED functionality. However this functionality is not activated until other programs are being installed that can utilise that functionality. And this is not different from Baloo.
Not so. The interface that invokes, for example, the web browser, can invoke any web browser: Konqueror, firefox, opera, Chrome ... The interface that invokes baloo invokes baloo, if it find it. It can't invoke anything else. Its not a configuration option. There is an analogy here with networking. We use symbolic names and DNS to map those names to whatever IP address is registered. We don't hard code IP addresses into programmes. What you've done is hard coded the address and what you are saying is that we can chose not to have the site present. This is not consistent with the way other parts of KDE work. -- The state can't give you free speech, and the state can't take it away. You're born with it, like your eyes, like your ears. Freedom is something you assume, then you wait for someone to try to take it away. The degree to which you resist is the degree to which you are free... --Utah Phillips -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org