f.navbar #153
Merged
f.navbar #153
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When visible-sm was the main size that the responsive css is/was using, it would freeze when trying to forever resize the font to make sure it doesn't take up too much room. Now it doesn't even check that. That caused problems and now it does not!
Originally, we didn't have to add form-control to the form elements to get them styled, but with the new version of bootstrap we did. The past commit since we've upgraded bootstrap, I had to just temporarily put some old bootstrap code in the CSS file. That CSS is now gone.
Layers don't actually work yet, but they will.
Also I put the message/edit/delete buttons on a second line so they don't get in the way with long names.
Layers now sort of work, but needs to be the ability to hide some of them. For instance, if I only want to view Active VPS nodes, it shouldn't show all Active nodes and all VPS nodes, it should only show Active VPS nodes.
|
@SashaCrofter has written up a short document outlining how we can use the layers efficiently. Until they are used efficiently, |
tilelayer, all, temp (NEW), newuser. Temp is going to be used for the layers/filter layers.
Also I moved around a large function that should go at the bottom of the file instead of the top because it was in the way of things. And lastly, I added a "filter" variable at the top and an empty `filterLayer` function that is going to be filled with code soon.
Also I'm beginning to do the ui section of the layers/filters. I feel like filters is a better thing to call it because we'll be filtering nodes out that don't match the criteria of your selected filters.
I need to think about the issue for a bit.
Not sure if that's what we want to do, but I'll leave it be for now. Not hard to change.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The branch f.navbar should be pulled in, and it fixes a lot of problems that we have been having.
This pull request does not, however, create full support for potential nodes, or implement searching. Those are all to come in the near future, but not yet.