Issues and Areas for Improvement

Oct 13, 2025 by sorusgentrification.com 54 views

As a user of a code-based WYSIWYG tool, I have had the opportunity to experiment with its features and provide feedback on its performance. In this article, we will delve into the strengths and weaknesses of the tool, highlighting areas for improvement and potential new features that could enhance the user experience.

A Flexible and Easy-to-Maintain Code-Based WYSIWYG Tool

I must say that after playing around with this tool on Windows, I am thoroughly impressed. Unlike other drag-and-drop WYSIWYG tools, this one is based on code, making it more flexible and easier to maintain. When it is more complete, I look forward to diving in and creating a full design with it.

Issues and Areas for Improvement

While the tool has shown great promise, there are some issues that need to be addressed. Firstly, I encountered problems when editing _gen.h/.c files, which is not recommended. However, the editor allows this without complaining, and it would be beneficial to have a warning or readonly mode in place to prevent such mistakes.

Another issue I faced was the mixing of XML and C code generated by the code generator. I'm not sure what I did exactly, but I've seen it a few times. Luckily, I was able to revert the changes in Git (client). To prevent such errors in the future, it would be helpful to have a more robust code generator that can handle different file types and prevent mixing of code.

External Interaction and Pub/Sub Idea

One feature that I personally would like to see implemented is external interaction. I think I read somewhere about a pub/sub idea, but I'm not sure where. To localize components externally by name would be a good start, as seen in the recent pull request on GitHub (https://github.com/lvgl/lvgl/pull/7768). Using a polling time approach with actions that are checked each tick for changes is inefficient, and a more efficient solution would be to use a pub/sub system.

Docker and Local LVGL Version

Another area of concern is the Docker instance of the editor, which has its own copy of LVGL (liblvgl.a). This can lead to issues with keeping the local version of LVGL in sync with the Docker instance. It would be more efficient to mount the local LVGL version inside the Docker instance, ensuring that both versions are up-to-date.

Git Actions and Preview Generator

The feature of Git actions and preview generator is a nice addition, but I personally don't see myself using it in the near future. However, it seems like a useful feature for bigger projects and organizations with multiple stakeholders. I do have some doubts about how this feature is currently implemented, particularly with regards to forking only for public repositories and corporate projects, which are often private.

Additional Features and Components

To further enhance the user experience, I would love to see the following features and components added:

Keyword search and replace functionalities
More components, such as lv_arc and lv_tileview

Conclusion

In conclusion, while the code-based WYSIWYG tool has shown great promise, there are areas for improvement and potential new features that could enhance the user experience. By addressing the issues mentioned above and implementing new features, the tool can become an even more powerful and efficient design tool.

Recommendations for Future Development

Based on my feedback, I recommend the following for future development:

Implement a warning or readonly mode for editing _gen.h/.c files
Improve the code generator to prevent mixing of XML and C code
Implement a pub/sub system for external interaction
Mount the local LVGL version inside the Docker instance
Add keyword search and replace functionalities
Add more components, such as lv_arc and lv_tileview

In our previous article, we discussed the strengths and weaknesses of a code-based WYSIWYG tool, highlighting areas for improvement and potential new features that could enhance the user experience. In this article, we will answer some frequently asked questions (FAQs) related to the tool and its future development.

Q: What is a code-based WYSIWYG tool?

A: A code-based WYSIWYG (What You See Is What You Get) tool is a design tool that allows users to create and edit graphical user interfaces (GUIs) using code, rather than a drag-and-drop interface. This approach provides more flexibility and control over the design process.

Q: What are the benefits of a code-based WYSIWYG tool?

A: The benefits of a code-based WYSIWYG tool include:

More flexibility and control over the design process
Easier maintenance and updates of the design
Ability to create complex and custom designs
Improved performance and efficiency

Q: What are some common issues with code-based WYSIWYG tools?

A: Some common issues with code-based WYSIWYG tools include:

Difficulty in learning and using the tool
Limited support for certain file types or formats
Inefficient code generation or editing
Difficulty in debugging and troubleshooting

Q: How can I improve the user experience of a code-based WYSIWYG tool?

A: To improve the user experience of a code-based WYSIWYG tool, consider the following:

Provide clear and concise documentation and tutorials
Offer support for a wide range of file types and formats
Implement efficient code generation and editing features
Provide debugging and troubleshooting tools and resources

Q: What are some potential new features for a code-based WYSIWYG tool?

A: Some potential new features for a code-based WYSIWYG tool include:

Keyword search and replace functionalities
More components, such as lv_arc and lv_tileview
Improved support for external interaction and pub/sub systems
Enhanced debugging and troubleshooting tools and resources

Q: How can I contribute to the development of a code-based WYSIWYG tool?

A: To contribute to the development of a code-based WYSIWYG tool, consider the following:

Provide feedback and suggestions for improvement
Participate in online communities and forums related to the tool
Contribute code or patches to the tool's open-source repository
Collaborate with the development team to implement new features and improvements

Q: What is the future of code-based WYSIWYG tools?

A: The future of code-based WYSIWYG tools is promising, with ongoing development and improvement of existing tools and the emergence of new tools and technologies. As the demand for more efficient and flexible design tools continues to grow, code-based WYSIWYG tools are likely to play an increasingly important role in the design and development process.

Conclusion

In conclusion, a code-based WYSIWYG tool offers a powerful and flexible approach to design and development. By understanding the benefits and challenges of these tools, and by contributing to their development and improvement, we can create more efficient and effective design tools that meet the needs of users and developers alike.