Hello August!

*** Monday 17.01.22 at 10:19, August Abolins wrote to Martin Foster:

[snip]

I'm still trying to wrap my head over the adhoc Origin line
feature in OXP. Dunno what to do with it. I thought it would
be better if it could access an associated text file and paste
things akin to a tagline in there, or drop something
preconfigured in a random way. But as it sits right now, its
usefulness seems wanting.

Hmmmmm, I find it quite useful and it's quick and easy to use.

It is critical to know in advance how many chars the line can
support including the space occupied by the node number.

Yes, it is.

And.. the adhoc one is replaced one with the static one if
there is a need to re-edit the message body before sending it.

Yes, that's correct.

What is the designer's/programmer's idea behind the function?

A basic simple way of changing the pre-defined origin for the current message. However, there's plenty of scope for improvement in future
releases.

How is anyone else using it?

Ummmmmmmm :)

Regards,
Martin

--- OpenXP 5.0.51
* Origin: OpenXP-Team (2:310/31.3)

Hello Martin Foster!

** On Tuesday 18.01.22 - 10:41, Martin Foster wrote to August Abolins:

No traffic for 5 days is not unusual for this echo.

Maybe there's nothing new or extraordinarly bad to report
in the realm of pointing. :D

There's plenty of new stuff to report in the realm of
pointing but it's being reported elsewhere.

Are you meaning Winpoint? That's just one thing.
Are you meaning in non-english echos?

I meant in the *realm* of pointing and the people using it.
--
../|ug

--- OpenXP 5.0.51
* Origin: Your six winning lottery numbers: 3 10 24 36 44 (2:221/1.58)

Hello Martin Foster!

** On Tuesday 18.01.22 - 10:52, Martin Foster wrote to August Abolins:

I'm still trying to wrap my head over the adhoc Origin line
feature in OXP. Dunno what to do with it...

Hmmmmm, I find it quite useful and it's quick and easy to
use.

I haven't seen you use it very much. :/

And.. the adhoc one is replaced one with the static one
if there is a need to re-edit the message body before
sending it.

Yes, that's correct.

That is a bit annoying especially if one has spent time to
craft something witty and profound but a simple re-edit would
undo it.

What is the designer's/programmer's idea behind the function?

A basic simple way of changing the pre-defined origin for
the current message. However, there's plenty of scope for
improvement in future releases.

But then why not build it so that it extracts predefined text
(that is known to fit) in that space?

I am just having trouble understanding what exactly the
designer had in mind to put in there each and every time.

How is anyone else using it?

Ummmmmmmm :)

-+- OpenXP 5.0.51
+ Origin: OpenXP-Team (2:310/31.3)

OK, sure.. nice, short and simple. But wouldn't it make better
sense to craft different versions of it so that you can pick
them from a drop-down or something?

Case in point.. I thought I'd enter "Que Cera Cera, Comme Se
Comme Sa, Oobla Dee Oobla Daa" ..but it wouldn't fit. So, the
writer wastes time entering something until it does fit - or
not bother using it at all.

When I entered the shorter version as per below, I noticed a
spelling mistake in the body of the message. Going back to fix
that "undoes" the crafted adhoc one, and I have retype it.

The designer had *something* in mind for its REGULAR use so
that there were no incidents like re-entering that text.

--
../|ug

--- OpenXP 5.0.51
* Origin: CommeCi, Comme€a, QueSeraSera, OoblaDeeOoblaDaa. (2:221/1.58)

Hi August,

On 2022-01-18 07:29:00, you wrote to Martin Foster:

@PID: OpenXP/5.0.51 (Win32)
@CHRS: ASCII 1

^^^^^^^

* Origin: CommeCi, Comme€a, QueSeraSera, OoblaDeeOoblaDaa.

^^

There's also the above problem...


(And yes I know my "@CHRS: UTF-8 2" kludge isn't correct ;-))


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

** On Tuesday 18.01.22 - 13:58, you wrote to me:

@PID: OpenXP/5.0.51 (Win32)
@CHRS: ASCII 1

^^^^^^^

* Origin: CommeCi, Comme€a, QueSeraSera, OoblaDeeOoblaDaa.

^^

There's also the above problem...

(And yes I know my "@CHRS: UTF-8 2" kludge isn't correct ;-))

The "€a" char made it back intact here. But your observation is
useful. Perhaps the @CHRS detection in OpenXP should extend to
looking at the characters in the Origin line as well. I
believe the FTSC spec defined the "message body" to include the
text in the Origin line.

This reply will have no special chars in the Origin line.
Prehaps the @CHARS line will be different now.
--
../|ug

--- OpenXP 5.0.51
* Origin: The ONLY point that matters! --> . <-- (2:221/1.58)

Hi August,

On 2022-01-18 08:15:00, you wrote to me:

@CHRS: CP437 2

@PID: OpenXP/5.0.51 (Win32)
@CHRS: ASCII 1

^^^^^^^

* Origin: CommeCi, Comme€a, QueSeraSera, OoblaDeeOoblaDaa.

^^

There's also the above problem...

The "€a" char made it back intact here. But your observation is
useful. Perhaps the @CHRS detection in OpenXP should extend to
looking at the characters in the Origin line as well. I
believe the FTSC spec defined the "message body" to include the
text in the Origin line.

Since there is only one way/place to define the used character set for a message, it applies to the complete message... Or maybe it is defined somewhere that an origin line, and the header fields should be strict ascii... But then we couldn't have names with high ascii/utf in them. Which isn't current practice...

This reply will have no special chars in the Origin line.
Prehaps the @CHARS line will be different now.

The @CHRS (not @CHARS) kludge is indeed different.

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred van Velzen!

** On Tuesday 18.01.22 - 13:58, Wilfred van Velzen wrote to August Abolins:

(And yes I know my "@CHRS: UTF-8 2" kludge isn't correct ;-))

It arrived as only "UTF-8" here. If you are meaning that you
need "UTF-8 4", then what is so hard to change "2" to "4" in
your Fmail?

--
../|ug

--- OpenXP 5.0.51
* Origin: The ONLY point that matters! --> . <-- (2:221/1.58)

Hi August,

On 2022-01-18 09:11:00, you wrote to me:

(And yes I know my "@CHRS: UTF-8 2" kludge isn't correct ;-))

It arrived as only "UTF-8" here.

That's strange! That would mean something is messing with it on route...?
(I checked the backup of my outbound .pkt files: It was still there!)

If you are meaning that you need "UTF-8 4", then what is so hard to
change "2" to "4" in your Fmail?

That's not a tossers job! Tossers are supposed not to change in-transit mail! It's my Golded that needs to be configured (if possible), to create the correct kludge.

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred van Velzen!

** On Tuesday 18.01.22 - 16:03, Wilfred van Velzen wrote to August Abolins:

It arrived as only "UTF-8" here.

That's strange! That would mean something is messing with
it on route...? (I checked the backup of my outbound .pkt
files: It was still there!)

My bad. Perhaps I should have checked the .PKT file. When it
gets tossed into OpenXP, the headers adjust to its own display
rules.

If you are meaning that you need "UTF-8 4", then what is so hard to
change "2" to "4" in your Fmail?

That's not a tossers job! Tossers are supposed not to change in-transit mail! It's my Golded that needs to be configured (if possible), to
create the correct kludge.

Ok. I should have said "editor" perhaps.
--
../|ug

--- OpenXP 5.0.51
* Origin: The ONLY point that matters! --> . <-- (2:221/1.58)

Hello August!

*** Tuesday 18.01.22 at 07:11, August Abolins wrote to Martin Foster:

No traffic for 5 days is not unusual for this echo.

Maybe there's nothing new or extraordinarly bad to report
in the realm of pointing. :D

There's plenty of new stuff to report in the realm of
pointing but it's being reported elsewhere.

Are you meaning Winpoint?

Oh, how did you guess :-))

That's just one thing.

There's more? :)

Are you meaning in non-english echos?

Nope.

I meant in the *realm* of pointing and the people using it.

Ummmm, WinPoint falls into that realm, doesn't it.

Regards,
Martin

--- OpenXP 5.0.51
* Origin: Sitting on the fence (2:310/31.3)

Hello August!

*** Tuesday 18.01.22 at 07:29, August Abolins wrote to Martin Foster:

I'm still trying to wrap my head over the adhoc Origin line
feature in OXP. Dunno what to do with it...

Hmmmmm, I find it quite useful and it's quick and easy to
use.

I haven't seen you use it very much. :/

I haven't used it much, I only use it when the need arises :)

And.. the adhoc one is replaced one with the static one
if there is a need to re-edit the message body before
sending it.

Yes, that's correct.

That is a bit annoying especially if one has spent time to
craft something witty and profound but a simple re-edit would
undo it.

I find it *very* annoying actually.

What is the designer's/programmer's idea behind the function?

A basic simple way of changing the pre-defined origin for
the current message. However, there's plenty of scope for
improvement in future releases.

But then why not build it so that it extracts predefined text
(that is known to fit) in that space?

Yes, why not?
Perhaps you could ask the developer about that.

I am just having trouble understanding what exactly the
designer had in mind to put in there each and every time.

See [1] below .....

How is anyone else using it?

Ummmmmmmm :)

-+- OpenXP 5.0.51
+ Origin: OpenXP-Team (2:310/31.3)

OK, sure.. nice, short and simple. But wouldn't it make better
sense to craft different versions of it so that you can pick
them from a drop-down or something?

A better solution would have been to implement something along the lines
of the Glossary feature, whereby all the user needs to do is to press
<Alt+G> from within the editor and then select an item from the pre-
defined list that pops up. In this case, it would be a list of origin
lines pre-defined by the user in an ascii text file, e.g. "origins.txt"
and the key-press could be <Alt+O>.

[snip]

The designer had *something* in mind for its REGULAR use so
that there were no incidents like re-entering that text.

[1] Seeing as origin lines could be defined on a global, group and area level, somebody(me) thought it would be nice if they could also be defined
at the single message level and I duly put in a feature request for a *simple*, *basic* means of doing so. He duly obliged by implementing
exactly what I'd asked for, no more, no less.

Regards,
Martin

--- OpenXP 5.0.51
* Origin: Watch This Space (2:310/31.3)

Are you meaning Winpoint?

Oh, how did you guess :-))

That's just one thing.

There's more? :)

InterPoint for IOS/Andriod is now starting to take form as we speak. Working on it and have been able to connect to other systems. Still have lots of work to do but glad to finally start making some traction for myself.


--- InterEcho 1.21
* Origin: Home Of InterMail/InterEcho (1:106/201)

Hello Dale!

*** Wednesday 19.01.22 at 13:02, Dale Barnes wrote to Martin Foster:

Are you meaning Winpoint?

Oh, how did you guess :-))

That's just one thing.

There's more? :)

InterPoint for IOS/Andriod is now starting to take form as we speak. Working on it and have been able to connect to other systems. Still have lots of work to do but glad to finally start making some traction for myself.

Ah, so that's what the weird message was about that you posted in here a
few days ago :)

Regards,
Martin

--- OpenXP 5.0.51
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Dale!

19 Jan 22 13:02, you wrote to Martin Foster:

Are you meaning Winpoint?

Oh, how did you guess :-))

That's just one thing.

There's more? :)

InterPoint for IOS/Andriod is now starting to take form as we speak. Working on it and have been able to connect to other systems. Still
have lots of work to do but glad to finally start making some traction
for myself.

I am looking forward to this for iOS.

Ray


--- GoldED+/W64-MSVC 1.1.5-b20180707
* Origin: Ham Radio operators do it with frequency! (1:214/23)

Hello Martin!

** On Wednesday 19.01.22 - 13:59, you wrote to me:

But then why not build it so that it extracts predefined text
(that is known to fit) in that space?

Yes, why not?
Perhaps you could ask the developer about that.

I thought YOU were the liason-man for OpenXP things.

A better solution would have been to implement something
along the lines of the Glossary feature, whereby all the
user needs to do is to press <Alt+G> from within the
editor and then select an item from the pre-defined list
that pops up. In this case, it would be a list of origin
lines pre-defined by the user in an ascii text file, e.g.
"origins.txt" and the key-press could be <Alt+O>.

Excellent. Did you include that as a tenny tiny detail with
your main suggestion? ;)

Personally, I haven't used Alt-G (Glossary) much at all. It
*does* seem like a handy way to dump pre-defined strings in a
message though.

..somebody(me) thought it would be nice if they could also
be defined at the single message level..

OK! Too bad you didn't describe how it would "function" (which
key strokes to trigger it, Alt-G as above, or sourcing from a
oring-lines.txt file, etc)

..and I duly put in a feature request for a *simple*,
*basic* means of doing so. He duly obliged by implementing
exactly what I'd asked for, no more, no less.

Hopefully this is then just the 1st baby-step to make it more
functional - especially to make lock in and stay put once the
text is entered and not overwritten by the global setting if
the message needs to be re-edited.

-+- OpenXP 5.0.51
+ Origin: Watch This Space (2:310/31.3)

^^^^^^^^^^^^^^^^^^^^

I just might from now on! <G>

--
../|ug

--- OpenXP 5.0.51
* Origin: System Up Time: 6 D, 10 H, 18 M (2:221/1.58)

Hello August!

*** Sunday 23.01.22 at 20:19, August Abolins wrote to Martin Foster:

But then why not build it so that it extracts predefined text
(that is known to fit) in that space?

Yes, why not?
Perhaps you could ask the developer about that.

I thought YOU were the liason-man for OpenXP things.

Sometimes but not always :)

In this instance, I thought it would be better if you were to ask him directly.

A better solution would have been to implement something
along the lines of the Glossary feature, whereby all the
user needs to do is to press <Alt+G> from within the
editor and then select an item from the pre-defined list
that pops up. In this case, it would be a list of origin
lines pre-defined by the user in an ascii text file, e.g.
"origins.txt" and the key-press could be <Alt+O>.

Excellent. Did you include that as a tenny tiny detail with
your main suggestion? ;)

Nope.

Personally, I haven't used Alt-G (Glossary) much at all. It
*does* seem like a handy way to dump pre-defined strings in a
message though.

I use it a fair bit.

..somebody(me) thought it would be nice if they could also
be defined at the single message level..

OK! Too bad you didn't describe how it would "function" (which
key strokes to trigger it, Alt-G as above, or sourcing from a oring-lines.txt file, etc)

Yeah well, at the time, I just wanted to keep it simple.

..and I duly put in a feature request for a *simple*,
*basic* means of doing so. He duly obliged by implementing
exactly what I'd asked for, no more, no less.

Hopefully this is then just the 1st baby-step to make it more
functional - especially to make lock in and stay put once the
text is entered and not overwritten by the global setting if
the message needs to be re-edited.

Hopefully yes but that will largely depend on what bells 'n whistles users want ;)

Regards,
Martin

--- OpenXP 5.0.51
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

InterPoint for IOS/Andriod is now starting to take form as we speak.
Working on it and have been able to connect to other systems. Still

have

lots of work to do but glad to finally start making some traction for
myself.

Ah, so that's what the weird message was about that you
posted in here a
few days ago :)

So that is the first message I have posted that was weird? Where have you been? LOL.


--- InterEcho 1.21
* Origin: Home Of InterMail/InterEcho (1:106/201)