Remove dev notes
This commit is contained in:
parent
99323a05ef
commit
a91003568f
1 changed files with 0 additions and 28 deletions
|
@ -1,28 +0,0 @@
|
||||||
# Refactoring
|
|
||||||
|
|
||||||
## ToDo
|
|
||||||
|
|
||||||
### Collapse namespaces
|
|
||||||
|
|
||||||
Currently there are two modes of operation in two explicit namespaces:
|
|
||||||
reply mode and account mode.
|
|
||||||
|
|
||||||
This leads to higher maintenance needs and more complex program structure. The overall goal is now to reduce this complexity.
|
|
||||||
|
|
||||||
Having one ns called to_html that produces html as needed seems appropriate at this time.
|
|
||||||
|
|
||||||
### Understand the data coming in from current reply mode
|
|
||||||
|
|
||||||
Assumption: We're just pulling in data from posts.
|
|
||||||
This should be about the same as the data for account mode.
|
|
||||||
|
|
||||||
- [x] The data are indeed statuses too
|
|
||||||
|
|
||||||
### Check whether or not we need to modify the current post html
|
|
||||||
|
|
||||||
### CSS per mode
|
|
||||||
|
|
||||||
Creating css that does basic styling depending on the mode.
|
|
||||||
|
|
||||||
### Automatically connecting CSS and appropriate HTML
|
|
||||||
|
|
Loading…
Reference in a new issue