haloopdy/qcs-python
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
13 Commits 2 Branches 0 Tags 230 KiB
Python 98.3%
Batchfile 1.7%
93d92780b5
Go to file
Carlos Sanchez 93d92780b5
Create README.md
2023-05-01 02:21:38 -04:00
.gitignore Login somewhat works, token file doesn't 2023-04-30 22:08:00 -04:00
contentapi.py Connecting to websocket 2023-05-01 01:55:20 -04:00
main.py Connecting to websocket 2023-05-01 01:55:20 -04:00
myutils.py Neat, loads from configs! 2023-04-30 21:12:14 -04:00
README.md Create README.md 2023-05-01 02:21:38 -04:00
run.bat Initial commit, what is going on 2023-04-30 18:13:02 -04:00
scrolltest.py Setup the main loop! 2023-05-01 00:34:56 -04:00
setup.bat Setup the main loop! 2023-05-01 00:34:56 -04:00
test_myutils.py Some testing 2023-04-30 21:03:03 -04:00
test.bat Some testing 2023-04-30 21:03:03 -04:00

README.md

qcs-python

A very basic python frontend for qcs, written for old machines

What this is for / assumptions

  • This is an extremely basic Python frontend meant to connect to a contentapi instance for chatting only. No other functionality from contentapi is preserved (such as creating rooms, managing permissions, avatars, etc)
  • This is meant to work on python 3.4 in order to satisfy user requirements for "must run on Windows XP"
  • This was developed on Windows 11 targeting a local copy of Python 3.4.4
  • I am unable to use curses as part of the requirements. This influenced the limited design
  • I am not a Python nor a Windows developer. If the bat files or python is garbage, I don't care (sorry!)

How to start

Because of the unique requirements given to me, this isn't setup like a normal python repository.

  • You need to manually download the required pip packages, which are listed in setup.bat
  • This was not setup to run with a virtual environment (but you're free to change that)
  • Run main.py for the whole thing. run.bat is for me, the developer, there's nothing you need from there

The list of required pip packages is listed in setup.bat. If you're on windows, feel free to run that yourself, just know that the default is to use a local python 3.4 installation in a specific folder; you'll need to change that. Furthermore, we don't specify versions for most of these, so we assume "any version" will work (even though I'm aware that these APIs change).