The hooking strata need's too be exploited further; this is similar to an event handler, exactly that what it is -- it is made with a cursor style entry.

Example in this call this is how you would change it in class/model/read.php.


Example in this call this is how you would change it in class/model/read.php.


The line that changed in this example between the two functions is, the part that has been added to include the child objects table name so it session more lower layer:-



The function triggerFunction will need to be created as well I am sure they might be some other type of preloaded apart from event... maybe you could make something as a handler class that set class sessioning.

Replacement for the Events handler to included a function/method handler as well for the events hooking stratums as well as by design to include preloads in theme as well the following class preloads.php need to be changed to so:~

class/preloads.php


This lists' the changes to the XoopsPreload that need to be made!!

Interesting. I have a couple of observations.

Dude, use the current source on GitHub :) The sourceforge code is moldy -- lots of changes since then.

If you put this hook in to Model\Read you would never be able to trust the expected return from anything. Any installed module would be able to interfere with any handler no matter if it was the active module or not. Sounds like a free for all that could get unstable very easily, and that is not good.

Doing this to an individual handler (extending and method override) is trivial.

Combine that with the existing Events class (what XoopsPreload grew into,) and you can accomplish this with less collateral risk.

One of the improvements is the addition of Events::addListener(). You can dynamically listen for any event and have it invoke any callable. This way, you don't have to set up the listeners unless it is needed.

There is no triggerFunction(), but since there is always the chance of more than one listener, you could never really rely on which return value you would get. You would have to include a strategy to combine or choose from possibly multiple returns.

The existing triggerEvent() takes one argument, but that can be anything. Historically, that has often been an array, but using an object as the argument is often a better choice. For example, the psr4loader event brings the Psr4ClassLoader object with it, so the preload listeners can just register what they need -- the return is done through the passed object. Even a humble ArrayObject or SplQueue can be quite useful here.

Using a custom object for a complex result mechanism would allow you to more cleanly document what is actually occurring, making it easier to use and reuse the solution.

Put these pieces together, you can build something that doesn't open up so many potential issues.

Quote:

I have a problem with using GitHub, for starters as the Module Team Leader I do not have access, also we are supported and one of the few projects that Sourceforge.net feature, for one reason, there total interface is made from XOOPS 1.

Also GitHub is sourceforge competitor, as well as git being available on Sourceforge.net which are a strong sponsor of us and we should be using Git on Sourceforge, can you give me access to the GitHub so I can start working on the modules for 2.6? I will set up a username now which is - LabsDotCoop

Just a thought I really think we should be using the git on source-forge, otherwise I am happy to migrate the modules to each unique GitHubs for Each one if necessary.

Quote:

Actually that is not the case, the purpose of reporting the for example 'table' name reported by the persistence is part of the reason, part the reason for the method one is to do the following for example in the XoopsModelRead::GetAll() from /class/model/read.php function, so if needed it can be event hooked by a preloader in those unique scenarios, I found like in multisite (Which I really think you should implement in the code as it is a great hack I found that can be done to allow for multiple session on domain and sub-domain’s please look at it, there where alot of demand in the forum previous to implement my multisite hack in the system and the core back when I was both in module teams and the core development of XOOPS 2.4)

Just looking at the example given for XoopsPreloader::triggerMethod() it really needs to look like so:-


Just looking at the example given for XoopsModelRead::GetAll() + XoopsModelRead::GetObjects() it really needs to look like so:-


The reason I need these changes made is the event hook stratum was my concept that I got trabis to implement who only did a small property of the total events on the core that needed to be hooked!

The purpose of an event hook is so all facilities of the core is reachable by the module development so any feature, query, question or otherwise can be some how determined and altered should it be needed!!

The purpose if you understand is fluid dynamics of the code, this means, to do some features in the core it become static and doesn't need to be later altered by module developers having to distribute the core files to replace, this triggerMethod() needs to go through all the functions as well as there needs to be functioning on function __destruct() as well as function __construct() with all the core classes the following preloader running:-



Cause these are components of events that all classes have that are missing!!

One thing you will notice is if you look at XoopsPreloader::setPreloads() is the ataption of preloaders for themes, this is a functional requirement as it need's to be in all facite of the events system as an eventing hooker (Which is how microsoft stuff works actually with Event Hooks for CPU MIPS)



I will continue my response in the next thread this is getting length.. but thanks for your reply so far geekwrite!!

Btw, geek write you want an invisible spot to mail from can you and the other team member send me 2 postcards to create a divine handshake - upto 5 days apart with a return either email or snail mail address for an @extraterrestrialmail.com - 500Mb Imap/pop3 mail box my snail mail address for one postcard with your always assumed password with Labs.coop as well as your return mail address and email address to:

Quote:

Make sure they are identical SO I know they are yours the post card, I have upto 50 Email address, I will be paying for a year supply, if you also want a forwarder on it specify it in the second postcard, and the email address you want the forwarder, separate from the first postcard with your email, return mail so i can send you the server setting in the snail mail and.. at least in some kind of order, just make sure the postcard for the postcardware email box is identical so they match up, mine is leshy@extraterrestrialmail.com

I don't sure about Preloaders introduced by trabis and wishcraft. It's a kind of Hook events?
Instead why don't use EventDispatcher or implement an Observer pattern.

Observer Pattern
https://github.com/domnikl/DesignPatternsPHP/tree/master/Behavioral/Observer

Mediator
https://github.com/domnikl/DesignPatternsPHP/tree/master/Behavioral/Mediator

Julio, did you read Richard's post, and looked into the Events class, incl. the Events::addListener() ?