search

adilyalcin / Keshif

Keshif - Data Made Explorable (Prototype)
https://keshif.me
BSD 3-Clause "New" or "Revised" License
458 stars 123 forks source link

calendar heatmaps and D3 module integration in general #155

Closed magneticnorth closed 7 years ago

magneticnorth commented 8 years ago

Appreciate this very powerful software. How would one get calendar heatmaps in keshif? In general, is there a recommended way to cleanly integrate a D3 module found on the side of the road somewhere? Stephen

adilyalcin commented 8 years ago

Hi Stephen,

Keshif is not aimed to be a modular programming interface. Such extensions are still possible, and can be implemented given the motivations of a specific project, and generalized properly to become a part of the "whole solution". Overall, I want to make sure that Keshif works seamlessly for its main use cases. That means that the way multiple components work together also should be seamlessly implemented. Achieving "seamless" modularity is even a greater challenge. I can say Keshif will not make it "easy" to integrate ineffective or poorly executed charts and designs as arbitrary d3 modules.

That said, I think one simple approach to think about calendar is to think of each dimension separately: One summary can be day of week, or the other can be time of day, for example. You get the overview of both components first, and can query and filter to see the relations across, and use existing visualization modalities to make the insights richer. That of course does not reveal all the combinations as a matrix-like view/heatmap. But, that's the first step I'd take in such a scenario, and it would provide a working interface to this data.

If you need an integrated solution for a specific "calendar" view and have resources to support the development, please let me know in person.

Adil

magneticnorth commented 8 years ago

Adil, thank you for explaining your approach. Also I will try again with the case to find some funding for this work. Companies are funny, and I’m not in an executive position any more so I don’t know about their budget situation. I do hope you find some interesting things to do and I would be more than happy to write a recommendation if it doesn’t have to be too lengthy. Stephen

On Jul 14, 2016, at 3:10 PM, Adil notifications@github.com wrote:

Hi Stephen,

Keshif is not aimed to be a modular programming interface. Such extensions are still possible, and can be implemented given the motivations of a specific project, and generalized properly to become a part of the "whole solution". Overall, I want to make sure that Keshif works seamlessly for its main use cases. That means that the way multiple components work together also should be seamlessly implemented. Achieving "seamless" modularity is even a greater challenge. I can say Keshif will not become a project where arbitrary d3 modules can be integrated with minimal effort. Keshif will not make it "easy" to integrate ineffective or poorly executed charts and designs.

That said, I think one simple approach to think about calendar is to think of each dimension separately: One dimension can be day of week, or the other can be time of day, for example. You get the overview of both components first, and can query and filter to see the relations across, and use existing visualization modalities to make the insights richer. That of course does not reveal all the combinations as a matrix-like view/heatmap. But, that's the first step I'd take in such a scenario, and it would provide a working interface to this data.

If you need an integrated solution for a specific "calendar" view and have resources to support the development, please let me know in person.

Adil

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/adilyalcin/Keshif/issues/155#issuecomment-232763069, or mute the thread https://github.com/notifications/unsubscribe/ACtWz5gn4I0gSp8c7xKuLyYAkjJIozFrks5qVonAgaJpZM4JLo60.