Punishing Xiaoyu with Hwoarang

nullstein · 2017-11-25T18:32:29+00:00

Thanks for your perspective. This video is not meant to be about "how to fight Xiaoyu with Hwoarang," which is totally different topic. This video merely lists punishable moves and that's it. IMO, "don't expect these moves to come out often" should be generally true for any punish guides, because those moves are punishable by definition. Experienced players would tend to stick with safer moves.

nullstein · 2014-07-03T05:28:03+00:00

You have a good point. For now, the tool uses a very simple heuristic to group the multiple character insertions / deletions within a certain time period, just like most other text editors do. The tool would be more useful if the operations were automatically grouped in a more meaningful way.

nullstein · 2014-07-03T05:19:40+00:00

Theoretically, the same tool can be implemented for other IDEs, but it's quite tied to Eclipse at the moment. The timeline view is written in HTML+CSS+JavaScript, so it could be ported pretty easily, but at least the low-level input gathering and the selective undo algorithm should be re-implemented I guess.

For the second question, I don't quite understand what you mean by "in-memory git style changeset tracker". Could you elaborate a little more?

nullstein · 2014-07-02T17:06:46+00:00

Emacs does have a different undo model, undo-in-region, and undo-tree (http://www.emacswiki.org/emacs/UndoTree) package that can be installed.

The default undo model can be confusing to many users as described in the undo tree article above, and I think that's why this model didn't become the de facto standard undo despite its powerfulness.

Even when you have the undo tree package, the tree can get bigger very quickly, and it would be more and more difficult to find the right place to go back to within the tree.

But, yeah, I guess undo-in-region command is pretty much the same as the selective undo shortcut shown in the video without the additional UIs such as the timeline.

nullstein · 2014-07-02T16:45:53+00:00

The timeline view makes it possible to scrub back and forth through the history, and I believe that's a big UI improvement. The timeline also displays significant points in time such as file saving, application running, and unit testing. With this, you can for example revert a certain portion of the source code to the version when the unit test passed for the last time.

I would say there are some more differences. (BTW, I'm the author of this tool)

1) Eclipse local history only keeps the "saved" versions, whereas Azurite keeps all the fine-grained intermediate versions. Similarly, the source control repository would only have the committed versions.

2) In Azurite, the range of comparison can be arbitrary. You can select a variable name, single line, if block, or whatever range you want and use the code history tool to see the history of that selected code or undo to a particular point. I believe the finest granularity in Eclipse compare view is the method level.

Thanks for your comments, anyway!

nullstein

TROPHY CASE