Prit,
That was just a way of asking if a plugin could span over multiple functions, but I think the answer for that is yes, as I guess that in most cases plugins are a collection of functions by itself.
The point were I think plugins would be more difficult to implement is where I made "significant changes to the original function logic"
Let's say a mod requires different If statements, place a link instead of a static text, and an extra field in the db. How could a plugin override the original code without the function itself being "prepared" to work with that plugin ? or even worse to work with the variety of plugins people could develop ?
Correct me if I'm wrong, but hooks are basically if statements around code sections that you would like to be able to modify.
////////////////////////////////////////////////////////////////
I just had this crazy idea to simplify the plugin implementation:
////////////////////////////////////////////////////////////////
Pritlog is already very "modular" using several functions, even for closely related tasks (new entry form, new submit, edit form, edit submit, delete form, delete submit, etc)
What about using plugins to replace one or more complete functions with modified ones, instead of struggling with hook placements within a given function to anticipate what people might want to do !
In this case, placing a few hooks on the mainLogic() function could do the job.
(in addition, original functions could be groupped into separate include files for related tasks)
This solution seem to me more simple, more flexible, and much more powerful.
.. it makes life easier to plugin developers
.. and for me to keep with the latest release :)
What do you think ?
