Read on Twitter
https://github.com/neomjs/neo
Pick">https://github.com/neomjs/ne... the next roadmap item:
1) means lazy loading inside the dist env.
#javascript #100DaysOfCode #301daysofcode #webdev #html #html5 #css3 #css #ux #code #DigitalTransformation #OSS #programming #software #WebApp #webworker #frontend #ui #framework
Pick">https://github.com/neomjs/ne... the next roadmap item:
1) means lazy loading inside the dist env.
#javascript #100DaysOfCode #301daysofcode #webdev #html #html5 #css3 #css #ux #code #DigitalTransformation #OSS #programming #software #WebApp #webworker #frontend #ui #framework
To be very clear on this one:
The winning option only counts in case there are at least 10 votes for it.
In case you need more input, feel free to ask here (reply).
#javascript #100DaysOfCode #301daysofcode #webdev #html #html5 #css3 #css #ux #code #DigitalTransformation
The winning option only counts in case there are at least 10 votes for it.
In case you need more input, feel free to ask here (reply).
#javascript #100DaysOfCode #301daysofcode #webdev #html #html5 #css3 #css #ux #code #DigitalTransformation
1) Enhanced build processes
The dev mode allows to use dynamic imports, meaning:
import();
This way you can lazy load whole JS modules (packages). E.g. the Docs app can lazy load example apps in dev mode.
This topic is about making this work for the dist versions as well.
The dev mode allows to use dynamic imports, meaning:
import();
This way you can lazy load whole JS modules (packages). E.g. the Docs app can lazy load example apps in dev mode.
This topic is about making this work for the dist versions as well.
More in detail:
We need to split the main thread from the workers build using target: & #39;web& #39;.
Then we need to set the target for the other threads to & #39;worker& #39; and get the split chunking to work.
Without this, webpack would add multiple versions of the same modules.
We need to split the main thread from the workers build using target: & #39;web& #39;.
Then we need to set the target for the other threads to & #39;worker& #39; and get the split chunking to work.
Without this, webpack would add multiple versions of the same modules.
Added detailed descriptions for each of the 3 roadmap voting options.
Please retweet this thread!
#javascript #100DaysOfCode #301daysofcode #webdev #html #html5 #css3 #css #ux #code #DigitalTransformation #OSS #programming #software #WebApp #webworker #frontend #ui #framework
Please retweet this thread!
#javascript #100DaysOfCode #301daysofcode #webdev #html #html5 #css3 #css #ux #code #DigitalTransformation #OSS #programming #software #WebApp #webworker #frontend #ui #framework
In case you think a not listed option should become the primary focus for now instead => reply ;)
#javascript #100DaysOfCode #301daysofcode #webdev #html #html5 #css3 #css #ux #code #DigitalTransformation
#javascript #100DaysOfCode #301daysofcode #webdev #html #html5 #css3 #css #ux #code #DigitalTransformation
The latest demo video is this one:
https://www.youtube.com/watch?v=8lqNVaoGNdU
https://www.youtube.com/watch... href="https://twtext.com//hashtag/javascript"> #javascript #100DaysOfCode #301daysofcode #webdev #html #html5 #css3 #css #ux #code #DigitalTransformation #OSS #programming #software #WebApp #webworker #frontend #ui #framework
https://www.youtube.com/watch?v=8lqNVaoGNdU
2) Mobile Support
Global config to optionally add touch events to the doc body (like tap, rotate, swipe).
As the next step, polish the biggest demo app (the covid dashboard) to be fun to use on mobile.
We could do more (e.g. mobile docs app), but for this i need more manpower.
Global config to optionally add touch events to the doc body (like tap, rotate, swipe).
As the next step, polish the biggest demo app (the covid dashboard) to be fun to use on mobile.
We could do more (e.g. mobile docs app), but for this i need more manpower.
3) Buffered Grid
The current table implementation is super lightweight and a great fit for smaller amounts of data.
If you want to render 1k, 10k or even 100k rows
=> performance nightmare.
Buffered rendering means to only show the visible rows & virtualised scrolling.
The current table implementation is super lightweight and a great fit for smaller amounts of data.
If you want to render 1k, 10k or even 100k rows
=> performance nightmare.
Buffered rendering means to only show the visible rows & virtualised scrolling.
Got pinged on Slack to add more input for the 3 options.
There we go:
There we go:
Going to tag some of my friends here. In case you get tagged, please retweet the top post of this thread.
After 1 year & 9 months I literally burned ALL of my personal savings to get Neo to this point. Since the project is not sustainable (lacking sponsors), it is no longer
After 1 year & 9 months I literally burned ALL of my personal savings to get Neo to this point. Since the project is not sustainable (lacking sponsors), it is no longer
