1000 issues is of course a huge number for a single project. Several hundres however not. And if you have multi-project boards 1000 is a number that can be pretty normal. And if you try to fish out a really old issue by sloppy remembering it's title I would still need to create/show it. It basically is not efficient to remove and create lots of (complex and not-absolute positioned) DOM-Elements in real time (like it is needed for real time search). Another way could be to "buffer" a number of elements that then get different content based on the currently visible issues. Maybe the entire canvas-way turns out as inefficient or inoparable, then I'll try to find a way around the problems faced in the prototype before in another way. However for now canvas seems very good and is utterly interesting.
Okay. After getting deeper into the integration I found out that canvas for now is no option. The initial performance gain gets zeroed out if redraw areas are not highly optimized and getting that done right would mean a lot of effort. I will try to roll the thing up with HTML/CSS again and experiment with other solutions instead. However it was a nice trip to canvas land.
let him burn
for example, ionic has this in their collection-repeat i think or some other similar directive http://ionicframework.com/docs/api/directive/collectionRepeat/
I would be very happy about submissions. Get creative. :sparkles:
I currently do not understand the purpose.
during build time
also the object can be generated dynamically
If everything goes well I might have a video demonstrating the new board next week.
Just found this: https://www.npmjs.com/package/mithril-express
@StephanHoyer I just found out that my performance bottleneck was mithrils diffing algorithm, not browser rendering. The browser handles 1000 cards pretty well, but mithrils diff will hickup on it on every "click". I now used
{ subtree: "retain" } and it's buttersmooth again. Guess I now have to find all the cases, where a redraw is needed.
Did not watch the code in detail, though
I'm still working on the new board. It still has some glitches, that's why I wasn't able to showcase a video demonstration of it yet. It hopefully will be ready next week so I can show.
It took more time then expected but here is the preview of the new issue board
waffle sucks, we need replacement
Did you got my newsletter?
it took not more then 2 hours. I really start to like static site generators.
awesome to hear :P
But it decouples public site and app and that is what I wanted to achieve in the first place, while making the public site super simple.