summaryrefslogtreecommitdiffstats
path: root/kicker/rich-ideas.txt
blob: afe55f33a25b55faf96ede35531850b02dacbcb6 (plain)
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
62

Positioning of extensions
=========================

How about using the alignment flags (or similar) for position, and the
direction flags for how to fill?


 ---------------
 |a    b      c|
 |             |
 |             |
 |             |
 |e           d|
 ---------------

a = Left | Top
b = Middle | Top
c = Right | Top
d = Right | Bottom

Now here's the filling

12345	   LeftToRight
54321	   RightToLeft (eg. for a right aligned thing)
5
4
3          BottomToTop
2
1


etc. etc.

Essentially, this splits the concept of positioning and layout. Now, lets get
crazy:

Imagine we're in position a and want to have a triangular corner layout:

1247
35
6

So, maybe we need some sort of concept of (one of):
 1) multiple linked rectangular blocks
 2) extensions/bars with a mask
 3) each item being considered independently (maybe some sort of magnetic
 blocks so they can be draggable?)

Finally, let's get really insane:

positions a AND c

12       65
34        7

This perhaps indicates that the details of placement should be passed off to
the extensions, but also that extensions might be 'linked'. eg. removing the
extension in position a should also remove c (and the configurations are also
linked).