I agree it would be better time spent developing for the LCDC program.
I would do it, IF he wasnt using Delphi.
If he was using just about any other language, I would be all over it.
---
Plus... I dont know his architecture.. but the MJ requires the plugin to be run inside itself. So my plugin for LCDC becomes very complex.
1. MJ plugin that interfaces with the MJ, and sends messages to the LCDC plugin.
2. LCDC plugin that gets messages from the MJ plugin.
So I would basically have 2x the amount of code to write unless I dont know what I am talking about
Writing a MJ plugin that directly interfaces with the display would be much easier.
----
Something like a nice XML messaging system would be great..
1. MJ plugin interface & send/recieve msgs
2. LCDC plugin interface & send/recieve msgs
1. Plugin that interfaces with MJ/winamp/etc.. sends XML msgs to display "server"
2. Display "server" recieves xml msgs and stuffs them into the display.
Off the top of my head, very easy to do using .NET.. all that xml stuff is native.. hehe. MJ doesnt support .NET's controls, have to use vb6.
---
either way, using LCDC becomes a very big project.. my background is %100 MS development.. am trained to scoff at anything nonMS
----
Eeks.. the winamp2 LCDC plugin is 500k, and there are 2 dll's. 1 for LCDC, and 1 for Winamp. So maybe my guess is right about some sort of msg'ing going back and forth between the 2 seperate applications.