jdubray/sam

Jean-Jacques Dubray

@metapgmr_twitter

const { intents: todoIntents } = addComponent(todo)

Then you can use todoIntents

sandsunsky

@sandsunsky:matrix.org

[m]

Awesome that makes sense

sandsunsky

@sandsunsky:matrix.org

[m]

My knowledge of javascript is very limited so some of it is done uglier than it needs to be but i got it to work

image.png

I'm not even sure if I need more than one base component but I learned alot figuring it out

instead of that one function

image.png

in theme.js

i have two

image.png

sandsunsky

@sandsunsky:matrix.org

[m]

image.png

do you reckon if im making a website

I should just keep one

like you have it in the todomvc-app-lit-html example

like this

image.png

sandsunsky

@sandsunsky:matrix.org

[m]

image.png

Jean-Jacques Dubray

@metapgmr_twitter

It really depends how big is your application and how modular you want it to be (e.g. microfrontends). One is a good start, especially if you are the only one working on it. In your function that assigns the intents to the window object, you may want to use a (component) label maybe such that you can assign different intent arrays export default function(component, intents)

you could then:

switch(component) {
     case 'MAIN': Object.assign(window, { ...


}

chatGPT knows about the SAM pattern today! Not a great summary, but a start!

sandsunsky

@sandsunsky:matrix.org

[m]

better than id expect it to do

sandsunsky

@sandsunsky:matrix.org

[m]

does this

image.png

mean you shouldn't wait for websocket to send you something

rather you should be asking periodly if its got something new to send you?

image.png

Jean-Jacques Dubray

@metapgmr_twitter

the webSocket handler should formulate an action. The idea is that it's perfectly ok to have async actions (queries for data enrichment or mutations). Mutations by nature are generally handled as next-actions since you want to validate the proposal to mutate in SAM's model.

1 reply

sandsunsky

@sandsunsky:matrix.org

[m]

FYI I’m trying to develop a decentralised wiki leaks where journalists can connect with leakers. Journalist curated leaks will be hosted on the decentralised site. Then journalists can embed their curated leaks into their websites.

Daniel Neveux

@dagatsoin

@sandsunsky:matrix.org I think SAM firs well dir a decentralized use case because it "easily" implementable with a messaging system.

Daniel Neveux

@dagatsoin

fits with

The different parts (state, actions, model) can be dispatched across nodes.eplication and synchronisation can be backed by the temporal logic.

*Replication (sorry I am on my phone)

I am curious to know about how you will implement your wiki.

sandsunsky

@sandsunsky:matrix.org

[m]

I'm letting this handle all the decentralized aspects. https://github.com/zeronet-conservancy/zeronet-conservancy

I might need something ontop of this for large files I guess IFPS would be the best bet for that

sandsunsky

@sandsunsky:matrix.org

[m]

Sam pattern via Sam-lib is forcing me to code way less spagbowly

Great stuff

Jean-Jacques Dubray

@jdubray

@sandsunsky:matrix.org I think that making application state mutations explicit and having the right structure to release the new application state is definitely helpful. That's what TLA+ taught me.

Jean-Jacques Dubray

@jdubray