Hotspots: Admin Pages | Turn-in Site |
Current Links: Case Final Project Summer 2007
M9: Final Design Twist
The last Demo
M9 was the last chance to demo our big project. We shouldn't have to do this but we ran into some trouble, which become our words of wisdom. Make sure you are saving the correct smalltalk file and including all the changes. Somewhere along the line after we had checked our sale policy and wrote our SUNITS we lost them. When we went to demo M7 the sale policy and SUNITS did not work. We had to go back change everything and rewrite all our SUNITS which was a pain. But in the end we got our credit back which is what counts.
M9 requirements
Your application MUST demonstrate the following features:
Use of a style sheet (css) to standardize look and feel
Use of query strings (?msg=111) to communicate information between the browser and web server
Use of session variables to maintain state between server calls
Static and Dynamic Web Pages
Use of forms to transmit data to the web page
Use of html include files for common data
Embedded smalltalk code (.ssp)
Create a site map, a flow chart of the required functionality, and a wireframe of the UI. See lecture notes for details.
Display a welcome screen and allow launching (creation) of a CCS.
Your CCS should autoload a saved configuration with some POS and Suppliers already created.
After launch, display a list of all POS already in the system.
Allow the user to use a text box to input a POS name. If the POS exists, display a screen with the POS details. If the POS does not exist, notify the user and redisplay the list of POS.
Allow the user to create a new POS, and then display the POS list and show that it was in fact added.
Any additional functionality (editing POS details, creating/displaying Suppliers) would be extra credit for M9, UNLESS that functinality is needed to demo the basic requirements above.
The work
M9 was a good refresher of looking stuff up you don't know. The whole thing was probably done in an hour and a half because of our excellent resource: http://www.cincomsmalltalk.com/tutorials/version7/webtoolkit/webtoolkit_overview.htm
The wireframe, site map, and flow chart are extremely easy and a no brainer. Strangely for us the hardest part was getting the server to start. After following the tutorial which is the easiest explanation we were off.
Cookies
Cookies were extremely easy. In our code brackets use the code: session at: 'something' put: 'object' Now to retrieve it: session at: 'something'
And Bam you got it.
Query Strings
For query string attach the ?msg=111 onto the end of the link to the next page. To retrieve you use request anyParameterValueAt: 'msg' and viola you got it.
Everything else like the forms, style sheet, and included files is extremely easy and you should have fun looking it up. One thing I would suggest is don't be shy from going through another simply "code" only site. You can use the redirect to: 'site' command to return to whatever site the user should eventually end up at.
And BAM! your CS2340 life is over and now smalltalk is your favorite language. haha
Link to this Page