I try to use Radzen + Radzen Blazor Studio (I'm aware RBS is in the beta stage) couple in my daily development process with their own tools. For example, RBS's Method Designer good tool for basic processes. One, two, or maybe three stages can be designed in it. But the bigger processes can not. This tool comes to an unreadable and unmanageable tool at that time.
My dream was to see and design complex processes visually. But this tool is not enough yet.
I'm sharing with you some parts of my realworld code. When I try to one level zoom goes to max value and sometimes it can't repaint the canvas. Writing code is easy than designing here.
And If the code has a problem the design screens totally not working. If I have to back to the code why do I use the design screen? Showing the compiled screen is a good idea but if this stops the design process it should be rethought. Sometimes I'm feeling that I'm wrestling with RBS I'm kidding.
I know it'll very good product but needs time.
Only I want to know these.
Method Designer: Will you continue to use this infrastructure?
Compiled Screen: Will the developer have to work on the code screen to solve problem to see the screen or method designer on the final product, if there is an error?
Indeed. We need to be able to parse the code in order to visualise it. Sometimes the C# parser can't handle very broken code.
Yes, but we plan to change it a bit. We will have normal scroll and zooming will be optional (from the toolbar). Using the method designer is entirely optional though. If you feel more comfortable writing code then you can continue to do so. RBS makes it easier than Radzen by providing a built-in code editor.
I like the visual design because it gives an alternative perspective in fact alternative dimension to a developer. I want to say that the RBS designer's this version is not easy. When you complete your RBS designer I prefer using it and suggest it to everybody.
I'll be waiting for this.
I used it with the same meaning as parsing code.
When the c# can't handle the code the RBS can show nothing on the screen. This is a challenging situation for both sides of the RBS. The one side is you as a developer of the RBS and the other side is we as the developers of using your development tool. Why do I choose Radzen and be excited about the RBS? The only answer is visual tools. I absolutely accept that showing rendered real page is a very sexy idea. But if the visual tools won't perfect RBS won't be sexy for the many potential developers/users from my point of view anymore.
Here is an idea. Maybe useful.
RBS;
creates a mockup (not the real page) with the same components very basic level in the first stage.
In the second stage parses the code and adds the data (must be shown) to the components.
In the last stage if there is an error, it marks that component as mistaken (for example with a red square) and adds the error string to it.
I'm kidding.