Show HN: WOPR – A markup for rich terminal reports • Hacker News Board

Re: Show HN: WOPR – A markup for rich terminal reports

#21

Post by OJFord » Mon, Nov 02, 2015, 8:44 PM UTC

For now I'm categorising this (mentally, I mean) under "awesome, but idky useful".

I'd love to be told I'm wrong though. It's the best thing when you discover how to usefully use awesome but hitherto useless tools :p

Re: Show HN: WOPR – A markup for rich terminal reports

#22

Post by gavazzy » Mon, Nov 02, 2015, 8:52 PM UTC

This would be useful for AWS instances where you don't want to install a desktop environment on the server.

Re: Show HN: WOPR – A markup for rich terminal reports

#23

Post by yaronn01 » Mon, Nov 02, 2015, 9:11 PM UTC

OJFord wrote: post #21

For now I'm categorising this (mentally, I mean) under "awesome, but idky useful". I'd love to be told I'm wrong though. It's the best thing when you discover how to usefully use awesome but hitherto useless tools :p

one use case is when ssh-ing machines you can see visual reports rather than text and numbers (think cpu metrics or app specific).

Re: Show HN: WOPR – A markup for rich terminal reports

#24

Post by themodelplumber » Mon, Nov 02, 2015, 9:12 PM UTC

mburns wrote: post #11

yaronn01 wrote: post #7

Earlier quoted context omitted.

XML is a standard format for markup (e.g. HTML). When XML is used where it shouldn't (object serialization) it adds complexity. Here it signals that creating a report is as simple (or at least as standard) as creating HTML. What other format you had in mind?

>XML is a standard format for markup (e.g. HTML). XHTML is maybe the most hated incarnation of HTML, and is no longer encouraged.

XML and XHTML are two different things. Related, but different. XHTML is no longer encouraged for website markup, that part is true too. That does not mean that XML is no longer encouraged.

Re: Show HN: WOPR – A markup for rich terminal reports

#25

Post by atmosx » Mon, Nov 02, 2015, 9:43 PM UTC

gavazzy wrote: post #22

This would be useful for AWS instances where you don't want to install a desktop environment on the server.

Why would you wanna do that (install a desktop env)?!

Re: Show HN: WOPR – A markup for rich terminal reports

#26

Post by sklogic » Mon, Nov 02, 2015, 10:08 PM UTC

Impressive. I keep using bare xterm since it still supports Tektronix emulation (but, unfortunately, no Regis nor Sixel). This seems like a viable substitution for all three.

Re: Show HN: WOPR – A markup for rich terminal reports

#27

Post by ivanceras » Mon, Nov 02, 2015, 10:15 PM UTC

I didn't know, you could display something like that in a terminal. And why tty.zone maps to that wopr site?

Re: Show HN: WOPR – A markup for rich terminal reports

#28

Post by astro1138 » Tue, Nov 03, 2015, 12:03 AM UTC

I wonder if it's manageable to build a converter to SVG with just XSLT?

Re: Show HN: WOPR – A markup for rich terminal reports

#29

Post by akkartik » Tue, Nov 03, 2015, 12:53 AM UTC

yaronn01 wrote: post #5

Hi everyone, I am the author. Feel free to ask me anything or come up with suggestions!

Very cool! It got me daydreaming about an alternative to html designed from the ground up to minimize webpage bloat and avoid tracking (1x1 pixel gifs, etc.)

Re: Show HN: WOPR – A markup for rich terminal reports

#30

Post by yaronn01 » Tue, Nov 03, 2015, 1:30 AM UTC

ivanceras wrote: post #27

I didn't know, you could display something like that in a terminal. And why tty.zone maps to that wopr site?

That's a shortcut for the wopr page