-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathnotes-1.txt
66 lines (42 loc) · 1.69 KB
/
notes-1.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
% python course - spring - class 1 talking points
Announcements
Course web page - whole schedule is there now
Tonight (as all nights) 1 hour lecture/demo,
then Brian and/or I circulate to discuss projects
~ 15 min/student (each student in a group)
Then ~20 minute summary to the class at the end
Have something prepared to discuss with us.
Lecture
Django-style web application is just one style: "CMS style"
- server has database, a bunch of documents, ...
- server creates and sends each web page, client (browser) just renders it
Alternate "API style"
- server does a *computation*
- server just sends data, not pages
- client (browser + software) creates, updates pages
- UI is in the client
- client software updates page with new data without reloading: "Ajax"
Example API-style web application - intro by JJ
- Physics simulation by JJ, JC to experiment with techniques
- Server is a Python CGI program that gets data from a form,
computes time series from the data, returns as JSON data
- Client shows time series in a couple of different formats
- bar graph of events
- line graph of polarization
- frame-by-frame animation - animation by switching between images
Demo example - Javascript, Ajax, canvas, etc. explanation by Jon Crump
Server needn't send HTML. Can also send:
- JSON
- SVG
- WebGL
- ...
Browser + server can provide the user interface even for applications
expected to run locally --- then optional use via the web is a bonus.
Projects
Suggested lab activity: start a repo on github (or your choice) with
project description in README
Consider: do you want to make your project public?
Groups? More than one project?
Wrap up
List of projects,
Common themes and issues?