|· Hosting provided by Anduin.net / Øverby Consulting ·|
|Anonymous | Login | Signup for a new account||2013-05-23 04:53 CEST|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002899||Scribus||User Interface||public||05-Dec-05 14:16||12-Aug-19 14:39|
|Target Version||Fixed in Version|
|Summary||0002899: Why don't make also base lines snapping?|
|Description||I think will be useful to make di "guide base lines" (I don't know how to call in english, I use italian version..., well, the grey ones...) snappable.|
The complete grid (green one) is not much useful because vertical lines doesn't match with margins and colmns, so I decided to use the Guide base lines (grey ones).
But the column guide do snap, others no...
|Additional Information||Another solution maybe separate horizontal and vertical lines in the "green" grid, so I can use horizontal "green" lines and not the grey ones|
|Tags||No tags attached.|
|Would love this too!|
I think baseline snapping is a good idea, so objects can be synchronized with text.
kavs0007, in the mean time, you could also make your own guides (the blue ones), with the manage guides tool on the page menu. You can have as many as you want automatically generated and apply them to all pages if you want them to act like the baseline grid.
This brings up a good point: all these concepts--main grid, baseline grid, guides, and margins--are closely related; maybe they could be unified into a single general framework. You would have a single general way to create guide lines, either individaully or in autospaced groups, the latter either by absolute spacing (like the baseline grid) or by subdivision of an existing space (the way you can with guides). You could define multiple guide sets as styles and apply them to as many pages or frames as you like, and any set could be allowed to be used as baselines for text, column boundaries, page subdivisions, print cropping boundaries (like margins), etc.--not only a single and/or equally spaced special-purpose set for each function. Any set could be set to snap or not independently.
What would be really neat is to allow them to be defined relative to each other (equal subdivisions within margins or columns, for instance) and/or to other objects (like bug 3343), and for some or all of these relationships to be able to be made persistent--so changing line spacing could adjust the baseline grid, or vice-versa, and persistently-snapped objects would adjust accordingly, or your four equal subdivisions of a column, along with anything snapped to them, would auto-update if you change the size of the column. Of course persistent snapping would be optional. Some CAD programs have facilities for this kind of thing.
This would integrate nicely with a more general idea for relative placement and stylable frame positioning that I had, which I'll post as soon as I finish thinking it through coherently. :)
Interesting! Though I do have a little concern: a snap to guide option is useful when you have a few guides, imo. The baseline grid has so many lines... it could become annoying to make this grid "snapable". What do you think?
How about an option to make any specific line on that grid snapable through the Guide Manager and show it with a different color?
I think this would help the designer better than having a whole lot of snapable lines everywhere on the page. But we could leave the option of making all the guides snapable as well, whenever needed, to make everyone happy!
Other consideration: I barely never use the small and large grids. But I use all the time the baseline grid and the margins and the columns guides. Mainly because this is really what defines the structure of the pages in publications of many pages, with text and pictures (eg. magazines). Of course, if I were to design posters and stand alone ad pages, I would prefer (maybe) to use the large/small grid. This is to say we might want to make a better integration of the columns/margins guides AND baseline grid on one hand, and the regular grid on the other. I have difficulties considering working with both at the same time. I think they exist for different purposes.
The synchronization of objects with text can be achieved a different way by anchoring objects to text. The objects then follow the paragraph settings or the wordspace, depending on where it is located. The object can also be aligned just like a paragraph. Changes into paragraph formatting make the objects move as well, with the text.
I agree that baseline grid should be set not too far away from the linespacing. Wether change in one should reflects on the other is questionable imo. Considering the fact that there may be lots of various linespace in a page, which one is THE one?
That said, I still think the idea is worth digging! The idea per se is interesting. I wonder what others would say.
Great idea to be able to set individual grid lines snappable. This could apply to normal guides too: you might want to define all the guides you need for various aspects of the layout but then on the fly enable or disable specific ones for snapping, depending on what aspect you're working on. If you could define separate sets of guides that you could switch between that would also help.
Maybe another idea could be to snap only when holding down some modifier key, so you can freely position objects except when you specifically want to snap.
>> This is to say we might want to make a better integration of the columns/margins guides AND baseline grid on one hand, and the regular grid on the other.
Arbitrary user-defined grid/guide sets where you can select at any time which one(s) to use would let everyone use exactly what they want.
Incidentally, a suggestion christoph_s brought up in bug 0002724 to have different guides for different layers could be possible with this scheme--it could be as simple or as intricate as users want.
>> The synchronization of objects with text can be achieved a different way by anchoring objects to text.
Right, like we can do to some extent now with inline frames. But snapping to a baseline would provide a different possibility, anchoring an object to a line in a text frame, regardless of what text is actually there. Both mechanisms are useful.
>> I agree that baseline grid should be set not too far away from the linespacing. Wether change in one should reflects on the other is questionable imo. Considering the fact that there may be lots of various linespace in a page, which one is THE one?
There are two ways you can define a baseline grid--as a fixed sequence with a set spacing between the lines (like it is now) or with the gridlines actually anchored to the real text baselines. If you change a paragraph's line spacing, the whole grid adjusts accordingly. The point of the second approach would be to allow what I described above, snapping another object to a given line of text in a frame. Again, I think both would be useful.
The general principle is that guides could be independent or defined by/anchored to objects, just like objects could be independent or anchored to guides.
|05-Dec-05 14:16||kavs0007||New Issue|
|06-Jan-16 23:46||plinnell||Severity||minor => feature|
|06-Jan-16 23:46||plinnell||Status||new => acknowledged|
|06-Jan-16 23:46||plinnell||Product Version||1.3.2cvs => 1.3.3cvs|
|06-Mar-08 19:41||PLucAuclair||Note Added: 0009162|
|06-Mar-13 21:34||mkoren||Note Added: 0009238|
|06-Apr-13 13:09||louisdesjardins||Note Added: 0009884|
|06-Apr-14 19:16||mkoren||Note Added: 0009963|
|06-Apr-20 21:14||mhanski||Relationship added||related to 0003538|
|06-May-24 21:31||christoph_s||Relationship added||related to 0003865|
|09-Dec-06 19:41||jghali||Relationship added||has duplicate 0008483|
|12-Aug-19 14:39||ale||Relationship added||related to 0011038|
|Main | My View | View Issues | Change Log | Roadmap|
|Copyright © 2000 - 2013 MantisBT Team|