Hello,
My name is Avinash Sharma, and I am a Computer Science student at Jaypee University of Engineering and Technology, Guna. I am interested in applying for “Develop a Mobile Phone UI for GNU XaoS” for Google Summer of Code 2026.
I am currently drafting my proposal and would sincerely appreciate any feedback or guidance before finalizing it.
About MeStrong experience with C/C++, Qt/QML, and CMake
Android development experience with focus on UI architecture and accessibility
Open-source contributor (merged PRs in large Android codebases)
Comfortable working with modular architectures and UI/engine separation
After exploring the XaoS repository, I understand that:
src/engine/ handles fractal computation
src/ui-hlp/ (notably uih_context) acts as a bridge layer
src/ui/ implements the existing desktop interface
This separation suggests that a mobile UI could be implemented independently without modifying the engine core.
Proposed Direction (Draft)Introduce a src/ui-mobile/ module
Implement the interface using QML with a C++ bridge around uih_context
Use Qt toolchains for Android (and potentially iOS)
Prioritize touch interaction design, performance, and maintainability
I would be grateful for guidance on:
Any preferred architectural conventions for new UI modules
Known build-system concerns for mobile targets
Features you would prioritize for a first mobile release
Thank you for maintaining such a unique and inspiring piece of free software. I look forward to your suggestions.
Best regards,
Avinash Sharma
https://github.com/Avinash-Codes
Hello,
My name is Avinash Sharma, and I am a Computer Science student at Jaypee University of Engineering and Technology, Guna. I am interested in applying for “Develop a Mobile Phone UI for GNU XaoS” for Google Summer of Code 2026.
I am currently drafting my proposal and would sincerely appreciate any feedback or guidance before finalizing it.
About Me
Strong experience with C/C++, Qt/QML, and CMake
Android development experience with focus on UI architecture and accessibility
Open-source contributor (merged PRs in large Android codebases)
Comfortable working with modular architectures and UI/engine separation
My Understanding So FarAfter exploring the XaoS repository, I understand that:
src/engine/ handles fractal computation
src/ui-hlp/ (notably uih_context) acts as a bridge layer
src/ui/ implements the existing desktop interface
This separation suggests that a mobile UI could be implemented independently without modifying the engine core.
Proposed Direction (Draft)
Introduce a src/ui-mobile/ module
Implement the interface using QML with a C++ bridge around uih_context
Use Qt toolchains for Android (and potentially iOS)
Prioritize touch interaction design, performance, and maintainability
I would be grateful for guidance on:
Any preferred architectural conventions for new UI modules
Known build-system concerns for mobile targets
Features you would prioritize for a first mobile release
Thank you for maintaining such a unique and inspiring piece of free software. I look forward to your suggestions.