1
- Cloud Save
1
+ ############# Cloud Save
2
2
3
3
It's actually really amazing how many people now use Cloud Save. In fact, when I
4
4
first built this, I had no idea how anyone would possibly find this extension of
@@ -11,4 +11,83 @@ Cloud Save is still pretty cool though. And it's not a terrible name, actually.
11
11
probably the one project of mine which actually has a fairly decent name.
12
12
13
13
Right now, I'm going to try doing development of cloud save on the cloud via the
14
- cloud9 IDE on a Cr-48. It's going pretty well so far and it's really awesome.
14
+ cloud9 IDE on a Cr-48. It's going pretty well so far and it's really awesome.
15
+
16
+ ############## Design for Cloud Save 1.2
17
+
18
+ Version 1.2 will feature tons and tons of magic. Really really magical magic.
19
+
20
+ The basis is a moving window-ish persistant stack which contains the names of hosts
21
+ used. eg. dropbox, dropbox, picasa, picasa, box.net, google docs, dropbox, google docs, dropbox
22
+
23
+ Right now, I figure the ideal value is 10. Why? Because Math.sqrt(10) day is next
24
+ week and also incidentally my birthday is on sqrt(10) day. It's also between five
25
+ and fifteen, if my third grade arithmetic skills are still intact.
26
+
27
+ So this moving window is kept persistantly via localStorage. It gets processed and
28
+ sorted into unique elements: dropbox, picasa, google docs, box.net. Then those are
29
+ sorted by a magical ranking coefficient.
30
+
31
+ The general formula for this ranking index is
32
+ number_of_times_used_in_past_10 + most_recent_index / index_dampening_factor
33
+
34
+ dropbox was used 4 times in that list - most recent is the last one of the list of so index 8
35
+ picasa twice - most recent index is 3
36
+ box.net once - most recent index is 4
37
+ google docs twice - most recent index is 7
38
+
39
+ the index dampening factor should be a big number. the second term in the magical
40
+ equation that is used here exists for the sole purpose of breaking ties between
41
+ things used an equal number of times to favor those who have been used more recently
42
+ (or should it be a smaller number?). A good value is something like the total
43
+ size of the moving window multiplied by 10. But to be safe, something like 1000 could
44
+ be used. Though any number should theoretically work, for debugging purposes it would
45
+ be nice if it was a power of ten.
46
+
47
+ The top six most recently used hosts will be shown. Or less than that if the last
48
+ ten include less than six items (again, ordered by the rank thing).
49
+
50
+ Once a file is uploaded, the list must be recalculated and generated.
51
+
52
+ The first level menu will be the same:
53
+
54
+ Cloud Save >
55
+
56
+ Second level:
57
+
58
+ Save As... >
59
+ ------------
60
+ HOst1
61
+ Host2
62
+ Host3
63
+ Host5
64
+ Host6
65
+ Host4
66
+ ------------
67
+ More >
68
+
69
+ There are two tertiary menus. Save As... however looks exactly like the secondary
70
+ level menu but without another save as submenu (obviously).
71
+
72
+ So the More.. menu, which is the only interesting tertiary menu will be as follows:
73
+
74
+ Add/Remove...
75
+ -------------
76
+ HostA
77
+ HostB
78
+ HostC
79
+ HostD
80
+ HostE
81
+ HostF
82
+ HostG
83
+ HostH
84
+ ...
85
+
86
+ As follows. The tertiary list will include all the other hosts in alphabetical order.
87
+
88
+ Add/Remove is sort of a misnomer as it will not actually do anything in verison 1.2
89
+ instead, it'll be a link to the settings page which will do virtually nothing except
90
+ for configuring some very magical variable coefficients and stuff. probably.
91
+
92
+ These plans were written at 4:23PM Eastern Standard Time on the Eleventh of March of
93
+ the year 2011.
0 commit comments