GitXplorerGitXplorer
b

screenconnect-achievements-extension

public
1 stars
0 forks
0 issues

Commits

List of commits on branch master.
Unverified
110a6db395fc7645be4157b9d03dd68c6e922fd8

first go at file locking... may be preemptive

bbrandon-irl committed 7 years ago
Unverified
49c4244dc5fe1cd1fd03ac0325bea00a5ef7a8ff

Changed the panel title to include the users display name

bbrandon-irl committed 7 years ago
Unverified
0622ec3cad436676b5c2454c2a4e845dc2c79dd2

80% of the way with the achievement message thing

bbrandon-irl committed 7 years ago
Unverified
e0b1a0ca312ef1f2109c5cf8f11081b3d9d124d1

Fixed bug, renamed achievement, and started on the snackbar thing

bbrandon-irl committed 7 years ago
Unverified
a501fd42bf4b1a064f05b0c2d96bca39ff0e99b8

changed how we set the visibility

bbrandon-irl committed 7 years ago
Unverified
47c78ee4207b013a32906114fece7ef1c9312910

Some ui updates

bbrandon-irl committed 7 years ago

README

The README file for this repository.

Known Issues

* #1 PROBLEM: session events don't include user info! Just "host" info. So if a user sets a display name, we get that string instead of the actualy unique user name, which we were going to rely on
* Updating the achievement definitions will be hard after the Extension is released. It's gonna take code to add them. That can get hairy... Maybe we can just add a web method to do it or something so that we can call it at any time
* The extension doesn't use the security context or anything. Just gets user data based on the username. Assuming usernames are unique this should be fine. But anyone is really able to get or update anyone elses achievements. The key this in the triggers mitigates this

Achievement Ideas

* Made a Session Group
* Added item to toolbox
* Ran toolbox item (elevated)
* Connected to Session
* Customized resoures(web/app)
* Created, Connected, and Ended certain # of support sessions
* # of total Host Connections
* # of connections for a single guest
* Publish an extension
* Edited database maintenance plan
* Created one of each session type
* Created a new role (admin only)
* Set up new user source (admin only)
* On-prem uptime
* Sending feedback to the survey