|
|
Post by bulldogg on Mar 17, 2009 16:53:04 GMT
I was thinking, currently with the plugin interface you (Eagle) are making it simpler to use with the classes youve made in your plugin dll's, i was wondering if it would be possible to add another part to the plugin interface where all FL Server hooks can be accessed like the flhook plugin interface does, it basically lets you use all the hooks instead of the currently avaliable ones that look nicer.
This would open up the plugin avaliablity for FLAC, although it would be upto the plugin coder to make the code look nice for the plugin.
what do you think? is this possible?
BD
|
|
|
|
Post by Eagle on Mar 17, 2009 19:34:34 GMT
No thats not possible as the plug ins are not flserver plug ins, they're FLAC plug ins which is a distinct difference. I recall a similar request a while back to which I suggested that its best to just post the desired end functionality so thought can be given to what sort of events/notifications are required to realize this.
Even though events like character load are available, which are basically notifications of the flserver characterselect method, the actual notification at the FLAC end is the result of a socket transmission of this fact and flserver is infact allready way past handling that particular "hook". There's no way to influence the outcome in any way, just the ability to observe this has taken place. Same goes for the other way around, you're able to send messages to flserver through the FLAC plug in interface, but even that isn't instantaneous. That too is cached and then send accross a socket pipe, only to be interpreted and processed at the flserver end.
A plug in is not the same as a hook, I know that FLHook offers this kind of plug ins but those aren't plug ins in the traditional sence as each piece of code inserted affects the whole. FLAC however is more oriented to top level development where you have far more power at your disposal, and no low level access at all. This ensures that both FLAC and the server can't be put in an unstable state through any plug in code, it also takes away the burden of having to know any specifics of what the server does or does not do at the lowest level, there's an abstraction layer (the plug in interface) with which to do what you must. No way to fire any invalid data into the server that way either as the plug ins are not only strong typed, it has been made impossible to fire any invalid events into the server without you ever having to give that a second thought.
Alot of the flserver events are redundant to the top level developer anyway, which could only lead to confusion and more importantly, misuse of such "hooks". FLAC extracts relevant information from those events for you and presents that in a neat abstraction layer. Adding all "hooks" to this layer would defy its purpose and clog up important communication pipes between FLAC and flserver. This is why thought has to be put into what is neccessary, and what its common use will be. For the readilly available events and notifications this is self explanatory, for future expansions thought has to be put into specific application before chucking in a random new feat.
My suggestion therefor is still the same, post what you wish to create and what's missing that stops you from implementing it with the current interface.
|
|
|
|
Post by bulldogg on Mar 18, 2009 18:29:11 GMT
ok fair enough
also, is it possible to add keyboard shortcuts to commands like the ship docking F3 ect in effects.dll?
BD
|
|
|
|
Post by Eagle on Mar 19, 2009 7:09:07 GMT
I believe such a request has allready been posted in the FLAC forum.
|
|
