Request for Visual Editor Similar to Windows Forms Designer #4662
Replies: 7 comments 2 replies
-
@asdqwe But i think it would be beneficial if it will be a part of raylib because it will help in designing the application and it should be a part of raylib not a binding or wrappers |
Beta Was this translation helpful? Give feedback.
-
@DevsHorizon It would be great but I'm afraid I don't have the resources to make it possible. Feel free to work on it like others users have done. By the way, my |
Beta Was this translation helpful? Give feedback.
-
@DevsHorizon I think there are two factors here. Secondly, for open-source projects, feature requests are usually relatively focused and even so require someone to volunteer to do it, along with maintainer (i.e., @raysan5) agreement that it is a worthy thing to incorporate and then be maintained. It works best when the folks who have the itch for it can step up, build it, and test it along with some commitment for any future maintenance. Otherwise, it is necessary to find someone who has such an itch and can commit to the work. An alternative is to do a flex project that integrates atop forks of raylib releases to provide a model with ambitions of such scope. That decouples from burdening raylib development while providing a clean, cooperative separation. That's not unlike how raylib has externals dependencies and (as a rule) does not do maintenance on those dependencies. I know I'm harping on this, in case others who see something nice think that is an easy thing to have here. Even for funded projects, this sort of goes against the grain. The expense of such an endeavor is unimaginable. That the result is simple and wonderful to use hides all of that background. Please appreciate that is a great achievement, but it was provided at non-trivial cost by a commercial software provider. |
Beta Was this translation helpful? Give feedback.
-
@raysan5 We want to help but we are new to raylib and do not have expertise in C or C++. Could you please advise us on what we should do next? We have laid out the basic planning for a visual designer. We would like to open a discussion to gather further ideas and suggestions from the community. Your expertise and feedback will be invaluable in shaping this project. Please share your thoughts, and any contributions are greatly appreciated. Thank you |
Beta Was this translation helpful? Give feedback.
-
Have all of these considerations in mind. There will also be considerations of platforms the designer will run on and what raylib configurations and versions are kept pace with and/or adapted/selected for. Depending on the coupling of the designer with raylib, it might not matter how the designer itself is programmed, but some degree of software development programming and engineering is required. I still suspect that it should be a separate project, once you determine that there are enough contributors to aid in the technical effort. PS: I am not volunteering for this. I have enough challenging work on my plate as it is and I have not done the work that is enumerated above for any kind of game-development tool-chain. PPS: I don't see how it is intended to make such a designer "part of raylib." Raylib has no framework or harness engine that is used in the manner of Visual Studio or even Visual Studio Code (and equivalent tools for other platforms). There have been integrated visual designers for games though. You might be able to find some when looking around for examples. |
Beta Was this translation helpful? Give feedback.
-
@DevsHorizon did you check |
Beta Was this translation helpful? Give feedback.
-
@raysan5 @orcmid Could you please provide a comprehensive list of all UI components in Raylib (e.g., Button, Label, etc.) along with their properties (such as position, size, color, text) for each component? |
Beta Was this translation helpful? Give feedback.
-
I would like to propose the addition of a visual editor in raylib, similar to the Windows Forms Designer. This tool will significantly enhance the user experience by providing a graphical interface for the placement of components such as buttons and other interactive elements.
Benefits:
Ease of Use: A visual editor allows for intuitive drag-and-drop placement of UI components, making it easier for developers, especially beginners, to design their applications.
Increased Productivity: It reduces the time needed to manually code the positions and properties of components, allowing developers to focus more on functionality and logic.
Improved Accuracy: With a visual representation, users can precisely place and align components, reducing the chances of errors and misplacement.
Simplified Coding: Placing components through code can be challenging and time-consuming. A visual editor eliminates the need for manual coding of component positions, making the process more straightforward and efficient.
Enhanced Creativity: A visual editor encourages experimentation and creativity, enabling developers to quickly test different layouts and designs.
Implementing a feature like this in raylib would bridge the gap between coding and design, making the development process more efficient and user-friendly.
Thank you for considering this request. I believe it will greatly benefit the raylib community.
Beta Was this translation helpful? Give feedback.
All reactions