I give up, what's the new secret to starting Linux-PgS, much less
actually using it???
I changed all the 'deron" libs files to point to me.
Does the old shell startup file I'm using, thanks to Tim Doty,not work?
What am I missing (beside my mind?)

#!/bin/bash
export PGSPATH=/home/gracia/PgS
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PGSPATH/SoftLogik/lib
export PATH=$PATH:$PGSPATH
$PGSPATH/PageStream4
exit 0

--
Gracia...living in Cooleemee, NC
***Registered Linux user #263390 - SuSE 8.2 Pro***

Hi!

On Tuesday 19 August 2003 16:12, Gracia M. Littauer wrote:
> I give up, what's the new secret to starting Linux-PgS, much less
> actually using it???
> I changed all the 'deron" libs files to point to me.
> Does the old shell startup file I'm using, thanks to Tim Doty,not work?
> What am I missing (beside my mind?)
>
> #!/bin/bash
> export PGSPATH=/home/gracia/PgS
> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PGSPATH/SoftLogik/lib
> export PATH=$PATH:$PGSPATH
> $PGSPATH/PageStream4
> exit 0

I'm still using the same script. What I did was backup my PgS directory,
create a new one, extracted the archive into the new directory, copied the
script into the new directory, and fixed the links.

If this does not work for you perhaps there is something wrong with the links?
If you open a terminal window, change to the SoftLogik/lib directory and type
"ls -l" (without the quotes) the output should look something like:

tim@thrim:~/PgS/SoftLogik/lib> ls -l
[snip]
lrwxrwxrwx 1 tim users 24 2003-08-18 17:20
libSoftLogikApp.so.1 -> libSoftLogikApp.so.1.0.0
-rwxr-xr-x 1 tim users 205728 2003-08-17 18:36
libSoftLogikApp.so.1.0.0
[snip]

Tim Doty

> Hi!

> If this does not work for you perhaps there is something wrong with
> the links? If you open a terminal window, change to the SoftLogik/lib
> directory and type "ls -l" (without the quotes) the output should
> look something like:
>
> tim@thrim:~/PgS/SoftLogik/lib> ls -l
> [snip]
> lrwxrwxrwx 1 tim users 24 2003-08-18 17:20
> libSoftLogikApp.so.1 -> libSoftLogikApp.so.1.0.0
> -rwxr-xr-x 1 tim users 205728 2003-08-17 18:36
> libSoftLogikApp.so.1.0.0
> [snip]

what I have is more like this:

gracia@linux:~/PgS/SoftLogik/lib> ls -l
total 540
-rw-r--r-- 1 gracia users 914 2003-08-14 22:26
SoftLogikApp.rsc
-rw-r--r-- 1 gracia users 2058 2003-08-14 19:54
SoftLogikDisp.rsc
lrwxrwxrwx 1 gracia users 24 2003-08-19 20:43
libSoftLogikApp.so.1 -> libSoftLogikApp.so.1.0.0
-rwxr-xr-x 1 gracia users 205728 2003-08-17 19:36
libSoftLogikApp.so.1 .0.0
-rwxr-xr-x 1 gracia users 241668 2003-08-17 19:40
libSoftLogikDisp.so. 1.0.0

I used your instructions...even cut & pasted so not to make a typo.
I have used every variation I could think of to make it work, but
without a degree in computer science, I cry 'uncle' and will wait for a
correct DL.

--
Gracia...living in Cooleemee, NC
Registered Linux user #263390 - SuSE 8.2 Pro
yahoo....n 1: not very intelligent or interested in culture

Gracia M. Littauer wrote:

> what I have is more like this:
>
> gracia@linux:~/PgS/SoftLogik/lib> ls -l
> total 540
> -rw-r--r-- 1 gracia users 914 2003-08-14 22:26
> SoftLogikApp.rsc
> -rw-r--r-- 1 gracia users 2058 2003-08-14 19:54
> SoftLogikDisp.rsc
> lrwxrwxrwx 1 gracia users 24 2003-08-19 20:43
> libSoftLogikApp.so.1 -> libSoftLogikApp.so.1.0.0
> -rwxr-xr-x 1 gracia users 205728 2003-08-17 19:36
> libSoftLogikApp.so.1 .0.0
> -rwxr-xr-x 1 gracia users 241668 2003-08-17 19:40
> libSoftLogikDisp.so. 1.0.0
>
> I used your instructions...even cut & pasted so not to make a typo.
> I have used every variation I could think of to make it work, but
> without a degree in computer science, I cry 'uncle' and will wait for a
> correct DL.
>
I'm not sure what has happened to libSoftLogikDisp.so. and
libSoftLogikApp.so.1 (filename split like that).

It looks to me that libSoftLogikApp.so.1 is the only one that's
pointing to correct filename (even though the file it is pointing to has
its filename split).

libSoftLogikOS.so.1.0.0 and libSoftLogikRsrc.so.1.0.0 are missing.

It may be easier to unpack the archive again, and use

ln -s libSoftLogikDisp.so.1 libSoftLogikDisp.so.1.0.0
ln -s libSoftLogikApp.so.1 libSoftLogikApp.so.1.0.0
ln -s libSoftLogikOS.so.1 libSoftLogikOS.so.1.0.0
ln -s libSoftLogikRsrc.so.1 libSoftLogikRsrc.so.1.0.0

(use the bash auto-complete [tab key] to avoid typos, my typing is
terrible, so don't cut and paste )

thanks,
<Ivan.

--
Ivan Dunn
Project Officer - Web Development and Support

Faculty of Mathematics & Computing,
The Open University,
Walton Hall,
Milton Keynes.
MK7 6AA.

On Wednesday 20 August 2003 03:41, I.Dunn wrote:
> Gracia M. Littauer wrote:
> > what I have is more like this:
> >
> > gracia@linux:~/PgS/SoftLogik/lib> ls -l
> > total 540
> > -rw-r--r-- 1 gracia users 914 2003-08-14 22:26
> > SoftLogikApp.rsc
> > -rw-r--r-- 1 gracia users 2058 2003-08-14 19:54
> > SoftLogikDisp.rsc
> > lrwxrwxrwx 1 gracia users 24 2003-08-19 20:43
> > libSoftLogikApp.so.1 -> libSoftLogikApp.so.1.0.0
> > -rwxr-xr-x 1 gracia users 205728 2003-08-17 19:36
> > libSoftLogikApp.so.1 .0.0
> > -rwxr-xr-x 1 gracia users 241668 2003-08-17 19:40
> > libSoftLogikDisp.so. 1.0.0
> >
> > I used your instructions...even cut & pasted so not to make a typo.
> > I have used every variation I could think of to make it work, but
> > without a degree in computer science, I cry 'uncle' and will wait for a
> > correct DL.
>
> I'm not sure what has happened to libSoftLogikDisp.so. and
> libSoftLogikApp.so.1 (filename split like that).
>
> It looks to me that libSoftLogikApp.so.1 is the only one that's
> pointing to correct filename (even though the file it is pointing to has
> its filename split).
>
> libSoftLogikOS.so.1.0.0 and libSoftLogikRsrc.so.1.0.0 are missing.
>
> It may be easier to unpack the archive again, and use
>
> ln -s libSoftLogikDisp.so.1 libSoftLogikDisp.so.1.0.0
> ln -s libSoftLogikApp.so.1 libSoftLogikApp.so.1.0.0
> ln -s libSoftLogikOS.so.1 libSoftLogikOS.so.1.0.0
> ln -s libSoftLogikRsrc.so.1 libSoftLogikRsrc.so.1.0.0
>
> (use the bash auto-complete [tab key] to avoid typos, my typing is
> terrible, so don't cut and paste )

I concur, especially long lines are prone to getting munged up by email and
having some sort of white space inserted in the names.

However, the lines you give are in error: the name order is swapped. The
"real" files are the .1.0.0. When making a link you specify the target of the
link and then the name of the link being created.

E.g.,

ln -s foo bar

creates the link bar pointing to foo. The -s specifies that the link be
symbolic. Think of it like a copy command. You are copying <from> <to>

Tim Doty

Tim Doty wrote:
> On Wednesday 20 August 2003 03:41, I.Dunn wrote:
--- cut --- 8< ---
>>It may be easier to unpack the archive again, and use
>>
>>ln -s libSoftLogikDisp.so.1 libSoftLogikDisp.so.1.0.0
>>ln -s libSoftLogikApp.so.1 libSoftLogikApp.so.1.0.0
>>ln -s libSoftLogikOS.so.1 libSoftLogikOS.so.1.0.0
>>ln -s libSoftLogikRsrc.so.1 libSoftLogikRsrc.so.1.0.0
>>
>>(use the bash auto-complete [tab key] to avoid typos, my typing is
>>terrible, so don't cut and paste )

> However, the lines you give are in error: the name order is swapped. The
> "real" files are the .1.0.0. When making a link you specify the target of the
> link and then the name of the link being created.
>
> E.g.,
> ln -s foo bar
>
> creates the link bar pointing to foo. The -s specifies that the link be
> symbolic. Think of it like a copy command. You are copying <from> <to>
>
> Tim Doty
>
Oops, Sorry.

I did say 'don't cut and paste' (especially my comments!)

thanks,
<Ivan.

--
Ivan Dunn
Project Officer - Web Development and Support

Faculty of Mathematics & Computing,
The Open University,
Walton Hall,
Milton Keynes.
MK7 6AA.

OK, there are a number of Linux experts on this list. What would be the
best way to deal with these issues? I guess the biggest issue is the
location of the libraries. Should they just be dumped into the usr/libs
like everything else? As I understand it, we still have to force an update
of the lib cache of names/paths?

Otherwise, should an installer script just create a script something like
below?

>I give up, what's the new secret to starting Linux-PgS, much less
>actually using it???
>I changed all the 'deron" libs files to point to me.
>Does the old shell startup file I'm using, thanks to Tim Doty,not work?
>What am I missing (beside my mind?)
>
>#!/bin/bash
>export PGSPATH=/home/gracia/PgS
>export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PGSPATH/SoftLogik/lib
>export PATH=$PATH:$PGSPATH
>$PGSPATH/PageStream4
>exit 0
>
>--
>Gracia...living in Cooleemee, NC
>***Registered Linux user #263390 - SuSE 8.2 Pro***

Deron Kazmaier - support@grasshopperllc.com
Grasshopper LLC Publishing -http://www.grasshopperllc.com
PageStream DTP for Amiga, Linux, Macintosh, and Windows

PageStream Support wrote:
> OK, there are a number of Linux experts on this list. What would be the
> best way to deal with these issues? I guess the biggest issue is the
> location of the libraries. Should they just be dumped into the usr/libs
> like everything else? As I understand it, we still have to force an update
> of the lib cache of names/paths?
>
that would require a root install, something I don't like doing at the
best of times.

I'm certainly not a linux expert, but wouldn't statically linked
libraries be easier?
(Only don't ask me how!)

thanks,
<Ivan.

--
Ivan Dunn
Project Officer - Web Development and Support

Faculty of Mathematics & Computing,
The Open University,
Walton Hall,
Milton Keynes.
MK7 6AA.

On Tue, 19 Aug 2003 17:36:49 -0500
PageStream Support <support@grasshopperllc.com> wrote:

> OK, there are a number of Linux experts on this list. What would be
> the best way to deal with these issues? I guess the biggest issue is
> the location of the libraries. Should they just be dumped into the
> usr/libs like everything else? As I understand it, we still have to
> force an update of the lib cache of names/paths?
>
> Otherwise, should an installer script just create a script something
> like below?
>
> >I give up, what's the new secret to starting Linux-PgS, much less
> >actually using it???
> >I changed all the 'deron" libs files to point to me.
> >Does the old shell startup file I'm using, thanks to Tim Doty,not
> >work? What am I missing (beside my mind?)
> >
> >#!/bin/bash
> >export PGSPATH=/home/gracia/PgS
> >export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PGSPATH/SoftLogik/lib
> >export PATH=$PATH:$PGSPATH
> >$PGSPATH/PageStream4
> >exit 0
> >
> >--
> >Gracia...living in Cooleemee, NC
> >***Registered Linux user #263390 - SuSE 8.2 Pro***
>
>
> Deron Kazmaier - support@grasshopperllc.com
> Grasshopper LLC Publishing -http://www.grasshopperllc.com
> PageStream DTP for Amiga, Linux, Macintosh, and Windows
========================

Deron,
I believe with the condition that PgS is in right now, it would be safer
to keep things as they are and only be installed by the user. As
unstable and unfinished as the whole project is, I just don't think
doing anything as root would be a wise idea. Plus it is already
difficult enough for many just getting it working now.

Are you planning on making a corrected download available, so that users
do not have to struggle to see at least what PgS looks like? I guess
you could just redirect them to the site, so they could see the
screenshots, but that won't do you much good for feedback on how badly
it's operating presently. ;o)

I guess that's just one of the differences in open source and commercial
software. Open source, although just a part time project for the
developers, tends to get fixed much quicker and respond faster to the
users requests than it seems commercial software and developers do. Not
saying that you don't respond and we certainly don't want you spending
all your time on the mail list, but I would think it wouldn't be so much
trouble to make available the software in a usable state and if not, in
error, at least respond quickly with a repaird download and simple
instructions on getting it working. If not you, then let someone help?

Ok, ok, ranting over and I know it sounds harsh, but I think myself and
others are a bit disappointed. I have used PgS since it's release on
the Amiga and as an Amiga dealer, pushed it like crazy to customers,
schools. When you announced it for Linux and made it seem to be ready
for release, I was estatic and began announcing it to my fellow Linux
users. Selling it again, if you will. Do you have an idea how unhappy
everyone became after realizing the state of the software?

Regards,
Patrick

--
---SuSE Linux v8.2 Pro---
Registered Linux User #225206
"Life's a garden, Dig It!" --Joe Dirt

On Wed, 20 Aug 2003 15:04:27 +0100
"I.Dunn" <I.Dunn@open.ac.uk> wrote:

> Tim Doty wrote:
> > On Wednesday 20 August 2003 03:41, I.Dunn wrote:
> --- cut --- 8< ---
> >>It may be easier to unpack the archive again, and use
> >>
> >>ln -s libSoftLogikDisp.so.1 libSoftLogikDisp.so.1.0.0
> >>ln -s libSoftLogikApp.so.1 libSoftLogikApp.so.1.0.0
> >>ln -s libSoftLogikOS.so.1 libSoftLogikOS.so.1.0.0
> >>ln -s libSoftLogikRsrc.so.1 libSoftLogikRsrc.so.1.0.0
> >>
> >>(use the bash auto-complete [tab key] to avoid typos, my typing is
> >>terrible, so don't cut and paste )
>
> > However, the lines you give are in error: the name order is swapped.
> > The "real" files are the .1.0.0. When making a link you specify the
> > target of the link and then the name of the link being created.
> >
> > E.g.,
> > ln -s foo bar
> >
> > creates the link bar pointing to foo. The -s specifies that the link
> > be symbolic. Think of it like a copy command. You are copying <from>
> > <to>
> >
> > Tim Doty
> >
> Oops, Sorry.
>
> I did say 'don't cut and paste' (especially my comments!)
>
> thanks,
> <Ivan.
>

Remember, you may need to edit the /etc/ld.so.conf file (that's what's
called under debian) to point to /the/path/you/installed/PageStream4,
and then rerun ldconfig -v to get things setup correctly.

--
Rodney D. Myers <rdmyers@pe.net> Registered Linux User #96112
ICQ#: AIM#: YAHOO:
18002350 mailman452 mailman42_5

They that can give up essential liberty to obtain a
little temporary safety deserve neither liberty nor safety.
Ben Franklin - 1759

[Non-text portions of this message have been removed]

> > OK, there are a number of Linux experts on this list. What would be the
> > best way to deal with these issues? I guess the biggest issue is the
> > location of the libraries. Should they just be dumped into the usr/libs
> > like everything else? As I understand it, we still have to force an update
> > of the lib cache of names/paths?
> >
>that would require a root install, something I don't like doing at the
>best of times.
>
>I'm certainly not a linux expert, but wouldn't statically linked
>libraries be easier?
> (Only don't ask me how!)

I don't think that would work well unless we also link in all the add ons
etc! All of the various filters, language modules, etc all use calls in the
library. If we make them static linked libraries we are going to have some
really big installs

>thanks,
> <Ivan.

Deron Kazmaier - support@grasshopperllc.com
Grasshopper LLC Publishing -http://www.grasshopperllc.com
PageStream DTP for Amiga, Linux, Macintosh, and Windows

[Non-text portions of this message have been removed]

>I believe with the condition that PgS is in right now, it would be safer
>to keep things as they are and only be installed by the user. As
>unstable and unfinished as the whole project is, I just don't think
>doing anything as root would be a wise idea. Plus it is already
>difficult enough for many just getting it working now.

I am asking about how a final product should be installed on a users
machine. Feedback that I would hope some folks on this list are interested
in giving.

I'm not sure what you were originally expecting, and I'm sorry if those
expectations were not met. On the other hand, from my point of view the
software is for the most part useable on my machine and now I am trying to
figure out what to do to help get it working at least that well on others
computers. Linux seems to be a power users OS trying to appear to a novice
user. I'm hoping that the power users on this list can help the novice
users, and I can figure out how to resolve these problems automatically for
the novice users.

At this point the only positive problem ID I have is that the links for the
libs where broken. As you may recall, I asked at the time if everyone was
OK fixing the links themselves or if they wanted a new download. I've not
heard from anyone who has asked for a new download. I'll presume that you
want that download.

>Are you planning on making a corrected download available, so that users
>do not have to struggle to see at least what PgS looks like? I guess
>you could just redirect them to the site, so they could see the
>screenshots, but that won't do you much good for feedback on how badly
>it's operating presently. ;o)
>
>I guess that's just one of the differences in open source and commercial
>software. Open source, although just a part time project for the
>developers, tends to get fixed much quicker and respond faster to the
>users requests than it seems commercial software and developers do.

Not sure how that conclusion is reached, but you are welcome to yours as I
am mine.

>Not
>saying that you don't respond and we certainly don't want you spending
>all your time on the mail list, but I would think it wouldn't be so much
>trouble to make available the software in a usable state and if not, in
>error, at least respond quickly with a repaird download and simple
>instructions on getting it working. If not you, then let someone help?
>
>Ok, ok, ranting over and I know it sounds harsh, but I think myself and
>others are a bit disappointed. I have used PgS since it's release on
>the Amiga and as an Amiga dealer, pushed it like crazy to customers,
>schools. When you announced it for Linux and made it seem to be ready
>for release, I was estatic and began announcing it to my fellow Linux
>users. Selling it again, if you will. Do you have an idea how unhappy
>everyone became after realizing the state of the software?

Well, I guess we just have different point of views and yours is tainted by
an initial expectation of being complete? I can see your disappointment.
You are looking for a finished product and looking back at an unfinished
product. On the other hand, I'm excited that a year ago we were just
finishing a survey trying to decide what platforms to support next (and
heck Amiga OS4 was "going to be out by Christmas 02" and I'm working
with an almost finished product (at least on my computer).

Either half full or half empty, it still has problems. Can we try and solve
them instead?

I will be uploading new libraries, links and a new PageStream all with
debug symbols. If folks who can, I would appreciate it if you could install
it over the full installation and then from a shell CD to the directory and
type:

gdb PageStream4

This will load the debugger (if it is installed on your machine and
load PageStream.
Then type a single "r" and press return. The debugger will then run
PageStream. Any errors should be reported back in the shell, and if it
crashes it should catch it there. Hopefully then you can enter "bt" and it
will give a back trace of the calls and how it got there. That should be
sufficient information to help me find the problem.

Thanks!

>Regards,
>Patrick

Deron Kazmaier - support@grasshopperllc.com
Grasshopper LLC Publishing -http://www.grasshopperllc.com
PageStream DTP for Amiga, Linux, Macintosh, and Windows

[Non-text portions of this message have been removed]

--- In PageStreamLinuxBeta@yahoogroups.com, PageStream Support
<support@g...> wrote:
> I will be uploading new libraries, links and a new PageStream all
> with debug symbols. If folks who can, I would appreciate it if you
> could install it over the full installation and then from a shell CD
> to the directory and type:
>
> gdb PageStream4
>
> This will load the debugger (if it is installed on your machine
> and load PageStream.
> Then type a single "r" and press return. The debugger will then run
> PageStream. Any errors should be reported back in the shell, and if
> it crashes it should catch it there. Hopefully then you can enter
> "bt" and it will give a back trace of the calls and how it got
> there. That should be sufficient information to help me find the
> problem.

DEBUGGING TIPS:
To automatically detect bad memory access:
valgrind -q --gdb-attach=yes PageStream4
seehttp://devel-home.kde.org/~sewardj for docs

To automatically trace system call including failed file opens:
strace PageStream4
look at the output for problems

For GUI debugging use insight or ddd followed by exe name.

LINKING AND INSTALLATION:
Loki Games used hybrid static/shared library linkage to maximize
portability (use -L for default linkage locations). This helps avoid
chasing GTK versions and bugs across different Linux distros.
Furthermore, their installer is available for free!

--Jonathan--

P.S. I was disappointed 4 months ago, but progress has been great!

>DEBUGGING TIPS:
>To automatically detect bad memory access:
> valgrind -q --gdb-attach=yes PageStream4
> see
> <http://devel-home.kde.org/~sewardj>http://devel-home.kde.org/~sewardj for docs
>
>To automatically trace system call including failed file opens:
> strace PageStream4
> look at the output for problems
>
>For GUI debugging use insight or ddd followed by exe name.
>
>LINKING AND INSTALLATION:
>Loki Games used hybrid static/shared library linkage to maximize
>portability (use -L for default linkage locations). This helps avoid
>chasing GTK versions and bugs across different Linux distros.
>Furthermore, their installer is available for free!

Thanks for sharing this great info!

>--Jonathan--
>
>P.S. I was disappointed 4 months ago, but progress has been great!

Deron Kazmaier - support@grasshopperllc.com
Grasshopper LLC Publishing -http://www.grasshopperllc.com
PageStream DTP for Amiga, Linux, Macintosh, and Windows

[Non-text portions of this message have been removed]

On Wed, 20 Aug 2003 16:04:22 -0500
PageStream Support <support@grasshopperllc.com> wrote:

[...]
> I am asking about how a final product should be installed on a users
> machine. Feedback that I would hope some folks on this list are
> interested in giving.
> ==============

Thanks for clarifying that as it makes a difference in the responses you
will get. With a finished product, it would be better to be installed
as root, so all users on the network could get to it and individual
settings be kept in the user's home, just like all other Linux programs.
I am guessing after the program becomes completely usable and stable, it
will be used in production circumstances, thus in a network environment.
------------------------

> I'm not sure what you were originally expecting, and I'm sorry if
> those expectations were not met. On the other hand, from my point of
> view the software is for the most part useable on my machine and now I
> am trying to figure out what to do to help get it working at least
> that well on others computers. Linux seems to be a power users OS
> trying to appear to a novice user. I'm hoping that the power users on
> this list can help the novice users, and I can figure out how to
> resolve these problems automatically for the novice users.
> ================

Well, I was expecting what was announced and that was a usable product
Deron. Sorry I misunderstood your original announcements or maybe I was
just being over zealous about the fact that PgS was available for Linux!
-----------------

> At this point the only positive problem ID I have is that the links
> for the libs where broken. As you may recall, I asked at the time if
> everyone was OK fixing the links themselves or if they wanted a new
> download. I've not heard from anyone who has asked for a new download.
> I'll presume that you want that download.
> =====================

Well, I think you might have many other problems you aren't aware of yet
by using Mandrake. I'll let you do the investigation on that part.
Yes, I remember you asking that, but I would have thought with people
having difficulties, you would have guessed a corrected upload would
have been a normal thing to do. Again, I am sorry for assuming too
much.
---------------------

>
> >Are you planning on making a corrected download available, so that
> >users do not have to struggle to see at least what PgS looks like? I
> >guess you could just redirect them to the site, so they could see the
> >screenshots, but that won't do you much good for feedback on how
> >badly it's operating presently. ;o)
> >
> >I guess that's just one of the differences in open source and
> >commercial software. Open source, although just a part time project
> >for the developers, tends to get fixed much quicker and respond
> >faster to the users requests than it seems commercial software and
> >developers do.
>
> Not sure how that conclusion is reached, but you are welcome to yours
> as I am mine.
> ==================

Not trying to offend with those statements, just wanting to make you
aware of what you face. In order to make the product worth purchasing,
then the product has to have the support and quality of a good
commercial product.
-------------------

> Well, I guess we just have different point of views and yours is
> tainted by an initial expectation of being complete? I can see your
> disappointment. You are looking for a finished product and looking
> back at an unfinished product. On the other hand, I'm excited that a
> year ago we were just finishing a survey trying to decide what
> platforms to support next (and heck Amiga OS4 was "going to be out by
> Christmas 02" and I'm working with an almost finished product (at
> least on my computer).
> ====================

I think any of us here that were Amiga users knew that AmigaOS 4 would
not see the light of day for a very long time if ever. Anyone expecting
otherwise had/has blinders on their eyes. I still believe you made a
good decision to make PgS available on Linux! I am hoping it rewards
you as well as the Amiga version did.
----------------------

> Either half full or half empty, it still has problems. Can we try and
> solve them instead?
>
> I will be uploading new libraries, links and a new PageStream all with
> debug symbols. If folks who can, I would appreciate it if you could
> install it over the full installation and then from a shell CD to the
> directory and type:
>
> gdb PageStream4
>
> This will load the debugger (if it is installed on your machine
> and load PageStream.
> Then type a single "r" and press return. The debugger will then run
> PageStream. Any errors should be reported back in the shell, and if it
>
> crashes it should catch it there. Hopefully then you can enter "bt"
> and it will give a back trace of the calls and how it got there. That
> should be sufficient information to help me find the problem.
>
> Thanks!

> Deron Kazmaier - support@grasshopperllc.com
> Grasshopper LLC Publishing -http://www.grasshopperllc.com
> PageStream DTP for Amiga, Linux, Macintosh, and Windows
====================

You might want to temporarily program in a setting in the preferences to
allow a debugging log for the users instead of expecting them to be
"power" users in Linux as you put it. I know the programs I am helping
to beta test in KDE are presently that way and make giving feed back
very easy to the developer. Or you might actually think about selecting
only beta testers while the program is in such an unfinished state,
rather than having the users get aggravated at not being able to use
something they paid for? If you are planning to have the program in a
stable release state sometime soon, you don't need the same reports
duplicated to go over. I am actually looking forward to someday
actually using PgS again in Linux, but for now, Scribus works nicely.

Regards,
Patrick

--
---SuSE Linux v8.2 Pro---
Registered Linux User #225206
"Life's a garden, Dig It!" --Joe Dirt

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 20 August 2003 02:04 pm, PageStream Support wrote:
- -------------snip------------
> At this point the only positive problem ID I have is that the links
> for the libs where broken. As you may recall, I asked at the time if
> everyone was OK fixing the links themselves or if they wanted a new
> download. I've not heard from anyone who has asked for a new
> download. I'll presume that you want that download.

I didn't have any problem re-creating the proper links but for some
reason I had a bear of a time extracting the archive.

(Note, I'm not much of a typist so) I first tried extracting w/
konqueror/karchiver's "extract here" option. This appeared to do the
job but on further inspection I found that no ..."/SoftLogik/lib/"
directory was extracted (as well as a few other directories). I tried a
couple of other gui tools for extraction which also failed to unpack
the whole archive, eventually I found something that worked (I don't
remember what.) I suspect a problem w/ the archive but no-one else has
reported it so maybe my experience was unique.

Curiously, the extracted directories also took more than a regular
amount of effort just to move them from one place to another(I was
working as root so that wasn't the problem). The file permissions
appeared to be in order but konqueror was not to willing to move/copy
things (directories) where I wanted them. Eventually I used the gentoo
(file manager) to place the files where I needed them.

I run SuSE 8.1 w/ xfree86 4.2.0 and kde 3.1.3, and consider myself
reasonably knowledgable about how things work in linux (even if I do
avoid the command line when I can).

> I will be uploading new libraries, links and a new PageStream all with
> debug symbols. If folks who can, I would appreciate it if you could >
> install

will do

> and I'm working with an almost finished product (at least on my
> computer).

The potential of Pagestream4 is beginning to show, unfortunately it
still segfaults before I get very far w/ it, I guess my glass is still
half empty ;-(

Thanks for your hard work, looking forward to the next archive.
- --
dh
Don't shop at GoogleGear.com!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/RNDzBwgxlylUsJARAlzcAJ0XOBG/1221Crakwzlk4phlG6i25ACgiJew
73H8OAhcJwabHuMBfa/2QSo=
=Stxu
-----END PGP SIGNATURE-----

On Thursday 21 August 2003 09:02, David Herman wrote:
[snip]
> (Note, I'm not much of a typist so) I first tried extracting w/
> konqueror/karchiver's "extract here" option. This appeared to do the
> job but on further inspection I found that no ..."/SoftLogik/lib/"
> directory was extracted (as well as a few other directories). I tried a
> couple of other gui tools for extraction which also failed to unpack
> the whole archive, eventually I found something that worked (I don't
> remember what.) I suspect a problem w/ the archive but no-one else has
> reported it so maybe my experience was unique.

In this case I think you'd have been much better off on the command line, but
maybe that's because I'm familiar with it. Here's a "mixed mode" idea:

Use Konqueror to move the archive where you want the files to be. In my case
this would be ~/PgS. Then go to the "Window" menu and select "Show Terminal
Emulator". Drag the archive icon to the terminal window. When you let go a
menu pops up; choose paste. Click to in front of the quoted text string and
type (w/o the quotes), "tar -xzf " -- including a space after the 'f'. Hit
return and voila the archive is extracted. It may not be an all gui tool, but
you are nominally working inside of konqueror.

Tim Doty

>
> Curiously, the extracted directories also took more than a regular
> amount of effort just to move them from one place to another(I was
> working as root so that wasn't the problem). The file permissions
> appeared to be in order but konqueror was not to willing to move/copy
> things (directories) where I wanted them. Eventually I used the gentoo
> (file manager) to place the files where I needed them.
>
> I run SuSE 8.1 w/ xfree86 4.2.0 and kde 3.1.3, and consider myself
> reasonably knowledgable about how things work in linux (even if I do
> avoid the command line when I can).
>
> > I will be uploading new libraries, links and a new PageStream all with
> > debug symbols. If folks who can, I would appreciate it if you could >
> > install
>
> will do
>
> > and I'm working with an almost finished product (at least on my
> > computer).
>
> The potential of Pagestream4 is beginning to show, unfortunately it
> still segfaults before I get very far w/ it, I guess my glass is still
> half empty ;-(
>
> Thanks for your hard work, looking forward to the next archive.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 21 August 2003 03:43 pm, Tim Doty wrote:
> On Thursday 21 August 2003 09:02, David Herman wrote:
> [snip]
>> (Note, I'm not much of a typist so) I first tried extracting w/
>> konqueror/karchiver's "extract here" option. This appeared to do the
>> job but on further inspection I found that no ..."/SoftLogik/lib/"
>> directory was extracted (as well as a few other directories)

- ----snip----

> In this case I think you'd have been much better off on the command
> line,

You're undoubtably right about that...

> but maybe that's because I'm familiar with it. Here's a "mixed
> mode" idea:

> Use Konqueror to move the archive where you want the files to be. In
> my case this would be ~/PgS. Then go to the "Window" menu and select
> "Show Terminal Emulator". Drag the archive icon to the terminal
> window. When you let go a menu pops up; choose paste. Click to in
> front of the quoted text string and type (w/o the quotes), "tar -xzf
> " -- including a space after the 'f'. Hit return and voila the
> archive is extracted.

Thanks, I did look at my command cheat sheet but couldn't find my notes
for tar's command switches, your tip will be kept close at hand.

the Problems I had extracting and moving the files from the archive
didn't show up when I tried it in mandrake (9.0 I think) so perhaps it
was a SuSE quirk.

Thanks again for the tip.
- --
dh
Don't shop at GoogleGear.com!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/RWe2BwgxlylUsJARAvgCAJwOnDHk3oiviVA5lGN0VASLhWQiPgCfWQXY
QJedpadk+J3/QgvpwDJs4vA=
=P6f1
-----END PGP SIGNATURE-----

On Tue, Aug 19, 2003 at 05:36:49PM -0500, PageStream Support wrote:
> OK, there are a number of Linux experts on this list. What would

I hasten to prefix my comments by stating that I'm a long way from
being an expert; but here goes:

> be the best way to deal with these issues? I guess the biggest
> issue is the location of the libraries. Should they just be dumped
> into the usr/libs like everything else? As I understand it, we
> still have to force an update of the lib cache of names/paths?

Pagestream's own libraries should be kept within its own application
tree, default install under /opt.

KDE, Gnome, etc all do that and it's a clean way of ensuring that
you get all the stuff when you have to clean up or upgrade the rest
of the system.

A variation of the theme is to place libraries in a sub-directory of
/usr/lib, but I much prefer the other method.

> Otherwise, should an installer script just create a script something like
> below?

A "wrapper" is a common thing to do, It's the only thing (IMHO) that
could legitimately be dropped in /usr/bin

The wrapper can be tailored at installation time.

--
/"\ Bernd Felsche - Innovative Reckoning, Perth, Western Australia
\ / ASCII ribbon campaign | I'm a .signature virus!
X against HTML mail | Copy me into your ~/.signature
/ \ and postings | to help me spread!