Reply to thread

Message

<blockquote data-quote="samuel337" data-source="post: 128457" data-attributes="member: 10347">Hi AdmiralUD and everyone else,I know progress on the new web interface has been extremely slow, but I've just started work on updating the ECP2 plugin for the new client/server configuration. This forms the base of the web-interface, e.g. send MP commands, add recordings, get connected clients, play songs etc. I've refrained from saying anything because I don't like raising expectations and then having everyone disappointed when they don't come, so I rather talk when I have something to show.AdmiralUD - its good that someone else is coming to the table with the skills needed for this. Your plans are basically what I've had in mind, so we're not too far off track.I do have issues with this point:I believe there should be a layer, and that layer should be the native MP methods. Why? Because then we don't have to worry about any changes that are made to the database structure, and also the way that MP operates. For example, if you add a recording directly to the database, I don't believe that MP will know about that, hence it should be added via MP (yes, this can be worked around using notifications, but its just an example). It means less work overall because we're not creating our own database code and updating it everytime it changes in MP.About the svn-repo, I can add you into the mp-webinterface sourceforge project if you like.Sam</blockquote>

[QUOTE="samuel337, post: 128457, member: 10347"] Hi AdmiralUD and everyone else, I know progress on the new web interface has been extremely slow, but I've just started work on updating the ECP2 plugin for the new client/server configuration. This forms the base of the web-interface, e.g. send MP commands, add recordings, get connected clients, play songs etc. I've refrained from saying anything because I don't like raising expectations and then having everyone disappointed when they don't come, so I rather talk when I have something to show. AdmiralUD - its good that someone else is coming to the table with the skills needed for this. Your plans are basically what I've had in mind, so we're not too far off track. I do have issues with this point: I believe there should be a layer, and that layer should be the native MP methods. Why? Because then we don't have to worry about any changes that are made to the database structure, and also the way that MP operates. For example, if you add a recording directly to the database, I don't believe that MP will know about that, hence it should be added via MP (yes, this can be worked around using notifications, but its just an example). It means less work overall because we're not creating our own database code and updating it everytime it changes in MP. About the svn-repo, I can add you into the mp-webinterface sourceforge project if you like. Sam [/QUOTE]

Verification