I've recently wanted to be able to display ANSI content with a scrollable interface, and tonight I found frame.js, which seems to do the job. I started using frame.js a bit tonight to see what it can do. I saw that it has a 'scrollbars' property, but it seems that even when I set it to true, it isn't displaying scrollbars. I tried making sure v_scroll and h_scroll are both true, but it still wasn't displaying scrollbars. Is that a known issue? Also, would it display a vertical scrollbar if v_scroll is true and h_scroll is false?

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com

Re: frame.js scrollbars
By: Nightfox to All on Mon Nov 23 2015 20:54:54

started using frame.js a bit tonight to see what it can do. I saw that it has a 'scrollbars' property, but it seems that even when I set it to true, it isn't displaying scrollbars. I tried making sure v_scroll and h_scroll

Those properties are placeholders and don't do much of anything at the moment.

You can use the ScrollBar object from scrollbar.js (note the camelCase - there is also a Scrollbar object in that same file, which is not Frame compatible) to add scrollbars to frames. See comments at the top of the file for options and instructions.

We'll see about bringing this into frame.js and making those placeholder properties actually do something. For now, just attach a ScrollBar to a Frame prior to calling Frame.open(), and call .cycle() on your ScrollBar as often as you call .cycle() on the Frame.

---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

Re: frame.js scrollbars
By: echicken to Nightfox on Tue Nov 24 2015 08:25:30

started using frame.js a bit tonight to see what it can do. I saw
that it has a 'scrollbars' property, but it seems that even when I
set it to true, it isn't displaying scrollbars. I tried making sure
v_scroll and h_scroll

Those properties are placeholders and don't do much of anything at the moment.

You can use the ScrollBar object from scrollbar.js (note the camelCase - there is also a Scrollbar object in that same file, which is not Frame compatible) to add scrollbars to frames. See comments at the top of the file for options and instructions.

properties actually do something. For now, just attach a ScrollBar to a Frame prior to calling Frame.open(), and call .cycle() on your ScrollBar as often as you call .cycle() on the Frame.

Thanks.

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com

Re: frame.js scrollbars
By: echicken to Nightfox on Tue Nov 24 2015 08:25:30

You can use the ScrollBar object from scrollbar.js (note the camelCase - there is also a Scrollbar object in that same file, which is not Frame compatible) to add scrollbars to frames. See comments at the top of the file for options and instructions.

I have set up a ScrollBar object with a Frame in my message reader script for displaying messages with ANSI content. It looks like it's working, but I've noticed a couple possible issues with it:
- When first displaying the file, it looks like the scrollbar has "holes" in it. This is a screenshot I made as an example (using white as the scrollbar foreground and light grey as the scrollbar background):
http://bit.ly/1Ndbr0G
- I have an input loop in my script that waits for a keypress and scrolls the Frame when the user presses the up or down arrow, PageUp, PageDown, Home, or End. The scrollbar refreshes when I scroll up & down one line (using the Frame's scroll() method), but after using the Frame's scrollTo() method (which I'm using for PageUp, PageDown, Home, and End), the scrollbar doesn't refresh until cycle() is called a 2nd time (which happens when I press PageUp, PageDown, Home, or End in my script).

For the 2nd issue, I'm not sure if it's something I'm doing wrong in my script or if it's an issue in the scrollbar/frame class.

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com

Re: frame.js scrollbars
By: echicken to Nightfox on Tue Nov 24 2015 08:25:30

Hi echicken,

Another thing I've noticed about using frame.js to display ANSI content is that it doesn't seem to totally refresh the background text when scrolling the ANSI up & down - Some text from some of the lines is left over when scrolling. For example, in the following screenshots, the ")" in the origin line at the bottom is left over when scrolling the message down (as the message text moves up): http://bit.ly/1Ntklt5
http://bit.ly/1Ndg5Mj
http://bit.ly/1Ib9YI5

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com

- When first displaying the file, it looks like the scrollbar has "holes" in it. This is a screenshot I made as an example (using white as the scrollbar foreground and light grey as the scrollbar background):

Not sure. Are you setting the background colour to LIGHTGRAY or BG_LIGHTGRAY? Is the ANSI content being loaded before or after the scrollbar is opened / cycled for the first time?

- I have an input loop in my script that waits for a keypress and scrolls the Frame when the user presses the up or down arrow, PageUp, PageDown, Home, or End. The scrollbar refreshes when I scroll up & down one line (using the Frame's scroll() method), but after using the Frame's scrollTo() method (which I'm using for PageUp, PageDown, Home, and End), the scrollbar doesn't refresh until cycle() is called a 2nd time (which happens when I press PageUp, PageDown, Home, or End in my script).

The ScrollBar doesn't actually redraw itself when you call .cycle() on it; it just updates its position info. The drawing takes place when .cycle() is called on the parent Frame. You could try calling .cycle() on the ScrollBar after you have called Frame.scrollTo() but prior to calling Frame.cycle(). (That may or may not help, but it's worth a shot.)

For the 2nd issue, I'm not sure if it's something I'm doing wrong in my script or if it's an issue in the scrollbar/frame class.

Probably just differences in the way you're using it and the way I expected to use it. In my input loops, I usually use console.inkey rather than console.getkey, and call [whatever].cycle() each time through the loop. This way, stuff gets updated as needed whether the user has pressed a key or not. (Useful if you want to update stuff in the terminal while the user is idling, etc.)

---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230

---
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

Re: frame.js scrollbars
By: echicken to Nightfox on Wed Nov 25 2015 15:32:39

- When first displaying the file, it looks like the scrollbar has
"holes" in it. This is a screenshot I made as an example (using white
as the scrollbar foreground and light grey as the scrollbar
background):

Not sure. Are you setting the background colour to LIGHTGRAY or BG_LIGHTGRAY? Is the ANSI content being loaded before or after the scrollbar is opened / cycled for the first time?

I was using LIGHTGRAY. I tried BG_LIGHTGRAY just now, and I think it actually looks/behaves better with LIGHTGRAY.
The ANSI content is being loaded before the scrollbar & frame are opened for the first time. Should it be loaded after?

- I have an input loop in my script that waits for a keypress and
scrolls the Frame when the user presses the up or down arrow, PageUp,
PageDown, Home, or End. The scrollbar refreshes when I scroll up &
down one line (using the Frame's scroll() method), but after using the
Frame's scrollTo() method (which I'm using for PageUp, PageDown, Home,
and End), the scrollbar doesn't refresh until cycle() is called a 2nd
time (which happens when I press PageUp, PageDown, Home, or End in my
script).

The ScrollBar doesn't actually redraw itself when you call .cycle() on it; it just updates its position info. The drawing takes place when .cycle() is called on the parent Frame. You could try calling .cycle() on the ScrollBar after you have called Frame.scrollTo() but prior to calling Frame.cycle(). (That may or may not help, but it's worth a shot.)

Ah, that seems to help. So it seems that the documentation (comments) in scrollbar.js are wrong - There's a section of the comments that has an example of how to use it, and it has this:
if(f.cycle()) {
s.cycle();
console.gotoxy(console.screen_columns, console.screen_rows);
}
That seems to suggest that if the frame cycle succeeds, then cycle the scrollbar. But as you suggested, it seems to work better when the scrollbar's cycle() is called before the frame's cycle().

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com

I was using LIGHTGRAY. I tried BG_LIGHTGRAY just now, and I think it actually looks/behaves better with LIGHTGRAY.

Only the BG_* values in sbbsdefs.js should be used for background colours; using the others may result in strange-looking things.

LIGHTGRAY incidentally looks better as a background here because - since WHITE is your foreground - it's like not setting a background colour at all. The foreground and background colours are OR-ed together to make an attribute number. In this case you end up with WHITE|LIGHTGRAY, which is 15|7, which is 15, which is WHITE. (You should see the same result when using any other non-BG_* colour as your background, so long as WHITE is your foreground.)

The ANSI content is being loaded before the scrollbar & frame are opened for the first time. Should it be loaded after?

Not sure - I was just curious. How are you loading the ANSI stuff into the Frame - using Frame.load(), or some other way (Frame.putmsg(), etc.)?

Ah, that seems to help. So it seems that the documentation (comments) in scrollbar.js are wrong -

Not really. The example works, but there's a crucial difference between it and what you're doing. (Which isn't to say that your way is wrong.)

if(f.cycle()) {
s.cycle();
console.gotoxy(console.screen_columns, console.screen_rows);
}
That seems to suggest that if the frame cycle succeeds, then cycle the scrollbar. But as you suggested, it seems to work better when the scrollbar's cycle() is called before the frame's cycle().

Frame.cycle() returns true if something changed, false otherwise. In my example, I'm only updating the ScrollBar if something changed in the Frame it's attached to. However changes to the ScrollBar's position won't be displayed until the Frame is cycled again. In my example, that next Frame.cycle() happens right away. In your code, there's presumably a blocking input prompt (console.getkey perhaps) in between.

The best solution would be for me to just bring ScrollBar into frame.js, and tie it into the Frame.cycle() method. Then you would use those currently-placeholder properties of Frame to enable scrollbars, and the rest would work behind the scenes - no need to manage the scrollbars separately.

---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230

---
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

Re: frame.js scrollbars
By: echicken to Nightfox on Wed Nov 25 2015 22:56:55

I was using LIGHTGRAY. I tried BG_LIGHTGRAY just now, and I think it
actually looks/behaves better with LIGHTGRAY.

Only the BG_* values in sbbsdefs.js should be used for background colours; using the others may result in strange-looking things.

LIGHTGRAY incidentally looks better as a background here because - since WHITE is your foreground - it's like not setting a background colour at all. The foreground and background colours are OR-ed together to make an attribute number. In this case you end up with WHITE|LIGHTGRAY, which is 15|7, which is 15, which is WHITE. (You should see the same result when using any other non-BG_* colour as your background, so long as WHITE is your foreground.)

Ah, I see. Perhaps I'll end up changing my script a bit to make things more the way they're supposed to be then.

The ANSI content is being loaded before the scrollbar & frame are
opened for the first time. Should it be loaded after?

Not sure - I was just curious. How are you loading the ANSI stuff into the Frame - using Frame.load(), or some other way (Frame.putmsg(), etc.)?

I'm using Frame.load() to load an ANSI file.

Ah, that seems to help. So it seems that the documentation (comments)
in scrollbar.js are wrong -

Not really. The example works, but there's a crucial difference between it and what you're doing. (Which isn't to say that your way is wrong.)

if(f.cycle()) {
s.cycle();
console.gotoxy(console.screen_columns, console.screen_rows);
}
That seems to suggest that if the frame cycle succeeds, then cycle the
scrollbar. But as you suggested, it seems to work better when the
scrollbar's cycle() is called before the frame's cycle().

Frame.cycle() returns true if something changed, false otherwise. In my example, I'm only updating the ScrollBar if something changed in the Frame it's attached to. However changes to the ScrollBar's position won't be displayed until the Frame is cycled again. In my example, that next Frame.cycle() happens right away. In your code, there's presumably a blocking input prompt (console.getkey perhaps) in between.

Ah, I see. I suppose that is a little different from what I am doing.

The best solution would be for me to just bring ScrollBar into frame.js, and tie it into the Frame.cycle() method. Then you would use those currently-placeholder properties of Frame to enable scrollbars, and the rest would work behind the scenes - no need to manage the scrollbars separately.

Would that break existing scripts that are currently managing them separately?

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com

Re: frame.js scrollbars
By: Nightfox to echicken on Wed Nov 25 2015 11:29:03

Another thing I've noticed about using frame.js to display ANSI content is that it doesn't seem to totally refresh the background text when scrolling the ANSI up & down - Some text from some of the lines is left over when scrolling. For example, in the following screenshots, the ")" in the origin line at the bottom is left over when scrolling the message down (as the message text moves up):
http://bit.ly/1Ntklt5
http://bit.ly/1Ndg5Mj
http://bit.ly/1Ib9YI5

Is this something that you think would need to be fixed in my script? I'm not sure if I would have to clear the frame's area on the screen in my script before I do scrolling in order to erase all the previous text so that everything appears correct after scrolling.

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com

Would that break existing scripts that are currently managing them separately?

What I think I'll do is leave scrollbar.js where it is, and then have frame.js load it. That way any script currently loading scrollbar.js will still have it available. Frame will then create ScrollBar instances if scrollbars are toggled on, and maintain them for you.

Even if some script is already using scrollbar.js and setting 'scrollbars' to 'true' on a Frame, it probably won't break anything. You'd just end up with two scrollbars, one layered over the other, doing the same thing, with only the topmost one visible.

---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230

---
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

Hello echicken,

On 26 Nov 15 00:41, echicken wrote to Nightfox:

Would that break existing scripts that are currently managing them>
separately?What I think I'll do is leave scrollbar.js where it is,
and then have frame.jsload it. That way any script currently
loading scrollbar.js will still have itavailable. Frame will then
create ScrollBar instances if scrollbars aretoggled on, and maintain
them for you.Even if some script is already using scrollbar.js and
setting 'scrollbars' to'true' on a Frame, it probably won't break
anything. You'd just end up withtwo scrollbars, one layered over
the other, doing the same thing, with only thetopmost one
visible.---echicken electronic chicken bbs -
bbs.electronicchicken.com - 416-273-7230

===
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
--- SBBSecho 2.27-Linux
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
(723:1/1)

Just an FYI, your replies are coming in here all mangled up. I think part of what you posted is in the above quote, but some of it is NIghtfox's comments.

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20150715
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (723:1/701)
þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)

Re: Re: frame.js scrollbars
By: Accession to echicken on Thu Nov 26 2015 02:27:04

Just an FYI, your replies are coming in here all mangled up. I think part of what you posted is in the above quote, but some of it is NIghtfox's comments.

Thanks. Some sort of newline problem that only shows up ... sometimes, for some people, apparently. I'll sort it out eventually. :|

---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

Re: frame.js scrollbars
By: Nightfox to echicken on Wed Nov 25 2015 20:40:51

Another thing I've noticed about using frame.js to display ANSI
content is that it doesn't seem to totally refresh the background
text when scrolling the ANSI up & down - Some text from some of the

Is this something that you think would need to be fixed in my script? I'm

Probably an issue with Frame itself. As a workaround you might try using Frame.invalidate() to force a redraw (on the next .cycle) after the user scrolls the Frame (but only if they scrolled it - otherwise you'll be
redrawing needlessly.) May or may not make a difference.

Are you dumping that message body to a temp file in order to use it with Frame.load()? If so, any chance you could post the file somewhere? I'd like to see if I can reproduce the problem and come up with a fix.

---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

Re: frame.js scrollbars
By: echicken to Nightfox on Thu Nov 26 2015 10:23:56

Another thing I've noticed about using frame.js to display ANSI
content is that it doesn't seem to totally refresh the background
text when scrolling the ANSI up & down - Some text from some of the

Is this something that you think would need to be fixed in my
script? I'm

Probably an issue with Frame itself. As a workaround you might try using Frame.invalidate() to force a redraw (on the next .cycle) after the user scrolls the Frame (but only if they scrolled it - otherwise you'll be redrawing needlessly.) May or may not make a difference.

I've added that, and it seems to work.

Are you dumping that message body to a temp file in order to use it with Frame.load()? If so, any chance you could post the file somewhere? I'd like to see if I can reproduce the problem and come up with a fix.

Yes, I am saving it to a file and then calling Frame.load(). I've put the file here:
http://www.digitaldistortionbbs.com/miscFilesForDL/tmpMsg.ans

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com

Thanks. Some sort of newline problem that only shows up ... sometimes, for some people, apparently. I'll sort it out eventually. :|

Happens for me via the default synchronet web interface... here's an example.

http://www.roughneckbbs.com/msgs/msg.ssjs?msg_sub=dove-syncjs&message=110

You may have to login, and I'll be offline from sunday until late tuesday for my
move.
--
Michael J. Ryan
tracker1(at)gmail.com
+o Roughneck BBS

---
þ Synchronet þ RoughneckBBS - http://www.roughneckbbs.com/

Just an FYI, your replies are coming in here all mangled up. I think part of what you posted is in the above quote, but some of it is NIghtfox's comments.

Regards,
Nick

I'm not sure if this will be any better ...

... but I'm spanning this message across multiple ...

... lines because it's fun to do. Anyway, pls respond and let me know if this continues to be mangled kthnx.

---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230

---
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

Hello echicken,

On 09 Dec 15 17:45, echicken wrote to Accession:

Just an FYI, your replies are coming in here all mangled up. I think
part of> what you posted is in the above quote, but some of it is
NIghtfox's comments.> Regards,> NickI'm not sure if this will be any
better ...... but I'm spanning this message across multiple ......
lines because it's fun to do. Anyway, pls respond and let me know
if thiscontinues to be mangled kthnx.---echicken electronic chicken
bbs - bbs.electronicchicken.com - 416-273-7230

Yep, still mangled. kwlcme. :D

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20151129
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (723:1/701)
þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)

Yep, still mangled. kwlcme. :D

Grr, what the fuck. I must sort this out.


---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

Grr, what the fuck. I must sort this out.

Relax, angry guy. You might have just fixed it.

Or maybe not. We'll see.

:|
---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

Hello echicken,

On 09 Dec 15 22:54, echicken wrote to echicken:

Grr, what the fuck. I must sort this out.

Relax, angry guy. You might have just fixed it.

Or maybe not. We'll see.

:|
---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

That's how it appears here. Looks a helluva lot better!

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20151129
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (723:1/701)
þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)

Hello echicken,

On 09 Dec 15 22:54, echicken wrote to echicken:

That's how it appears here. Looks a helluva lot better!

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20151129
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (723:1/701)
â–  Synchronet â–  thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)

Yay! Thanks for the reply. Glad that's sorted out.

---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com

Re: Re: frame.js scrollbars
By: echicken to Accession on Wed Dec 09 2015 05:45 pm

Just an FYI, your replies are coming in here all mangled up. I think part of what you posted is in the above quote, but some of it is NIghtfox's comments.

Regards,
Nick

I'm not sure if this will be any better ...

... but I'm spanning this message across multiple ...

... lines because it's fun to do. Anyway, pls respond and let me know if this continues to be mangled kthnx.

Not mangled here... maybe because I've to the newest, most awesomeest word_wrap() implementation?

---
http://DuckDuckGo.com/ a better search engine that respects your privacy.
Mro is an idiot. Please ignore him, we keep hoping he'll go away.
þ Synchronet þ My Brand-New BBS (All the cool SysOps run STOCK!)

Not mangled here... maybe because I've to the newest, most awesomeest word_wrap() implementation?

I had forgotten to run messages through lfexpand() before saving them. :|

---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com