Sponsored Content
Top Forums Web Development Notes with Ravinder on Badging System Development Part II Post 303028268 by Neo on Thursday 3rd of January 2019 07:22:04 AM
Old 01-03-2019
Update:

41 of 48 prototype badges done, or 85%.

Ravinder is working on the logic for a "consecutive days or forum activity" badge, which sounds cool, so that would be number 42 I guess, which will leave 6 "Reserved" badges left to do.

If one of those "Reserved" badges is allocated for the the mod system of member ranking; then that means:

Code:
41 Badges Done
1 Badge Under Development (Ravinder)
1 Badge for Mod Scoring / Points (Reserved)

This is real progress in a relatively short time.

If anyone has an idea for a badge, please post!

Thanks.
 

3 More Discussions You Might Find Interesting

1. What is on Your Mind?

New Badging System - Badges Prototype Beta 1 (Badges Only)

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

2. What is on Your Mind?

Status of Badging System - Beta 1

Dear All, Here is the current status of the badging system: The Beta 1 phase of the new badging system is close to completion. 42 prototype badges have been "allocated" 6 prototype badge slots are held in reserve The "alert you have new badges" prototype is running and is currently... (4 Replies)
Discussion started by: Neo
4 Replies

3. What is on Your Mind?

Badging System: UNIX.COM Bug Hunter Badge (New)

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
dat_ep_free(3DAT)				     Direct Access Transport Library Functions					 dat_ep_free(3DAT)

NAME
dat_ep_free - destroy an instance of the Endpoint SYNOPSIS
cc [ flag... ] file... -ldat [ library... ] #include <dat/udat.h> DAT_RETURN dat_ep_free ( IN DAT_EP_HANDLE ep_handle ) PARAMETERS
ep_handle Handle for an instance of the Endpoint. DESCRIPTION
The dat_ep_free() function destroys an instance of the Endpoint. The Endpoint can be destroyed in any Endpoint state except Reserved, Passive Connection Pending, and Tentative Connection Pending. The destruction of the Endpoint can also cause the destruction of DTOs and RMRs posted to the Endpoint and not dequeued yet. This includes com- pletions for all outstanding and in-progress DTOs/RMRs. The Consumer must be ready for all completions that are not dequeued yet either still being on the Endpoint recv_evd_handle and request_evd_handle or not being there. The destruction of the Endpoint during connection setup aborts connection establishment. If the Endpoint is in the Reserved state, the Consumer shall first destroy the associated Reserved Service Point that transitions the End- point into the Unconnected state where the Endpoint can be destroyed. If the Endpoint is in the Passive Connection Pending state, the Con- sumer shall first reject the associated Connection Request that transitions the Endpoint into the Unconnected state where the Endpoint can be destroyed. If the Endpoint is in the Tentative Connection Pending state, the Consumer shall reject the associated Connection Request that transitions the Endpoint back to Provider control, and the Endpoint is destroyed as far as the Consumer is concerned. The freeing of an Endpoint also destroys an Event Stream for each of the associated Event Dispatchers. Use of the handle of the destroyed Endpoint in any subsequent operation except for the dat_ep_free() fails. RETURN VALUES
DAT_SUCCESS The operation was successful. DAT_INVALID_HANDLE The ep_handle parameter is invalid. DAT_INVALID_STATE Parameter in an invalid state. The Endpoint is in DAT_EP_STATE_RESERVED, DAT_EP_STATE_PASSIVE_CONNECTION_PENDING, or DAT_EP_STATE_TENTATIVE_CONNECTION_PENDING. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard: uDAPL, 1.1, 1.2 | +-----------------------------+-----------------------------+ |MT-Level |Unsafe | +-----------------------------+-----------------------------+ SEE ALSO
libdat(3LIB), attributes(5) SunOS 5.11 16 Jul 2004 dat_ep_free(3DAT)
All times are GMT -4. The time now is 12:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy