VOLUME LXXII 02/09/2021
Please welcome Michael Sidenstick, our newest addition to the Nioxus Team and Programmer/Consultant.
Michael, hailing from Cincinnati, Ohio, is a student at The Ohio State University. He is majoring in Computer Science and Engineering. Right now he is learning about best practices in coding and systems, algorithms, and computer hardware. Michael liked that software development is diverse as far as careers go. He likes to problem solve, and got into technology because he wanted a career where he could always continue to learn new skills. “I’ve always wanted to work for a company that I can contribute a lot to, but that I can also learn a lot from, because I think that’s what’s most important to me.”
When asked about his experience as Nioxus so far, Michael said, “It’s still pretty early on and I’m still learning the fundamentals of the system. It’s been very pleasant so far and I’ve enjoyed getting to meet people and learning how the company runs.”
Michael is an Eagle Scout, the highest rank a BoyScout can earn. He achieved this by coordinating and implementing the building of an accessibility trail at his favorite local park, Winton Woods.
Michael’s hobbies include intramurals, especially volleyball and basketball, and games with his friends. He especially likes board games and card games. Michael’s favorite board games are Avalon and Settlers of Catan.
– Cleaner Code –
There are many different ways to write a coding block- some clearer than others. One way that I’ve found improves readability is by not using a variable in my table records. Both codes work, but I find the latter to be cleaner.
Using a variable:
Let i := create ‘Table Name’; i.‘Field 1’ := “Something”; i.‘Field 2’ := “Something2”; popupRecord(i)
Not using a variable:
– ID as Field Name –
I have seen people creating their own ID field in Ninox. They simply create a text or number type field and name it ID. DON’T DO THAT! 🙂
Ninox uses a hidden internal ID that is not visible unless we use a formula type field to call it. If I create a text or number field called “ID” (it is not case sensitive) and somewhere else in my code I try to refer to the internal ID, it won’t be found because of the conflicting ID field I created. If you need to create your own ID field, name it something slightly different like “InvoiceID”.
We are often asked, how can I get data out of my old (non-Ninox) database into my new Ninox app without losing all the links and relationships?” Another common question is “how can I convert my flat Excel spreadsheets into a relational Ninox database?”
Join us for this week’s Ninox Learning Lab on the 11th at 12:00pm EST and we’ll give you all the answers!
Template of the week
Travel Journal and Mileage Log
Did you know that Nioxus has built over 135 templates which are available to all Standard, Deluxe and Premier Nioxus members?
While your databases should have logical architecture and bug-free coding, nothing takes your work to the level of excellence like a masterful user interface design (“UI”). Table forms that are simple, consistent and pleasing to the eye make an enormous difference in how the user experiences a database. Let’s look at a few techniques you can use to take your database from bland looking to beautiful.
Background color – Are you still using the Ninox default color for your tables? If so, you’re missing out on an enormous opportunity to enhance your table forms. Think about what color the user might find pleasing. Consider a color that coordinates with a logo they are using for their business, the colors in their web site or their business cards. Make sure it isn’t so light that the user has a hard time distinguishing the form’s fields on the form, but don’t use anything so intense that it’s annoyingly loud or garish. It also needs to look good next to the Ninox blue of the navigation pane on the left side of the database window. To try a color, place a tab on the form and drag it to the top of the table’s field list. Then set the tab’s color property to your desired color by entering its RGB value. Unless you have a very good reason, it’s best to use the same background color for all forms in your database.
Object colors – Continue your color scheme by coordinating the color of buttons, headers, borders and lines with your background color. Instead of using the default blue for buttons, for example, use the style function to give them a color that works well with your chosen background. Click the style box, click background color and then select RGB. Enter the RGB value for the color you want to use and then click once on the resulting color. Press OK and save your work.
Field styling – Apply a consistent style to your fields where doing so tells the user what to expect. Do you style your formula fields in such a way that the user recognizes them as fields where no input is needed or allowed? Are you using the tooltip function to explain the purpose of fields whose intended use is not obvious? You should be. A confused user is not a pleased user, so do whatever you can to make your fields predictable and understandable from one field to another and from one form to another.
Symmetry – Line up fields so as to avoid a scattershot look. It’s okay to add fields at random when you first create your forms, but, before you present them to the user, take time to line up your fields and group them into logical sections. Don’t crowd too many things into too small an area on the screen. Think about where on the form headings might make things more organized.
Hidden elements – The ability to hide fields and form objects using the “display field only if” function is a gift. Use it. There are a variety of techniques for hiding and exposing fields and other form objects based on criteria of your choosing. For example, if the user selects an option in choice field 1, choice field 2 is exposed – otherwise it’s hidden. Experiment with this kind of thing to simplify your forms.
HTML – Not only is there a style function for most fields, but also you can make use of HTML to extend your styling options. This is useful in creating striking headers and titles where information is displayed with emphasis placed on particular elements. The basics of HTML are easily available online and don’t take long to learn.
Logical Thinking – Put important things first and take time to think about those who will use your form for the first time. Will the purpose of the form be obvious, and will the user instantly understand what to do? If not, slow down and take time to see it through their eyes and arrange the form accordingly.
Here’s an example of a nicely formatted form.
The form’s title was created using this bit of HTML in a formula field:
The color and the font size were applied using the field’s style function. The field’s label is set to “hidden”.
The background color of the form works nicely with the theme of the database. Notice how the color of the title’s font matches the color of the buttons and looks nice against the background color? The fields are nicely lined up with the most important information on top.
Any of these design techniques will pay immediate dividends in improved form design and better user experience.
Artificial intelligence is a part of the computer sciences that make computers and different machines replicate a human’s natural intelligence. AI also enables machines and computers to think and learn from these experiences. The difference is that human learning may take a few times where as AI is a one time learning experience. Artificial intelligence works by enabling devices to become cognizant of its environment and take the necessary actions in order to successfully achieve its goals.
AI uses machine learning techniques like intense learning and artificial neural networks to learn from given data sets and use those learnings to achieve its goals. These algorithms must be capable of enhancing themselves by learning new techniques from the actions that worked well in the past. And, some algorithms are capable of updating/writing other algorithms of their own from previous experiences and learnings. Now the one worry with AI, at a very minimum, there must be some type of a safeguard. But what if the AI makes a mistake? We must be able to use AI and still not violate a person’s human & legal rights.
For us to live happily with the technology we create, we have to make sure that the technology serves us and and not the other way around.
All logos, trademarks and names are the protected property of Nioxus Corporation or their respective owners.
“Ninox,” “Ninox Database” and the blue Ninox owl eye logo are the property of Ninox Berlin and are used with permission.