Main
From
HandlingCairoDakarPluginDifferences and
PluginsConformanceReport
>
Can we collate a table of CommonlyAbusedCairoEntryPoints? so to aid people adjusting plugins. I'm thinking:
Cairo non-published method |
conformance popularity |
Purpose |
Dakar equivalent |
TWiki::Prefs::getPreferencesValue |
10 |
Get preference values. Usually specifically for this plugin |
TWiki::Func::getPluginPreferencesValue (most common), TWiki::Func::getPreferencesValue (less common). With older plugins the author may have parsed the topic themselves, leading to irregular behaviour |
TWiki::securityFilter |
9 |
|
|
TWiki::wikiName |
7 |
|
|
TWiki::webName |
7 |
|
|
TWiki::getEmailOfUser |
7 |
|
|
TWiki::cmdQuote |
6 |
|
|
TWiki::pubUrlPath |
6 |
|
|
TWiki::sharedSandbox |
6 |
|
|
TWiki::sharedSandbox |
6 |
|
|
TWiki::handleIncludeFile |
5 |
|
|
TWiki::normalizeFileName |
5 |
|
|
TWiki::Form |
5 |
|
|
TWiki::userToWikiName |
5 |
|
|
TWiki::normalizeFileName |
5 |
|
|
TWiki::RELEASE |
5 |
|
|
This comes from 27 Jan 2006 conformance report. We should:
- Understand why people needed to use that non-published function
- Recommend the alternative for Dakar
Of course, instead of tabulating it here, bridging contribs could be written.
The purpose would be to help people move to Dakar whilst retaining the functionality that locks them on Cairo.
--
Contributors: MartinCleaver
Discussion