@@ -18,6 +18,7 @@ This project is a port of the Themesberg [tailwind-dashboard-windster] project t
18
18
- [X] Add table pagination
19
19
- [X] Add table search
20
20
- [X] Add gitHub Stars Button
21
+ - [ ] Add table CRUD operations (inc multi-record delete)
21
22
- [ ] Work out how to access client-side storage
22
23
- [ ] Stop the crazy python stack dump when the a user leaves the site.
23
24
- [ ] Figure out why my pytest tests need * @pytest .mark.anyio* but the ReactPy pytest tests don't
@@ -31,20 +32,19 @@ This project is a port of the Themesberg [tailwind-dashboard-windster] project t
31
32
pytest --headed
32
33
33
34
34
- ## reactpy_table
35
-
36
- * [ use_reactpy_table] ( tmp/table/examples/react/pagination/src/main.tsx#L110 )
37
- [ useReactTable] ( tmp/table/packages/react-table/src/index.tsx#L57 )
35
+ ## Tailwind CSS
38
36
37
+ During development [ tailwindcss play] is used. Tailwind play generates CSS rules
38
+ on the fly. They are accumulated, as pages are visited, into a custom
39
+ style tag. This process a fast and seamless.
39
40
40
- ## Tailwind CSS
41
+ You can, if neccecery, create a static CSS file containing all the
42
+ accumulated rules. To do this you need to copy the content of the tailwind play
43
+ style tag from a live browser session and dump it to file.
41
44
42
- During development [ tailwindcss play ] is used.
45
+ Chrome debug tools are used to dump the style tag to the file:
43
46
44
- To get a static css file containing all the CSS active rules, you need to copy
45
- the tailwind play generated style tag from a live browser session and
46
- dump it into a file. See * static\css\tailwind-3.3.5.css* . This file will
47
- contain the accumulated CSS rules for every page visited.
47
+ ./static/css/tailwind-3.3.5.css
48
48
49
49
## Links
50
50
0 commit comments