One should use what is necessary and no more. If server side templates work for ...

TekMol · on Nov 17, 2018

Could you add the lines needed to the above example to make the user list grow / shrink real time via websockets?

Would be interested to see how you would implement that.

gbuk2013 · on Nov 17, 2018

Pseudo-ish code because I’m typing from my phone.

Vuex code as per docs to create state.stuff and mutations.update_suff() then in main Vue instance

    mounted () {
      this.$socket.subscribe(‘stuff’, data => {
        this.$store.commit(‘update_stuff’, data);
      });

where $socket is a subscriber client I wrote wrapped as a Vue plugin.

Then inside the components

    computed () {
      stuff () {
        return this.$store.state.stuff;
      }
    }

then use stuff as in your example.

So very simple, and nothing that I couldn’t do without Vue but it takes care of the boring DOM manipulations and using the browser extension during development I can watch state change (which becomes interesting when there are multiple subscriptions with data combined).

TekMol · on Nov 17, 2018

So the first step towards your solution would be to include vuex? Like this?

    <script src="/path/to/vuex.js"></script>

And then?

What are mounted() and computed()? They look like methods of a class?