Recent changes to Example Programs

Example Programs modified by Karl H. Beckers

Karl H. Beckers — Wed, 05 Sep 2018 06:54:17 -0000

--- v12
+++ v13
@@ -49,6 +49,7 @@
 This is a quickly hacked together and totally ugly demo web application to spark off some imagination. You can download it from the ["griffin-web-app" folder](https://sourceforge.net/projects/griffin/files/griffin-web-app/) in the files section.

 Use it like this with a NWN:EE installation that has subdirectories in the server vault by player public key:
+
 1. Install [tomcat](http://tomcat.apache.org/) 7.x somewhere
 2. Edit the file `conf/tomcat-users.xml` below where you extracted the tomcat archive. Add lines like the following: `<role rolename="player"> <user username="player1" password="ready" roles="player">`
 3. Deploy the griffin-web-app, ideally by creating a directory `webapps/griffin` in the tomcat installation and extracting the war file there: `jar xvf griffin-web-app-<version>.war`
@@ -59,11 +60,12 @@
 8. DON'T RESTART TOMCAT WHILE YOU PLAY AROUND WITH THIS (because everything gets stored in an automatically created in-memory database that will get wiped with a restart.) 

 The use case that is implemented here is where you want to allow people to manage their own player characters, but need to be sure they actually _own_ the account. You likely don't want to manually process people's claims that account XYZ is theirs. A challenge-response mechanism springs to mind, like this:
+
 1. You have this web application that you log in to somehow (we are using the most simple way provided by tomcat, here, but login mechanisms could easily be switched out.)
-1. The application now knows you are some person, but needs to verify you acutally own a certain account / public key before it can let you do stuff with it, so it allows you to claim a public key and will then ask you to log in to your account and create a character with a random first and last name
-1. After you do that, you can to back to the web application where you will see a list of accounts you have claimed and where you can either request a new challenge or tell the system you're done and that it should check.
-1. The web application then goes and checks if a character with the requested names is present and marks the account as confirmed for your user.
-1.  After that, the web application could allow you to do whatever with the characters in your account, e. g. delete them, change description, etc. etc. (Though not everything that's technically possible might be a good idea, too.)
+2. The application now knows you are some person, but needs to verify you acutally own a certain account / public key before it can let you do stuff with it, so it allows you to claim a public key and will then ask you to log in to your account and create a character with a random first and last name
+3. After you do that, you can to back to the web application where you will see a list of accounts you have claimed and where you can either request a new challenge or tell the system you're done and that it should check.
+4. The web application then goes and checks if a character with the requested names is present and marks the account as confirmed for your user.
+5.  After that, the web application could allow you to do whatever with the characters in your account, e. g. delete them, change description, etc. etc. (Though not everything that's technically possible might be a good idea, too.)

 This is all a long way from complete. It doesn't even do conflict resolution for when multiple people claim an account. But feedback is very welcome.
 And if you're a UI hacker and want to turn this into a cool HTML5 AJAX thing that pulls everything from the game resources to eventually become a full-blown graphical character editor, go for it :P
</version></user></role>

Example Programs modified by Karl H. Beckers

Karl H. Beckers — Wed, 05 Sep 2018 06:53:31 -0000

--- v11
+++ v12
@@ -50,7 +50,7 @@

 Use it like this with a NWN:EE installation that has subdirectories in the server vault by player public key:
 1. Install [tomcat](http://tomcat.apache.org/) 7.x somewhere
-2. Edit the file `conf/tomcat-users.xml` below where you extracted the tomcat archive. Add lines like the following: <role rolename="player"> <user username="player1" password="ready" roles="player">
+2. Edit the file `conf/tomcat-users.xml` below where you extracted the tomcat archive. Add lines like the following: `<role rolename="player"> <user username="player1" password="ready" roles="player">`
 3. Deploy the griffin-web-app, ideally by creating a directory `webapps/griffin` in the tomcat installation and extracting the war file there: `jar xvf griffin-web-app-<version>.war`
 4. Change the path in `webapps/griffin/WEB-INF/classes/nwn.properties` to point to your server vault directory
 5. start tomcat
</version></user></role></user></role>

Example Programs modified by Karl H. Beckers

Karl H. Beckers — Wed, 05 Sep 2018 06:53:03 -0000

--- v10
+++ v11
@@ -50,13 +50,13 @@

 Use it like this with a NWN:EE installation that has subdirectories in the server vault by player public key:
 1. Install [tomcat](http://tomcat.apache.org/) 7.x somewhere
-+ Edit the file `conf/tomcat-users.xml` below where you extracted the tomcat archive. Add lines like the following: <role rolename="player"> <user username="player1" password="ready" roles="player">
-+ Deploy the griffin-web-app, ideally by creating a directory `webapps/griffin` in the tomcat installation and extracting the war file there: `jar xvf griffin-web-app-<version>.war`
-+ Change the path in `webapps/griffin/WEB-INF/classes/nwn.properties` to point to your server vault directory
-+ start tomcat
-+ browse to http://localhost:8080/griffin/home.jsf
-+ log in with user name "player1" and password "ready"
-+ DON'T RESTART TOMCAT WHILE YOU PLAY AROUND WITH THIS (because everything gets stored in an automatically created in-memory database that will get wiped with a restart.)
+2. Edit the file `conf/tomcat-users.xml` below where you extracted the tomcat archive. Add lines like the following: <role rolename="player"> <user username="player1" password="ready" roles="player">
+3. Deploy the griffin-web-app, ideally by creating a directory `webapps/griffin` in the tomcat installation and extracting the war file there: `jar xvf griffin-web-app-<version>.war`
+4. Change the path in `webapps/griffin/WEB-INF/classes/nwn.properties` to point to your server vault directory
+5. start tomcat
+6. browse to http://localhost:8080/griffin/home.jsf
+7. log in with user name "player1" and password "ready"
+8. DON'T RESTART TOMCAT WHILE YOU PLAY AROUND WITH THIS (because everything gets stored in an automatically created in-memory database that will get wiped with a restart.) 

 The use case that is implemented here is where you want to allow people to manage their own player characters, but need to be sure they actually _own_ the account. You likely don't want to manually process people's claims that account XYZ is theirs. A challenge-response mechanism springs to mind, like this:
 1. You have this web application that you log in to somehow (we are using the most simple way provided by tomcat, here, but login mechanisms could easily be switched out.)
</version></user></role></version></user></role>

Example Programs modified by Karl H. Beckers

Karl H. Beckers — Wed, 05 Sep 2018 06:51:01 -0000

--- v9
+++ v10
@@ -50,13 +50,13 @@

 Use it like this with a NWN:EE installation that has subdirectories in the server vault by player public key:
 1. Install [tomcat](http://tomcat.apache.org/) 7.x somewhere
-1. Edit the file `conf/tomcat-users.xml` below where you extracted the tomcat archive. Add lines like the following: <role rolename="player"> <user username="player1" password="ready" roles="player">
-1. Deploy the griffin-web-app, ideally by creating a directory `webapps/griffin` in the tomcat installation and extracting the war file there: `jar xvf griffin-web-app-<version>.war`
-1. Change the path in `webapps/griffin/WEB-INF/classes/nwn.properties` to point to your server vault directory
-1. start tomcat
-1. browse to http://localhost:8080/griffin/home.jsf
-1. log in with user name "player1" and password "ready"
-1. DON'T RESTART TOMCAT WHILE YOU PLAY AROUND WITH THIS (because everything gets stored in an automatically created in-memory database that will get wiped with a restart.)
++ Edit the file `conf/tomcat-users.xml` below where you extracted the tomcat archive. Add lines like the following: <role rolename="player"> <user username="player1" password="ready" roles="player">
++ Deploy the griffin-web-app, ideally by creating a directory `webapps/griffin` in the tomcat installation and extracting the war file there: `jar xvf griffin-web-app-<version>.war`
++ Change the path in `webapps/griffin/WEB-INF/classes/nwn.properties` to point to your server vault directory
++ start tomcat
++ browse to http://localhost:8080/griffin/home.jsf
++ log in with user name "player1" and password "ready"
++ DON'T RESTART TOMCAT WHILE YOU PLAY AROUND WITH THIS (because everything gets stored in an automatically created in-memory database that will get wiped with a restart.)

 The use case that is implemented here is where you want to allow people to manage their own player characters, but need to be sure they actually _own_ the account. You likely don't want to manually process people's claims that account XYZ is theirs. A challenge-response mechanism springs to mind, like this:
 1. You have this web application that you log in to somehow (we are using the most simple way provided by tomcat, here, but login mechanisms could easily be switched out.)
</version></user></role></version></user></role>

Example Programs modified by Karl H. Beckers

Karl H. Beckers — Wed, 05 Sep 2018 06:50:16 -0000

--- v8
+++ v9
@@ -50,9 +50,7 @@

 Use it like this with a NWN:EE installation that has subdirectories in the server vault by player public key:
 1. Install [tomcat](http://tomcat.apache.org/) 7.x somewhere
-1. Edit the file `conf/tomcat-users.xml` below where you extracted the tomcat archive. Add lines like the following:
-`<role rolename="player">
-<user username="player1" password="ready" roles="player">`
+1. Edit the file `conf/tomcat-users.xml` below where you extracted the tomcat archive. Add lines like the following: <role rolename="player"> <user username="player1" password="ready" roles="player">
 1. Deploy the griffin-web-app, ideally by creating a directory `webapps/griffin` in the tomcat installation and extracting the war file there: `jar xvf griffin-web-app-<version>.war`
 1. Change the path in `webapps/griffin/WEB-INF/classes/nwn.properties` to point to your server vault directory
 1. start tomcat
</version></user></role></user></role>

Example Programs modified by Karl H. Beckers

Karl H. Beckers — Wed, 05 Sep 2018 06:49:03 -0000

--- v7
+++ v8
@@ -51,10 +51,8 @@
 Use it like this with a NWN:EE installation that has subdirectories in the server vault by player public key:
 1. Install [tomcat](http://tomcat.apache.org/) 7.x somewhere
 1. Edit the file `conf/tomcat-users.xml` below where you extracted the tomcat archive. Add lines like the following:
-```
-<role rolename="player">
-<user username="player1" password="ready" roles="player">
-```
+`<role rolename="player">
+<user username="player1" password="ready" roles="player">`
 1. Deploy the griffin-web-app, ideally by creating a directory `webapps/griffin` in the tomcat installation and extracting the war file there: `jar xvf griffin-web-app-<version>.war`
 1. Change the path in `webapps/griffin/WEB-INF/classes/nwn.properties` to point to your server vault directory
 1. start tomcat
</version></user></role></user></role>

Example Programs modified by Karl H. Beckers

Karl H. Beckers — Wed, 05 Sep 2018 06:47:53 -0000

--- v6
+++ v7
@@ -51,8 +51,10 @@
 Use it like this with a NWN:EE installation that has subdirectories in the server vault by player public key:
 1. Install [tomcat](http://tomcat.apache.org/) 7.x somewhere
 1. Edit the file `conf/tomcat-users.xml` below where you extracted the tomcat archive. Add lines like the following:
-`<role rolename="player">
-<user username="player1" password="ready" roles="player">`
+```
+<role rolename="player">
+<user username="player1" password="ready" roles="player">
+```
 1. Deploy the griffin-web-app, ideally by creating a directory `webapps/griffin` in the tomcat installation and extracting the war file there: `jar xvf griffin-web-app-<version>.war`
 1. Change the path in `webapps/griffin/WEB-INF/classes/nwn.properties` to point to your server vault directory
 1. start tomcat
</version></user></role></user></role>

Example Programs modified by Karl H. Beckers

Karl H. Beckers — Wed, 05 Sep 2018 06:47:02 -0000

--- v5
+++ v6
@@ -49,12 +49,12 @@
 This is a quickly hacked together and totally ugly demo web application to spark off some imagination. You can download it from the ["griffin-web-app" folder](https://sourceforge.net/projects/griffin/files/griffin-web-app/) in the files section.

 Use it like this with a NWN:EE installation that has subdirectories in the server vault by player public key:
-1. Install tomcat 7.x somewhere
-1. Edit the file conf/tomcat-users.xml below where you extracted the tomcat archive. Add lines like the following:
-    <role rolename="player">
-    <user username="player1" password="ready" roles="player">
-1. Deploy the griffin-web-app, ideally by creating a directory "webapps/griffin" in the tomcat installation.
-1. Change the path in "webapps/griffin/WEB-INF/classes/nwn.properties" to point to your server vault directory
+1. Install [tomcat](http://tomcat.apache.org/) 7.x somewhere
+1. Edit the file `conf/tomcat-users.xml` below where you extracted the tomcat archive. Add lines like the following:
+`<role rolename="player">
+<user username="player1" password="ready" roles="player">`
+1. Deploy the griffin-web-app, ideally by creating a directory `webapps/griffin` in the tomcat installation and extracting the war file there: `jar xvf griffin-web-app-<version>.war`
+1. Change the path in `webapps/griffin/WEB-INF/classes/nwn.properties` to point to your server vault directory
 1. start tomcat
 1. browse to http://localhost:8080/griffin/home.jsf
 1. log in with user name "player1" and password "ready"
</version></user></role></user></role>

Example Programs modified by Karl H. Beckers

Karl H. Beckers — Wed, 05 Sep 2018 06:39:37 -0000

--- v4
+++ v5
@@ -46,26 +46,26 @@

 ##GriFFin Web-App

-While I am slowly expanding the files GriFFin can  read and write (and there's a LOT of cleanup to do, increase test coverage, fix findbugs findings, etc.) I've just quickly hacked together a little (totally ugly) demo web application to spark off some imagination. You can download it from the "griffin-web-app" folder in the files section.
+This is a quickly hacked together and totally ugly demo web application to spark off some imagination. You can download it from the ["griffin-web-app" folder](https://sourceforge.net/projects/griffin/files/griffin-web-app/) in the files section.

-You use it like this with a NWN:EE installation that has subdirectories in the server vault by player public key:
+Use it like this with a NWN:EE installation that has subdirectories in the server vault by player public key:
 1. Install tomcat 7.x somewhere
-2. Edit the file conf/tomcat-users.xml below where you extracted the tomcat archive. Add lines like the following:
+1. Edit the file conf/tomcat-users.xml below where you extracted the tomcat archive. Add lines like the following:
     <role rolename="player">
     <user username="player1" password="ready" roles="player">
-3. Deploy the griffin-web-app, ideally by creating a directory "webapps/griffin" in the tomcat installation.
-4. Change the path in "webapps/griffin/WEB-INF/classes/nwn.properties" to point to your server vault directory
-5. start tomcat
-6. browse to http://localhost:8080/griffin/home.jsf
-7. log in with user name "player1" and password "ready"
-8. DON'T RESTART TOMCAT WHILE YOU PLAY AROUND WITH THIS (because everything gets stored in an automatically created in-memory database that will get wiped with a restart.)
+1. Deploy the griffin-web-app, ideally by creating a directory "webapps/griffin" in the tomcat installation.
+1. Change the path in "webapps/griffin/WEB-INF/classes/nwn.properties" to point to your server vault directory
+1. start tomcat
+1. browse to http://localhost:8080/griffin/home.jsf
+1. log in with user name "player1" and password "ready"
+1. DON'T RESTART TOMCAT WHILE YOU PLAY AROUND WITH THIS (because everything gets stored in an automatically created in-memory database that will get wiped with a restart.)

 The use case that is implemented here is where you want to allow people to manage their own player characters, but need to be sure they actually _own_ the account. You likely don't want to manually process people's claims that account XYZ is theirs. A challenge-response mechanism springs to mind, like this:
 1. You have this web application that you log in to somehow (we are using the most simple way provided by tomcat, here, but login mechanisms could easily be switched out.)
-2. The application now knows you are some person, but needs to verify you acutally own a certain account / public key before it can let you do stuff with it, so it allows you to claim a public key and will then ask you to log in to your account and create a character with a random first and last name
-3. After you do that, you can to back to the web application where you will see a list of accounts you have claimed and where you can either request a new challenge or tell the system you're done and that it should check.
-4. The web application then goes and checks if a character with the requested names is present and marks the account as confirmed for your user.
-5.  After that, the web application could allow you to do whatever with the characters in your account, e. g. delete them, change description, etc. etc. (Though not everything that's technically possible might be a good idea, too.)
+1. The application now knows you are some person, but needs to verify you acutally own a certain account / public key before it can let you do stuff with it, so it allows you to claim a public key and will then ask you to log in to your account and create a character with a random first and last name
+1. After you do that, you can to back to the web application where you will see a list of accounts you have claimed and where you can either request a new challenge or tell the system you're done and that it should check.
+1. The web application then goes and checks if a character with the requested names is present and marks the account as confirmed for your user.
+1.  After that, the web application could allow you to do whatever with the characters in your account, e. g. delete them, change description, etc. etc. (Though not everything that's technically possible might be a good idea, too.)

 This is all a long way from complete. It doesn't even do conflict resolution for when multiple people claim an account. But feedback is very welcome.
 And if you're a UI hacker and want to turn this into a cool HTML5 AJAX thing that pulls everything from the game resources to eventually become a full-blown graphical character editor, go for it :P
</user></role>

Example Programs modified by Karl H. Beckers

Karl H. Beckers — Wed, 05 Sep 2018 06:36:44 -0000

--- v3
+++ v4
@@ -42,15 +42,7 @@
 -v, --verbose                Print verbose output.
 ```

-
-
-
-
-
-https://sourceforge.net/projects/griffin/files/griffin-cli/
-
-
-
+Build from source or [download here](https://sourceforge.net/projects/griffin/files/griffin-cli/)

 ##GriFFin Web-App