| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
References #195
This is the first dumb-ass implementation of the collector-api.
It actually works fine for write AS IS, but has 0 safties. But I'm thinking the
API itself is reasonably stable and ready for testing.
I will need to extend it for dhcp-specific stuff, and the plan is to
create a secondary table with metadata (hidden from the user) and a few
other nice things.
Also, indexes. We need indexes. Obviously.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sort of.
It's two issues at once, related:
1. API: The problem here was that the old way of updating tags simply didn't
use actual JSON, but just sent "'foo','bar','baz'" as a text string. This
seems dumb so I've made it send actual JSON now - just like the "placement"
field. This meant updating the API. And it's not pretty, but it works.
2. Front: I've simplified nms-types a bit (hopefully to provide to simple
methods: either get/set the raw value, or get/set strings. There was a bug
where we sent text-encoded json instead of real json, and the reason
was a confusion between when we're dealing with JSON and when we're
dealing with strings. Now we are explicit.
This makes the nmsEditRow-thing slightly uglier, but it needs to be fixed
properly either way. In the future, we should provide renderers and editors
based on types, e.g.: Placement-editor could start as a general-purpose
JSON-editor, and the "switch reference" should be a drop-down.... etc.
Fixes #202
|
|
|
|
|
|
|
|
|
|
|
| |
The integration is a hack, but a first step. I will eventually remove all the
code in nms-info-box, but I needed a simple test.
This also demonstrates how to add a new switch.... simply hit edit, then change
the name. It aint pretty, and shouldn't work like it does today, but it's
a decent example.
Also, had to fix the backend again now that I actually tested the write-api :D
|
|
|
|
|
|
|
|
| |
Fixes #150
Fixe #88
Closes #3
Probably lots of bugs introduced, will fix ASAP.
|
| |
|
| |
|
|\ |
|
| | |
|
|/
|
|
| |
Still work in progress
|
|
|
|
| |
Lots of cruft
|
| |
|
|
|
|
|
|
| |
Fixes #84
It's really stupid simple, but it will work.
|
|
|
|
|
| |
You can now use "foo" to find a switch called foo, but not also the ones
called foobar foobar1, etc
|
|
|
|
| |
Needs a lot of work, including the API side, possibly also the schema.
|
|
|
|
|
|
|
|
| |
First up: Add a switch, get a log entry.
This might require some filtering in the GUI eventually. This is why the
user is set to 'system', even when we have an actual user that triggered
the event.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It still needs to be integrated with switches/info box, but this is a good
start.
Shows the last 5 log messages in an overlay on the map, with the rest
visible in an oplog tab.
Fixes #20
|
|
|
|
| |
References #54
|
|
|
|
| |
Still lots to do
|
| |
|
|
Fetched from tgmanage.
|