Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generate Requests #3

Open
wants to merge 43 commits into
base: master
Choose a base branch
from

Conversation

CrypticSwarm
Copy link

  • Core Protocol Request/Reply handling.
  • Converted many of the tests

Most things work.

PolyText8 doesn't work. It seems the XML and the spec differ and I am not sure why.
Render Extension is probably broken if it uses the old api.

Still need to calculate the length.
Still need to handle normal list types.
result: should now be able to handle requests with nested structs.
mainly because the result has a nested struct and I wanted to make sure
that it was working.
pretty messed up.
 - sometimes end of request needs to be padded to 4 byte align
 - some requests reference the request Length
   (may have issues with a few others that do operations on req Length)
 - makes sure variable is set to empty array even when no fields.
 - sends body length to all reply handler functions.
 - handle operators and nested operators for list length.
why draw multiple rects ontop of eachother?
Solution turn one of them red.
@CrypticSwarm
Copy link
Author

Continued from: (#5)

Leaving the attributes names as is.
Comment: If you leave them the same can also generate the docs.
Response: Can generate the docs even if the names are changed. That part doesn't matter as long as we have consistent names. Consistent API's I think are nice :) Also most of the XCB uses underscores instead of camel case. This uses camel case for the most part already.

Comment: don't use value_mask either value or merge mask into parent obj.
Response: agreed value_mask isn't the most appropriate. Either one is good.
Note: If merge attributes with the rest of the request params. Need to change code to not throw errors if a wrong value_mask key is passed.
Question: Are there any requests that a Key from the value mask will collide with any of the other request params in any of the extensions? This is one thing to think about.

@CrypticSwarm
Copy link
Author

Thoughts?

@sidorares sidorares mentioned this pull request Oct 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant