View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0015915 | Scribus | Properties Palette | public | 2019-11-05 13:43 | 2023-11-25 19:08 |
Reporter | ale | Assigned To | ale | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | assigned | Resolution | open | ||
Product Version | 1.7.0.svn | ||||
Target Version | 1.7.0 | ||||
Summary | 0015915: Indigo UI: refactor the Color and Line panels | ||||
Description | Martin's proposal is to create a Fills panel (most of the current color panel) and a Line one (the line panel plus the stroke color selection). On top of that I'd suggest: - Using the XYZ basepoint (it can already indirectly be used... and with the new widget it's "trivia" to only show two or three base points) - Moving the arrow properties to a new content panel for lines (and beziers) | ||||
Tags | No tags attached. | ||||
Patch | No | ||||
related to | 0003766 | feedback | UI improvement proposals to reduce the number of clicks | |
parent of | 0003752 | new | move or replace hidden line basepoint setting in properties | |
parent of | 0012434 | closed | nitramr | basepoint: different widgets for shapes and lines |
parent of | 0009483 | assigned | ale | [PATCH] Ability to choose a basepoint for a line |
parent of | 0007287 | new | Add to ability change basepoint of lines | |
parent of | 0003751 | new | additional/clearer basepoint options for lines | |
related to | 0012439 | closed | ale | on canvas basepoint for rotation |
Not all the children of this issue are yet resolved or closed. |
|
one question: what is the use of "basepoint: end points"? i see that it changes the width and height in x2 and y2... is it all? then i would suggest that for lines we replace the width chain button by a new button that switches between the width and x2, y2 the button would show "x2" in the normal state and "w" when checked. |
|
0003765 has an interesting proposal for allowing 5 basepoints for lines. |
|
martin is defining two widgets for the line panel. since the arrow heads are moving to the content panel, and the "basepoint" drop down will be a button in the xyz panel, the advanced part shrinks to three buttons that we should integrate in the main panel. now, one big issue i have in martin's proposal are the labels below and above the fields. i think that the proposals i've created for the xyz and do well with less labels than martin did plan. for the lines panel is a bit harder. does anybody want to make suggestions for improved layouts based on the considerations above and the screenshots down here? |
|
p.s.: martin has forgotten, that when the line type is custom, then a further widget popsup: |
|
|
|
friday evening... status report: - the arrow heads are now in the content panel for the lines - the easy part of the properties panel is done - two screenshot attached and an appimaged linked: https://gitlab.com/a.l.e/scribus/-/jobs/345940624/artifacts/file/Scribus-nightly-x86_64.AppImage - the color square shows the current color of the stroke but no pop up for setting the colors is there - basepoint will go to the xyz panel - the styles will be a fancy combobox... one big question: i think that all fields are very clear... only for the shade (the 100%) i wonder if we can find an icon to put in front of it... |
|
That is my current implementation. The color selection is still missing in top left corner. I like the idea of moving the base point selection to X,Y,Z panel. It could be a simple QToolButton instead on a QComboBox, because it just has two options. |
|
nice. two things from my side: - do you plan to make the labels below the buttons optional? they look rather useless for my usage, but i guess they can be very useful for somebody starting with DTP. - the arrows are probably a feature that are not that much used but take lot of space here... we could go with the same solution as in inkscape: - call them "Markers" (most of them are technically not arrows ....) - show the names when the drop down is open but not when it is closed Which would result in: Markers: [ v] [ ] [ v] [ ] (when no marker is selected, just show an empty field instead of None; disable the scale) Markers: [<- v] [100%] [-() v] [100%] btw, i tend to really like the "in place" dialog with a "real" preview in the button. no idea if it's possible to do the same in qt. (at the end we could just have two buttons for the arrows on the first row of the dialog [0.0003 mm] [------ v] [<- v] [-> v] Width Type Markers ) |
|
>> do you plan to make the labels below the buttons optional? they look rather useless for my usage, but i guess they can be very useful for somebody starting with DTP. << => yes >> the arrows are probably a feature that are not that much used but take lot of space here... we could go with the same solution as in inkscape:<< => See attached screenshot. It is a first implementation. I think we should remove M and S size and just keep L, next to the scale input we could have 2x or 4x buttons for a predefined scaling. Currently, I hide the marker buttons if no line item is selected. What do you think? |
|
yeah! not sure about the 2x and 4x buttons. maybe rather a 1/2 and 2x button that halves / doubles the current value? but, in my eyes, scribus is not a tool made for drawing arrows. of course it must support arrows imported from inkscape, should be able to tweak them to the maximum extent and it should be possible to draw an arrow from time to time... so i would focus on making the essential features easy to reach and not add further buttons for now. |
|
Ok, next update. I redesigned the custom dash editor. In case the pattern should repeat correctly, you need an even amount of stops. If not, the dash and gap get inverted. There is a red and green color that indicates this error. Line base point widget has been moved to XYZ panel. I think a button to swap the start and end marker could be nice. At least InDesign and Affinity Publisher have such a feature. |
|
since your UI theme is mostly black and white: i would avoid using green for a correctly working line pattern. just set it to gray. (could be lighter than the gray currently in use) on the other side, i'm fine with the area being red when the pattern is not "sound". but i wonder if there shouldn't be some explanation of the reasons for the error (a tooltip might be enough). a slightly different idea: currently, the active triangle is red. i wonder if in the new widget the triangle could be gray and black (one color for the active one, the other for the inactive...) and if there is an error, the last stop point gets red (instead of the "right" area) that might show a bit better where the problem is finally, since you're working on this widget: while testing the current widget, i noticed that the cursor also changes to a + when hovering the line but one can only add stop points when the mouse is below the line, where the triangles are. personally, i'd prefer to be able to add the stop points also on the pattern preview, but if that is not easy / possible, the mouse cursor should only to be set to a + when it's indeed possible to add a stop point. |
|
By the way, for the "Type of Line" I would also copy Inkscape and create a Table with two column and the full line and Custom at the top. Currently, it's almost impossible to discover that "Custom" is even possible. |
|
>> i wonder if in the new widget the triangle could be gray and black (one color for the active one, the other for the inactive...) and if there is an error, the last stop point gets red (instead of the "right" area) << I agree, now the active stop uses the highlight color of the OS and the last stop get a red color if the stop count is not even. I added a scale to get an idea of the pattern length. The value input only shows the relative distance from the previous stop and not an absolute position. Also, I fixed an issue I found (at least I suspect it was a problem). The pattern doesn't always fit the width of the widget. It was possible to move stops out of the visible area. To edit or select these stops you had to make the properties window wider. Now everything always fits within the width of the widget and displays the pattern at a relative scale. At the end of the scale there is always a buffer of 1 unit (the gray area) so that you can move the last stop or add a new one. |
|
� looks perfect to me : - ) |
Date Modified | Username | Field | Change |
---|---|---|---|
2019-11-05 13:43 | ale | New Issue | |
2019-11-05 13:43 | ale | Status | new => assigned |
2019-11-05 13:43 | ale | Assigned To | => ale |
2019-11-05 13:48 | ale | Note Added: 0046973 | |
2019-11-05 13:52 | ale | Relationship added | parent of 0003752 |
2019-11-05 13:53 | ale | Relationship added | parent of 0012434 |
2019-11-05 13:54 | ale | Relationship added | parent of 0009483 |
2019-11-05 13:56 | ale | Note Added: 0046975 | |
2019-11-05 13:56 | ale | Relationship added | parent of 0007287 |
2019-11-05 13:57 | ale | Relationship added | parent of 0003751 |
2019-11-05 13:58 | ale | Relationship added | related to 0012439 |
2019-11-06 21:04 | ale | File Added: indigo-martin-lines.png | |
2019-11-06 21:04 | ale | File Added: indigo-martin-lines-advanced.png | |
2019-11-06 21:04 | ale | Note Added: 0047002 | |
2019-11-06 21:07 | ale | File Added: custom-type-of-line.png | |
2019-11-06 21:07 | ale | Note Added: 0047003 | |
2019-11-07 13:35 | ale | Relationship added | related to 0003766 |
2019-11-08 17:57 | ale | File Added: cp-lines.png | |
2019-11-08 17:57 | ale | File Added: pp-lines.png | |
2019-11-08 17:57 | ale | Note Added: 0047035 | |
2023-11-14 20:05 | nitramr | Product Version | 1.5.6.svn => 1.7.0.svn |
2023-11-14 20:05 | nitramr | Target Version | => 1.7.0 |
2023-11-14 20:14 | nitramr | Note Added: 0050462 | |
2023-11-14 20:14 | nitramr | File Added: Bildschirmfoto vom 2023-11-13 23-21-01.png | |
2023-11-15 06:42 | ale | Note Added: 0050467 | |
2023-11-15 06:45 | ale | Note Edited: 0050467 | |
2023-11-15 06:45 | ale | Note Edited: 0050467 | |
2023-11-15 06:46 | ale | Note Edited: 0050467 | |
2023-11-15 06:46 | ale | Note Edited: 0050467 | |
2023-11-15 06:47 | ale | Note Edited: 0050467 | |
2023-11-20 20:03 | nitramr | Note Added: 0050495 | |
2023-11-20 20:03 | nitramr | File Added: line_markers.png | |
2023-11-20 20:05 | nitramr | Note Edited: 0050495 | |
2023-11-21 11:24 | ale | Note Added: 0050496 | |
2023-11-22 22:51 | nitramr | Note Added: 0050502 | |
2023-11-22 22:51 | nitramr | File Added: error.png | |
2023-11-22 22:51 | nitramr | File Added: ok.png | |
2023-11-23 06:40 | ale | Note Added: 0050503 | |
2023-11-23 06:45 | ale | Note Added: 0050504 | |
2023-11-25 18:55 | nitramr | Note Added: 0050514 | |
2023-11-25 18:55 | nitramr | File Added: Bildschirmfoto vom 2023-11-25 19-40-24.png | |
2023-11-25 18:55 | nitramr | File Added: Bildschirmfoto vom 2023-11-25 19-40-35.png | |
2023-11-25 19:08 | ale | Note Added: 0050515 | |
2023-11-25 19:08 | ale | Note Edited: 0050515 |