Expand participant web functionality
Reported by Ben Hood | October 5th, 2010 @ 12:28 PM | in 0.8
The demo app needs a little bit more functionality:
The ability to generate historical data for a sessionChange the version content to be the body content and then MD5 the body (in the browser) to create the version- A link or box that does the same thing as the declare script
Comments and changes to this ticket
-
Ben Hood October 5th, 2010 @ 12:28 PM
- no changes were found...
-
Paul Jones October 6th, 2010 @ 09:03 AM
The Web UI now has a "Scenarios" section with a link that loads in a scenario with a bunch of data (which ranges from recent through to a day ago). This is severely breaking the rendering in the Agent for me, so it gives some good targets to fix...
-
Ben Hood October 6th, 2010 @ 01:29 PM
The Web UI now takes the body content as input and MD5's this to create the version. For note, the server side does this as well, just to keep things reasonably tidy. Were this not the case, the browser clients would have to be queryable, which they are not.
-
Ben Hood October 6th, 2010 @ 01:29 PM
- State changed from “new” to “open”
-
Ben Hood October 6th, 2010 @ 02:18 PM
- Assigned user set to “Ben Hood”
-
Ben Hood October 7th, 2010 @ 01:18 AM
- State changed from “open” to “closed”
I've implemented the last task by adding the declaration of the necessary endpoints, groups and pairs into the Spring config of the participant web app, so now there is no need to run the declare script by hand.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
Ben Hood
Jonathan Lister