-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare control panel for the rocket launch #13
Conversation
Any news here? |
Read through the PR and looks great to me! I noticed lots of |
@rreusser I found out with surprise that these styles were duplicated 3 times! So I merged them. |
Hi guys @rreusser @freeman-lab! |
Hey @dfcreative, thanks for the work you've put into this! Have looked at the code and taken it for a spin. A couple high-level thoughts, as I didn't get to comment further on #10. I'm psyched that you want to use this in Looking at this PR, I'd prefer to separate all the code clean-up (e.g. which looks fantastic overall and is super helpful!) into one PR, and then consider any new features one at a time, with the fair warning that I might be resistant! Of what's here:
Sorry if this all sounds annoying! And if you just want to move full steam ahead, that's totally cool too! You could fork starting from here and make |
@dfcreative Sorry was slow taking a look at it! Traveling at the moment (yayy montreal! 😄) and wifi is sparse. Looks like the repo has disappeared though. Hate to think your work/time has been wasted. I like the idea in general of a lightweight drop-in for datgui, so if there's a consensus on what could lead to the perfect (or good-enough) solution here, I'm still glad to pitch in. At a high level, FWIW, things that prevent control-panel being the perfect solution for me:
At any rate, giving prama a try and will continue to try to iterate. 👍 |
All good. I've been struggling to find the time to use these things as much as I'd like, so I'm (unfortunately) not in an urgent rush. It's a solution I'd like to see refined though, so just hated to think you put a bunch of effort in that didn't find the right fit. This is not the place for it, but because I hate to open a bunch of issues on your WIP repo, two small things on prama: needs |
Yeah, ok, thanks for the feedback, I am working on that! |
@rreusser totally agree, and didn't want the effort from @dfcreative to be wasted either! I'm also all for adding the input specific events, so will try to put that back in to Anyway, also excited to see where these various efforts go, and really appreciate the contributions from both of you! 👍 👍 |
Hi @rreusser @freeman-lab.
Here I have a list of changes discussed in #10 and related to #12.
Technically you can skim through commits, they are narrative, but in case, I list the main changes here.
input[type=number]
for value instead ofdiv
<label>
tags pointing to proper inputs, to allow clicking on themhelp
andinput
properties to componentshack
font - it saves extra-request in case if user decides to use his own font. Alsohack
was not loading by default due to error in code (style
instead oflink
tag). One option would be using google-fonts, but that is a separate feature.Please review!
Looking forward to starting work on prama.
PS I think that there might be some other patches, like fixing ids, minor interactions or something, so if you don’t really mind my code style, I would really appreciate if you grant me contributor’s access to the repo and npm, to avoid delays.