4 ms·

i honestly can’t say i see the usefulness in your UI diagram. The issue is that you’re basically displaying all of the code so it’s just redundant. You need to

i honestly can’t say i see the usefulness in your UI diagram. The issue is that you’re basically displaying all of the code so it’s just redundant. You need to make it higher-level, e.g. add an annotation which you can apply to specific methods and fields and constructors, and then only show nodes in the diagram when they have that annotation. Another case where a UI view would be especially useful, is live interactive UI/UX previews. Whether that be HTML or Java Swing GUI. The left window is code to render a part of your application’s UI, and the right window is an interactive preview of the UI itself. You can resize the preview, change attributes like color, and maybe add components, and it will affect the code. Or a game engine where the “scene” is actually constructed by code that you can edit, and it will edit the scene.

vyomkeshj 5y ago
Thank you for your response! It's supposed to be either edit with code or edit with UI. The UI is supposed to provide one with more flexibility in terms of input options. Instead of a text file, you can have a canvas to arrange your code on. You can put methods side by side and pan between them, see the relationships between them, put stickies on them, highlight statement background to any color to make it more visible. You can put statements side by side to use more h-space on your screen. The UI diagram is not very essential but it gives us the surface area to do such things. Yes, we plan to add plugins that will allow side by side ui previews, another benefit of going ui first is we can do things like draw overlaid arrows to show the user which part of the code binds to which part of the UI in the preview. These will be library specific plugins that can use ex. a set of annotations to allow the library to integrate certain of its features within the UI. We are thinking about ways to make this easy to implement for libraries. __________________________ If you zoom out, we can provide higher level views. You can say right click-> tag a set of methods/fields with a tag and use the tags to filter what is visible in the view. Do I make sense to you? :)

vyomkeshj 5y ago

Thank you for your response! It's supposed to be either edit with code or edit with UI. The UI is supposed to provide one with more flexibility in terms of input options. Instead of a text file, you can have a canvas to arrange your code on. You can put methods side by side and pan between them, see the relationships between them, put stickies on them, highlight statement background to any color to make it more visible. You can put statements side by side to use more h-space on your screen. The UI diagram is not very essential but it gives us the surface area to do such things. Yes, we plan to add plugins that will allow side by side ui previews, another benefit of going ui first is we can do things like draw overlaid arrows to show the user which part of the code binds to which part of the UI in the preview. These will be library specific plugins that can use ex. a set of annotations to allow the library to integrate certain of its features within the UI. We are thinking about ways to make this easy to implement for libraries. __________________________ If you zoom out, we can provide higher level views. You can say right click-> tag a set of methods/fields with a tag and use the tags to filter what is visible in the view. Do I make sense to you? :)