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

raindev wrote: post #6

yaronn01 wrote: post #5

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

Why do you decided to use XML as the basic format?

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?

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

#8

Post by chazu » Mon, Nov 02, 2015, 7:20 PM UTC

Very cool indeed - pair this with 'watch' and you have instant ASCII monitoring tools implemented as http endpoints.

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

#9

Post by rglover » Mon, Nov 02, 2015, 7:23 PM UTC

mannycalavera42 wrote: post #4

Joshua: Shall we play a game?

Global Thermonuclear War

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

#10

Post by ratboy666 » Mon, Nov 02, 2015, 7:25 PM UTC

Haven't tried this. Just want to know -- what advantage does this give over using gnu plot with sixel output?

I can see the advantage over tek 4010 (this could be dynamic). If this is static (again, haven't tried yet), with multiple pages, why not just use tek 4010?

I also don't understand the admonish to use something other than xterm. What is the issue that was observed?

Ratboy