Hi!

Not everything reported to date has been fixed, but a good number of them
have been in this release! The biggest ones off the top of my head:

Text sped way up. Now it is actually useable for documents with more than a
few words. Funny thing is I first added character caching, and the speed
barely changed. As it turns out, the font caching wasn't working right. So
with _each_ character FreeType had to rebuild internal font data. It was a
silly 1/2 line error that once fixed accounted for 99% of the speed up.
Could have had fast text all along had I noticed (I just assumed it would
be slow without text caching. As it turns out, Freetype is very fast!)

Printing Type 1 fonts had a bug in it if the datasegment was odd length it
wouldn't get printed right.

Windows will more or less stay where you put them when you "remember window
position".

TextFX, gradient text, text to path, etc now working!

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]

Great! New version! Woohoo!

Um... where did the menu strip go?

Tim Doty

On Tuesday 02 December 2003 10:55, PageStream Support wrote:
> Hi!
>
> Not everything reported to date has been fixed, but a good number of them
> have been in this release! The biggest ones off the top of my head:
>
> Text sped way up. Now it is actually useable for documents with more than a
> few words. Funny thing is I first added character caching, and the speed
> barely changed. As it turns out, the font caching wasn't working right. So
> with _each_ character FreeType had to rebuild internal font data. It was a
> silly 1/2 line error that once fixed accounted for 99% of the speed up.
> Could have had fast text all along had I noticed (I just assumed it would
> be slow without text caching. As it turns out, Freetype is very fast!)
>
> Printing Type 1 fonts had a bug in it if the datasegment was odd length it
> wouldn't get printed right.
>
> Windows will more or less stay where you put them when you "remember window
> position".
>
> TextFX, gradient text, text to path, etc now working!
>
>
>
> 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]
>
>
>
> To unsubscribe from this group, send an email to:
> PageStreamLinuxBeta-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject tohttp://docs.yahoo.com/info/terms/

Ok, what do you mean by menu strip? The toolbar can be turned on and off
from the window menu?

>Great! New version! Woohoo!
>
>Um... where did the menu strip go?
>
>Tim Doty
>
>On Tuesday 02 December 2003 10:55, PageStream Support wrote:
> > Hi!
> >
> > Not everything reported to date has been fixed, but a good number of them
> > have been in this release! The biggest ones off the top of my head:
> >
> > Text sped way up. Now it is actually useable for documents with more than a
> > few words. Funny thing is I first added character caching, and the speed
> > barely changed. As it turns out, the font caching wasn't working right. So
> > with _each_ character FreeType had to rebuild internal font data. It was a
> > silly 1/2 line error that once fixed accounted for 99% of the speed up.
> > Could have had fast text all along had I noticed (I just assumed it would
> > be slow without text caching. As it turns out, Freetype is very fast!)
> >
> > Printing Type 1 fonts had a bug in it if the datasegment was odd length it
> > wouldn't get printed right.
> >
> > Windows will more or less stay where you put them when you "remember window
> > position".
> >
> > TextFX, gradient text, text to path, etc now working!

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 Tuesday 02 December 2003 17:56, PageStream Support wrote:
> Ok, what do you mean by menu strip? The toolbar can be turned on and off
> from the window menu?

There is a toolbar, but no menu. None. Nada. E.g., you cannot go to the File
menu and open a file as there is no menu. Period.

Using KDE 3 on SuSE.

Tim Doty

>
> >Great! New version! Woohoo!
> >
> >Um... where did the menu strip go?
> >
> >Tim Doty
> >
> >On Tuesday 02 December 2003 10:55, PageStream Support wrote:
> > > Hi!
> > >
> > > Not everything reported to date has been fixed, but a good number of
> > > them have been in this release! The biggest ones off the top of my
> > > head:
> > >
> > > Text sped way up. Now it is actually useable for documents with more
> > > than a few words. Funny thing is I first added character caching, and
> > > the speed barely changed. As it turns out, the font caching wasn't
> > > working right. So with _each_ character FreeType had to rebuild
> > > internal font data. It was a silly 1/2 line error that once fixed
> > > accounted for 99% of the speed up. Could have had fast text all along
> > > had I noticed (I just assumed it would be slow without text caching. As
> > > it turns out, Freetype is very fast!)
> > >
> > > Printing Type 1 fonts had a bug in it if the datasegment was odd length
> > > it wouldn't get printed right.
> > >
> > > Windows will more or less stay where you put them when you "remember
> > > window position".
> > >
> > > TextFX, gradient text, text to path, etc now working!
>
> 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]
>
>
>
> To unsubscribe from this group, send an email to:
> PageStreamLinuxBeta-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject tohttp://docs.yahoo.com/info/terms/

Okay, I don't know what is going on. I went back to what I have here as 4.1.6
and it also does not have the menu strip any more. Nor does 4.1j.

I removed the .PageStream directory and ran 4.1.6.12 again. Of course it asked
for registration. After that, same thing, no menu strip.

Removed the directory and ran 4.1.6 again. Same thing.

What the ?!?!?

Started combing through my work spaces. Ah hah! The menu strip is being
created in work space 6 (the last place I had run PgS before downloading the
new version).

All is well, sorta. I have no idea why that one window (the menu strip) got
locked into that work space. I *had* tried to get window positions
remembered, but it had never worked and in any case did not lock the other
windows to that work space.

Tim Doty

This may not be new, but I noticed that when drag selecting text it does not
register the "mouse up" event. This causes some interesting problems as the
selection activity does not terminate...

Tim Doty

On Tue, Dec 02, 2003 at 10:55:20AM -0600, PageStream Support wrote:
>
> Not everything reported to date has been fixed, but a good number
> of them have been in this release! The biggest ones off the top of
> my head:

...

Anything about the file opening problem I'm getting? i.e. PageStream
file from my Amiga won't open on SuSE 8.2 Linux with KDE 3.1.

--
/"\ 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!

I'm using the latest PgS to create a new document. I must say that I am very
impressed. I wish that the (looked up names in Preferences to get this right)
toolbar was around, but I am getting by without it. Even though shift-ctrl-d
is not the same as the ctrl-c I'm familiar with, it works and is not *too*
much of a finger contortion. To be honest if it can't be the ctrl-c short cut
I'd rather it be ctrl-d and then have the number code be the shift-ctrl-d.
The mnemonics are so much more useful for me that I'd rather them be the easy
ones to type. Something else I'd like is the click-delay to get the fly-outs.
I'm sure I'll get used to right-clicking, but I still keep trying to
click-and-hold.

Typing is going quite well. I loaded an existing document and played around a
little and the speed was quite comfortable.

The display of text frames feels a little funny. If the text frame follows the
guides most of the guides are completely obscured and their frame is not
drawn so the edges are indistinct.

D*mn, I got carried away and tried to use the borders tool. Instant seg-fault.
I think I'd saved my work ;^) I ran PgS again and opened the file. Font
substitution requestor appears (?) and suggests that for Tomas Regular (?!) I
display it as Classical Garamond Regular. Tomas? I have no such font. For
what its worth the document was created in Classical Garamond. I told it to
convert the font and the document opened. Save and reopen and no substitution
requestor.

Scrolling the page still trashes the display of it. Not the end of the world,
but annoying.

Scroll select works now though it consistently did not get mouse-up events
previously.

Selecting type style (e.g., italic) does not style the text, even though the
style is present. This is desirable, as would be shortcuts for invoking them.
I guess ctrl-p for plain is right out as that is already for printing. Is it
possible for PgS to use the windows meta keys common on recent keyboards?
That would alleviate some of the only-so-many-keys-for-so-many-shortcuts
syndrom.

And before I head to bed: Printing is broken here. It went back to an old
behavior: substituting Courier for the font. And for some reason I was
expecting it to duplex. I then printed thumbnails. Since I haven't used this
in a long time if ever I don't have a whole lot for comparison, but the
output simply doesn't look right. I said to use printers marks (which I have
done before) and it overprinted the greyscale over the registration marks.

There were outlines for the pages that were numbered, but these did not align
with the pages (which mis-printed identical to the normal print). Also note
that the printer is set to 180lpi/1200dpi according to the PgS print
requestor, but the printout says its 60.0lpi.

I decided to see if I needed to specify the PPD again and in Print Setup
clicked on the button to specify the PPD. I noticed that it defaulted to a
PPD named lp.ppd located in the PPD directory. I copied my ppd from its
current name and location to here. Same results.

Because I'm a glutton I tried to save as a PDF. This generated in invalid PDF
(acroread complained a lot and was unable to display it).

Question: have you decided for sure on the scripting language yet? How far are
we from getting an implementation? I used scripting on the amiga and am eager
to do so again. In fact, I really need it to be able to do work, otherwise
some repetitive tasks are simply far too repetitive.

Tim Doty

A minor point. Tip #39, the second character "that should always be followed
by a space" displays as an S-caron (I think that's the right name). I don't
remember for sure, but perhaps the intended character is the british pound?
Also, for the en- and em- dashes there are screwy looking things: a box with
0097 and 0098 inside as a matrix.

Tim Doty

Tried printing another document, but as I need it to duplex and PgS turns off
duplexing I printed it to a postscript file and then converted the postscript
to PDF so that I can print it duplex from Acrobat Reader. Convoluted? Well,
its how I've done this before from PgS Amiga.

The document in question is actually a set of pictures, one to a page. Note:
even though konqueror and pixie have not trouble reading the original images
(tiff), PgS (Amiga or Linux) cannot read them. Unsupported compression was
the error IIRC. So I converted them to gif. These load fine. Because they are
images I wasn't concerned about the print issues with the most recent release
of PgS Linux beta.

The problem is that the print is for a booklet so I need signatures. I
selected two across in imposition and ran through the above steps. However,
only even numbered pages printed.

For the curious, the "booklet" consists of page scans from the Zoega Old
Icelandic dictionary of 1910 and PgS seemed like a reasonable way of getting
this printed for easier reference.

Tim Doty

Problem with pasting non-printing objects.

1. Use the note tool to create a non-printing text frame
2. Cut (or copy) it
3. Paste does not work

It seems to me that it is getting to the clipboard because it disappears when
doing a cut. The cursor flashes when trying to paste, but nothing happens.

Tim Doty

On Sat, 6 Dec 2003 05:39 am, Tim Doty wrote:
> Tried printing another document, but as I need it to duplex and PgS turns
> off duplexing I printed it to a postscript file and then converted the
> postscript to PDF so that I can print it duplex from Acrobat Reader.
> Convoluted? Well, its how I've done this before from PgS Amiga.
>
> The document in question is actually a set of pictures, one to a page.
> Note: even though konqueror and pixie have not trouble reading the original
> images (tiff), PgS (Amiga or Linux) cannot read them. Unsupported
> compression was the error IIRC. So I converted them to gif. These load
> fine. Because they are images I wasn't concerned about the print issues
> with the most recent release of PgS Linux beta.
>

re your tiffs. I usually use PNG but PGS doesn´t support PNG so I used tiff.
Use The Gimp to save them as uncompressed tiff. PGS supports that. I didn´t
try the other tiff options (just in case)

> The problem is that the print is for a booklet so I need signatures. I
> selected two across in imposition and ran through the above steps. However,
> only even numbered pages printed.
>

Ah! That would confirm the problem I am having.
re: the 4 page A4 newsletter I have produced. It´s on hold until I can come up
with the final PDF. I too print to a postscript file, run it through
Distiller (on my networked Mac) to produce the PDF. As separate A4 pages it´s
OK but, like you, have to do signatures, 2 across and 1 down.

There are pics on pp 1, 2 and 4. When I checked the PDF the pics on p1 were
missing. Two unframed graphics and one whose frame is stroked. The frame is
printed. I was thinking it was because they were on p 1.
I tried rearranging the pages as p1 and 4 became 2 & 3 etc and then discovered
it was odd numbered pages that have the problem. (I also tried inserting two
blank pages and making chapters but nothing overcomes the problem)

> For the curious, the "booklet" consists of page scans from the Zoega Old
> Icelandic dictionary of 1910 and PgS seemed like a reasonable way of
> getting this printed for easier reference.
>
> Tim Doty
>
>
>
> To unsubscribe from this group, send an email to:
> PageStreamLinuxBeta-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject tohttp://docs.yahoo.com/info/terms/

--
Ken

ken at kenandjj dot net

>I'm using the latest PgS to create a new document. I must say that I am very
>impressed. I wish that the (looked up names in Preferences to get this right)
>toolbar was around, but I am getting by without it.

If you choose "show toolbar" from the window menu, does it not appear
directly below the menu bar?

>Even though shift-ctrl-d
>is not the same as the ctrl-c I'm familiar with, it works and is not *too*
>much of a finger contortion. To be honest if it can't be the ctrl-c short cut
>I'd rather it be ctrl-d and then have the number code be the shift-ctrl-d.

This was done back on the Windows machine. The problem is of course, that
control-c is "copy" on Windows/Linux.

>The mnemonics are so much more useful for me that I'd rather them be the easy
>ones to type. Something else I'd like is the click-delay to get the fly-outs.
>I'm sure I'll get used to right-clicking, but I still keep trying to
>click-and-hold.

I'll take a look and see what I can do.

>The display of text frames feels a little funny. If the text frame follows
>the
>guides most of the guides are completely obscured and their frame is not
>drawn so the edges are indistinct.

Could you be more specific? If your guides are drawing "in back", then
wouldn't they be obscured by something drawn to them?

>Scrolling the page still trashes the display of it. Not the end of the world,
>but annoying.

This one is perplexing. The problem seems to be that I can get multiple
scroll events before the first refresh occurs. So un-redrawn region of the
screen gets scrolled down/up and doesn't get refreshed.

>Selecting type style (e.g., italic) does not style the text, even though the
>style is present. This is desirable, as would be shortcuts for invoking them.
>I guess ctrl-p for plain is right out as that is already for printing. Is it
>possible for PgS to use the windows meta keys common on recent keyboards?
>That would alleviate some of the only-so-many-keys-for-so-many-shortcuts
>syndrom.

The problem is conforming to standards. I'll look and see if I can even use
the key.

>Question: have you decided for sure on the scripting language yet? How far
>are
>we from getting an implementation? I used scripting on the amiga and am eager
>to do so again. In fact, I really need it to be able to do work, otherwise
>some repetitive tasks are simply far too repetitive.

I've not done anything. I have been trolling for some python help (it was
the most requested scripting language last year) but all I'm getting is
offer for perl help!

>Tim Doty

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 Sunday 07 December 2003 14:56, PageStream Support wrote:
> >I'm using the latest PgS to create a new document. I must say that I am
> > very impressed. I wish that the (looked up names in Preferences to get
> > this right) toolbar was around, but I am getting by without it.
>
> If you choose "show toolbar" from the window menu, does it not appear
> directly below the menu bar?

You got me! I'm so used to it just being there in PgS Amiga it didn't even
occur to me to look for that. Color me idiotic...

>
> >Even though shift-ctrl-d
> >is not the same as the ctrl-c I'm familiar with, it works and is not *too*
> >much of a finger contortion. To be honest if it can't be the ctrl-c short
> > cut I'd rather it be ctrl-d and then have the number code be the
> > shift-ctrl-d.
>
> This was done back on the Windows machine. The problem is of course, that
> control-c is "copy" on Windows/Linux.

Right, which brings me back to the crtl-d vs. shift-ctrl-d argument. Of
course, it probably needs to stay the way it is to avoid too many changes,
but it just easn't as easy to hit on the fly. Sigh.
>
> >The mnemonics are so much more useful for me that I'd rather them be the
> > easy ones to type. Something else I'd like is the click-delay to get the
> > fly-outs. I'm sure I'll get used to right-clicking, but I still keep
> > trying to click-and-hold.
>
> I'll take a look and see what I can do.

Thanks!
>
> >The display of text frames feels a little funny. If the text frame follows
> >the
> >guides most of the guides are completely obscured and their frame is not
> >drawn so the edges are indistinct.
>
> Could you be more specific? If your guides are drawing "in back", then
> wouldn't they be obscured by something drawn to them?

Sorry I wasn't clear. I do a lot with two-column frames. Use 100% view, draw a
two-column frame. The left side of the frame obscures the frame guide, but
there is no line drawn to indicate that the frame is there. Without starting
UAE up I'm reasonably sure that in PgS Amiga the frame has something drawn to
indicate its existance. Note also that the right side of the frame *does not*
obscure the frame guide. Likewise the top guide is obscured but the bottom
one is not.

If this is still not clear perhaps I could send you a screen shot of what I
mean?

Also, playing around to get this email written I managed to, after scrolling
the window down in 100% view, get the select state of the text frame toggled.
That is, the resize boxes were drawn when the text frame was not selected and
disappeared when it was. Once I figured out what was going on I resized the
frame and it returned to normal behavior.
>
> >Scrolling the page still trashes the display of it. Not the end of the
> > world, but annoying.
>
> This one is perplexing. The problem seems to be that I can get multiple
> scroll events before the first refresh occurs. So un-redrawn region of the
> screen gets scrolled down/up and doesn't get refreshed.

I have confidence that you'll get it worked out. I doubt there is anything I
could do to help with that particular problem, but if you have any ideas I'm
willing to try.
>
> >Selecting type style (e.g., italic) does not style the text, even though
> > the style is present. This is desirable, as would be shortcuts for
> > invoking them. I guess ctrl-p for plain is right out as that is already
> > for printing. Is it possible for PgS to use the windows meta keys common
> > on recent keyboards? That would alleviate some of the
> > only-so-many-keys-for-so-many-shortcuts syndrom.
>
> The problem is conforming to standards. I'll look and see if I can even use
> the key.

Thanks.
>
> >Question: have you decided for sure on the scripting language yet? How far
> >are
> >we from getting an implementation? I used scripting on the amiga and am
> > eager to do so again. In fact, I really need it to be able to do work,
> > otherwise some repetitive tasks are simply far too repetitive.
>
> I've not done anything. I have been trolling for some python help (it was
> the most requested scripting language last year) but all I'm getting is
> offer for perl help!

Well, I think perl is great ;^) An oracle front-end project I was working on
got moved from C++ to perl at the last minute and even with learning perl
from scratch I got it done in time. Since then I have written a CMS for a
company using perl and mysql as well as numerous other programs and utilities
for personal use. Perl may not always be the "best" solution, but it sure is
quick to develop. And after getting used to some of the layout quirks in Tk
I've done some stuff in Perl/Tk as well.

I'm sure I could learn python fast enough so I don't mind if you go that
route, but I am itching to get some scripting done. ;^)

Tim Doty

> > >Question: have you decided for sure on the scripting language yet? How far
> > >are
> > >we from getting an implementation? I used scripting on the amiga and am
> > > eager to do so again. In fact, I really need it to be able to do work,
> > > otherwise some repetitive tasks are simply far too repetitive.
> >
> > I've not done anything. I have been trolling for some python help (it was
> > the most requested scripting language last year) but all I'm getting is
> > offer for perl help!
>
>Well, I think perl is great ;^) An oracle front-end project I was working on
>got moved from C++ to perl at the last minute and even with learning perl
>from scratch I got it done in time. Since then I have written a CMS for a
>company using perl and mysql as well as numerous other programs and utilities
>for personal use. Perl may not always be the "best" solution, but it sure is
>quick to develop. And after getting used to some of the layout quirks in Tk
>I've done some stuff in Perl/Tk as well.
>
>Tim Doty

OK Tim, I'll test that enthusiasm. Maybe you can help with perl. How about
a simple sample script that would do something in PageStream as you would
envision the interface to PageStream working? As I recall, perl is object
based.

Maybe a script like the old replace graphic script or something like that?
Or just read the coordinates of a selected box, and then draw a column
inside it that is a little smaller and then fill it with some text? Use
something as close to the PageStream arexx implementation.

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]

Okay, here goes an adaptation of a script I use. I won't say its the best way
because (especially in perl) there is more than one way to skin a cat. I'm
assuming the SelectObject function would be overloaded and that PageStreamLib
would exist as an installed perl module.

Tim Doty

--snip--
#!/usr/bin/perl

# BorderBox.ps
# Draws a border box around the selected object
# Border box has the object style 'tint' applied

use PageStreamLib; # the library of PgS functions

$hObject = PGS->GetObject();
$hObject->SetFilled("off");

%Coords = $hObject->GetCoords();
$Coords{'left'} -= 0.0625;
$Coords{'top'} -= 0.0625;
$Coords{'right'} += 0.0625;
$Coords{'bottom'} += 0.0625;

$hBox = PGS->DrawBox(%Coords);
$hBox->SendToBack();
$hBox->SetObjectStyle("tint");
PGS->SelectObject($hBox,"add");
PGS->Group();

$TextWrap{'type'} = "boundingbox";
$TextWrap{'xstandoff'} = 0.0625;
$TextWrap{'ystandoff'} = 0.0625;
$TextWrap{'mode'} = "wraparound";
PGS->SetTextWrap(%TextWrap);

Thanks for this. I've been digging around on the perl website, but they
certainly make it hard to find the kind of information I need to integrate
it into an existing application. I'm not about to rewrite PageStream in
their pseudo C preprocess format

I do have a question for you about your choice of possible implementation.
The PageStream data model could be looked at as a simple "tree". PageStream
has a list of documents. Each document has things like chapters, articles,
pages. Pages have objects. Objects have objects.

First, I presume that the only initially exposed object would be PageStream
(or in your example, PGS)?

Second, this makes reasonable sense:
>$hObject->SetFilled("off");

But

>$hObject = PGS->GetObject();

This would be like a shortcut then for (forgive me, my total knowledge of
perl is from what you just wrote so if I have something wrong please explain).

$hDocument = PGS->GetDocument();
$hObject = $hDocument->GetObject();

Also, would it error out if more than one object was selected? Or would
GetObject have parameters like FAIL | FIRST | LAST | NEAR x y??

I've got a new version coming tonight. It fixes a pretty large number of
loose ends, and should make PageStream useable for everyone (assuming that
everyone reported the problems they were having!)

Of course, don't expect scripting to be running!

Deron

>Okay, here goes an adaptation of a script I use. I won't say its the best way
>because (especially in perl) there is more than one way to skin a cat. I'm
>assuming the SelectObject function would be overloaded and that PageStreamLib
>would exist as an installed perl module.
>
>Tim Doty
>
>--snip--
>#!/usr/bin/perl
>
># BorderBox.ps
># Draws a border box around the selected object
># Border box has the object style 'tint' applied
>
>use PageStreamLib; # the library of PgS functions
>
>$hObject = PGS->GetObject();
>$hObject->SetFilled("off");
>
>%Coords = $hObject->GetCoords();
>$Coords{'left'} -= 0.0625;
>$Coords{'top'} -= 0.0625;
>$Coords{'right'} += 0.0625;
>$Coords{'bottom'} += 0.0625;
>
>$hBox = PGS->DrawBox(%Coords);
>$hBox->SendToBack();
>$hBox->SetObjectStyle("tint");
>PGS->SelectObject($hBox,"add");
>PGS->Group();
>
>$TextWrap{'type'} = "boundingbox";
>$TextWrap{'xstandoff'} = 0.0625;
>$TextWrap{'ystandoff'} = 0.0625;
>$TextWrap{'mode'} = "wraparound";
>PGS->SetTextWrap(%TextWrap);
>

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 Friday 12 December 2003 16:54, PageStream Support wrote:
> Thanks for this. I've been digging around on the perl website, but they
> certainly make it hard to find the kind of information I need to integrate
> it into an existing application. I'm not about to rewrite PageStream in
> their pseudo C preprocess format

Quite understandable.
>
> I do have a question for you about your choice of possible implementation.
> The PageStream data model could be looked at as a simple "tree". PageStream
> has a list of documents. Each document has things like chapters, articles,
> pages. Pages have objects. Objects have objects.

Yep
>
> First, I presume that the only initially exposed object would be PageStream
> (or in your example, PGS)?

Yep. And I used PGS only because I like shorter (meaningful) names as opposed
to longer names.
>
> Second, this makes reasonable sense:
> >$hObject->SetFilled("off");
>
> But
>
> >$hObject = PGS->GetObject();
>
> This would be like a shortcut then for (forgive me, my total knowledge of
> perl is from what you just wrote so if I have something wrong please
> explain).
>
> $hDocument = PGS->GetDocument();
> $hObject = $hDocument->GetObject();

You got me! Sorry about that. Just to make clear, I was using a naming
convention for those, its not part of perl per se. $hDocument reads 'handle
(for) document'.

>
> Also, would it error out if more than one object was selected? Or would
> GetObject have parameters like FAIL | FIRST | LAST | NEAR x y??

I was considering that when I wrote the pseudo code. I think it would be good.
I think passing parameters via ... I'm drawing a blank on the perl name for
it, but associative lists (e.g., %Coords) is the way to go.
>
> I've got a new version coming tonight. It fixes a pretty large number of
> loose ends, and should make PageStream useable for everyone (assuming that
> everyone reported the problems they were having!)
>
> Of course, don't expect scripting to be running!
>
> Deron
>
> >Okay, here goes an adaptation of a script I use. I won't say its the best
> > way because (especially in perl) there is more than one way to skin a
> > cat. I'm assuming the SelectObject function would be overloaded and that
> > PageStreamLib would exist as an installed perl module.
> >
> >Tim Doty
> >
> >--snip--
> >#!/usr/bin/perl
> >
> ># BorderBox.ps
> ># Draws a border box around the selected object
> ># Border box has the object style 'tint' applied
> >
> >use PageStreamLib; # the library of PgS functions
> >
> >$hObject = PGS->GetObject();
> >$hObject->SetFilled("off");
> >
> >%Coords = $hObject->GetCoords();
> >$Coords{'left'} -= 0.0625;
> >$Coords{'top'} -= 0.0625;
> >$Coords{'right'} += 0.0625;
> >$Coords{'bottom'} += 0.0625;
> >
> >$hBox = PGS->DrawBox(%Coords);
> >$hBox->SendToBack();
> >$hBox->SetObjectStyle("tint");
> >PGS->SelectObject($hBox,"add");
> >PGS->Group();
> >
> >$TextWrap{'type'} = "boundingbox";
> >$TextWrap{'xstandoff'} = 0.0625;
> >$TextWrap{'ystandoff'} = 0.0625;
> >$TextWrap{'mode'} = "wraparound";
> >PGS->SetTextWrap(%TextWrap);
>
> 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]
>
>
>
> To unsubscribe from this group, send an email to:
> PageStreamLinuxBeta-unsubscribe@yahoogroups.com
>
>
>
> Your use of Yahoo! Groups is subject tohttp://docs.yahoo.com/info/terms/