minor improvements - suggestions

[aaronkaplan]

• (high prio) : allow for other delimiter characters than [';', '#', ',']: spaces are valid as well, TAB characters etc... basically a user should be able to specify the delimiter freely.
• if you upload a file and want to skip 129 lines , the default behaviour is to load only 100 lines. But this does not mean that 100 lines - //after// skipping the 129 lines are loaded! This is confusing and should be fixed.
• text in the second screen should not be a HTML INPUT field but a HTML TEXTAREA field.

[ghost]

text in the second screen should not be a HTML INPUT field but a HTML TEXTAREA field.

You mean the text selector? So it's not referring to an existing boilerplate text but a new - temporary - one?
We (3) need to discuss the whole text topic first IMHO.

[ghost]

basically a user should be able to specify the delimiter freely.

So a text field?

[ghost]

text in the second screen should not be a HTML INPUT field but a HTML TEXTAREA field.

See also #11

[aaronkaplan]

I think yes. That makes sense. In addition a few radio boxes with the most common delimiters. Might need a bit of JS onclick()

…

--- Mobile

On 20 Sep 2017, at 17:18, Wagner ***@***.***> wrote: basically a user should be able to specify the delimiter freely. So a text field? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[aaronkaplan]

Okay needs to be saved in the session/request. No idea yet on how to push it to the bots

…

--- Mobile

On 20 Sep 2017, at 17:25, Wagner ***@***.***> wrote: text in the second screen should not be a HTML INPUT field but a HTML TEXTAREA field. See also #11 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[ghost]

First item: was not necessary in the last years, so most probably not needed
Third item is already covered by #11

Closing here