Hi Alex,
I did join the HackXmas last week and it was amazing experience. Thank you for your help setting it up.
I was part of team No: 3 and we did a prototype of the Family Roadmap component. I decide to build the component with SVG because it is responsive out of the box, it is easy to draw none-liner paths and animate them. I think the prototype worked quite well but it was far from being used for anything in production. So now, I would like to sync up with you on the requirements and API of the component and build it. I don't have experience with Angular (I am React dev) but I would like to build it as a WebComponent. Here are my few questions:
What is the min and max number of goals that can be on the map? I saw designs for 3, 4 and 5 goals.
What is the optimal/ideal size of the map in pixels?
How do you work with icons in your application? Are they used as images (png, svg, etc...), inline SVG-s or font icons, or something else?
We will need to map goal to icon and color to percentage completion for the roads. Is that something you do on the Back-end or I should do in on the Front-end?
We need to map number of goals to a backgorund image for the map. Is that something you do on the Back-end or I should do in on the Front-end?
Progress animation, how are we going to trigger it? When the whole map enters the view port or when the map is mounted on the page?
Once I know all of the above we can agree on the Component API and I will build it.
Hi Alex, I did join the HackXmas last week and it was amazing experience. Thank you for your help setting it up.
I was part of team No: 3 and we did a prototype of the Family Roadmap component. I decide to build the component with SVG because it is responsive out of the box, it is easy to draw none-liner paths and animate them. I think the prototype worked quite well but it was far from being used for anything in production. So now, I would like to sync up with you on the requirements and API of the component and build it. I don't have experience with Angular (I am React dev) but I would like to build it as a WebComponent. Here are my few questions:
Once I know all of the above we can agree on the Component API and I will build it.