Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: This website is valid JSON

webdatarender.com

Post reply on HN
Print view View original

111–120 of 240 posts

Re: Show HN: This website is valid JSON

#111

Post by jammaloo »

mstade wrote: post #105
pjgalbraith wrote: post #50

Earlier quoted context omitted.

In regards to the character encoding issue, I wonder if they could just move the #render to the top of the object by inserting it as the first property.

I'm guessing there might be issues with the streaming nature of html parsers then. If you put it at the top and the JSON is of any non-trivial size you might end up with the script trying to read invalid JSON since it's not fully loaded yet.

The script could be tied into the global onload event, so that it will only attempt to parse the JSON after the page has been fully loaded. Likely the HTML block is just placed at the bottom of the JSON for aesthetic reasons.

Re: Show HN: This website is valid JSON

#112

Post by vincnetas »

mark_and_sweep wrote: post #64
mark_and_sweep wrote: post #33

Earlier quoted context omitted.

XSLT is the only way to do HTML templating on the client without using JS. I think that is valuable.

HTML templating with XSLT may be used to save data, too. For example, if you build a social network profile page using XSLT, alice.xml and bob.xml can reference the same profile.xsl stylesheet which converts the XML profile data to the rendered HTML page. Since the profile.xsl stylesheet can be cached, whenever a new profile is visited, only the profile data in XML needs to be transferred. Note that the templating ca…

XML+XSTL twitter clone in showHN in 3... 2... 1...

Re: Show HN: This website is valid JSON

#114

Post by mst »

rabidrat wrote: post #107
zelly wrote: post #99

Earlier quoted context omitted.

> Apparently web standards folks in the early 2000s thought the future was XML all the way down. It should have been, but just like the masses rejected LISP for its parens, the masses rejected XML for the closing tag. We could have avoided PHP and the zoo of MVC frameworks.

I tried programming in XSLT and it was not fun . I'm sure if it took off we'd have the equivalent of Clojure that compiled down to it, but by itself it is not a hacker's language, if you know what I mean.

SXML and SXSLT did that in scheme and were really rather good fun.

Re: Show HN: This website is valid JSON

#116

Post by DaiPlusPlus »

mstade wrote: post #106
Kimitri wrote: post #100

Earlier quoted context omitted.

XSLT is mainly used to transform XML into XML. The resulting document doesn’t have to be XML, though. I remember being assigned a task of parsing and importing a large XML document into a MySQL database. This was supposed to be done on PHP. I kind of felt repulsed by the idea of writing the parser in PHP (it would have been horrible). So, I used XSLT to transform the document into CSV and then just imported it using…

In the beginning of my career, about 15 years ago, I had a job working with a large auto parts retailer and they had all of their products in these massive XML files. We used XSLT to transform those into all kinds of things, including physical printed catalogues that would go in their stores. Obviously the XSLT didn't actually print catalogues, but we did turn them into some format that I forget now (maybe PDF!) that…

> Obviously the XSLT didn't actually print catalogues, but we did turn them into some format that I forget now (maybe PDF!) that we could just send straight to the printers.

Was Adobe FrameMaker involved?

Re: Show HN: This website is valid JSON

#117

Post by mst »

gpnt wrote: post #2

Hello everyone, I created a simple script that allows a website to be a valid JSON and still be able to present the information on the browser. Any feedback is appreciated!

You may also be entertained by my http://github.com/shadowcat-mst/App-plx/ project which has a script that produces a documentation page that's both valid HTML and a valid perl bootstrap installer for 'curl | perl -' purposes.

An example of the output is at http://trout.me.uk/perl/plx.html (that one's actually served over http, it's a demo, please don't blindly run it).

Re: Show HN: This website is valid JSON

#118

Post by habitue »

ardy42 wrote: post #60
habitue wrote: post #10

This is a really cool hack. > The JSON must contain only pure information without any concern about design or markup. Wellll.. I mean the json has markdown syntax in it. That's a lot nicer than html tags for markup, but it's still markup. In case anyone reading hasn't seen it before, browsers have a thing called XSLT built into them that does something similar for XML documents. You serve up your data as XML, add a t…

> Wellll.. I mean the json has markdown syntax in it. That's a lot nicer than html tags for markup, but it's still markup. Isn't markdown literally just HTML shortcuts for a limited set of common markup cases? IIRC, it's not uncommon to have to insert HTML tagging into markdown to get certain things to work.

Markdown compiles to html, and if I had to guess, it's probably a superset of html? (Maybe, possibly not all html is valid markdown, I haven't checked)

Assuming it's a superset though, the part I was talking about above was the (markdown - html) part, where markdown adds less noisy syntax for bolding, headings, lists etc.

Re: Show HN: This website is valid JSON

#119

Post by forgotmypw17 »

mst wrote: post #117
gpnt wrote: post #2

Hello everyone, I created a simple script that allows a website to be a valid JSON and still be able to present the information on the browser. Any feedback is appreciated!

You may also be entertained by my http://github.com/shadowcat-mst/App-plx/ project which has a script that produces a documentation page that's both valid HTML and a valid perl bootstrap installer for 'curl | perl -' purposes. An example of the output is at http://trout.me.uk/perl/plx.html (that one's actually served over http, it's a demo, please don't blindly run it).

Thanks for sharing, this is very cool. I'm also working on a Perl-HTML project, and I may reuse some of this :)
Post reply on HN