Random Ramblings on LabVIEW Design
-
KVR9
on:
Some Boring Statements
-
ManuelSebald
on:
LabVIEW and Linux Review
-
swatts
on:
LabVIEW in a Box!
-
Taggart
on:
Influence
-
swatts
on:
TMiLV (This Month in LabVIEW) - Definitely NOT another podcast!
-
swatts
on:
AI is going to take our jobs - everyone should panic now.
-
swatts
on:
LabVIEW Firmata - Easy control of Arduino Microcontrollers
-
Dhakkan
on:
LabVIEW OpenSUSE Leap15.5 on a LattePanda V1
-
swatts
on:
LabVIEW and Linux - Intro
-
swatts
on:
It's time for me time.
Recovery Part 3 of 3 Bug Reporting
The final piece in the recovery puzzle is bug reporting.
I didn't fancy designing the whole thing from scratch so instead I searched around for a MySQL schema for such things, step up bugzilla. I was quite pleased with how I got hold of it. On a virtual machine I loaded a turnkey linux bugzilla system I then did a MySQLDump of the schema and loaded it onto my VPS.
I wanted to have bug reporting in our General Template and as a standalone application. I downloaded some MySQL LabVIEW VIs that work very nicely and stuck these in my project and wrapped them as I normally do.
Then I put in a bug reporting screen.
If you are doing a reasonable amount of MySQL I advise coughing up for Navicat, it saves so much time on creating and testing queries.
We can then take the generated SQL and make this in LabVIEW.
We just replace the variables in the query with %s and away we go.
The other aspect of Bug Reporting is to see the status of the reported bugs.
I put in a filter that controlled my queries, preloaded with all the status's (already loaded this for the previous screen, so just a menu item on the string)
Another right-click menu item allows us to edit the bug.
Because I don't want to maintain the bug reporting screen on all my projects I make it into an executable and have it as separate project. I call it using the command line and use command line arguments to pass the project name.
This is the bug reporting screen for our Project Management Utility. I add some posh splash screens etc to the build, the final bit of the puzzle is to get it to update itself. Here's how
Phew that was a few hours work! Thanks codespaces and your careless disregard for simple security.
If anyone is going a similar direction, leave a comment, I am happy to give what advise/help I can.
Now where was I with Open Document Format???????
Lots of Love
Steve
PS I'm only implementing a part of bugzilla at the moment, it's a big lump of database and quite nicely designed too. Looking at the schema is a good place to start.
