Sadly, I don't know Go Lang though, so my help is limited to the HTML/JS parts. π
I can probably contribute the most on the pwa repo.
Sadly, I don't know Go Lang though, so my help is limited to the HTML/JS parts. π
I can probably contribute the most on the pwa repo.
> Sadly, I donβt know Go Lang though, so my help is limited to the HTML/JS parts. π
This is fine! π― There's a lot you can contribute to in the default theme -- No real Go experience required really, the Go html/template is not hard to get used to π
There is also a Guide for Template Authors on our Wiki.
> Sadly, I donβt know Go Lang though, so my help is limited to the HTML/JS parts. π
This is fine! π― There's a lot you can contribute to in the default theme -- No real Go experience required really, the Go html/template is not hard to get used to π
There is also a Guide for Template Authors on our Wiki.
Actually, if you're good with Javascript and specifically MithrilJS you _could_ help us get the PWA repo/project -- Currently it's just a bit of a skeleton. I also don't like to use NodeJS or NPM as you can tell π over complicates things for me!)
Actually, if you're good with Javascript and specifically MithrilJS you _could_ help us get the PWA repo/project -- Currently it's just a bit of a skeleton. I also don't like to use NodeJS or NPM as you can tell π over complicates things for me!)
I never used MithrilJS but it seems to be the usual JSX style of DOM structure.
I can see that you're using the templating in the html but i'm lost on how it bind with the backend.
My usual PWA setup is entirely separated from the backend.
I also worked a lot with NodeJS too and now i'm working on creating a bundle-less setup that is light and easy to use and don't need any tooling at all except for a static server and a browser.
yarnd server via -t/--theme to the directory for the pwa theme and voila. But this is probably a bad idea, so you can largely ignore most of the templating you see there, it would only get used once to render the index.html or / anyway -- the PWA takes over at that point via it's Javascript and Service Worker, etc...
yarnd server via -t/--theme to the directory for the pwa theme and voila. But this is probably a bad idea, so you can largely ignore most of the templating you see there, it would only get used once to render the index.html or / anyway -- the PWA takes over at that point via it's Javascript and Service Worker, etc...
While MithrilJS is a good library I find if wasted when not used with JSX, you can probably enhance the syntax by using htm for the templating if you want to keep it light or use the renderer of esbuild directly.
In my projects I usually use uhtml, it's a simple to use and blazing fast templating library, It doesn't even use the Shadow DOM the usual JSX rely on, you should try it for your next project. π
I'd like to steer clear of things ike JSX, etc. MithrilJS fortunately lets you just write regular things like:
export default function Login (vnode) {
const { context } = vnode.attrs;
return {
view: function () {
return m("twt-login",
m("form", [
m("input", {"type":"text","placeholder":"Username"}),
...
π
I'd like to steer clear of things ike JSX, etc. MithrilJS fortunately lets you just write regular things like:
export default function Login (vnode) {
const { context } = vnode.attrs;
return {
view: function () {
return m("twt-login",
m("form", [
m("input", {"type":"text","placeholder":"Username"}),
...
π
yarnd and the separate SPA/PWA with a mobile-first design and a more "native"(ish) feel π
The _trick_ will be to reuse as much code between what drives the API and the SSR so changes, improvements or new features can be rolled out to the API, SSR and PWA all at once quite easily... π€
yarnd and the separate SPA/PWA with a mobile-first design and a more "native"(ish) feel π
The _trick_ will be to reuse as much code between what drives the API and the SSR so changes, improvements or new features can be rolled out to the API, SSR and PWA all at once quite easily... π€
Then I'll try to make my best to make something nice. π
One last question, is it okay to go with standard fetch for API calls or you're planning to use twt.js?
The repo seems archived though.
=> (arrow functions) and all the new so-called "modern" language in Javascript is just well umm crap IHMO π
=> (arrow functions) and all the new so-called "modern" language in Javascript is just well umm crap IHMO π
I too ended up wanting less and less but exactly for that reason I really enjoy those new stuff the platform offers natively.
Anyway, I'll keep your style as much as I can. π