Perhaps the application layout should be more tidy and symmetric :) #1092
Replies: 12 comments 1 reply
-
That's an interesting idea on the layout of the ribbon panel/toolbar. I'd be inclined to keep the I could see making the placement of the Property panels an option. I would personally never want it on the right because I utilize a very wide window to maximize the Code generation windows. That's way too much movement to click on a control in the navigation and then have to move the mouse to the other side of the screen to change properties (some of which then show up back in that Navigation panel on the other side of the screen). But that's just me -- I know wxFormBuilder has the option to move the properties to the other side. It certainly looks a lot better, even if it is (IMHO) harder to use. :-) |
Beta Was this translation helpful? Give feedback.
-
... something like this? With a vertical toolbar on left side |
Beta Was this translation helpful? Give feedback.
-
Ideally, I'd like to have the buttons close to where the user sees the effect of clicking the button. So in the example above, most of the time undo/redo buttons will affect properties on the opposite side of the screen. The "hidden controls" and "magnify" buttons affect the Mockup panel but are grouped with project buttons. I'd still be inclined to do a double row of toolbar buttons -- those 7 smaller buttons that are currently above the Navigation Pane only affect what's in that pane. The first three are just for convenience and have no affect on the project itself. The next four change parents -- so that does change the project, so could be moved to the larger sized toolbar. I'll play around with this sometime next week. I do like the idea of the ribbon panel at the very top, and I would add a Project tab to carry through on the idea of working with the tabs from left to right. That frees up a bit of vertical space, so it might make sense for the Mockup Panel to have it's own toolbar. I was already planning on all the various code display windows having a common toolbar. Then it's a question of how to work in the rest of the toolbar buttons in a way that doesn't become overwhelming to the user. |
Beta Was this translation helpful? Give feedback.
-
The ribbon panel should be on top starting with the 7/20 daily build. I have not moved the first group of four toolbar buttons. wxWidgets still uses fixed size bitmaps in the Ribbon panel that do not scale up on a high-resolution display -- and it doesn't directly support SVG files (the toolbar is composed entirely of SVG images). I already get frustrated when I try to use the other RAD tools that don't scale up which are very difficult to see on a high-res monitor. The ribbon panel bitmaps are larger then the average non-scalable toolbar button, but still quite a bit smaller than the regular toolbar scalable buttons. I don't want to go blind using my own program... 😄 At some point I want to revisit code generation for wxRibbonBar. There is a branch on wxWidgets that has done some of that work, but it stalled and has not been worked on for several months. I may be able to workaround this in wxUiEditor-generated code, but I want to wait a bit longer to see if the status on the wxWidgets side changes first. |
Beta Was this translation helpful? Give feedback.
-
Indeed a great result, about the toolbar I reckon it is OK as it is. The only thing which is missing, for those like me that love symmetry and a dynamic space in the center :), is the option to move properties and events to the right side of the screen. |
Beta Was this translation helpful? Give feedback.
-
I did verify that it's possible to do the switch, but I want it to be an option before I implement it. Before I do that, I need to do a complete overhaul of Preferences (both the dialog, how the settings get stored retrieved for the user, how they get accessed internally, etc.). While I do currently have a system in place, I haven't worked on it in a couple of years, and I'm not even sure the current options actually do anything. So it's on my list of things to do, but that one probably won't show up for a month or so. |
Beta Was this translation helpful? Give feedback.
-
New File:Preferences menu will display a dialog that includes swapping the properties panel with the mockup/code/docs panels. Width is not automatically switched, but once you set the property panel width to your preference, it will be retained. This should be in the August 2nd Daily Build. Be aware that the regular 1.1.2 build will revert the panel since it doesn't know anything about the preference. |
Beta Was this translation helpful? Give feedback.
-
Indeed a good result, my best compliments. I noticed the option to import DialogBlocks project is available in this new beta version. |
Beta Was this translation helpful? Give feedback.
-
I enabled it again because I needed to take a pass through all of the
project types that generate validators and ensure I could still import
validator code correctly. Aside from verifying that validators still work,
I have not looked any further at it. Quite honestly, I don't remember where
I left off working on it, so I don't actually know what doesn't import
correctly. The one thing you won't have from the Daily builds is any
specific information about what didn't convert correctly. That's going to
make it a bit harder for you because you will need to visually confirm that
what got converted is correct. The debug build that I work with creates a
separate window reporting everything that doesn't get converted, along with
the ability to create a log file from that. If you run into a lot of
problems with a project file, and you are comfortable attaching the project
file, I can run it in my debug build and more easily see where the
problem(s) is.
I do code generation comparisons on a couple of large projects before
checking in changes that have the potential of breaking existing projects,
but occasionally something slips through and some projects no longer
generate valid code in the Daily builds. I just wanted to warn you that
Daily builds aren't always stable -- and the project files they create are
often not backwards compatible with the last release version.
…On Tue, Aug 1, 2023 at 11:15 PM ROSSANO PARIS ***@***.***> wrote:
Indeed a good result, my best compliments.
I noticed hte option to import DialogBlocks projet is available in this
new beta version.
Do you think I could use it for debugging purpose [ my proposal
<#1134 (comment)>
], or it is too early.
[image: image]
<https://user-images.githubusercontent.com/33904565/257717772-7a12666f-caf9-43c8-a271-a6f416fed573.png>
—
Reply to this email directly, view it on GitHub
<#1092 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKGN3UZQWRPLQHSGQTNJWLTXTHWBVANCNFSM6AAAAAA2HSWIKI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
OK Got it! I don't have any intention to use a night build for my production environment :), however I could try to convert my UI projects made with DialogBlocks in order to keep you posted regarding possible issues. Do you think this kind of activity could be usefull for you ? |
Beta Was this translation helpful? Give feedback.
-
You could certainly try it out -- if you run into a few minor problems,
then by all means add a bug report for them. If you run into a lot of
problems, then it makes more sense to just wait until I've done a full pass
on the importing code and consider it complete. It *will* be part of the
next beta and release, but right now I'm focused on code generation, and
I'm not planning on working on the DialogBlocks importer until code
generation for the three programming languages and XRC is in much better
shape.
…On Wed, Aug 2, 2023 at 5:38 AM ROSSANO PARIS ***@***.***> wrote:
OK Got it!
I don't have any intention to use a night build for my production
environment :), however I could try to convert my UI projects made with
DialogBlocks in order to keep you posted regarding possible issues.
Do you think this kind of activity could be usefull for you ?
Do you suggest to wait till you will be able to say "OK Rossano go ahed
with your tests using this night build ..."
—
Reply to this email directly, view it on GitHub
<#1092 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKGN3U2UCRJYQFFZT56WZ4TXTJC4VANCNFSM6AAAAAA2HSWIKI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Thank you @KeyWorksRW for keeping me posted about your roadmap once again thank you and good work |
Beta Was this translation helpful? Give feedback.
-
kind @KeyWorksRW here I come with another suggestion.
I beg your pardon, I know this suggestion could be taken as an annoying one, anyway I try to propose a new main layout for your application; the actual one seems not well aligned with the common use of ribbon control.
These functionalities should be added at the beginning of the ribbon bar as another group with the label "Project".
The property and event tabs should be moved on left in order to obey at "symmetry" rules :)
My proposal
Beta Was this translation helpful? Give feedback.
All reactions