Re: [E-devel] Elm_Entry assuming markup input???

Hi, Whilst more API may seem counterintuitive I am a proponent of each method does 1 thing well. Therefore if we want to handle markup and handle plain text then a 2* API count actually makes sense. Andy On Mon, 17 Jul 2017 at 08:33 Carsten Haitzler wrote: > On Wed, 5

Re: [E-devel] Elm_Entry assuming markup input???

On Wed, 5 Jul 2017 09:14:02 +0300 Daniel Hirt said: > Hello all, > > > On 07/05/2017 08:48 AM, Carsten Haitzler (The Rasterman) wrote: > > On Wed, 05 Jul 2017 03:26:09 + Andrew Williams > > said: > > > >> Hi, > >> > >> Unfortunately I don't have

Re: [E-devel] Elm_Entry assuming markup input???

Hi, That sounds excellent. I like the idea of markup handling being separate but just as convenient as before. The more we can split out the logo from widgets the more testable our apis will be as well. Thanks, Andy On Wed, 5 Jul 2017 at 07:13, Daniel Hirt wrote: > Hello

Re: [E-devel] Elm_Entry assuming markup input???

Hello all, On 07/05/2017 08:48 AM, Carsten Haitzler (The Rasterman) wrote: On Wed, 05 Jul 2017 03:26:09 + Andrew Williams said: Hi, Unfortunately I don't have time to reply to all of these thoughts right now but I wanted to reply to the first one before any more

Re: [E-devel] Elm_Entry assuming markup input???

On Wed, 05 Jul 2017 03:26:09 + Andrew Williams said: > Hi, > > Unfortunately I don't have time to reply to all of these thoughts right now > but I wanted to reply to the first one before any more replies arrive. I am > not (and nether is anyone else) suggesting that we

Re: [E-devel] Elm_Entry assuming markup input???

Hi, Unfortunately I don't have time to reply to all of these thoughts right now but I wanted to reply to the first one before any more replies arrive. I am not (and nether is anyone else) suggesting that we remove markup support. Please stop implying that. Also my email was about api and not

Re: [E-devel] Elm_Entry assuming markup input???

On Tue, 04 Jul 2017 18:50:34 + Andrew Williams said: > Hi, > > Apologies I did not realise it was a question that needed answering. As I > moved in to discuss if we are worrying about text manipulation in our > widgets then we probably have bigger issues around

Re: [E-devel] Elm_Entry assuming markup input???

Hi, Apologies I did not realise it was a question that needed answering. As I moved in to discuss if we are worrying about text manipulation in our widgets then we probably have bigger issues around separation of concerns. Our text handling apis should worry about that - and the widget have a

Re: [E-devel] Elm_Entry assuming markup input???

2017-07-04 14:22 GMT+02:00 Andrew Williams : > Hi, > > I jumped back to this email I sent a week ago and realised that we have > just spent a bunch of time revisiting a discussion that had clearly wrapped > up at the EDD in Malta. One reason I wanted to post our conclusion

Re: [E-devel] Elm_Entry assuming markup input???

Hi, I jumped back to this email I sent a week ago and realised that we have just spent a bunch of time revisiting a discussion that had clearly wrapped up at the EDD in Malta. One reason I wanted to post our conclusion to the list was for visibility and a chance to comment for anyone who was not

Re: [E-devel] Elm_Entry assuming markup input???

On Sun, 02 Jul 2017 21:42:01 + Andrew Williams said: > As I'm on the move I have no decent email app so I can't interleave with > your replies so it's all up-top: > > First time: Maybe not on ML but this has been discussed before on IRC, but > that does not exactly

Re: [E-devel] Elm_Entry assuming markup input???

As I'm on the move I have no decent email app so I can't interleave with your replies so it's all up-top: First time: Maybe not on ML but this has been discussed before on IRC, but that does not exactly make angood source of documentation for issues or api confusion. UTF8: we are in agreement

Re: [E-devel] Elm_Entry assuming markup input???

On Sat, 01 Jul 2017 06:37:03 + Andrew Williams said: > Hi, > > This is not the first time this has come up (just search phab for "HTML" or > "encoding") and given that we agreed we don't have many app developers it > seems dismissive to state it's not a problem as

Re: [E-devel] Elm_Entry assuming markup input???

On Sat, 1 Jul 2017 09:07:27 +0200 Davide Andreoli said: > 2017-07-01 4:28 GMT+02:00 Carsten Haitzler : > > > On Fri, 30 Jun 2017 16:22:03 +0200 Davide Andreoli > > > > said: > > > > > 2017-06-30 1:37 GMT+02:00 Carsten

Re: [E-devel] Elm_Entry assuming markup input???

2017-07-01 4:28 GMT+02:00 Carsten Haitzler : > On Fri, 30 Jun 2017 16:22:03 +0200 Davide Andreoli > > said: > > > 2017-06-30 1:37 GMT+02:00 Carsten Haitzler : > > > > > On Thu, 29 Jun 2017 11:13:51 + Andrew Williams < >

Re: [E-devel] Elm_Entry assuming markup input???

Hi, This is not the first time this has come up (just search phab for "HTML" or "encoding") and given that we agreed we don't have many app developers it seems dismissive to state it's not a problem as we've had no complains from app developers... Markup vs text does not introduce cursor

Re: [E-devel] Elm_Entry assuming markup input???

On Fri, 30 Jun 2017 16:22:03 +0200 Davide Andreoli said: > 2017-06-30 1:37 GMT+02:00 Carsten Haitzler : > > > On Thu, 29 Jun 2017 11:13:51 + Andrew Williams > > said: > > > > > Hi, > > > > > > Just to wrap this thread up

Re: [E-devel] Elm_Entry assuming markup input???

2017-06-30 1:37 GMT+02:00 Carsten Haitzler : > On Thu, 29 Jun 2017 11:13:51 + Andrew Williams > said: > > > Hi, > > > > Just to wrap this thread up following EDD: > > > > * no-one is proposing that we remove the ability to mark up text through > >

Re: [E-devel] Elm_Entry assuming markup input???

On Thu, 29 Jun 2017 11:13:51 + Andrew Williams said: > Hi, > > Just to wrap this thread up following EDD: > > * no-one is proposing that we remove the ability to mark up text through > the markup format mechanism, it is a great feature > * we cannot make changes to

Re: [E-devel] Elm_Entry assuming markup input???

Hi, Just to wrap this thread up following EDD: * no-one is proposing that we remove the ability to mark up text through the markup format mechanism, it is a great feature * we cannot make changes to this legacy API as apps depend on it or have adapted to it * the new textblock API, which is

Re: [E-devel] Elm_Entry assuming markup input???

On Fri, 23 Jun 2017 21:55:14 +0200 Davide Andreoli said: > 2017-06-19 13:36 GMT+02:00 Daniel Hirt : > > Hi, > > > > On Mon, Jun 19, 2017 at 12:01 PM, Andrew Williams > > wrote: > > > >> Hi, > >> > >> Looking at the tests you

Re: [E-devel] Elm_Entry assuming markup input???

2017-06-19 13:36 GMT+02:00 Daniel Hirt : > Hi, > > On Mon, Jun 19, 2017 at 12:01 PM, Andrew Williams > wrote: > >> Hi, >> >> Looking at the tests you point me at - selection (and the past) is a plain >> text copy with the markup stripped - exactly what

Re: [E-devel] Elm_Entry assuming markup input???

Hi, On Mon, Jun 19, 2017 at 12:01 PM, Andrew Williams wrote: > Hi, > > Looking at the tests you point me at - selection (and the past) is a plain > text copy with the markup stripped - exactly what I would expect for > text_get - but the current content transformed with

Re: [E-devel] Elm_Entry assuming markup input???

On Mon, 19 Jun 2017 09:01:50 + Andrew Williams said: > Hi, > > Looking at the tests you point me at - selection (and the past) is a plain > text copy with the markup stripped - exactly what I would expect for > text_get - but the current content transformed with the

Re: [E-devel] Elm_Entry assuming markup input???

I recall that this was one of the more confusing parts of EFL when I started out, but at this point the API has been shipped in enough releases that we definitely cannot change it. Overall, I think it would be nice to have text conversion facilities at a lower level such as eina (not just

Re: [E-devel] Elm_Entry assuming markup input???

Hi, Looking at the tests you point me at - selection (and the past) is a plain text copy with the markup stripped - exactly what I would expect for text_get - but the current content transformed with the helper will not get you there - there is no built in interpretation of formatting - just

Re: [E-devel] Elm_Entry assuming markup input???

On Sun, 18 Jun 2017 16:53:34 -0700 Cedric BAIL said: > On Sun, Jun 18, 2017 at 4:45 PM, Carsten Haitzler > wrote: > > On Sun, 18 Jun 2017 16:20:59 -0700 Cedric BAIL said: > >> On Sun, Jun 18, 2017 at 3:58 PM, Carsten Haitzler

Re: [E-devel] Elm_Entry assuming markup input???

On Sun, Jun 18, 2017 at 4:45 PM, Carsten Haitzler wrote: > On Sun, 18 Jun 2017 16:20:59 -0700 Cedric BAIL said: >> On Sun, Jun 18, 2017 at 3:58 PM, Carsten Haitzler >> wrote: >> > On Sun, 18 Jun 2017 15:22:04 -0700 Cedric BAIL

Re: [E-devel] Elm_Entry assuming markup input???

On Sun, 18 Jun 2017 16:20:59 -0700 Cedric BAIL said: > On Sun, Jun 18, 2017 at 3:58 PM, Carsten Haitzler > wrote: > > On Sun, 18 Jun 2017 15:22:04 -0700 Cedric BAIL said: > >> On Sun, Jun 18, 2017 at 3:07 PM, Andrew Williams

Re: [E-devel] Elm_Entry assuming markup input???

On Sun, Jun 18, 2017 at 3:58 PM, Carsten Haitzler wrote: > On Sun, 18 Jun 2017 15:22:04 -0700 Cedric BAIL said: >> On Sun, Jun 18, 2017 at 3:07 PM, Andrew Williams >> wrote: >> > Can we be a little careful with that response? The

Re: [E-devel] Elm_Entry assuming markup input???

On Mon, 19 Jun 2017 07:55:01 +0900 Carsten Haitzler (The Rasterman) said: > On Sun, 18 Jun 2017 20:18:33 + Andrew Williams > said: > > > Hi team, > > > > Netstar pointed out something to me today that I had completely missed for > > ages -

Re: [E-devel] Elm_Entry assuming markup input???

On Sun, 18 Jun 2017 20:18:33 + Andrew Williams said: > Hi team, > > Netstar pointed out something to me today that I had completely missed for > ages - elm_entry assumes you are typing markup. Type "a>b" and text_get > will return "ab" - what is the reason for this? It

Re: [E-devel] Elm_Entry assuming markup input???

On Sun, 18 Jun 2017 15:22:04 -0700 Cedric BAIL said: > Hi, > > On Sun, Jun 18, 2017 at 3:07 PM, Andrew Williams wrote: > > Can we be a little careful with that response? The behaviour you think > > people are relying on is undocumented and confusing.

Re: [E-devel] Elm_Entry assuming markup input???

Hi, On Sun, Jun 18, 2017 at 3:07 PM, Andrew Williams wrote: > Can we be a little careful with that response? The behaviour you think > people are relying on is undocumented and confusing. Are people truly > relying on the "HTML encoding" behaviour of user input? > I think

Re: [E-devel] Elm_Entry assuming markup input???

It is python but this caused us (Bodhi linux) some headache with Jeffs esudo program: https://github.com/JeffHoogland/esudo/issues/2 On Sun, Jun 18, 2017 at 4:59 PM, Daniel Hirt wrote: > Hi Andrew, > > Markup uses tags like

Re: [E-devel] Elm_Entry assuming markup input???

Can we be a little careful with that response? The behaviour you think people are relying on is undocumented and confusing. Are people truly relying on the "HTML encoding" behaviour of user input? I think that something so unintuitive is better fixed rather than live with it forever! Simple user

Re: [E-devel] Elm_Entry assuming markup input???

2017-06-19 0:11 GMT+03:00 Andrew Williams : > Marking up an input field is not the most common use-case - and is surely > inputted by the app rather than the user normally? > > I propose that ...text_get should return stripped markup and a new method > markup_text_get returns

Re: [E-devel] Elm_Entry assuming markup input???

It's certainly a bit of a surprising feature. An additional method would save loads of code duplication? Also documenting the behaviour? On Sun, Jun 18, 2017 at 10:11 PM, Andrew Williams wrote: > Marking up an input field is not the most common use-case - and is surely >

Re: [E-devel] Elm_Entry assuming markup input???

Marking up an input field is not the most common use-case - and is surely inputted by the app rather than the user normally? I propose that ...text_get should return stripped markup and a new method markup_text_get returns the current stuff. That would cater for both use cases... Thanks, Andrew

Re: [E-devel] Elm_Entry assuming markup input???

Hi Andrew, Markup uses tags like

[E-devel] Elm_Entry assuming markup input???

Hi team, Netstar pointed out something to me today that I had completely missed for ages - elm_entry assumes you are typing markup. Type "a>b" and text_get will return "ab" - what is the reason for this? It seems completely crazy default behaviour. Is there any reason we can't turn this off by