quotient-im/pyquotient

pyquotient's Issues

Week 9: More event classes

• RoomMessageEvent
• RoomMemberEvent
• RoomNameEvent / RoomTopicEvent / RoomCanonicalAliasEvent

Week 4: Event classes

Expose Event/RoomEvent/StateEventBase

Week 9-10: Basic state changes to the room

• Change room name
• Change room topic

Week 2*: Automate generation of bindings using GTAD

Week 1: NetworkAccessManager, ConnectionData (except `submit`), begin BaseJob

Milestone 1: minimal syncing client

This client should be able to log in, start sync loop and make some sense of incoming events (e.g., display the contents in some generic manner, even if just JSON).
Stretch goal: the client should be able to subclass Quotient::Room, and, e.g., highlight the current user's mentions if they are in the message.

Week 8: Client: Room list

Week 9: Client: Basic message sending

Support entering plain text and sending it. The client should show the sent text once it arrives through sync.

Week 8: Initial work on sending events

• Send plain text
  • (optional) Send HTML
• Send m.notice/m.emote messages

Week 3: Connection

Week 2: Complete BaseJob bindings and at least one concrete job class (LoginJob, e.g.)

Week 10: visualising pending events

Week 3: initial client

Should be able to resolve the server, log in, obtain the access token, log out.

Week 2-3: ConnectionData::submit()

Week 8: Validate Python/QML interface

1. Add Quaternion QML files (Timeline.qml, TimelineItem.qml and so on) to the Python client codebase
2. Implement stub message event model passing a minimal set of data to QML.
3. Validate that data are correctly marshalled from Python to QML.

Week 9: Client: basic timeline

It's mainly about extending the message event model to support RoomMessageEvent and actually connect to libQuotient for data.

Week 10: uploading/downloading files in the client

Not essential for Milestone 2

Some packages are required to run unit tests in CI, but are not used in project

Packages httpretty and cleo are not used in project explicitly and are not required by packages used in the project, but are needed to be able to run unit-tests in CI environment(Github Actions). Locally it works also without them.

error property is missed in BaseJob

Change curl'ing of poetry to getting from its repository by a tag

Week 9: Basic visualisation of room state

Extend the message event model to support RoomNameEvent, RoomTopicEvent, RoomCanonicalAliasEvent.

Week 6-7: Room class bindings

BaseJob has only one costructor instead of 2 in libQuotient

Week 3-4: User class bindings