-
-
Notifications
You must be signed in to change notification settings - Fork 182
Components specs #1
Comments
HospitalRun/hospitalrun-frontend#387 requested a dashboard like feature which will require the use of some graphs and charts. Possible React libraries for charts/graphs:
|
One note on those libraries is that they're all fairly heavy for low bandwidth internet connections (see bundlephobia.com), which is the same concern raised about socket.io. I found something called Frappe charts which is lighter and may be worth considering. bundelphobia. |
Ok, I think that the best way is to add always bundlephobia link, when suggesting libs. Can you please modify your comments? |
A non-socket.io WebSocket option for the chat is ws. |
@fox1t I've updated my comments with bundlephobia links. |
@jackcmeyer and @lancerutkin check the repo now. We decided to use tsdx and it is one of the best devexperience I've ever seen! |
@fox1t does it make sense to break out each one of these components into an issue with specific requirements so the community can start tackling them? |
@jackcmeyer @irvelervel @fox1t can we update this list? or close the issue? |
Here are listed must-have components. The list will be expanded and improved over time. If a component depends on a 3rd party component, it must be wrapped it in a way that it could be replaced with no effort, if we want to change that dependency in the future: we need to expose our public API. Some dependency are still missing because we need to test some libraries before deciding.
Components we need:
The text was updated successfully, but these errors were encountered: