[Scribus] Congratulations and initial comments...

[Louis Desjardins]

2007/9/26, Asif Lodhi <asif.lodhi at gmail.com>:
>
> Hi John,
>
> On 9/25/07, John Beardmore <John at t4sltd.co.uk> wrote:
> > > * In addition to the existing feature of creating a Scribus file,
> > introduce yet
> > >   another option - "Create Project..." - that will make Scribus create
> a
> > >   directory (instead of a single SLA file), bearing the Project-Name
> or
> > Scribus
> > >   file-name, and place all SLA files related to
> > >   the project in the project directory.
> >
> > Including the .sla ?
>
> Yes. The suggestion is to create "a project" (in a project directory)
> and put SLA file in that directory AND provide the user "an option to
> copy the image-file to the project directory" upon insertion of each
> image in the SLA. That's when you try to insert an image into the
> current SLA, the Scribus should give you an option to copy that image
> into the project directory. That's how it goes in normal
> web-application development tools like DreamWeaver in which you also
> have to deal with external images. This way all the images, etc. get
> copied to the project folder and you can clearly see that "your
> project is the whole folder" and NOT a single SLA file - so you will
> remember to move the whole folder/directory instead of just an SLA
> file. Of course, you can do all that yourself - that is, create a
> project folder and move all the related images in that directory.
> Having Scribus do the same thing just adds to the usability and helps
> alleviate inconvenience.
>
> > > The project directory could be a local directory or one created in a
> > > remote server or whatever. Actually, this is just like the web
> > > application management
> > > feature present in Macromedia DreamWeaver (now owned by Adobe).
> >
> > Not sure how this differs from the 'collection directory' idea expressed
> > earlier ?


Actually, it doesn't. This is, phrased in a more elegant and detailed
manner, exactly what I am talking about since the beginning of this thread.
:)

I do think the way Scribus handles images is ok ? that is, linked files. I
do not support the idea of having pictures embedded into the .sla file for
workflow reasons. What I suggest is of course a RFE and is not at all in my
view a "must have feature" but it is a "should have" or "would be nice to
have" since I see so many people struggling with the broken links or, worst,
lost images. And this is not a Scribus-only issue. I of course agree that
embedding images would clearly save the broken links and lost images issues
but I think we would have far more issues dealing with such huge file, and
editing images in the workflow. For this reason, I think the "dynamic
collect" (optional) would be a better way.

When I make the workshops on Scribus, I strongly insist on the fact that the
work must be well organized in order to take full advantages of the
software. Creating a Text and an Image folder in the early stages of a
project does help keep things together. If for various reasons someone finds
this way to work is not suitable in a particular environment, then simply
don't check the "Dynamic Collect" option and use whatever method you prefer.
In the end, one would still have the option to "Collect for output" (and
actually, this "for output" is a bit of a disturbance here because there are
other reasons why one would want to "Collect", archiving the job being one
of them).

I haven't used that feature if you're talking about the "Collect for
> Output" option. But that creates a folder only when you use that
> option. I am suggesting to have Scribus create an SLA file in a
> project-directory right from the beginning and putting each image,
> that user inserts in the SLA, in the project directory.


Right.

--
> Best regards,


Louis

Asif
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://nashi.altmuehlnet.de/pipermail/scribus/attachments/20070926/c2869f87/attachment.html