search

NeXTs / Clusterize.js

Tiny vanilla JS plugin to display large data sets easily
https://clusterize.js.org
MIT License
7.22k stars 412 forks source link

How about hierarchical table structure #67

Closed bharatpatil closed 8 years ago

bharatpatil commented 8 years ago

Will this work for hierarchical table structure which offers collapse and expand?

NeXTs commented 8 years ago

Hi I need some examples of your hierarchical structure There are cool project with "collapse and expand" functionality based on div's. Table structure may be implemented in same manner

bharatpatil commented 8 years ago

I'm currently using fancytree with it's table extension. You can find example here: http://wwwendt.de/tech/fancytree/demo/index.html#sample-ext-table.html

NeXTs commented 8 years ago

Oops, my fault, forgot to add links take a look http://cheton.github.io/infinite-tree/examples.html#/filebrowser

infinite-tree powered by FlatTree and Clusterize.js

NeXTs commented 8 years ago

How it's going?

bharatpatil commented 8 years ago

Currently exploring how that can be integrated with fancytree

bharatpatil commented 8 years ago

@NeXTs - sorry for my less knowledge, this might be a very silly question, however I would like to know, why fetchMarkup() does not return original DOM elements, instead of returning outerHTML?

NeXTs commented 8 years ago

@bharatpatil fetchMarkup function was designed for internal use only. outerHTML needed because internally clusterize works with strings rather than DOM elements

bharatpatil commented 8 years ago

@NeXTs - I've modified it to work with actual DOM elements, because I want that to work with Fancytree because it has data associated with DOM elements and I'm very thankful to this wonderful library, it is handling 110160 nodes without any problem.

Though the new change made is maintaining one more array of actual DOM nodes, in addition to rows. I may have to consider some improvements memory wise because now if I open task manager of Chrome it is consuming 1.2 GB of Memory.

NeXTs commented 8 years ago

1.2 GB of Memory :open_mouth: Not sure this may be solved (if you want to actually store all DOM nodes in memory)

NeXTs commented 8 years ago

@bharatpatil Do you still have some questions or we can close this issue?

bharatpatil commented 8 years ago

Can close it.

On Fri, Jul 15, 2016 at 8:07 PM +0530, "Denis Lukov" notifications@github.com wrote:

@bharatpatil Do you still have some questions or we can close this issue?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.