[scribus] Bullets and numbering

Ken Springer snowshed1 at q.com
Thu Mar 3 16:23:05 UTC 2016


On 3/2/16 9:35 AM, ale rimoldi wrote:
> hey
>
>>
>>> This video is a bit dated, but shows the process. There might be a
>>> nonvideo page on the wiki about this, but I'm not sure.
>>
>> The video definitely does not apply to 1.4.6 or 1.5.1
>
> the process is the same for 1.4.6.
> menus have changed a bit but the features to be used are the same and
> you will find them in similar places.
>
> this applies to 1.5.x, too. (even if the menus are even more different)
>
> if you don't see the similarities, i would suggest you to make a few
> steps back and go through an introductory tutorial in scribus. most of
> all the parts on paragraph formatting.

I found it.  OE on my part.

I would suggest videos like this need to be kept up to date.

>> The Help File for 1.5.1 says there's automatic bullets, but doesn't
>> bother to tell you where to find the settings.
>
> it's in the paragraph effects, iirc...

I found it, thank you.  The phrase "paragraph effects" isn't in the help 
file, though.  :-)

>
>> One thing I've noticed about a lot of help files...  To access a
>> feature, the file will say "Open X and select Y".  The problem is,
>> they don't tell you where X is.  :-(  Extremely frustrating for the
>> new user.
>
> easily frustrated new users, might first want to go through an
> introduction to scribus.

You're not frustrated until you start getting pi$$ed.  <G>

> the flossmanuals (en.flossmanuals.net/scribus-2/) is not a bad resource.

IMO, this resource should be on the web page, and linked in the help file.

> some people can jump in the middle and figure out the missing bits (or
> where to find them), other need a more structured, step by step approach...

Agreed, but this is where ease of use comes in to play.  The easier it 
is for a new user to get something done, the better the program design, IMO.

I've tinkered/used/played with a few page layout programs over they 
years.  Including but not limited to:
	DA's Layout
	Calamus
	Pagestream
	MS Publisher
	Pages (there is a page layout portion in the program, just like MS 
Office now.)
	Serif Page Plus X6 (X8 is the current version.)
	Scribus

Granted, all those programs are not the same level of sophistication, 
but it's easy to see when ease of use is a primary concern, as opposed 
to more features.

IMO, the least user friendly are Calamus and Scribus.  Most user 
friendly, Page Plus.  Definition of user friendly being how easy it is 
to actually get something accomplished right out the box.  Being able to 
find the tools and features you want easily, or discover you want as you 
use the program, makes a big difference.

> once you got through that, you will know where the style manager or the
> properties palette are...
>
> it's a hard task to keep the balance between repeating over and over all
> the details and write a readable text (also for people who already know
> scribus but need a reference text).

But you need to repeat for the benefit any *new* user that tries Scribus 
or any other program.  Those new users represent the future success of 
any program, both commercial and open source.

>> I'll have to find the wiki and see if it's there.
>
> good luck!

Thank you.

>> The devs have put things in the Windows menu that I would never look
>> for under that menu heading.  Such as Align and Distribute. You're
>> aligning and distributing frames, not windows.
>
> i feel some very bad karma here...
> but i agree with you: the menus in scribus are getting crazier and crazier.

In this area, IMO you should emulate the menus and contents thereof of 
what most programs do.  That's one thing I've admired about Macs, once 
you know where a particular feature is located, such as Print, you know 
where it is in almost every other program.  *That* is user friendly.

> in most cases, there is a reason why something is in windows rather than
> in edit, but i don't think it makes much sense to start a discussion on it.
> most of the entries in windows should be moved out from there.
>
>> Also discovered that closing the program doesn't close the help
>> window.  Bad manners there.
>
> yes. no. yes. no... maybe.
>
> there are several requirements for the help window, and the easiest way
> to meet most of them, is to run scribus and the help tool as separate
> programs.
> that's why, once scribus started the help, it cannot close it...
>
> if you know a better way: closing the help when closing scribus is
> indeed a good idea!

Why can't Scribus check to see if the help manual is open, and if so 
close it, during the shut down process?

-- 
Ken
Mac OS X 10.8.5
Firefox 44.0
Thunderbird 38.0.1
"My brain is like lightning, a quick flash
      and it's gone!"




More information about the scribus mailing list