The User Manual is now posted on the documentation page.
Recent Forum Posts
The initial configuration file needs to be saved as initial.cfg for our code to work correctly.
in discussion General Chat / All those Informalities....like saying hi » Goodbye!
Just saying goodbye… Pleasure working with all of you
-Seth
We have what we are presenting…. I uploaded a file called DiscoveryCenter_v1. This version works on our touch screen. We did not implement timeoutResponse.
There seems to be an error in the file TouchMap.java. The hotspot recognition does not seem to work correctly in circumstances. We believe it is a logical error on lines 88 and 90. We replaced the two if statements with the following code:
if(corner_x <= clicked_x && (corner_x + width) >= clicked_x && corner_y <= clicked_y && (corner_y + length) >= clicked_y)
this seems to fix the problem.
Also the resolution of the touch screen is 1024X768.
SJMSU is planning on presenting the app to some people from the Discovery Center next Wednesday afternoon. Just took a look at the GUI stuff that SJOC posted earlier this week, and it looks great!… We were just wondering if you guys had any type of users manual that we could present to the Discovery Center during our presentation next week? I think it'd be good if we could show them how to use the whole thing when we present it. I guess just let us know, so we can learn how to use the admin tool before then.
- Brandon
Does anyone know the native resolution of the touch screens? They're LCDs and therefore very resolution-sensitive. If you don't know, I have two of them in my office you can experiment with. The touch map JPG images should have same dimensions as the screen to completely fill it without distortion and for optimum viewing quality.
You are hereby banned from posting after 9pm. That is all.
Does anyone happen to know people that use their notebooks as desktops and only desktops?
Be prepared to make TouchMap compatible with Java 1.4, in case that's the version that SJ-MSU installs on the DC machines. The only problem I see is the List<String> and ArrayList<String>. Parameterized types were not introduced until 1.5 (5.0). Basically, just remove the <String>, and be prepared to typecast the return value of any "get()" calls — I only saw one. Should only take a couple minutes.
I've uploaded the jar file for TouchMap. This has both the source and class files for the interface. See: touchmap.jar under files off the main page.
Just to make sure we're all on the same page: the origin of the TouchMap coordinate system will be upper-left corner, right?
I'm thinking back to this 1999 news item: "NASA lost a $125 million Mars orbiter because a Lockheed Martin engineering team used English units of measurement while the agency's team used the metric system for a key spacecraft operation…"
Seems like there is one thing missing from the interface that might be useful. Thought I'd throw out the suggestion and see what everybody thinks:
/*
- Called to initiate a timeout, if applicable, on the current TouchMap object. Returns the next TouchMap object to be processed.
*/
public TouchMap triggerTimeout();
Seems like this may be useful with "int getDelay()"
in discussion Project Discussion / Planning and Vision » SJOC- Requirements Use Cases
Use cases updated again!
Alright guys, looks like we've come up with a pretty good definition to work from. Here's the details:
The interface is going to be centered around "TouchMap" objects. These objects have as their interface:
/*
- Returns the TouchMap object that will need to be processed next, responding to a MouseEvent triggered by the display.
*/
TouchMap executedEvent(MouseEvent me);
/*
- Returns the necessary filename for the .jpg (image file) to be displayed.
*/
String getImage();
/*
- Returns the associated timeout delay for the current TouchMap object.
*/
int getDelay();
The display component will be responsible for obtaining the first desired config file to be displayed and creating a new TouchMap object with the following constructor:
TouchMap(String cfgFile); //cfgFile will need to be the full path of the file to be opened.
Subsequent TouchMap objects will be created in the background using the "executedEvent" method provided through the TouchMap interface.
Even though the display will not need to parse through the config file, it may be beneficial to see the overall structure of it. I have replaced the initial "Example-Config-File.txt" with the newest version to include all the details specified in this post.
With this, SJMSU should be able to proceed with the display component.
in discussion Project Discussion / Planning and Vision » SJOC- Requirements Use Cases
Use cases are updated!
You do not need to worry about parsing the text file, only calling the methods of the interface.
I uploaded an example text file that has the format we're working with, as Josh mentioned. While it is only a sample, I believe it has all the parts that are needed to get the main points across. File is located under "files" on main page, Example-Configuration-file.txt I believe. It is conceivable that the file extension will change, but that should not be a big deal. Hope this helps.
Text file is made up with hotspots associated with that screen that follow this:
(int x, int y, int width, int height, screenName)
- x : Left-most x-coordinate of the HotSpot
- y : Upper-most y-coordinate of the HotSpot
where (x,y) is the ordered pair for the upper-left corner of the HotSpot.
- width & height : define the resulting rectangle when combined with x and y
- screenName : is the name of the screen to go to when that hotspot is pressed
in discussion Project Discussion / Planning and Vision » SJOC- Requirements Use Cases
The use cases for shark jumpers OC are posted in the documentation section. Or here.
step 1: cut a hole in a box…
