|
JCapper Message Board General Discussion
|
| Home |
Register
Log In |
| By | HTML Changes - Brisnet SuperTote - The Live Play Module | |
| jeff 11/15/2012 1:44:54 PM | Brisnet has made some unannounced html changes for the web pages at their SuperTote site. One result is that these changes "break" 3rd party apps designed to parse SuperTote - including the Live Play Module in JCapper. I'm looking at it right now - and will post an update as soon as I know more. -jp .
| |
| jeff 11/15/2012 4:59:29 PM | I spoke with one of their progammers about the new changes. Now that I know what they have done - and after being assured that work for the current round of changes is complete, I can go ahead and make the needed mods to the Live Play Module. Barring something unforseen... I expect to have a working prototpe Live Play Module up and running at my end sometime tomorrow - and from there will need a day or so to fully test it. Based on that I'm going to set ETA for publishing a new Live Play Module only download package on the Platinum downloads page sometime within the next 48 hours. -jp .
| |
| chrisl 11/29/2012 8:13:04 AM | Hey Jeff: Is there a update on getting the auto scratch up and running. Thanks Chris
| |
| jeff 11/29/2012 12:21:17 PM | I should have waited before making the posts that appear at the top of this thread Chris. This project is a lot more involved than I initially thought. I do have a working prototype at my end. However, getting that prototype out to you and getting it delivered in a format that you can use... That's another matter. Brisnet changed all of their tote links. The main change in their tote links has to do with the characters "type=0" (without the quotes) found in the query string: "type=0" (without the quotes) was changed to "type=1" (again without the quotes.) The second change has to do with their track codes: Previously, all of their tote codes had 3 characters and these always matched the first 3 characters of their data file names. For example, the track code in their tote link for Fingerlakes was FLX - and this matched the first 3 characters of the Fingerlakes data file - also FLX. That's no longer the case. Now the track code in the tote link is "FL" but the data file name is "FLX." The next change has to do with changes to both track code and tote code. In the Brisnet world, Hollywood Park is now "BHP" and Philadeplphia Park is "PRX" (also tote code "PRX".) At this point it starts to get complicated... 1. I can't just assume that the X character means that a track will have a 2 character tote code. "PRX" differs conceptually from tracks like "GGX" that have 2 character tote codes (the tote code for Golden Gate is "GG." 2. The Live Play Module also has to work for HDW customers. Unlike Brisnet, in my opinion, HDW did the right thing and left the track code for Hollywood Park unchanged at "HOL" - HDW also left the track code for Philly Park unchanged at "PHA" - this makes things easier to manage in a database. 3. Up to this point in time, ALL of the tote links have been hard coded into the Live Play Module. It wasn't overly difficult because the track code and the tote code always matched and there were only a handful of track names that needed special handling. I thought about just recoding the above changes into the Live Play Module and publishing it as a one time fix. (In fact that WAS my initial intention when I made the posts at the top of this thread.) However, maintaining the current info model where tote links for 100 or more tracks are hard coded into the Live Play Module is just asking for trouble every time Brisnet makes a change to their tote link schema. The more I thought about this, the more I realized that the better info model would be to enable the USER to handle changes by Brisnet to tote links on the fly. I decided to create a new table (it's called the ToteCodes table) and I added it to the JCapper2.mdb file. I also created a new screen called the ToteCodes Table Mgr. Next I added a launch button for it to the Live Play Module. This new module empowers the user to persist entries to the ToteCodes table (one record persisted to the table for each track code that you want to enable the module to parse.) The new Live Play Module reads the ToteCodes table and uses tote links read from the table to parse the win pool, exacta pool, and get auto scratches for each requested track. I have a working prototype of the above at my end. The module's interface is kind of cool and includes an Assist Button that QUICKLY lets you build tote links for the tracks you want to parse. What I don't have yet is an illustrated help doc or video. The basic operation of the module is pretty straighforward and a post or two in this thread can probably suffice until such time as I can cut a video or write up a formal help doc. The other thing I don't have yet is a way for you to import the new table structure into your current JCapper2.mdb file. That still needs to be created - and that's what I need to finish up before I can publish the new Live Play Module. I apologize for jumping the gun by posting at the top of this thread - but I'm still several days away from having everything tied together and fully tested so that I can deliver it. -jp . ~Edited by: jeff on: 11/29/2012 at: 12:21:17 PM~
| |
| STUBALL 11/29/2012 1:43:59 PM | It seems it is a love it --- hate it relationship with Bristote If they can break it they will--intentionally or not..?????? Keep up the great work you do Jeff Stuball
| |
| chrisl 11/29/2012 2:09:27 PM | Hey No problem: I have all faith it will be taking care of. Thank You Chris
| |
| jeff 12/23/2012 1:46:39 PM | New Platinum program update is now out... Link to release notes pdf: http://www.jcapper.com/helpDocs/newprogramupdate_12232012.pdf Cut and paste from the above as relates to the new Live Play Module and the ToteCodes Table Mgr Interface: JCapper Program Update – Dec 23, 2012 (Build 190) What’s Inside This new program update has LOTS of new features. It WILL take me several days just to publish write ups in these release notes for everything in this new version (so check back frequently.) The primary reason I’m publishing now (as opposed to waiting until I have a write up about everything) is to get the new Live Play Module out to JCapper Platinum Customers. Happy Holidays, -jp . ToteCodes Table Mgr I also created a new screen called the ToteCodes Table Mgr. You will find a launch button for it on the left side of the Live Play Module beginning with this new program update. The new Live Play Module empowers you the user to persist entries to the ToteCodes table (you need one record persisted to the table for each track code that you want to enable the module to parse.) The new Live Play Module reads the ToteCodes table and uses tote links read from the table to parse the win pool, exacta pool, and get auto scratches for each requested track. BASIC OPERATING INSTRUCTIONS: 1. Launch the module by finding the ToteCodes Table Mgr button on the face of the Live Play Module and clicking it. Note that when you launch the ToteCodes Table Mgr Interface, the Live Play Module is automatically put into ML/Manual Mode. Once you are done with the ToteCodes Table Mgr you can kick the Live Play Module back into Live Tote Mode by unchecking the Manual Mode and ML Mode boxes – after which you will be able to operate the module normally. 2. Pull Up or Find the entry for a track code by keying a valid 3 character track code into the Find field and click the Find button. If an entry exists in the table for the track code you are searching for the interface will pull it up. If not, the interface will tell you that the track code you are searching for was not found. 3. To create a New Entry for a 3 character track code: a. Click the New button. b. Key a 3 character track code into the Track Code field. Hint: Use the first 3 characters of the data file name. c. Key a 2 or 3 character tote code into the Tote Code field. Hint: Tracks that have 3 character track codes such as AQU-BEL-SAR, etc will have 3 character tote codes. Tracks that have 2 character track codes such as GG, SA, WO, etc. will have 2 character tote codes. You might try looking closely at the tote url itself for that track by loading SuperTote into a web browser. If you still can’t figure it out, goto the JCapper Message Board and ask. d. Key a numeric 1 character into the Type field. e. Click the Assist button. The Interface will auto generate tote urls for you using the tote code and type that you supplied. f. Key a valid NHPlay track description (if you know it) into the NHPlayDescr field. This will prove helpful later if you are an NHPlay customer and want to import a CSV file containing your own tickets directly from the NHPlay site into the JCapper WagerHistory Module. If you don’t know what the NHPlay TrackDescr is for a give track just leave this field blank. g. Key your own track description into the Notes field. (Optional) h. Click the Save button to save your work. Or, alternately, click one of the paging buttons (Back, Next, etc. to abandon your work.) That’s it! Once you create a valid entry in the ToteCodes table for a given track, the Live Play Module will be able to parse the tote stream for that track from then on. Troubleshooting: If the Live Play Module refuses to parse the tote stream for a given track the first thing you should ask yourself is: Q. Do I have a valid entry in the ToteCodes table for that track? Link to a screenshot of a valid entry for Gulfstream Park: http://www.jcapper.com/messageboard/avatars/totecodesgpx.jpg What you need to know about the screenshot: 1. GPX is the Track Code (also the first 3 characters of the data file name.) 2. GP is the Tote Code (embedded in the tote urls.) 3. 1 is the Type (embedded in the tote urls.) 4. Both of the tote urls were auto generated by clicking the Assist button after keying in GPX as the Track Code, GP as the Tote Code, and 1 as the Type. (Alternately, I suppose you could have keyed both urls out by longhand if for some reason you hate the idea of an Assist button.) 5. Gulfstream is the NHPlay Track Description (You would know that once you downloaded a CSV file from the NHPlay site containing tickets for wagers made on Gulfstream races.) Entering the correct NHPlay Track Description in the ToteCodes table here saves you the added step later of having to resolve the characters Gulfstream to track code GPX when importing Gulfstream tickets from the NHPlay CSV file directly into your WagerHistory table using the new CSV Import Screen in the WagerHistory Module. --end section for ToteCodes Table Mgr-- -jp . ~Edited by: jeff on: 12/23/2012 at: 1:46:39 PM~
| |
| Arnold 12/24/2012 4:32:07 PM | Works in UDM mode but not SQL mode. Will try to go back to old build. Update have it working. ~Edited by: Arnold on: 12/24/2012 at: 4:32:07 PM~
| |
| jeff 12/27/2012 2:28:44 PM | I'll take that to mean you have it and running. I'm traveling and in AZ visiting family right now. Internet access where I am is spotty at best. Best way to reach me would be to call my cell (8 5 8 - 8 6 9 - 7 2 6 9) -jp .
| |
| Ishmael 1/4/2013 3:02:02 PM | Anyone else experiencing long delays in downloading Brisnet files?
|
| Reply |
|
Copyright © 2018 JCapper Software back to the JCapper Message Board www.JCapper.com |