Difference between revisions of "Development:Third-Party Preference Panes"
Jump to navigation
Jump to search
(link to stuart's article about how not to write a camino haxie) |
(draft) |
||
| Line 1: | Line 1: | ||
| − | + | {{draft}} | |
==How do I build a prefPane for Camino?== | ==How do I build a prefPane for Camino?== | ||
Revision as of 20:08, 29 June 2007
DRAFT
This page is not complete.
Contents
How do I build a prefPane for Camino?
- When thinking about building a third-party add-on for Camino, please keep the principles laid out in this blog post in mind; they will save you and the Camino team a lot of grief in the future.
- In order to make your prefPane as visually consistent with the Camino UI experience as possible, we suggest using the guidelines laid out in Development:Editing_Nibs when designing the UI of your prefPane.
Error messages
Undefined Symbols
it compiles ok, but if it's in deployment mode I get an undefined symbol error
- Get info on your target (or project) and set "Other Linker Flags" to "-undefined dynamic_lookup" for all configurations
- You only need the appropriate header files (the header files for the classes you're using/subclassing) if you're using -undefined dynamic_lookup; you don't need to link against the Gecko code (often, this is just PrefPaneBase.h)
Camino doesn't like my prefPane; it says it has to have a 'MOZC' signature
- Get Info on your prefpane target
- Go to "Properties"
- Change the "Creator" field to "MOZC" (without quotes)
