Fork me on GitHub
#om
<
2016-06-23
>
hkjels06:06:58

Is there a standardized way of implementing undo/redo?

hkjels06:06:14

I was thinking I could create my own undo-stack by pushing states upon each mutation except for the undo itself, but there might be a cleaner way..?

hkjels06:06:13

Found a blog-post about it for om.now, probably the same idea

mitchelkuijpers07:06:23

@nxqd: I switched from params using set-query to putting it in app-state, can highly recommend it

cjmurphy07:06:11

@mitchelkuijpers: still it would be interesting to know the cases where set-query / IQueryParams is a good choice. My mental picture at the moment has 'none' in that category. But that must be wrong.

mitchelkuijpers07:06:38

@cjmurphy: I agree.. Maybe for a autocomplete like in the tutorial?

jimmy08:06:25

@mitchelkuijpers: I can see that it works perfectly fine and reasonable clean in simple example. but the more componentes involved it gets out of hand pretty quickly ...

mitchelkuijpers08:06:03

@nxqd: do you mean putting it in the app-state or using params?

jimmy08:06:56

using it as IQueryParams ( set-query!) I meant.

mitchelkuijpers08:06:47

Aha yes i cannot recommend that

adamfrey18:06:54

@selfsame: what is the interactive application in the gif you posted yesterday?

tony.kay20:06:02

From the #C0PULSD25 channel. I've been making a number of videos for getting started with Untangled (which uses Om underneath). A number of the topics and solutions are pretty Om-centric, so even those that want to use raw Om can pick up a thing or two. If you like learning from video, check them out: https://www.youtube.com/playlist?list=PLVi9lDx-4C_T_gsmBQ_2gztvk6h_Usw6R

selfsame21:06:15

@adamfrey: WIP html/css design tool 🙂