How often do you experience your whole lane blocked by the content of a whole appartement?

In Stockholm where I live snow, and ice make bike lanes hard to see and also makes them inaccessible.

I really agree that you shouldn't keep a speed where you can't control your vehicle, but so common design flaw puts an unreasonable amount of responsibility on the biker compared to heavier vehicles misusing the bike lane.

I'm building a tool where a text editor and group chat plays the leading characters. I use Markdown in both instead of WYSIWYG.

My requirements for choice of markup language was:

- easy to read and write

- converts easily to clean HTML, ePub, PDF and other formats

- content blocks can be tagged with one or more tags

- content blocks can be targeted to one or more user/role

- allow simple data (key value pairs, lists)

TAGGING

With the risk of provoking a heart-attack on Markdown purists I present my first implementation of syntax for tagging:

#tag Header

Readability is an issue with more than one tag but I can live with only one tag per level of heading.

TAGGING EXAMPLE

The would allow us to write:

#chapter At the riviera

...

##scene On the beach

...

##scene The Ice Cream parlour

...

Which would help to render text differently depending on tagging - use tags as classes when parsed to HTML.

TARGETING

I use a simple and well known syntax at the start of a line:

@username ...

...

...

Is not very loud but allows a parser to understand that content on a certain level and below is targeted to a restricted audience.

An alternative way I've been pondering is expanding the {} syntax used for IDs in Kramdown and PHP Markdown Extra.

{@role,@role2}

{.tag,.tag2} or just {tag,tag2}

Targeting content will allow soft access control as well as being able to write Markdown in group chat and route parts of the text to different users/sub-groups

DATA IN MARKDOWN

I'm hoping to solve data with the

: data

Or maybe do some mixin with YAML?

Comments URL: https://news.ycombinator.com/item?id=6915605

Points: 1

# Comments: 0

Small thought - when you're moving an object, wouldn't it be logical to also allow for small step moves with the arrows?Now it will move the camera position.

I'm working with very simple HTML and Bootstrap. I also use JSON files with actual data and some simple jquery to populate and handle states. After a while you'll get a library of HTML snippets, javascript code and dummy content. You'll work quite fast. The result is much closer to the truth and you might actually be able to re-use some of the stuff you've created when you build the actual app.

I've been using Axure and Balsamico which are quite good tools, but I find myself getting stuck and wasting a lot of time on emulating behaviour which is quite easy to code.

A great point with using paper is that anyone can draw on paper. Just take out the contractors board, give your co-worker a pen and you're creating something together.

When I'm on the go and have some good ideas lying around I might shuffle them in with the other paper just to develope them further when I get a slot. The good ones get photographed and stored, the not so good I try to give a second round of thought and fresh sketches. If that fails it's straight to the bin.

I also keep a simple notebook app in my mobile which I use just for ideas. Lately I've been testing Trello and also Hollyapp.com, task tracking for nerds. I like the markup syntax of Hollyapp. Very fast to write. I like splitting my ideas to managable chunks and todos since I in the moment of the idea often have a picture on how to accomplish it. I'm writing more and more Markdown for this

A lot of credit to Mårten Agner http://angner.se/ for the sketching techniques I use daily.

I'm not sure about the cut-scene advice. Yes - I can see you loosing players but It's part of what makes this game feel very retro. Sure, you could tweak it a bit and do the cut scenes a bit shorter. Also you should add an option of skipping the cut-scenes alltogether. I did a replay of the first part and would happilly trade x-x-x with a single escape press.

Agree with the @reitzensteinm. You should have visual reaction to hit. I was kind of expecting it since you had a lot of other visual effects such as screen shake etc.

You've done an amazing job. Do you have a twitter account we could follow? app.net?

Inline editing is the one feature i miss the most. Also the tree list is a bit hidden. If they were visible you could switch faster betweem them and setup the app as a lightweight project management tool or issue tracker. Just add your users, milestones etc as own trees and copy/paste between them. Also a syntax like: (someissuenumber) ... which renders issue number in front of the line would make it kick-ass.

Great job!

Even though jQuery handles most of my cross-browser issues I still have to test and worry, create workarounds and lots of additional code, consider it in my architecture, take care in the design and handle it in the application lifecycle.

I have been looking for and at able framework that DON’T support old browsers. Thank you for not supporting IE-ancient in your 2.+ releases, I will continue using you jQuery!