When setting up more than 100 objects (keypad buttons, labels, indicators, sliders, etc) the resulting code is HUMONGUOUS ---almost each attribute is a separate line. Sometimes that is handy, but sometimes rather unwieldy, generating listing after listing after listing* to wade through , or to paste code into a document turning it into a "book"
instead of
self.Label1.configure(activebackground="#f9f9f9")
self.Label1.configure(background="#112fa8")
self.Label1.configure(foreground="#ff0000")
etc
Have a checkbox in the options, to generate a compact mode (an entire object can be generated in one or two lines. For example:
This is MUCH more condensed & makes pasting a whole screenful of objects into a report less unwieldy or easier to see more settings with less scrolling around.
*note, I didn't say page after page after page : )
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That is a good idea. I will add that to the wish list. At this point, PAGE is in a feature freeze and only critical bugs are being worked on so we can get the next version out.
Greg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2021-12-16
Have a checkbox in the options, to generate a compact mode
...By this, I mean in the general preferences area, to generate expanded or condensed objects code.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That having been said, you should NEVER edit the GUI module. I understand you are looking at the options and not editing the code, but things can get messy if you accidentally change something.
Greg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2021-12-16
That having been said, you should NEVER edit the GUI module That is usually true, though not always. With a big project you may find you want to add in some parameter or make a small tweak & don't want to redo at that moment with page & regenerate. Additionally, I had a page but a bunch of controls really overlay others, so they are extracted from the page generated file and put into the support file of another. This is because they are really 2 pages (a popup of other controls), but must be drawn together on one page to see how they layout together. In essence you have one initial drawing that is the combinations of 2 screens. The code extraction is not too hard, but not something you want to repeat unless needed. This might not be the best way, but one I did in the "early days".
It would be interesting if page could display 2 pages & show how they look when overlayed, but that is likely low on the need totem pole! One page would just show up as background for layout purposes, while you edit the 2nd as the active foreground.
When setting up more than 100 objects (keypad buttons, labels, indicators, sliders, etc) the resulting code is HUMONGUOUS ---almost each attribute is a separate line. Sometimes that is handy, but sometimes rather unwieldy, generating listing after listing after listing* to wade through , or to paste code into a document turning it into a "book"
instead of
self.Label1.configure(activebackground="#f9f9f9")
self.Label1.configure(background="#112fa8")
self.Label1.configure(foreground="#ff0000")
etc
Have a checkbox in the options, to generate a compact mode (an entire object can be generated in one or two lines. For example:
Button(ws, text='HELLO', height=10, width=20, bg='#567', fg='White', command=myalarm).pack(pady=10)
This is MUCH more condensed & makes pasting a whole screenful of objects into a report less unwieldy or easier to see more settings with less scrolling around.
*note, I didn't say page after page after page : )
That is a good idea. I will add that to the wish list. At this point, PAGE is in a feature freeze and only critical bugs are being worked on so we can get the next version out.
Greg
Have a checkbox in the options, to generate a compact mode
...By this, I mean in the general preferences area, to generate expanded or condensed objects code.
That having been said, you should NEVER edit the GUI module. I understand you are looking at the options and not editing the code, but things can get messy if you accidentally change something.
Greg
That having been said, you should NEVER edit the GUI module That is usually true, though not always. With a big project you may find you want to add in some parameter or make a small tweak & don't want to redo at that moment with page & regenerate. Additionally, I had a page but a bunch of controls really overlay others, so they are extracted from the page generated file and put into the support file of another. This is because they are really 2 pages (a popup of other controls), but must be drawn together on one page to see how they layout together. In essence you have one initial drawing that is the combinations of 2 screens. The code extraction is not too hard, but not something you want to repeat unless needed. This might not be the best way, but one I did in the "early days".
It would be interesting if page could display 2 pages & show how they look when overlayed, but that is likely low on the need totem pole! One page would just show up as background for layout purposes, while you edit the 2nd as the active foreground.