question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[UPDATE] Development Progress

See original GitHub issue

So we’ve been receiving a lot of feature requests lately. I discovered however, that the components in the current implementation aren’t sufficiently decoupled to allow for easy extensibility. Here’s what currently happens (as we’d expect from a functional program): Step 1: make_components() makes groups for every component required. Step 2: draw() renders the svgs for all them Step 3: At some further point in time when values are updated, run_animation() follows a similar pattern.

This came out of the project’s origins and incremental feature updates. But UI in general is better describable with OOP. I’ve been trying out some restructuring; we could instead go for some initial registering for any chart component like so (ChartComponent implements a component’s properties): screen shot 2017-12-08 at 10 15 43 pm copy

Then BaseChart could just follow a life-cycle. That’d mean every component will know what it has to do, without the chart needing to bother: screen shot 2017-12-08 at 10 20 03 pm

Here’s some of the stuff I was able to add without much effort (more on the way):

Mixed charts:

screen shot 2017-12-05 at 5 19 02 am

Multiple Axis:

screen shot 2017-12-08 at 9 55 42 pm

Most of the logic has now been transferred to utils, and no chart has more than 200-250 LOCs. As we look forward to test coverage, this’ll help the project to have predictable (and less) tests. And the contribution guidelines to have a well-defined code structure.

These will constitute v0.1.0, which will be released by the end of this month.

Apologies for the delay in updates, but I feel this detour was needed before any more feature additions. Haven’t been able to catch up with the current issues and pull requests; will go ahead release a first cut with most of the fixes and merges by the in the coming week, tagging the in-progress ones in the meantime. Thanks for your patience 😃

Will keep posting updates, check this space. You can track the progress on the develop branch 😄

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:26
  • Comments:7 (1 by maintainers)

github_iconTop GitHub Comments

11reactions
tomconcommented, Jan 20, 2018

@pratu16x7 am getting concerned, It’s now Jan 20th, nothing for almost 3 weeks on dev branch + over 6 weeks ago you said:

These will constitute v0.1.0, which will be released by the end of this month.

Can we have an update where things are or when v0.1 might be released please? Many thanks

6reactions
pratu16x7commented, Mar 3, 2018

Greetings all.

It is a pity this didn’t go quite as planned, and I had to abandon the earlier pure OO model for a functional approach at the micro-component(drawBar, drawLine etc) level, leaving the component approach for macros (the axis component and so on) that update/animate collectively. Looks like this works fairly well, and I’m working on porting the aggregation charts (Pie/Percentage) in a similar fashion over the weekend (reflected on develop lately). This was far too many threads I have ever handled, and I am happy that it came about in the end.

Apologies for the less than active maintenance of an appreciated project, I admit it could have taken a lot less time. I would say I would be shipping 1.0.0 beta on Monday, but it would probably be better to ship first and announce later. This sure would close many issues as it would probably create, along with some existing PRs. Thank you all for your support on it 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

8 steps to write an effective project status report - Asana
Project status reports are timely updates on the progress of your projects. Written concisely, project reports offer high-level information ...
Read more >
Project Status Reports - ProjectManager
A project status report is a document that describes the progress of a project within a specific time period and compares it against...
Read more >
Project Status Report Template & Example - TeamGantt
Download a simple project status report template, and use these examples to write weekly or monthly status updates you can send to clients...
Read more >
Project Status Report Checklist - Creating Your Weekly Report
As a project manager, you need to create regular project status reports to update stakeholders on project progress.
Read more >
A Project Update Template That Your Executives Will ...
What a project update template is used for. A project status report template is a standardized document you use to show the progress...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found