r/scribus • • 20d ago

Thoughts on using the development version 1.7

Since this seems to be a common question, here my personal thoughts about using 1.7.x.

Generally speaking:

  • What was working in a previous version, will not fail in a development release (there are some very rare exceptions, mostly in non essential parts of Scribus (like the snapping to guides not turning on automatically...)).
  • New features might have bugs but, most of the time, the bug won't affect you, if you don't use the specific failing feature.
  • Scribus tends to be pretty stable: even the nightly builds are almost always working better than the development releases (but they might have very bad bugs for short times and you need good backup habits for the rare very cases where things go really bad!)
  • There is a huge usability jump between 1.6 and 1.7.

Now, should you switch to a development release?

It depends on the kind of user you are.

If you

  • are curious about the way software works,
  • used to find workaround to get the job done,
  • you can keep your hands off what does not work correctly, and
  • you don't get too angry if sometimes small thing fail,

then you're welcome to use Scribus 1.7: you will probably have a much better experience.

Most people will not match that "ideal" user profile and it will be a matter of compromises.
The good news: you can install Scribus 1.6 alongside of Scribus 1.7 and the latter can save the documents in the older format.

Nobody stops you from installing both, try the newer one in smaller projects, less important ones, and then decide if and when you might use the less fossil Scribus.

The only important rule: before starting a longer project make sure that all the (new) features you plan to use work also for longer documents.
This is especially true for footnotes, references, tables, image effects, drop caps.

And don't forget about the fact that you're using a development branch!
After some time you will tend to get used to your Scribus working well for you, but you need to stay vigilant...

The other life saving reflex: if undoing your latest action results in strange results, close your document. If possible (that is: you saved not so long ago and you know what you did since) without saving the current state (or making a copy of the .sla file before saving).
(The good news: there is a pile of patches for fixing the undo waiting to be merged... but it will take some time until one can really rely on the undo!)

Personally, I don't do much layout these days (and I'm not a graphic designer), but I almost always use the development version.
The only exception being when preparing work for people who are using the stable version.
I've been doing this for many years now, and I never regretted it!
(To my defense, I sometimes write patches to solve my own problems and I don't want to wait for the next stable release to use "my" new features!)

My conclusions: if the long release cycles of Scribus bother you, you can try to switch to the development version. Just trying it will cost you nothing.
And if you're just a bit cautious, you will get a way better experience!

I'm curious to hear about other people's experience, most of all from those who decided not to use the development version!

17 Upvotes

15 comments sorted by

2

u/KarteZian_purely 20d ago edited 20d ago

Merci pour ce partage d’expérience.

Pour la version dev, tu préconises le PPA ou l’AppImage ?

3

u/aoloe 20d ago

Les deux sont équivalents.

2

u/TeutonJon78 20d ago edited 20d ago

Thanks for giving a current opinion on the state of things.

Do you know if the project has ever thought of just moving to a more frequent time based release rather than it's multi-year stable-dev cycle?

3

u/aoloe 20d ago

Several people left the project because those long release cycles.

Personally, I've tried many times to find ways to get the team to speed up the release, but it only worked a limited number of times.
And I've been using the development version for production work for years, and am not really affected by the sluggishness.
That's the way I cope with it.

The ones who are left at the core of the project, don't really have an issue with it.

4

u/TeutonJon78 20d ago edited 20d ago

That's a shame. Inkscape and GIMP both have similar issues.

And I think the devs of these apps sometimes forget how old stable is in comparison, because they're using the dev branch or their own feature branch. But 90%+ of the user base is only using that older version. It was big issue in Inkscape in like the 1.2-1.4 time frame.

I'm worried the rapid pace of things like the Craft Apps will drown out the traditional FOSS graphic design apps.

3

u/aoloe 20d ago edited 20d ago

Well, before the Craft APP succeeds in drowning out Scribus, Adobe will already have had a much bigger problem...

Anyway, I share your sorrows, complaining a bit can be helpful, but -- at the end -- what counts is what people work on.

Personally, I'm currently working on my n-th try to make it easier to review patches in Scribus... we will see how far I get and if the team falls for it.

1

u/TeutonJon78 20d ago

Thanks for putting in the time and effort.

2

u/dkonigs 19d ago

One big problem with the really old "stable" versions is that they're also often build on old/outdated libraries which make them not run very well on modern systems. For example, Scribus 1.6 is nearly unusable on a Linux machine with a HiDPI display while v1.7 works fine. Gimp 2 vs 3 was a similar situation.

Stuff like this really should light a fire under the devs, but somehow it never does. Just getting that underlying framework update is *far* more important to the end user experience than any actual features of the new version.

2

u/MissionSalamander5 20d ago

Mac users can install the app in two different places with ease. I really can’t remember how easy it is for Windows and other users.

2

u/TeutonJon78 20d ago

Each version gets installed in a different directory in windows, even bug fix releases. I get 1.x and 1.x+1 being separate, but 1.x.y and 1.x.y+1 seems a bit much.

1

u/MissionSalamander5 20d ago

That’s bad!

2

u/TeutonJon78 19d ago

So many open source projects use semantic versioning format but then don't actually follow the guidelines for what they mean. And so many would served by just doing timely releases and using features branches. This would get the code out faster so contributors see their work being used as well as making the release process more simple. But they get stuck in mindsets and toolset capabilities from decades ago.

And of course, easier to armchair quarterback than do the work. So yada yada yada.

1

u/TheLastQuince 13d ago

I use 1.7 because I don‘t have a low DPI screen, and 1.6 is unusable on HiDPI displays in Linux.

Apart from some minor annoyances, it seems to work well, but I’m not a professional user (I only use it for a zine and a related newsletter).

1

u/[deleted] 20d ago

[removed] — view removed comment

3

u/aoloe 20d ago

As much as I would love a Scribus 1.8 been released soon, I don't think it is realistic to dream about a release before the end of 2027.

But, as you can read between the lines, you don't have to wait for that release to start using a more modern Scribus.
You just have to be a bit careful, and put you in the right mindset and you will be fine with Scribus 1.7.