Open GoogleCodeExporter opened 9 years ago
Good idea. To plan this well, it would be helpful to first think about what the
functionality of such plugins could be. I guess we'd need to define several
types of plugins, or a plugin could perform several types of actions. So we
need to think about what these types of actions could be.
Original comment by crazy4ch...@gmail.com
on 3 Nov 2012 at 3:28
Hey crazy :)
I really like the way how wordpress implements the plugins. I didn’t know how
they do that but i succeed to make my own way for havalite CMS
http://www.havalite.com .
-- To plan this well, it would be helpful to first think about what the
functionality of such plugins could be --
There are plenty of needed functions, i mention some of them here:
[The_begin]
• Import from MySql
• ****** Oracle
• ****** XML, html
• etc…
• Export to ***** etc..
• Search / Replace (with RegEx support, ignore white space, html tags ... )
• Save own SQL statements (maybe as templates for further changes)
• Configurations or options
• Any mathematical or scientifical functions
• Create public site/gallery.. from table
[The_head]
• Any JS, jQuery, CSS …
[The_content]
• Reduce columns (view only title, text columns)
• Edit in place (ajax)
• View Blob as image or swf etc.
• View as html
• **** as Charts, colored code editor etc.
[The_sidebar]
• Quick Navigation
• A list <select> with names of all saved statments
• Favorite links
[The_footer]
• Any results need to be shown
• Additional buttons
I noticed by Havalite that i mostly use the first 4 braches
begin/head/content/sidebar when developing plugins. The most difficult part is
the content, but if the code is well organized than it’s no problem.
Original comment by teryaki1...@googlemail.com
on 3 Nov 2012 at 8:45
I also like how Wordpress built their plugin system. They use hooks. We just
need to find all the places physically as well as functionally where people
would want to "extend" behavior. The list above is good. I'm going to work on a
new Plugin class. It will allow us to strategically place our hooks throughout
the code.
Original comment by daneirac...@gmail.com
on 7 May 2014 at 11:10
I have some code ready for this, see Issue 214.
Original comment by dreadnaut
on 11 May 2014 at 4:16
Original issue reported on code.google.com by
teryaki1...@googlemail.com
on 3 Nov 2012 at 7:39