Planning for WebThrottle Version2 #63
Comments
|
Why don't we move this to "discussions"? I need to learn a bit more since we have issues and projects and now discussions... It can be frustrating trying to figure out how it all works together. In general, I want to:
If anyone has ideas or knows more about the most efficient way to use GitHub, jump in. |
|
Sounds good! By the looks of it, there is a way to turn a discussion into a issue, so once a set of features emerge from a discussion, they can be turned into an issue and added to the project boards. Using discussions will make the dev process more transparent and allow people outside the org to give suggestions and feedback. I wonder if we should also get in the habit of PRing more and reviewing each others PRs, as this could scale easier as we get more people involved? |
|
Hi guys, has anyone considered using React for the V2? I have just started using DCC++ and when not playing with trains, I am a React web developer. JQuery is (was?) great but React takes a lot less code and is a lot easier. I could definitely help out. I will start a “Discussions” topic on React. |
|
It has been suggested that we use Vue instead of React. Personally, I would be reluctant to use anything that has anything to do with Facebook and they control React. I'm not saying it it out of the question, but I would have to be convinced. Of course at the moment, because I can't dedicate time to the project, whoever can help us advance it would need to be able to use the tools that work for them, while also not taking things in a direction, that when they leave, no one can pick up the code again. We would welcome your help. Send me your email to "frightrisk" at g-mail so I can add you to an email thread we have. I'll look for your discussion topic. |
|
Having looked through the current codebase, I wouldn't recommend rewriting using any other framework at this time. Given that there are people using this web app it would be wise to add a test suite to ensure functionality is not removed or broken, before moving forward. Unfortunately adding a test suite would come with the overhead of having to use a Node-based environment. I understand the friction that this may cause however these tools are widely used within the JavaScript community and are very well maintained. I'd add that keeping things simple is the key to maintainability. With a test suite in place, it would then become a lot easier to refactor the existing codebase. I would advocate for implementing ES-Modules - supported by all major browsers - in place of a frontend framework. |
|
I'm trying to coordinate the issues and discussion here into one discussion. We are ready to move forward and needs to see who can help |
|
@ManiAkasapu , @dcyoung-dev , @matt-vdv @cjmayo , @murfett-au posting here as well and hoping someone is still interested and can help us finish this project |
|
I'm still interested in this project as I believe it has the lowest barrier to entry for newcomers. I'd say the current codebase is incredibly difficult to maintain, with unrelated breakages when implementing changes. This led me to extract some functionality into separate modules, the serial connection and a command library, which in an alternative codebase has provided a lot of extra functionality. My previous comment around testing is still relevant however I would, in hindsight, advocate for a full rebuild using a modern JS framework, React being by far the most popular, Angular being the most opinionated and Vue being the most accessible. My advice would be to have a go at rebuilding in a framework with clear features outlined in a GH Project board. Each framework will have differing approaches to development, which will need to be agreed on before opening up for general code contributions. Feel free to look at https://github.com/cloudthrottle/cloudthrottle-web/ as an example of a throttle built in React - I wouldn't go down the event driven route if I'd to start over - too much complexity |
|
@dcyoung-dev I have looked at this. I can support you in getting the UI/UX for the the Throttle if you are fine with it. |
Are you saying that there is UI/UX planned out for V2? |
|
Let me know if you cannot access. I am moving things around. This is the first screen I designed. |
|
@ManiAkasapu this looks good - nice work. I'd be happy to build out a prototype and see how it feels 👌 |
|
@dcyoung-dev Great. @FrightRisk Can we add @dcyoung-dev (David?) To Webthrottle Discord dev channel? |
|
Also @murfett-au is a react developer. Could contribute to the project. May be he is waiting on Decision. |
|
If anyone is not on Discord, join there and send a DM to @FlightRisk (Long story, but I am FlightRisk most places, but FrightRisk (created for Halloween) on places where that ID was already in use. I'll see your DM and add you to the developer role |
Hi All,
Let's use this space for planning next WebThrottle version.
The text was updated successfully, but these errors were encountered: