[wp-hackers] Modifying admin forms via plugins

Ryan Boren ryan at boren.nu
Wed Jun 23 04:09:25 UTC 2004


On Tue, 2004-06-22 at 22:00, Stephen O'Connor wrote:
> Two things about this thread bug me.
> 
> First, the additioanl hooks. So far most of these examples can be solved
> using the DOM. Yet people don't like the DOM... Um, tough? I personally
> would like the devs to work toward more meaningful goals than adding hooks
> to every three lines... How about an action/filter registry in WP? This
> would GREATLY help with backwards-compatibility.
>
> And the plugin extensiblility/configuration/gui thing? Didn't I already do
> that?
>
> Somebody even mentioned "framework" in this discussion, which is
> perfect cause guess what I called it!
> 
> http://stevarino.com/wp/framework/

Looks good.  However, there are several proposed frameworks out there. 
I whipped together one that simply uses the plugin header to allow
callbacks for install, uninstall, etc. to be specified.    Matt may
already have his one of his own going.  We need to evaluate what's out
there.

> Anyway it's .1 now, and it's probably going to mature to 1.0 in a day or two
> with some minor changes, cleanups, and improvements. If you don't take it
> seriously now, then you should check out my static-posts plugin that
> utilizes the framework (again, to be released in a day or two). I really
> like my framework and think it has some real potential. Check out these
> screenshots if you don't believe me (these are from my upcoming plugin)...
> 
> http://stevarino.com/wp/fakedfolders/img1.jpg
> http://stevarino.com/wp/fakedfolders/img2.jpg
> 
> (all of that is in one file too!) :)

Very nice.

Ryan

> The idea is super-user friendliness and maximizing modularity. I don't
> define 50 unique functions for this to work, just a normal plugin function
> and a new plugin class. Inside that class is where I store the UI, install,
> uninstall, and other methods to make it really easy for a user to figure out
> what's up.
> 
> I'm not declaring this as THE PLAN, but I've yet to hear a better idea. So
> far Jason is the only one to comment on it. :\
> 
> Have a good night!
> - Stephen
> 
> -----Original Message-----
> From: hackers-bounces at wordpress.org
> [mailto:hackers-bounces at wordpress.org]On Behalf Of Alex King
> Sent: Tuesday, June 22, 2004 7:28 PM
> To: hackers at wordpress.org
> Subject: Re: [wp-hackers] Modifying admin forms via plugins
> 
> 
> A little extra work by the plugin developers is better than a little
> extra configuration for end users.
> 
> Your plugin doesn't need an extra file for settings, you can store the
> configuration settings in the database and use the form to manipulate
> them. This is even more friendly for the users. :)
> 
> Maybe I should do a proof of concept when I get some time (if no one
> else has by then).
> 
> --Alex
> 
> http://www.alexking.org/
> 
> 
> On Jun 22, 2004, at 5:23 PM, Jason goldsmith wrote:
> 
> > it seems
> > silly to force plugin writers to do that or to have a big block of
> > code surrounded by an if statement to check if the plugin file is
> > being called via the plugins.php page or it is being called by another
> > page and therefore needs to execute.





More information about the hackers mailing list