refactor: moving to my own template, using fomantic instead of uikit. removing uikit, and some other removed stuff

This commit is contained in:
2024-01-15 21:55:28 +01:00
parent b5f9be7e5a
commit 8b42c94aa6
29 changed files with 564 additions and 37519 deletions
+43 -3
View File
@@ -1,7 +1,14 @@
# SeaORM
# NOTES
This is a heavily opinionated logbook I keep here until there is something usable.
## Some Rant about ORM Implementations
Please keep in mind, that I sometimes rant in writing, but learn later that I was wrong.
It was not supposed to be read by anyone else than me.
## SeaORM
### Some Rant about ORM Implementations
#### Entity, ActiveModel, Model
@@ -43,7 +50,7 @@ It is better to just see your storage layer as a global database layer, and impl
It's not like that is a bad thing, given this is also one of the downsides I witness in django projects, where models start to become swiss army knives around a domain topic.
## Accepting Fate
### Accepting My Fate
#### Generating Entities from a Database
@@ -135,3 +142,36 @@ As I started by quickly using a django admin template with CSS to jump start the
- implement views for app
- implement a static implementation for repository
- eventually AdminRegistry needs to become an `Arc<Mutex<T>>`, if internal data needs to change *after* creating the main state.
## CSS Library Brainhurt
### Bootstrap
Everybody says it is evil. I am not sure why yet.
### Pico.css
maybe it would be better to go for something simple?
### UiKit
in general really nice, but I got annoyed by uk- prefixes pretty fast.
It would however seem to align with hx- prefixes of htmx?
### Tailwind/DaisyUI
Tailwind supposed to make you uber designer.
Strongly suggested by professionals like theo/t3, however I kind of started to see everything he says as an anti-pattern. Jonathan, you are rubbing off.
I kind of want less "class"es not more. I understand why tailwind might be good. But then again, I don't get why I should decorate each tag with classes.
### Semantic/Fomantic
Semantic seems aligned with the idea of htmx and hyperscript a lot in it's philosophy of naming things.
It comes with jQuery basement, which is also a good recall to how a htmx site might work in the end.
Not having access to the main repo since 2 years, and being developed by the community is both a red flag and a good sign: there is an active community, but hampered potential.
I think it is important to go into form validation or interactive things quickly with htmx to properly sort out which to use.