Add ncurses like windowing support to monitor multiple products #705
Replies: 7 comments
-
|
As a rice lover (but not doer), I find this extremely cool. But the effort here I think will outweigh the return (in my opinion). As a workaround (not optimal, of course) would be to spin up a couple tmux/screen windows and boot each one with a different config (inline, as files I don't think are supported right now, but easy to do). BUT! That being said, I think something like this is important and @michaelzhou1987 has been working on a VueJS frontend. It's in its early stages, but I think this type of work would appeal to more people rather than us nerds. What are your thoughts? |
Beta Was this translation helpful? Give feedback.
-
|
Ok, real talk time I guess! I think the best route for a long life of this project is to break the backend and frontend up. Have the backend support a nice REST API + maybe something like WebSockets. Then UI creation can be whatever a UI author wants it to be. I think a lot of normal users would LOVE a web ui like what you already referenced...and crazy nerds (like me!) would dig some terminal view. |
Beta Was this translation helpful? Give feedback.
-
I agree 100% This also warrants transitioning the discussion to: #706 In my opinion. I think keeping the two "projects" (if you will) in the same repository makes sense as well. I think using WS is a great candidate for keeping open connections and live feeding. Someone has implemented GraphQL which is also pretty cool #700.
I think this is pretty cool as well -- being able to create an API for those wanting to consume streetmerchant is also pretty sweet. That would expand its usage quite a bit. But I think some default UI and terminal would equally be important for those who are using on their own. I think we're at a really good turning point here and think the project can go in many directions. |
Beta Was this translation helpful? Give feedback.
-
This was me. Not sure if this is the place for this discussion to be continuing, but IMO creating a separate API becomes more and more essential as scale/complexity grow; the data and the views shouldn't be so tightly coupled when the data starts getting complex.
I think this is a great idea. A default client being included serves a few purposes:
|
Beta Was this translation helpful? Give feedback.
-
Yes, yes, yes! I don't want to push micro services here (completely separate projects), but I think separating these implementations will be much better. (Kind of #706; and I've mentioned a bit more in the Discord.) This is one of the side effects you see in this project as it initialized as a gist. I do have an org for streetmerchant and there is opportunity there as well (backend, frontend, etc), but I think as of now, we can let it grow naturally to that if it becomes that. |
Beta Was this translation helpful? Give feedback.
-
I agree with this; the size of this project isn't big enough to warrant splitting into micro services. A monorepo with separation of frontend/backend within it is easier to manage for something of this size. If somehow things grow crazy dramatically crazy fast, that bridge can be crossed when we come to it. |
Beta Was this translation helpful? Give feedback.
-
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Beta Was this translation helpful? Give feedback.
-
Description
Now...I might be crazy, but would it be nice to have an ncurses based layout to have separate "windows" in the shell showing tracking of each product type?
Possible solution
Could use a library like https://github.com/chjj/blessed to render the layout.
Beta Was this translation helpful? Give feedback.
All reactions