Open prastut opened 6 years ago
@digi0ps @jeremyphilemon @Tanay2112 divide between yourself what work you are going to start. Ideally level of ownership if high produces the best results -> so take issues which are disparate in nature.
I will take up View 1 Task 1. So I have to remove the navBar's html and use D3 to render the title using text. Right?
That's correct.
On Aug 12, 2017 12:20, "Sriram" notifications@github.com wrote:
I will take up View 1 Task 1. So I have to remove the navBar's html and use D3 to render the title using text. Right?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/prastut/bubble-frontend/issues/41#issuecomment-321962023, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzbBgx0SgMC8zYb3TTKZZPWeY96EVDqks5sXUszgaJpZM4O0YSE .
Right now we have 2 views in place for the viz. Real estate documentation can be found here: https://github.com/prastut/bubble-frontend/blob/master/docs/VIZ.MD#charts
For testing, sample URL's that you can use:
The whole data: https://bubble.social/get-webview?match_id=0b808074-7aa8-11e7-949c-0669e02bb0da&team_id=0b808075-7aa8-11e7-949c-0669e02bb0da&name=arsenal
The view with less data, helps to make quick changes to frontend and check: https://bubble.social/get-webview?match_id=0b808074-7aa8-11e7-949c-0669e02bb0da&team_id=0b808075-7aa8-11e7-949c-0669e02bb0da&name=arsenal&end_timestamp=1502026867
Replace
https://bubble.social/
withlocalhost:8000/
:3View 1: Webview
Right now the biggest problem is that D3 works with SVG elements which are not same as HTML elements eg: SVG has it's own coordinate system and DOM has it's own. So a y coordinate in SVG land is different than a top coordinate in HTML land.
https://www.sitepoint.com/how-to-translate-from-dom-to-svg-coordinates-and-back-again/
Task 1
Make all elements be rendered by D3. Since 95% of the view is being rendered by D3, it makes no sense to render the rest of the page with HTML. Right now as you can see in the above image that our events timeline is being overlapped by the scatter+chart timeline and a whole lot of problems due to this mixup. Currently we render things like this:
Work:
params
object to JS Global Namespace here. All you need to is use that and render theTask 2
yPos
function. So each element has an own Y Pos. Rather than hardcoding elements by placing them iteratively by hand (i.e hardcoding values like yPos(100)) you can use the getBoundingRect and use it's dimensions to render charts. Specifically the render flow would look like:View 2: Video Demo's
Task 1: Setup and getting used to:
npm i
&&npm start
.Semantics which separate the webview and the video demo view would be that there is no main big barchart inside the webview but there is a players chart which shows the top 2 trending players barchart. Please look at the images again and again to draw inferences.
Work:
Task 2: Get the video demo online.
The means don't matter. I just want the demo online.