ferbivore/nestview-old

HTML viewer for nested content, Python library and tools.

nestview-old's Issues

rename nestview to nvbase

split nestview.html up and set up a build system

See #4.

• rip out and modularize the JS and CSS needed to render a viewer (see #2)
• create a template including them, to be used by the Python modules
• have a script combine and minify them, either at build- or run-time

add --sanitize option to nvxml

Right now, nvxml will gladly take something like this:

<description>
<table> <tr><td> <a href="http://www.reddit.com/r/sysadmin/comments/2gekpj/a_sysadmin_learns_his_network_has_been/"><img src="http://b.thumbs.redditmedia.com/valdQffaCLvBpYSR7xo0UirenADh2TfFpXcoUdIVOMU.jpg" alt="A Sysadmin learns his network has been infiltrated by the NSA (english subs)" title="A Sysadmin learns his network has been infiltrated by the NSA (english subs)" /></a> </td><td> submitted by <a href="http://www.reddit.com/user/tdobson"> tdobson </a> <br/> <a href="http://www.spiegel.de/video/nsa-und-gchq-hoeren-telekommunikationsunternehmen-ab-video-1521330.html">[link]</a> <a href="http://www.reddit.com/r/sysadmin/comments/2gekpj/a_sysadmin_learns_his_network_has_been/">[31 comments]</a> </td></tr></table>
</description>

And turn it into this:

The reason being that the HTML viewer uses .innerHTML to create text nodes. Which is great if you want to add in formatting and links in there, but unfortunately there's no way to tell it to use .textContent instead, for situations like this. We need one.

nvToFolder can't handle excessive/infinite nesting

NVSimple, or rather nvToFolder, seems to be unable to preview instances of NVSimple or NVCommon. Instances of other objects (that I've tested) work fine.

refactor nvcommon's interactive functionality

Right now, opening a server to look at some data looks like this:

from nvcommon import nvServer, nvToTree
nvServer(nvToTree(data))

This is too unpythonic for my tastes. Here's how it should look like:

from nvcommon import NVSimple
NVSimple(data).serve()

You should also be able to so things like .save(filename) or .open().

make the HTML viewer embeddable

Right now, it's a sprawling mess of mashed up HTML and JavaScript. I want to reduce it to something easy to embed in other web apps, callable with something like nestview.viewer(htmlnode, data). Maybe have an API for modifying data on the fly and responding to clicks, so we can have some interactivity.

nestview.Folder: expandable nodes always appear before text nodes

Right now, the way Folder is defined in nestview.py, expandable nodes will always appear before text nodes when exporting. We need a way to mix node types - which is to say, stop differentiating between subfolders and items.

This requires no changes to the viewer.

move nvToTree and nvGenericToFolder into nvbase

nvcommon was started as a library for building nvtree-like command line tools; nvToTree and nvGenericToFolder (which should be renamed nvToFolder, by the way) are broader in scope and belong in nvbase.

turn nestview into a proper Python library

• rename nestview to nvbase, see #6
• add an __init__.py (done as of c0f2340)
• move HTML to another folder and possibly set up a build system, see #1
• rip out JS as detailed in #2
• move utilities to another folder