Plug-In: Event Logger -Tool to make Plug-ins

[loadman]

Here is a quick Plug-in I made for JukeBox software complying to the JPS standard

It is more of a quick and dirty plug-in development tool really.

Just put the unzipped file in your plug-ins folder and configure via your Jukebox Plug-in configure section

The plugin can be download from this link:
http://www.jukeplugsys.com/?page_id=8

[Space Fractal]

I fixed the link, which got screewy. When uploading a file, remember to write a title before doing it to make a nice like. When updating, you need to delete the file under browsing and reupload the new file again.

If you want a FTP account for easier upload of files (or PM me), so you only need to update the version number, let me know.

[unclet]

I looked at this very quickly before leaving for work this morning.   

If I have this correct then this plugin is just used to display messages sent to the plugin ... right?

I would suggest adding an option to turn on ALL messages except "GET" messages.   Seems like you have other variations but I would assume this one would be more important.   

Now ... are you working on other jukebox plugins as well?   

[Space Fractal]

otherwice I have planning to create a webstats like something that one Freebox have.... There are few bugs in MultiJuke in Linux version I need to look on, and have thetouchscreen support more important than writing a plugin (even I like spinoff projects like this).

Mightbe this could been a idea to Loadman?

[loadman]

I fixed the link, which got screewy.

Thanks 

 
If I have this correct then this plugin is just used to display messages sent to the plugin ... right?

Yes    And Log to a file. Can be very handy when you have this running at the same time your are testing a real plug-in. If something does not go as expected you can check the log to see what message was sent from the jukebox at a certain time. As the same commands are sent to all enabled plug-ins at the same time (as you know)

I would suggest adding an option to turn on ALL messages except "GET" messages.   Seems like you have other variations but I would assume this one would be more important.   

That is what the default option is.  Possibly my wording could have been more clear?   

Now ... are you working on other jukebox plugins as well?   

Yes, When I suggested plug-in support I did not expect you guys to impliment it so quickly. I was really just putting the idea in the suggestion box as writing a plug-in or two for my Jukebox was on my timeline. Sorry . Is there any plug-in you are eager for soon ? 

[unclet]

I would expect a plugin to do no less than retrieve all songs I do not have in my library, categorize them, get the associated lyrics (of course check for spelling and all gramatical errors) and obtain all the required artwork images as well.  If it does not do all of this then I am not sure if anyone would use it but I could be wrong   

[loadman]

I would expect a plugin to do no less than retrieve all songs I do not have in my library, categorize them, get the associated lyrics (of course check for spelling and all gramatical errors) and obtain all the required artwork images as well.  If it does not do all of this then I am not sure if anyone would use it but I could be wrong   

...Sure. But deleting some Country music artists might be a priority for me 

[unclet]

Gotta leave the Reba for the wife     

[Space Fractal]

I would expect a plugin to do no less than retrieve all songs I do not have in my library, categorize them, get the associated lyrics (of course check for spelling and all gramatical errors) and obtain all the required artwork images as well.  If it does not do all of this then I am not sure if anyone would use it but I could be wrong   

If I known you just kidding, this is not possible, since there is no file sent to the plugin. We could add a another agument to the song tags, so it also got the file used  too? This would not break the combatible if we just add this as last argument.

[unclet]

I was kidding ..... lets see how many people actually use the JPS before expanding it right now....... 

[Space Fractal]

of course I know it. I guess you hare completly right here (why did I write, If I known you just kidding?), let hold here and wait expandend it after a while if needed.

[loadman]

Minor Bug Fixes:

0.07

- Version displayed correctly
- Current directory fixed for re-loading last log on disk. This was failing to reload as it could not find the file with some apps.

[AussieJuke]

Just checked it out now. I have a question though.
Shouldn't the log be created in the same directory as the plugin that created it?
This is how I resolve the paths in mine:

Code: [Select]

// This gets called when the dll first loads
procedure InitializeDll;
var
  Buf: array[0..MAX_PATH] of char;
  DllPath: string;
begin
  // Get the host's full path and name
  GetModuleFileName(0, Buf, SizeOf(Buf));
  // Extract just the filename from it
  HostName := ExtractFileName(Buf);
  // Get this dll's full path and name
  GetModuleFileName(hInstance, Buf, SizeOf(Buf));
  // Extract just the path from it
  DllPath := ExtractFilePath(Buf);
  // Add the trailing backslash & fully qualify the event log filename
  EventLogFileName := IncludeTrailingPathDelimiter(DllPath)+'JPS_Event_Logger.log';
end;


[loadman]

Just checked it out now. I have a question though.
Shouldn't the log be created in the same directory as the plugin that created it?

I could...

Thanks but I was decided to keep it in the same dir as the app that uses the plugin 

Just me I suppose 

[AussieJuke]

Yeah, I couldn't make my mind up on where to write the log file at first.
I can see pros and cons for both locations. No real hassle either way.