mbk/pesterchum
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Formatting consistency for README and TODO.

Browse source
This commit is contained in:
karxi 2016-12-23 12:53:21 -05:00
parent 0a073afda2
commit e657138dad
2 changed files with 89 additions and 84 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
README.mkdn
View file

@ -57,10 +57,12 @@ necessary.
* [Download from main branch][pchum-zip] * [Download from main branch][pchum-zip]
5. Unzip Pesterchum somewhere easily-accessible. 5. Unzip Pesterchum somewhere easily-accessible.
6. **If you have any custom themes**, copy/paste them into the 'themes' folder. 6. **If you have any custom themes**, copy/paste them into the 'themes' folder.
You can find this in `%APPDATA%/Local/pesterchum`. You can find this in `%LOCALAPPDATA%\pesterchum`, which is the same as
Oftentimes it doesn't exist, so you'll have to make it and copy the custom `%APPDATA%\..\Local\pesterchum`. Copy/paste one into Explorer's address bar
themes into it. and you'll end up where you need to be.
__If that doesn't work:__ Oftentimes the 'themes' folder doesn't exist in Pesterchum's shared config
folder, so you'll have to make it and copy the custom themes into it.
__If, for some reason, that doesn't work:__
You can also copy the missing themes into the 'themes' folder of the version You can also copy the missing themes into the 'themes' folder of the version
you just unzipped. **Don't overwrite any files** if you do this - the themes you just unzipped. **Don't overwrite any files** if you do this - the themes
used by this have been updated, and the older default themes may break when used by this have been updated, and the older default themes may break when

9
TODO.mkdn
View file

@ -37,7 +37,8 @@
* Add more comprehensive status support - IDLE, DND, INVISIBLE for now - or at * Add more comprehensive status support - IDLE, DND, INVISIBLE for now - or at
least add similar functionality. least add similar functionality.
* SEPARATE FUNCTIONALITY from CONNECTED STATE!! This is a huge problem! Being * SEPARATE FUNCTIONALITY from CONNECTED STATE!! This is a huge problem! Being
shunted off our nick closes windows and breaks things! Just D/C and reconnect? shunted off our nick closes windows and breaks things! Just D/C and
reconnect?
* It'd probably be best to give an option to either CHANGE NICKS or * It'd probably be best to give an option to either CHANGE NICKS or
DISCONNECT upon nick collision...? But, then how would we GHOST? DISCONNECT upon nick collision...? But, then how would we GHOST?
* Auto-disconnect if collsion before joining channels, make it * Auto-disconnect if collsion before joining channels, make it
@ -61,6 +62,8 @@
* Right-click Time entry field to see those used? (Replace left/right buttons?) * Right-click Time entry field to see those used? (Replace left/right buttons?)
* Save commonly-used times on a per-handle basis! * Save commonly-used times on a per-handle basis!
* Make the memo name entry box accept a comma-separated list * Make the memo name entry box accept a comma-separated list
* Make the memo list highlight/recolor the names of channels you're in
(including secret ones)
* Make right-clicking on a tab open up the right-click menu one would get on * Make right-clicking on a tab open up the right-click menu one would get on
right-clicking the title (frame??) right-clicking the title (frame??)
* Add an option to Cycle (for log separation) * Add an option to Cycle (for log separation)
@ -124,8 +127,8 @@
something, and save it all to a separate JSON file or two. something, and save it all to a separate JSON file or two.
Said JSON file should keep the extra information on hand - or rather, the Said JSON file should keep the extra information on hand - or rather, the
'recent users' JSON file should keep most of the detailed information and be 'recent users' JSON file should keep most of the detailed information and be
accessed first, with the larger 'inactive users' file being accessed to check accessed first, with the larger 'inactive users' file being accessed to
for unfamiliar handles. check for unfamiliar handles.
These would have to output the old data to pesterchum.js for backwards These would have to output the old data to pesterchum.js for backwards
compatibility purposes. compatibility purposes.
* Finish creating the sound wrapper. Just make it check what the type of sound * Finish creating the sound wrapper. Just make it check what the type of sound