Re: [FlexJS] InnerHTML new bead

2016-12-14 Thread Carlos Rovira
Hi Alex, I'm rethinking the problem, so I'll be experimenting a bit to see where I should go. Thanks! :) 2016-12-14 2:37 GMT+01:00 Alex Harui : > What problem are you trying to solve? What are some usage scenarios? > > -Alex > > On 12/13/16, 4:53 PM, "carlos.rov...@gmail.com on behalf of Carlos

Re: [FlexJS] InnerHTML new bead

2016-12-13 Thread Alex Harui
What problem are you trying to solve? What are some usage scenarios? -Alex On 12/13/16, 4:53 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >> The issue may be that there are multiple ways to specify and operate on >> innerHTML. If you want to set it directly, then you should

Re: [FlexJS] InnerHTML new bead

2016-12-13 Thread Carlos Rovira
> The issue may be that there are multiple ways to specify and operate on > innerHTML. If you want to set it directly, then you shouldn't be able to > specify any other children. Hence my earlier suggestion to have a > DivWithInnerHTML component that doesn't subclass Container and only has an > i

Re: [FlexJS] InnerHTML new bead

2016-12-13 Thread Carlos Rovira
After search a way to do this I only found this (not tested) that people says works http://stackoverflow.com/questions/15553280/replace-a-textnode-with-html-text-in-javascript but this depends on linking js script. * What do you think about this? * License is MIT what is seems to conform to apac

Re: [FlexJS] InnerHTML new bead

2016-12-13 Thread Alex Harui
On 12/13/16, 4:15 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >Hi Alex, > >I remember I tried this approach some time ago and it didn't work, maybe >it >was since I was returning Text and not a WrappedHTMLElement. >Now it compiles and work in example but I have a new problem

Re: [FlexJS] InnerHTML new bead

2016-12-13 Thread Carlos Rovira
Hi Alex, I remember I tried this approach some time ago and it didn't work, maybe it was since I was returning Text and not a WrappedHTMLElement. Now it compiles and work in example but I have a new problem. It seems a TextNode is always a leaf and can't have html tags for that reason the text in

Re: [FlexJS] InnerHTML new bead

2016-12-13 Thread Alex Harui
On 12/13/16, 3:43 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >So better to remove the InnerHTML bead in favor of a TextNode component >right? No need to remove it. Maybe someone will find a use for it. It is up to you. -Alex

Re: [FlexJS] InnerHTML new bead

2016-12-13 Thread Carlos Rovira
2016-12-14 0:23 GMT+01:00 Alex Harui : > > IMO, if you had a TextNode component, it would be a child just like any > other child and you would define its order the way it should appear in the > DOM. > > > This is some text > > This is more text > > > Would product the DOM > This is some t

Re: [FlexJS] InnerHTML new bead

2016-12-13 Thread Alex Harui
On 12/13/16, 1:21 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >2016-12-12 6:24 GMT+01:00 Alex Harui : > >> Would it be useful to have a component that generates a TextNode? Then >> you could interleave them between other child components. >> > >Right, I was trying that and

Re: [FlexJS] InnerHTML new bead

2016-12-13 Thread Carlos Rovira
2016-12-12 6:24 GMT+01:00 Alex Harui : > On 12/11/16, 1:11 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" > wrote: > > > That's clever (adding new properties as beads). For this particular > implementation, are you concerned about collisions in other scenarios? > For Div/Container (pro

Re: [FlexJS] InnerHTML new bead

2016-12-11 Thread piotrz
Hi Alex, I filled a bug -> https://issues.apache.org/jira/browse/FLEX-35213 Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-InnerHTML-new-bead-tp57155p57175.html Sent from the Apache F

Re: [FlexJS] InnerHTML new bead

2016-12-11 Thread Alex Harui
On 12/11/16, 1:11 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >Hi, > >just committed a InnerHTML bead that solves one of my main concerns with >how to output HTML from MXML/AS in any component > >Right now the text is always added first (due to flexjs component life >cycle). >

Re: [FlexJS] InnerHTML new bead

2016-12-11 Thread Alex Harui
On 12/11/16, 12:37 PM, "piotrz" wrote: >Carlos, > >I just tried to build of examples and once I run it there seems to be some >issue with section CDATA. >Before text "Lorem ipsum..." there is been added next line sign and it >causes exception in JS. I've removed them and it's working, basically

Re: [FlexJS] InnerHTML new bead

2016-12-11 Thread Carlos Rovira
/paste.apache.org/nLu7 > > Piotr > > > > - > Apache Flex PMC > piotrzarzyck...@gmail.com > -- > View this message in context: http://apache-flex- > development.247.n4.nabble.com/FlexJS-InnerHTML-new-bead- > tp57155p57164.html > Sent from the Apache Flex

Re: [FlexJS] InnerHTML new bead

2016-12-11 Thread piotrz
section in one line. Not sure whether this is an issue. [1] https://paste.apache.org/nLu7 Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/FlexJS-InnerHTML-new-bead-tp57155p57164.html Sent from the Apa

Re: [FlexJS] InnerHTML new bead

2016-12-11 Thread piotrz
Hi Carlos, Really like this Bead :) Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-InnerHTML-new-bead-tp57155p57163.html Sent from the Apache Flex Development mailing list archive at

[FlexJS] InnerHTML new bead

2016-12-11 Thread Carlos Rovira
Hi, just committed a InnerHTML bead that solves one of my main concerns with how to output HTML from MXML/AS in any component For example: outputs: