CamiSearch 1.0beta

[Michael_O]

When I click the search bar thing in Camino it still shows only the 3 default. It's very weird!

You did quit and relaunch, right?

Yes. I tried many different times and I quit and relaunched on all of them.. It just is not showing up for some reason, even if it's in the file. Maybe it is showing a cache version of the SearchURL plist file or something?

[eccoana]

It just is not showing up for some reason, even if it's in the file. Maybe it is showing a cache version of the SearchURL plist file or something?

Two things to try:
1) empty the cache
if that doesn't help:
2) try to rename the SearchURL plist file inside of Camino. it is stored in Contents/Resources/English.lproj

[Michael_O]

It just is not showing up for some reason, even if it's in the file. Maybe it is showing a cache version of the SearchURL plist file or something?

Two things to try:
1) empty the cache
if that doesn't help:
2) try to rename the SearchURL plist file inside of Camino. it is stored in Contents/Resources/English.lproj

Emptying the cache didn't work.

Renaming the Search URL plist inside of Contents/Resources/English.lproj didn't work either. Camino wouldn't show a window when that file was renamed. But I opened that file and saw that it only had the 3 default ones in there. Is that the problem?

I was wondering if I can replace it with the one that has all the custom search engine stuff in it and if it would work, or if I should just leave this file how it is.

Edit: i just tried doing that, and Camino didn't show a window when replacing or renaming that file.

[eccoana]

Edit: i just tried doing that, and Camino didn't show a window when replacing or renaming that file.

please check all search engine urls and replace every single '&' with '&'
for example:
old: http://www.google.de/search?hl=de&q=qqq
new: http://www.google.de/search?hl=de&q=qqq

that could be the reason why Camino didn't show the new edited file.

[Michael_O]

Edit: i just tried doing that, and Camino didn't show a window when replacing or renaming that file.

please check all search engine urls and replace every single '&' with '&'
for example:
old: http://www.google.de/search?hl=de&q=qqq
new: http://www.google.de/search?hl=de&q=qqq

that could be the reason why Camino didn't show the new edited file.

Thanks so much! That worked. I didn't see one of the '&' in one of the long URL's. But once I changed it to &, it worked fine!

A request, if this is possible would be for CEP to automatically convert & to & ?

[Uncle Asad]

Oooh, this bugfix will be nice for those of us using nightlies and ecco's tools:

https://bugzilla.mozilla.org/show_bug.cgi?id=184394

[eccoana]

Oooh, this bugfix will be nice for those of us using nightlies and ecco's tools

that's fine!
but to be honest: it only would be really useful if Camino could recognize by itself which extensions there are. currently CEP has to copy itself into the application folder of Camino *and* then edit a config file inside of Camino.app
using a nightly would still raise the problem that CEP isn't in the preferences window of Camino.

ciao
ecco

[smorgan]

it only would be really useful if Camino could recognize by itself which extensions there are. currently CEP has to copy itself into the application folder of Camino *and* then edit a config file inside of Camino.app

Right, and I'm pretty sure that's a big part of what the fix is; creating a location where Camino will dynamically load prefpanes from without them having to be in that config file.

If I understand it correctly, after the patch the whole CEP install process will consist of putting CEP in ~/Library/Application Support/Camino/PreferencePanes.

[Uncle Asad]

Right, and I'm pretty sure that's a big part of what the fix is; creating a location where Camino will dynamically load prefpanes from without them having to be in that config file.

That's certainly how I understood the bug (although I'm no guru); otherwise, it seems like there would be no point to the changes

[eccoana]

Right, and I'm pretty sure that's a big part of what the fix is; creating a location where Camino will dynamically load prefpanes from without them having to be in that config file.

That's certainly how I understood the bug (although I'm no guru); otherwise, it seems like there would be no point to the changes

Using 20050313 the additional preference panes are only displayed in the preference window if they are manually added to the file MVPreferencePaneDefaults.plist

fyi: having two different versions of the same pref pane in ~/Library/Application Support/Camino/PreferencePanes and inside Camino.app/Contents/PreferencePanes the first one will be used.

ciao
ecco

[petard]

Using 20050313 the additional preference panes are only displayed in the preference window if they are manually added to the file MVPreferencePaneDefaults.plist

This is incorrect. I just tested with both a CVS build and the 20050313 nigthly from ftp.m.o using a preference pane I built. It was loaded from /Library/Applicaton Support/Camino/PreferencePanes and ~/Library/Application Support/Camino/PreferencePanes with no problem. MVPreferencePaneDefaults.plist is only used to specify the order of the default preference panes on the toolbar now. Others are tacked on to the end.

Some time "real soon now" I'll post some sample code and a brief explanation of how to build a prefpane for Camino... If you want, though, point me to the source code for the one you're working on and I'll see if I can tell what's going on.

HTH,

petard

[eccoana]

This is incorrect.

this may be incorrect for you but it is correct for me.
I tested it with two preference panes and none of them appeared in the preference window unless I edited the plist file.
Or does Camino use its very own preference pane file format?

ciao
ecco

[japser]

One thing I found could cause the prefpane not to load is the fact that info.plist of the prefpane needs a CFBundleSignature string set to CHIM in order for camino to load it, don't ask me why but that did it for another pane.

Look in the console log to see any errors when loading a prefpane.

[petard]

Or does Camino use its very own preference pane file format?

Not really. It's just a bundle with a signature 'CHIM', a unique identifier (I'd recommend using something with your domain components in the form com.example.camino.productname), and a principal class derived from NSPreferencePane. So the format is exactly the same as a system preference pane with a signature indicating it's for Camino.

You can see exactly how we load preference panes here:
MVPreferencesController.mm

[eccoana]

It's just a bundle with a signature 'CHIM'

thank you both for the information. I think that's the reason because this signature doesn't seem to be necessary if you embed the prefpane within the plist file.

I will try it this evening.

EDIT: I changed the info.plist from

Code: Select all

<key>CFBundleSignature</key>
   <string>????</string>

to

Code: Select all

<key>CFBundleSignature</key>
   <string>CHIM</string>

and now the pref pane shows up in the preferences window.

Great!