update: I was able to get the classroom monitor to work with PasProjects.all the code is checked in and builds fine on continuum. when you click on step in the VLE it broadcasts that to the monitor. The monitor displays the status of the VLE. The parts i have not implemented are Resume/Pause and shouter. those are on hold for now.
The next steps would be for us to find a way to abstract this into SAIL. Turadg thanks for your implementation help. -Tony On [Aug 15], at 4:03 PM, Turadg wrote: > > On Aug 14, 3:12 pm, Anthony Perritano <[EMAIL PROTECTED]> wrote: >> i got the the fixmes fixed. now its time to test with the server. >> >> is this service setup on tels develop? >> what is the usage? > > Oh, I forgot to mention that part. You need to have ActiveMQ > running. To install it on your machine, just get the main > distribution, unzip it, and run bin/activemq. > http://activemq.apache.org/download.html > > It is already "installed" on tels-develop, meaning I unzipped it at "/ > usr/local/apache-activemq-5.1.0/". So if you want to run it on tels- > develop you can do so with `/usr/local/apache-activemq-5.1.0/bin/ > activemq`, but it'll die when you log out. We could set it up as a > daemon but I figure this is appropriate for now while the usage is > alpha. > >> i also tried your tests. the MapMessageSender. what is the procedure >> to use them? is there a start order? > > MapMessageSender is a utility, not a test. You can use it to send map > messages to a SAIL messaging topic. You type the topic in the > JTextField at the top (e.g. "agentNotification") and then the name/ > value pairs in the table (e.g. event=navigation, fromNode=/0/0, > toNode=/0/1, timeSpent=30000) > >> my current next step is to make it so the classroom monitor use >> otrunkcurnits. > > Cool. I spent a lot of time separating the messaging code from Pas. > So I hope it's straightforward but I can help if not. > >>> make a navigation abstraction that this and Pas speak >>> take Pas code out of this project >>> evaluate moving the project into SAIL codebase >> >> can you clarify. doesn't OrderedTreePath provide some abstraction for >> communication? > > It does, but the INavigationListener interface depends on Pas. (It > has one method, "newCurrentStep(PasStep currentStep)") That means > that synchronous-monitor can't go in SAIL. And the > NavigationPublisherService in synchonous-monitor can't go in PLR > because it depends on the messaging interfaces. > > I'd like to see a generic classroom monitor that worked for all SAIL > projects. That's why I came up with OrderedTreePath. But I didn't > have many other use cases to consider so I don't know if that really > does the job. > > So before that, we should separate just the JMS support facilities and > move that into sail-messaging or sail-jms. Then each thing can send > whatever messaging it wants. And we can keep synchronous-monitor as a > a Pas thing while we figure out what types of messages would be useful > across SAIL technologies. > > Maybe a good topic for the retreat. I see messaging as a good way to > do the glue we've been talking about lately. > > -t > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
