Simple implementation for 'one team-line per member' on Therion and S…

[rsevero]

…urvex eports

Proposed solution for issue https://github.com/marcocorvi/topodroid/issues/125

I created it as a branch so you can analyze it, merge or toss it away.

[marcocorvi]

The proposed solution requires that the user follow some syntax. This is therion-like, which (over)loads the user with syntax. i can see two roads for the user: [1] disregard therion and the programs that separate team members, and thus enter a free text line for the team [2] pretend to separate team members, and thus adhere to a strict (too be defined) syntax, or have a too to enter (and edit) team members so that separation is specified to the program.

[rsevero]

The proposed solution requires that the user follow some syntax. This is therion-like, which (over)loads the user with syntax.

Yes, this is a Therion and Survex only feature. It does not affect at all files exported in other formats. And users that use only other formats should not even care about it.

i can see two roads for the user: [1] disregard therion and the programs that separate team members, and thus enter a free text line for the team [2] pretend to separate team members, and thus adhere to a strict (too be defined) syntax, or have a too to enter (and edit) team members so that separation is specified to the program.

Exactly. There is a syntax to adhere to but I would hardly call "strict" a syntax that demands the user to separate names of different people with commas, bars or slashes.

My idea was to offer the user some way to get the desired "one team line per person" output in a simple way.

I know it does not cover all use cases but I bet it covers most. And again, this output tries to solve a Therion/Survex only issue as many other features also do in ToopoDroid.

You do prefer to have no support at all for a "one team line per person" than having one that "only" covers most use cases?

[marcocorvi]

people who dont care for therion write whatever they wish.

this is the default behavior.

people who use therion can opt for a string written with a certain syntax (which is a thing one can get wrong), or a program assisted input method (no need to remember the syntax).

On Thu, Oct 31, 2024, 10:16 Rodrigo Severo @.***> wrote:

The proposed solution requires that the user follow some syntax. This is therion-like, which (over)loads the user with syntax.

Yes, this is a Therion and Survex only feature. It does not affect at all files exported in other formats. And users that use only other formats should not even care about it.

i can see two roads for the user: [1] disregard therion and the programs that separate team members, and thus enter a free text line for the team [2] pretend to separate team members, and thus adhere to a strict (too be defined) syntax, or have a too to enter (and edit) team members so that separation is specified to the program.

Exactly. There is a syntax to adhere to but I would hardly call "strict" a syntax that demands the user to separate names of different people with commas, bars or slashes.

My idea was to offer the user some way to get the desired "one team line per person" output in a simple way.

I know it does not cover all use cases but I bet it covers most. And again, this output tries to solve a Therion/Survex only issue as many other features also do in ToopoDroid.

You do prefer to have no support at all for a "one team line per person" than having one that "only" covers most use cases?

— Reply to this email directly, view it on GitHub https://github.com/marcocorvi/topodroid/pull/127#issuecomment-2449388117, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACXMYC6R7WROY3LK4QHJCMLZ6HYNBAVCNFSM6AAAAABQXWGXYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBZGM4DQMJRG4 . You are receiving this because you modified the open/close state.Message ID: @.***>

[rsevero]

people who dont care for therion write whatever they wish.

this is the default behavior.

Yes. And that's unchanged by my commit.

people who use therion can opt for a string written with a certain syntax (which is a thing one can get wrong),

Which won't be a big problem at all. They will just have to manually edit the team lines on exported Therion and Sruvex files as they are already doing without my commit.

BUT, if they get it right (which might very well happen without they even thinking about it) because probably they are already separating person names with commas (or semi colons, or slashes or vertical bars), it will just work.

or a program assisted input method (no need to remember the syntax).

Which could be great but unfortunatelly does not exist.

I really think this commit is a simple improvement from current situation. A more "enginered" solution could be better. When it is created, if it is created.

As I said before, it's your call. I won't bother you any longer with this.

Thanks for the comments.