I like the table. Organized
-Mark
On Wed, Jul 2, 2014 at 8:01 PM, OmPrakash Muppirala
wrote:
> Thanks to Aaron Nash, we now have skins for Android 4.3 - TextArea and
> TextInput. In the meantime, I have completed the Callout and related
> skins.
>
> I have updated the wiki page here:
>
> htt
I use tons of dot path references for xml/e4x. And much less frequently
the inline filtering.
-Mark
On Fri, Jul 4, 2014 at 3:21 AM, Alex Harui wrote:
> There are functions, but I've seen significant use of XML as an "Object".
> IMO it is what makes e4x possible: the dot-path lookup as below:
I'll throw tortoisegit [1] in the pot as well for a nice GUI git that has a
good integrated context menu set.
[1] https://code.google.com/p/tortoisegit/
-Mark
I certainly won't stop someone from trying to implement e4x in JS. I
think there may already be some attempts. I think a significant number of
folks use dot-path like Mark Kessler reported and so it will still be a
porting challenge for folks to re-code to using functions.
That's why it isn't on
On Sun, Jul 6, 2014 at 9:49 PM, Alex Harui wrote:
> I certainly won't stop someone from trying to implement e4x in JS. I
> think there may already be some attempts. I think a significant number of
> folks use dot-path like Mark Kessler reported and so it will still be a
> porting challenge for
On 7/6/14 9:54 PM, "OmPrakash Muppirala" wrote:
>On Sun, Jul 6, 2014 at 9:49 PM, Alex Harui wrote:
>
>> I certainly won't stop someone from trying to implement e4x in JS. I
>> think there may already be some attempts. I think a significant number
>>of
>> folks use dot-path like Mark Kessler
On Sun, Jul 6, 2014 at 10:12 PM, Alex Harui wrote:
>
>
> On 7/6/14 9:54 PM, "OmPrakash Muppirala" wrote:
>
> >On Sun, Jul 6, 2014 at 9:49 PM, Alex Harui wrote:
> >
> >> I certainly won't stop someone from trying to implement e4x in JS. I
> >> think there may already be some attempts. I think
I was thinking of creating a class which stores the xml structure internally as
javascript objects using these methods [1]
Then we could build on top of that all the standard E4X functions for accessing
nodes and attributes.
Dot notation would be complex (or impossible) to handle natively, but
I used the wrong link. It should have been:
https://developer.mozilla.org/en-US/docs/JXON
On Jul 7, 2014, at 8:50 AM, Harbs wrote:
> I was thinking of creating a class which stores the xml structure internally
> as javascript objects using these methods [1]
>
> Then we could build on top of th
On 7/6/14 10:27 PM, "OmPrakash Muppirala" wrote:
>
>Things like public Atom, RSS feeds do require XML processing.
I would assume someone has successfully handles RSS in JS already,
probably by using whatever XML apis are there. And that is always an
option, but I believe Flash and JS XML APIs
And I've been meaning to see if anyone has invented a proxy server that
does this sort of thing.
I'm still not convinced the compiler can convert e4x to these calls. We
can if we force folks to strongly type everything, but I'd bet a lot of
existing code is not strongly-typed enough. For example
Hi,
Just a heads up for the more legally inclined folks:
https://www.facebook.com/occupyhtml5/posts/1484874435063216
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
HI,
IMO (but I'm not a lawyer etc etc) but it's probably fine from an Apache Flex
point of view as it:
- not using "Apache Flex" in the domain name
- not any confusion with Apache Flex trademarks, products, distribution etc
But no objection if the PMC wants to send a friendly email asking for
a
13 matches
Mail list logo
