mirror of
https://github.com/tuxis-ie/nsedit.git
synced 2026-04-26 16:15:54 +03:00
[GH-ISSUE #27] Move menu/ appearance #14
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
pull-request
question
question
upstream
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nsedit#14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @piwats on GitHub (Feb 19, 2015).
Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/27
Hello,
I'm using/testing nsedit for a week now and I noticed how strange the menu which consists at this time only of 3 menu entries looks like.
Wouldn't it be nicer if the three menu items could move in a horizontal bar on top of the nsedit view? Also it might be useful if this bar could be fixed during scrolling.
The other thing I noticed about nsedit: DNS entries/records should be printed in a monospace font.
The records are technical, so having a monospace font there would fit it probably better.
Is this possible to change?
@tuxis-ie commented on GitHub (Feb 24, 2015):
Feel free to write a patch for the menu. The menu is hardly used, so I don't see the use of investing time in it.
As for the fonts, that should be doable to make configurable.
@piwats commented on GitHub (Apr 17, 2015):
Here is a quick and dirty patch:
@tuxis-ie commented on GitHub (Apr 17, 2015):
Welcome to github, where you can create PR's ;) 👍
@piwats commented on GitHub (Apr 17, 2015):
Sorry for the inconvenience - this will be the next step :)
@piwats commented on GitHub (Apr 17, 2015):
That was easier as I expected - see pull request #44 .
@tuxis-ie commented on GitHub (Apr 17, 2015):
Yeah, I personally don't like this. But, there nothing a css class and a configoption can't fix. Can you incorporate that in your PR?
@piwats commented on GitHub (Apr 17, 2015):
What do you mean by a configoption?
something like:
in index.php:
together with $cssadditions = TRUE; in config.inc.php and all the css changes in css/additions.css?
@tuxis-ie commented on GitHub (Apr 17, 2015):
Well, I wouldn't call it additions. But I'd say something like "$menutype = 'horizontal|vertical';" And add cssclasses to the appropriate elements.
@piwats commented on GitHub (Apr 17, 2015):
Done, see my PR and Pull Req..
@tuxis-ie commented on GitHub (Jul 30, 2015):
Closing with PR #44