|
|
Sponsored Content
The Lounge
What is on Your Mind?
Status of Badging System - Beta 1
Post 303028620 by Neo on Friday 11th of January 2019 09:28:01 AM
01-11-2019
Administrator
I have been testing the badging system, and it works really good.
The only hiccup (with I have a work-around for) is that when I add new badges to the grid in the future, which includes enabling the "Reserved" badges, this causes a change in the hash values and also in the arrays, so a "new badge alert" is issued.
I created a work-around which reverses the order of the PHP array_diff_assoc() call and then compares the size of the two arrays (in forward and reverse order), and so when I bring a new badge on line to the grid, there is no alert generated.
So, I may bring all of the badges "online" even though they are now in "reserve" so that all badges will have a default color assigned; and then assigning a new color to a member (assigning the badge a state) will insure a proper alert.
These are small nuances from testing, and actually, could just bring them all on line and turn off alerts for a day or two, and then turn alerts back on, and it would work out as well.
At some point, when we code a new live application, we need to say "it's good enough" and stop trying to make the code perfect, and I'm getting close to that point.
Basically, the badging system and the alerts work fine and I continue to test them for exceptional situations, and basically, not 100% as I would like, but very good
The only hiccup (with I have a work-around for) is that when I add new badges to the grid in the future, which includes enabling the "Reserved" badges, this causes a change in the hash values and also in the arrays, so a "new badge alert" is issued.
I created a work-around which reverses the order of the PHP array_diff_assoc() call and then compares the size of the two arrays (in forward and reverse order), and so when I bring a new badge on line to the grid, there is no alert generated.
So, I may bring all of the badges "online" even though they are now in "reserve" so that all badges will have a default color assigned; and then assigning a new color to a member (assigning the badge a state) will insure a proper alert.
These are small nuances from testing, and actually, could just bring them all on line and turn off alerts for a day or two, and then turn alerts back on, and it would work out as well.
At some point, when we code a new live application, we need to say "it's good enough" and stop trying to make the code perfect, and I'm getting close to that point.
Basically, the badging system and the alerts work fine and I continue to test them for exceptional situations, and basically, not 100% as I would like, but very good
These 2 Users Gave Thanks to Neo For This Post:
|
|
6 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi
i m new to this forum as well as UNIX. I've got an assignment but i don't know how can I start it.
can anyone please help to tell me how can I start it?
I added here few lines from my assignment.
In industry, it is common for a single organisation to provide technical support for a... (0 Replies)
Discussion started by: moco
0 Replies
2. Shell Programming and Scripting
Hi, I am trying to access and read certain lines from a configuration XML file on multiple servers (within the LAN). Fortunately the file name and path is always the same for all servers. An example extract of the file is as follows:
<DUMMY-SMSC>false</DUMMY-SMSC> ... (2 Replies)
Discussion started by: jaz8212
2 Replies
3. Homework & Coursework Questions
1. Edit a script named update.sh that generates status.html in your web directory: ~/public_html/.
I need to write specific commands to show each specific item
2. The generated webpage should include information related to:
UNIX : kernel version of ed-lab server
USER : number of users on the... (13 Replies)
Discussion started by: devinj
13 Replies
4. What is on Your Mind?
Today I mapped out the new badging system using FA icons, Beta 1 in no particular order except a 6 x 8 grid:
https://www.unix.com/members/1-albums215-picture991.png
The prototype HTML code for this layout:
<style>
.fa-badge-grid {
font-size: 1.5em;
}
.row {
... (38 Replies)
Discussion started by: Neo
38 Replies
5. Web Development
Part II: Current PHP file Beta 73 Not Optimized:
<?php
$version = 73;
$query = "SELECT * FROM " . TABLE_PREFIX . "user WHERE userid='" . $uid . "'";
$usertable = $db->query_read_slave($query);
$modaluser = $db->fetch_array($usertable);
$modaluser = gmdate("d F Y", $modaluser);
$modaluser... (48 Replies)
Discussion started by: Neo
48 Replies
6. What is on Your Mind?
I have moved the bug badge out of reserve and into the main stream. Basically, I will assign a color level like the others, based on who has made a good actionable bug report for UNIX.COM. "Good" means screenshots, links, and even details from web dev tools our the HTML source code. So far,... (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT OSF1
status
Status(4) Kernel Interfaces Manual Status(4) NAME
Status, .Status - Contains information about the status of the uucp program contacts with remote systems SYNOPSIS
/usr/spool/uucp/.Status DESCRIPTION
The /usr/spool/uucp/.Status directory contains information about the status of the uucp program contacts with remote systems. For each remote system contacted, the uucp program creates a file in the .Status directory called SystemName, where the SystemName file is named for the remote system being contacted. In the .Status/SystemName file, the uucp program stores the following information: Time of the last call in seconds Status of the last call Number of retries Retry time, in seconds, of the next call The times given in the .Status/SystemName file are expressed as seconds elapsed since midnight of January 1, 1970 (the output of a time system call). Thus, the retry time is in the form of the number of seconds that must have expired since midnight of January 1, 1970 before the system can retry. To make this entry in the .Status/SystemName file, uucp performs a time system call, adds 600 seconds, and places the resulting number of seconds in the file. If the last call was unsuccessful, the uucico daemon will wait until the time specified by the retry time before attempting to contact the system again. RELATED INFORMATION
Daemons: uucico(8) Functions: time(3) delim off Status(4)