[geeklog-devel] Configuration tooltips
websitemaster at cogeco.net
Tue Apr 5 15:03:18 EDT 2011
I am hoping that is what is meant when the file type "config" is passed.
Dirk I think you added the function what is your take on this?
I guess I could create a new type "config_180" or something and then
differentiate between the 2 and disable the tooltips for config documents if
a config_180 document type doesn't exist. Plugins that don't handle
different document types and just passed one document for any request I
would then consider it to be the plugins problem since they are not using
the function correctly.
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rouslan
Sent: April-05-11 2:18 PM
To: Geeklog Development
Subject: Re: [geeklog-devel] Configuration tooltips
I'd say plugins should explicitly specify if their documentation is suitable
for being loaded in the tooltips or not (and the option should be disabled
Just a thought.
On Tue, 2011-04-05 at 14:00 -0400, Tom wrote:
> Geeklogs New Configuration UI now includes tooltips for each config
> option as long as a file gets returned from the function
> Since the tooltips are automatically plucked from the actual document
> page they need to follow a format close to how Geeklog and the core
> plugins config docs are written. Can we assume this as long as the
> document type being passed is "config"?
> I notice some plugins just pass a wiki page or something and don't
> even differentiate between document types.
> I would like to add to the wiki page something that tells developers
> that for the config tooltips to work 100% of the time the page will
> have to be formatted similarly to Geeklog config docs and an
> appropriate anchor will have to exist for each config option.
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
More information about the geeklog-devel