rteslaru / meteor-circular-progress Goto Github PK

I am trying to use 3 progress circles on one page but they are all collating at the first call of {{> circularProgress}}. From what I can see, using multiple {[> circularProgress}} results in non-unique id of "#svg-progress-container".

Is there a way I can specify unique ids of the containers? Or Could you please advise on a workaround.

Many thanks for a great package otherwise.

It would be great if I could set progress via template helpers instead of session variables. This would allow me to use this in an {{#each}} loop, for instance, and just pass a 'percent complete' (perhaps as a decimal?), instead of trying to figure out how to set up session variables for each possible progress indicator.

Example:

{{> circularProgress outerPadding=0 spacer=0}}

Those values are set to the default value, as 0 is a falsey value. The code should check on undefined values instead of falsey values.

So far so good! Much easier to use than nprogress! Thank you!

Hi rteslaru,

I am currently experimenting with meteor a lot and was very happy to come across your package on atmosphere. I appreciate the work you obviously put into it and in particular value the documentation you created. To such a greater extend I am confused by not getting the circular progress in my app. I added the package as described and did put {{> circularProgress}} into the template I want it to be but the only thing I am getting is an empty div.
I tried different ways of integrating it even trying to apply the template definition directly in the html calling the template but was not successful.

I fiddled a bit with node-inspector and even downgraded meteor to 0.8.0.1 as this was the version you suggested but I was not succeeding.
I imagine this as a newbie problem and hope you find the time to give a hint on what needs to be done.

Thanks in advance,
mitschwimmer

Hey,

I'm using this to count down time, and I've noticed a serious hit to performance when I'm changing the progressPercent in session by the second.

I'm not sure how to fix this issue, maybe it's just how session works?

Anyways, I thought I'd bring this to your attention!

Thanks for the great package nonetheless