Not wanting to hijack you thread, but I found this plugin to wrap .asm files for use in vue:
feel free to hijack or byejack 🙂
Could that be interesting approach to integrate/use .asm in Vue?
Sure. The ffmpeg is interesting because it is highly useful in some applications. The general WASM imho is rather hard to find a purpose at least in my line of work.
Anyway - you asked about general solution - from the user point of view, then yes, this is specialized project, BUT from a developer point of view, the whole ffmpeg integration as a project a developer environment on github could be useful in other wasm projects. BUT on the other hand, the new WASM projects are started with rust or nim with llvm backend probably, so I don’t really know if it could/would be useful in real world applications.
So, ffmpeg in the browser could be VERY useful. From what I’ve seen it is an early project BUT there’s active development.
So have you done UNDO / REDO before with a relational database ? Did it work well for you ?
yes, many times, BUT it of course depends on the definition of undo 🙂
The most “classic” undo/redo is in banking systems. There is a concept of transaction log, every event has a date, a money transfer, a source, destination and if you want to make a undo, then you just replay needed transaction (banking not db) with opposite value sign.
There were apps where in some domains the undo were beneficial and where this behaviour was implemented by record version history. It works very well when you do not need to undo many inter-table connections. As a matter of fact, I implement very, very often the record version history and operations log for almost every table. It is beneficial in long run.
And there are some tables, where it is possible to model the reality in such a way, where the actions and states of the records in those tables mimics the finite state machines. I do prefer and strongly recommend using this technique in relational tables. Imagine that you have a table “Users”. You can add a column “status” with such possible values: “N” - new, “P” - in process of registration, “C” - registration cancelled, “Z” - user active, “B” user blocked, “U” - user deleted. There are possible transitions (just as example):
If you have a table with versions of this table, than every update to users table would insert last version (automatically by trigger) to your version table. You have full log, full operations register, full info about who did what and when and… undo/redo possibility.
FSM (finite state machines) gives you guarantee, that your system, as a whole, will always be in determined and correct state.
Oh, this is my main modelling/architecture concept which works in most situations. It is of course only a tip of the iceberg, but I’m sure it is somewhat obvious, because all this is described and known from many years.
@s-molinari definitely it was a good food. About stateless he proposes to reverse the mvc and just pass the state with control, which in my opinion works superb, I used that.
You took that reactivity to another level, wow - whole reactive system, not only visuals. I agree it would be an overkill. In context of Quasar, I’d like to think of specific use cases, where such architecture level decision would be necessary. As for now, I found something like this:
Imagine QTree, where underlying hierarchical data model is lazy loaded. Changes are synchronized with backend in real-time allowing collaboration (as in google docs), with multi selection and multi cursors. And of course this data model and QTree themself allows to work offline (mobile) and supports non hierarchical data model actions (drag-n-drop and copy-paste of subtrees). Ideally data model would support peer-to-peer synchronization. Oh, sweet dreams…
@lucasfernog sure, but please read the thread carefully - we’re not talking about components but about thousands of free bootstrap themes, used as a base for frontend sites in business, blogs, landing pages and many other categories of sites.
It is possible to get those momentum in frontend technology because Quasar has a set of compatible with B4 CSS classes which means, that if there would be a clear or relatively easy path of conversion from B4 to Quasar, there is a big chance of putting Quasar mainstream and let the world use it instead of B4. Why? Because B4 has poor components but it’s very easy to start with good looking theme or template but when it comes to really making a site it is very hard. So, as you can see, CSS classes for layout, typography and colors are not a “developer” problem but rather a “marketing” problem.
I’ve just come across this issue converting a project that uses Bootstrap css, which I’m converting into Quasar.
It would have been helpful to have a guide. The point that @qyloxe makes above is very smart business sense as well.
@rstoenescu “after v1.0 (next major version after v0.15)…” - do you envision that the changes to v1.0 will be as disruptive as the changes from 0.14 to 0.15? Our application (projectfinance.io) is pretty robust and perhaps I hopped on the Quasar train a bit early, but It took me almost two weeks with some pretty pervasive code changes to move to 0.15.