GitHub - NE-Robotics/Advanced-Subsystems Currently you have to just publish to maven local I’m dealing with a 403 error using github packages right now that I’m trying to resolve, any help at all or advice would be extremely helpful.
403 is “forbidden”, so your token likely doesnt have access to push packages. This SO post seems to cover it pretty well
That’s ironically the post I used to try and figure it out, I’m using the repository token built in same thing I use for my other grade package.
Seems like a good start. Although, and I’m not 100% sure about this, but I think if your package requires revlib, phoenix, navx, etc, then anyone trying to install it would need to have all of those vendordeps installed as well, which would be pretty rare. So doing it as a package may be a little difficult if that is actually the case.
How much bloat is installing both Rev & CTRE libraries from the poll I just did both are used by at least 85% of teams, I know the NavX isn’t as common but it’s a support library for one device but I could make it an optional variant of the library.
CTRE is giant, takes about a minute to download and install only CTRE libs on first build.
Well unfortunately CTRE is required at they’re the second most popular vendor providing software for themselves and vex.
During this offseason I am working on a revamp of 3015’s pit display, it will allow full customization from the app/gui plus some additional features. You can find it here and a project board. Feel free to open issues with feature requests. I am currently busy with school atm so its on hold for a bit.
Alex mind hooking that API into the Advanced Subsystem package since they’re built off the same original code base, also I’m going to go Linux test this so you can change that commit message from untested.
Are there pictures available of the pit display in action?
That was just some testing I didn’t get pictures of it in the pits at RIT but I’m sure someone from 3015 has a few
This is the display in “Event Mode” showing the current rankings and such.
I do not have any pictures of the pit in “Robot Check Mode” but I will see if any of the students have any good ones.
The problem isn’t necessarily bloat, just an annoyance for teams to have to download other libraries they won’t use when installing it. If you just make a note in the installation steps that you need those other vendordeps it shouldn’t be a huge deal.
Apologies in advance for how much of a headache it will probably be lol. Our pit TV is 1920x1080 so we just hardcoded everything for that size instead of spending the time to make it react to different screen sizes properly.
Definitely seems interesting though, looking forward to seeing what you make of it. If you need any help with anything feel free to reach out.
I have a question relating to your network tables integration with Flutter.
One project I have for this summer is to make a Shuffleboard alternative using flutter. One widget I want to have in it is a tree showing all of the entries and topics in network tables, in the same way Shuffleboard has. I looked through the code for your dashboard and pit display, and I’m confused as to how I would use the network tables library you wrote to be able to be able to put all the NT data into some sort of tree widget.
I was very impressed by your dashboard and pit display when I looked through it, and its given me a lot of inspiration for the dashboard I plan on making.
Additionally, if you have any suggestions or advice let me know!
There should be functionality in there to subscribe to topic names. If you subscribe to all topic names at the root /
then the NT server will send you the name of every topic. You can store those internally to create your tree and then subscribe to the topics themselves if you want to show data.
Got it
Another thing I want to be able to display is a tree of the topics. From what I researched earlier, the only way of creating a tree display is by using a library since I don’t think flutter has it built in. Is there a specific one you would recommend? They all seem to be the same
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.