[geeklog-devel] [Fwd: Re: Redesign the Plugin "Editor"]

[Joe Mucchiello]

"Rouslan Placella" <rouslan at placella.com> wrote:
>Couldn't that information go into a "info" tooltip? Or if it needs to be
>changed, it could go directly into the list of plugins.

Do you really think "This plugin requires the social networing plugin active in 
order to work" is the kind of information that belongs in a tooltip? Last summer 
everyone was all up about making plugins that were built off the socnet plugin 
(where ever that is). Well, knowing that if you deactivate the socnet plugin it 
will affect other plugins doesn't sound like something that goes in a tooltip. 
Adding this information to the main plugin list doesn't sound good either. 


What is the motivation to remove the editor screen? Are you going to remove the 
topic editor too? It's kind of sparse. I just think it would confusing to have 
some admin screens that lead to editors and some that are edited in place.

>The oldest entry in the bugtracker that I can see is from 2008...
There was a big crash in 2008. They are older.

>> Geeklog needs that much more than it needs pretty admin screens.
>Why?
Because only admins see pretty admin screens. Making pretty admin screens 
benefits one or two people per geeklog installation and usually only during 
their first few weeks of installation: how often to admins go to the plugin 
screen really? User facing screens getting beautified helps every user at every 
geeklog installation.

The plugin load order fix is as simple as adding a pi_order field to the plugin 
table. Stealing the up/down arrow interface from the blocks admin screen and 
changing the spot where the plugins are initially loaded so that it uses the new 
order field when it loads the plugin list. The request is at least as old as 
Geeklog 1.3.x. And the old bug tracker had a patch lost in the above crash. If 
you can get it into core, more power to you.

  Joe



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20110115/a2d628bd/attachment.html>