Re: [FlexJS]DropDownList dataProvider

Yes. I’ll try to put together a test case. > On Jul 9, 2017, at 6:57 PM, piotrz wrote: > > Actually could you provide small example ? I would like to make sure myself > that is a bug. > > Thanks, > Piotr > > > > - > Apache Flex PMC > piotrzarzyck...@gmail.com > -- > View this message in

Re: [FlexJS]DropDownList dataProvider

://issues.apache.org/jira/browse/FLEX-35336 <https://issues.apache.org/jira/browse/FLEX-35336> Harbs > On Jul 9, 2017, at 7:19 PM, Harbs wrote: > > Yes. I’ll try to put together a test case. > >> On Jul 9, 2017, at 6:57 PM, piotrz wrote: >> >> Actually could

Re: [FlexJS]DropDownList dataProvider

Yeah. I noticed that too. > On Jul 9, 2017, at 8:20 PM, piotrz wrote: > > Additionally I see in ArraySelectionModel which has been used in DropDownList > in dataProvider setter this one: > > if (value === this._dataProvider) >return; > > Piotr > > > > - > Apache Flex PMC > piotrzarz

Re: [FlexJS]DropDownList dataProvider

It was always like that, but I think it’s incorrect. You can go back in the history, but you need to follow the changes across the rename from HTML. SourceTree makes that pretty easy. > On Jul 9, 2017, at 9:00 PM, piotrz wrote: > > I cannot check when those changes was introduced, cause for so

Re: [FlexJS]DropDownList dataProvider

I fixed it. If someone feels that it’s not a bug we can revert the commit... Next issue… ;-) > On Jul 9, 2017, at 9:27 PM, Harbs wrote: > > It was always like that, but I think it’s incorrect. > > You can go back in the history, but you need to follow the changes across the

[FlexJS] Bindable and consts

com.acme.foobaz.model.Foo becomes k) k.BAZ even though k.BAZ was optimized away and k.BAZ is undefined. Why does [Bindable] on a class cause the bracket notation to be used? Harbs

Re: [FlexJS] technical debt

I have permissions to edit profiles, but I don’t seem to have permissions to assign profiles. I created another profile and I’m waiting for INFRA to look at my permissions again. > On Jul 10, 2017, at 9:28 AM, piotrz wrote: > > Hi Justin, > > Thank you. > > Harbs, >

Re: [FlexJS] technical debt

time for this now so I’m going to just leave this alone for the time being. Thanks, Harbs > On Jul 10, 2017, at 10:43 AM, Justin Mclean wrote: > > Hi, > >> I have permissions to edit profiles, but I don’t seem to have permissions to >> assign profiles. > > You d

Re: [FlexJS] technical debt

That’s a good idea, and I will probably do so next time I’m inclined to spend time on this. > On Jul 10, 2017, at 10:43 AM, Justin Mclean wrote: > > If you are trying things out rather than experimenting on the live server you > can run Sonar Cube locally.

Re: [FlexJS] Question about Events/possible bugs

Good catch. Without looking at them, I’d guess that they are bugs. Clipboard was my error and I just committed a fix for that. Thanks, Harbs > On Jul 10, 2017, at 11:06 AM, Greg Dove wrote: > > I noticed a problem with VerticalFlexLayout in IE11 (and presumably older > IE browser

Re: [FlexJS] Question about Events/possible bugs

GraphicContainer was another one I was involved in, so I know that’s an omission as well. (committed) > On Jul 10, 2017, at 11:16 AM, Harbs wrote: > > Good catch. > > Without looking at them, I’d guess that they are bugs. Clipboard was my error > and I just commit

Re: [FlexJS] Question about Events/possible bugs

It could, but there’s no reason to. The Clipboard class is just a proxy to the native Flash Clipboard class on the SWF side. > On Jul 10, 2017, at 11:02 AM, piotrz wrote: > > Harbs, > > I think this import could be outside COMPILE::JS. > > Piotr > > &

Re: [FlexJS] States Bug?

The bug (if it is one) seems to be when using nested includeIn attributes. What happens is that you get two objects with the same key (i.e. the same object is included twice in the class) > On Jul 10, 2017, at 11:07 AM, yishayw wrote: > > It looks like the compiler gets confused when we add ne

Re: [FlexJS] Bindable and consts

? Thanks, Harbs > On Jul 9, 2017, at 11:27 PM, Harbs wrote: > > I just discovered something: > > Foo.as: > package com.acme.foobaz.model{ > [Bindable]public class Foo{ > static public const BAZ:String = “baz”; > } > } > > In some other

Re: [FlexJS] technical debt

How can you use filtering to change what the dashboard shows? > On Jul 10, 2017, at 2:02 PM, Justin Mclean wrote: > > Hi, > >> I was trying to set up an alternate set because it’s easier to have two sets >> to compare rather than having long drawn-out discussion. > > As opposed to using the f

Re: [FlexJS] States Bug?

It does. It was code that was imported from a regular Flex component. It worked in the old app (although it was probably not necessary). > On Jul 10, 2017, at 6:45 PM, Alex Harui wrote: > > If you have time, see if it works in regular Flex. > > Thanks, > -Alex > > On

Re: [FlexJS] Bindable and consts

that I keep putting off until we’re in a better place. Harbs > On Jul 10, 2017, at 6:54 PM, Alex Harui wrote: > > How urgent is this? I'm trying to figure out why the compiler did not > respond properly to bad MXML. > > I thought public APIs were all exported so the

Re: [2/5] git commit: [flex-asjs] [refs/heads/develop] - FLEX-35338 stop cursor from spinning / CPU from spiking

Shouldn’t the event be triggered by rollover rather than mouseover? That seems like the issue to me… > On Jul 11, 2017, at 10:13 AM, Alex Harui wrote: > > This seems like "just-in-case" code. I could see that it might be needed > in a different bead for Express though. > > Without this change

Re: [2/5] git commit: [flex-asjs] [refs/heads/develop] - FLEX-35338 stop cursor from spinning / CPU from spiking

Did you try mouseenter? (See my other responses) It seems like that should solve the problem. > On Jul 11, 2017, at 11:01 AM, Justin Mclean wrote: > > Hi, > > I not sure how this could be consider "just in case" when previous the > tooltip didn’t work and had an infinite loop? Before it was i

Re: [2/5] git commit: [flex-asjs] [refs/heads/develop] - FLEX-35338 stop cursor from spinning / CPU from spiking

to rollOver. That should mean that mouseenter should be the better option. [2]https://www.quirksmode.org/js/events_mouse.html <https://www.quirksmode.org/js/events_mouse.html> > On Jul 11, 2017, at 10:48 AM, Harbs wrote: > > No. I’m wrong. > > First of all, it’s m

Re: [2/5] git commit: [flex-asjs] [refs/heads/develop] - FLEX-35338 stop cursor from spinning / CPU from spiking

re the MouseEvent constants wrong for Javascript? > On Jul 11, 2017, at 10:38 AM, Harbs wrote: > > Shouldn’t the event be triggered by rollover rather than mouseover? > > That seems like the issue to me… > >> On Jul 11, 2017, at 10:13 AM, Alex Harui wrote: >> &g

Re: [2/5] git commit: [flex-asjs] [refs/heads/develop] - FLEX-35338 stop cursor from spinning / CPU from spiking

unnecessary mouse events when mousing in and out of the tool tip. On the other hand, placing it inside the target element might effect layout and the like. It’s possible that this can be solved using absolute/fixed positioning and zindex. Thoughts? Harbs > On Jul 11, 2017, at 11:16 AM, Jus

[FlexJS]MouseEvent.ROLL_OVER (was Re: [2/5] git commit...)

and ROLL_OUT events for any elements which have listeners registered for them. This seems horribly inefficient and I don’t understand why it’s necessary. It seems to me that mouseenter and rollOver (as well as mouseleave and rollOut) are analogous. Am I missing something? Thanks, Harbs > On

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

outweigh the “correctness” of using constants. Thanks, Harbs > On Jul 11, 2017, at 11:46 AM, piotrz wrote: > > I just think that we should use const whenever we can, but won't fight for > that if no one think similar. :) If I found such code around my interest my > natural mov

Re: [FlexJS]MouseEvent.ROLL_OVER (was Re: [2/5] git commit...)

and-mouseeventmouse_over-in-as3/> > On Jul 11, 2017, at 12:19 PM, piotrz wrote: > > Harbs, > > I have found following examples [1][2][3]. Maybe it will help us. > > [1] > https://siongui.github.io/2012/08/07/javascript-compare-mouseenter-mouseleave-mou

Re: [FlexJS]MouseEvent.ROLL_OVER (was Re: [2/5] git commit...)

mouseover is needed if you need bubbling. That’s sometimes the correct behavior. > On Jul 11, 2017, at 1:19 PM, piotrz wrote: > > It seems to. MouseOver is launching really often - Maybe Enter/Leave would be > really better. > Need test to see whether we have same behavior having Enter/Leave as

CSS compiler issues

I just created a couple of JIRAs on compiler issues that have been bugging me for a while.[1][2] Neither of these are super-important, but it would be nice if it worked better. Harbs [1]https://issues.apache.org/jira/browse/FLEX-35340 <https://issues.apache.org/jira/browse/FLEX-35340&

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

PONSE_STATUS','httpResponseStatus');fqa.prototype.h={names:[{name:'HTTPConstants',i:IF,kind:g}]};w(IF,fqa); elsewhere: IF='org.apache.flex.net.HTTPConstants’, That’s 807 bytes. That’s quite a penalty for avoiding typing “POST”… No idea what wiki you are referring to. Ha

Re: [FlexJS]MouseEvent.ROLL_OVER (was Re: [2/5] git commit...)

performance issues. My question here is why are we not using the standard mouseenter and are using a hacky solution for custom ROLL_OVER events instead. I think Alex wrote that code, so I’m going to wait until he can respond. Thanks, Harbs > On Jul 11, 2017, at 1:50 PM, piotrz wrote: >

Re: Flash Builder desktop debugging issue

Same for me. > On Jul 11, 2017, at 4:18 PM, Jeffry Houser wrote: > > To debug a browser based applications, I use Firefox. I couldn't get a > debugger to work in any other browser.

Re: [FlexJS]MouseEvent.ROLL_OVER (was Re: [2/5] git commit...)

was only supported by IE. If we agree it > is safe to use on all of our target browsers, we can switch to using it. > > I don't think it will solve the flicker problem. I think the tooltips > need to be "mouse transparent". > > My 2 cents, > -Alex > >

Re: [FlexJS]MouseEvent.ROLL_OVER (was Re: [2/5] git commit...)

That should have been MOUSE_ENTER rather than MOUSE_OVER. > On Jul 11, 2017, at 6:58 PM, Harbs wrote: > > It’s been supported by every browser since 2014. I think we should switch to > that. > > I was pondering whether we should standardize on ROLL_OVER or MOUSE_OVER. I &

Re: [FlexJS]MouseEvent.ROLL_OVER (was Re: [2/5] git commit...)

pointer-events:none; Definitely the right way to go. > On Jul 11, 2017, at 6:01 PM, piotrz wrote: > > Alex, > > What do you mean by Mouse "transparent" ? We still need to use some event > mouse (enter/leave) where after roll over on the element tooltip should be > shown. > > Piotr > > > >

Re: [FlexJS]MouseEvent.ROLL_OVER (was Re: [2/5] git commit...)

To be clear: That css should be applied to the ToolTip element. > On Jul 11, 2017, at 6:54 PM, Harbs wrote: > > pointer-events:none; > > Definitely the right way to go. > >> On Jul 11, 2017, at 6:01 PM, piotrz wrote: >> >> Alex, >> >> What do

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

+1. I also think that we have bigger fish to fry first. My point was not to force one way or the other. Rather that the way it currently stands there’s a valid reason to use string literals. I was not suggesting changing anything. Thanks, Harbs > On Jul 11, 2017, at 6:33 PM, Josh Tynj

Re: [1/5] git commit: [flex-asjs] [refs/heads/develop] - FLEX-35337 place tool tip anchor point in the centre rather than the bottom right

Why are you assuming that this behavior is wrong? Don’t you think a functional change should require discussion? Thanks, Harbs > On Jul 11, 2017, at 8:40 AM, jmcl...@apache.org wrote: > > Repository: flex-asjs > Updated Branches: > refs/heads/develop e93c11d7c -> 1d73de00b

[FlexJS]Runtime type checking and PAYG

catch this in the compiler, because the argument is different for SWF and JS. Is this a violation of PAYG? It’s sort-of just in case code, but not really because it’s protecting against errors. Thoughts? Other solutions? Harbs

Re: [FlexJS]Runtime type checking and PAYG

tps://stackoverflow.com/questions/11402218/removing-debug-code-from-inside-a-function-using-closure-compiler-simple-optimis> > On Jul 12, 2017, at 12:37 AM, Harbs wrote: > > Sounds interesting. > > I’m not sure I understand how this would work. I am willing to explore this >

Re: [FlexJS]Runtime type checking and PAYG

mpile outside of COMPILE::JS blocks > that might be ok. > > -Alex > > On 7/11/17, 1:07 PM, "Harbs" wrote: > >> I just wasted over an hour because I was initializing a BinaryData with a >> string instead of an ArrayBuffer. >> >> I would like

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

needs to be some way to invoke the app… Harbs > On Jul 11, 2017, at 11:40 PM, Greg Dove wrote: > > Guys, we certainly have been here before. > > From a js release 'size' perspective, I don't think it matters whether we > use constants or liteterals, I think t

Re: [FlexJS]Runtime type checking and PAYG

ds during development that have more code paths that check for common >>> mistakes is certainly within the charter. We want to maximize developer >>> productivity. >>> >>> I think Google Closure Compiler supports a debug flag you can use in >>> COMPILE

[FalconJX] Debugging minified code

, Harbs [1]https://github.com/google/closure-compiler/wiki/Debugging-Compiled-Code <https://github.com/google/closure-compiler/wiki/Debugging-Compiled-Code>

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

d wanted to bring up for a long time: I think trace statements should disappear in the release JS build. Should we put all the JS trace code inside an if(goog.DEBUG) block? Thanks, Harbs

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

Not super important, but it would be nice if at some point we can figure out if there’s a way to strip out the calls completely. > On Jul 12, 2017, at 10:07 AM, Harbs wrote: > > Oof. I think I’m still waking up. ;-) > > I did not realize what I was looking at with the goog.DEBUG. M

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

; be taught to do it. We visit almost every line of the JS output in the > publishers right now. > > My 2 cents, > -Alex > > On 7/11/17, 11:47 PM, "Harbs" wrote: > >> >>> On Jul 12, 2017, at 8:20 AM, Alex Harui >>> wrote: >>> >

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

There is a goog.log package.[1] Unless I’m mistaken, those calls are removed by the compiler. It might be nice to have a generic cross-platform logging package. [1]https://google.github.io/closure-library/api/goog.log.html > On Jul 12

Re: [FalconJX] Debugging minified code

> in the article to GCC. > > I haven't had to debug anything really big, but I often delete the source > map, add line breaks to the area of code that is failing and step through > it. Painful for sure, but often successful. > > HTH, > -Alex > > On 7/11/1

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

I don’t know. I don’t use logging nearly as much as I probably should. I was just pointing out the goog.log package on the JS side in case you want to implement something. Thanks, Harbs > On Jul 12, 2017, at 10:39 AM, Justin Mclean wrote: > > Hi, > >> It might be nice

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

Like I said, it would be nice to figure out how to remove it completely. It’s not awfully expensive though. It’s a simple copy of an array with a single string. > On Jul 12, 2017, at 11:52 AM, Justin Mclean wrote: > > Hi, > >> function >> uM(a){a=Array.prototype.slice.call(arguments,0)}w('or

[OT] FYI: XHR pitfall

upload progress events to URLBinaryLoader, but this throws a monkey wrench into those plans. We’ll probably do it as a subclass and document a warning about using it... Harbs [1]https://stackoverflow.com/a/17057853

Re: [FalconJX] Debugging minified code

n some way… Harbs > On Jul 12, 2017, at 4:15 PM, Josh Tynjala wrote: > > You should include the dashes, and you should surround everything in > quotes. I think you put spaces between each option, but I've never used > more than one. > > Here's a Closure option

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

be stripped out. Of course, I have no idea how to go about doing that… ;-) Harbs > On Jul 12, 2017, at 4:32 PM, Josh Tynjala wrote: > > Probably the same with function calls too: > > trace(someFunction()); > > They wanted this to remain: > > someFunction(); >

Re: [FalconJX] Debugging minified code

FYI, here’s a sample of what the code looks like with those options enabled.[1] Harbs [1]https://paste.apache.org/OM4H <https://paste.apache.org/OM4H> > On Jul 12, 2017, at 5:03 PM, Harbs wrote: > > Never mind. There was an error in my app that was preventing the minification

Re: [FalconJX] Debugging minified code

app is still over 62,000 lines. It’s pretty impressive how well the compilers do with an app of this size. :-) Harbs > On Jul 12, 2017, at 4:53 PM, Harbs wrote: > > Thanks. That does in fact work. > > Here’s what I used: > -js-compiler-option='--formatting PRETTY_PRINT

Re: [1/5] git commit: [flex-asjs] [refs/heads/develop] - FLEX-35337 place tool tip anchor point in the centre rather than the bottom right

it stands, the tooltips are significantly less useable than they were before your changes. Thanks, Harbs > On Jul 12, 2017, at 2:08 AM, Justin Mclean wrote: > > Hi, > >> Why are you assuming that this behavior is wrong? > > Because if you have two components side by

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

folks are just used to trace and the > cool thing about JS right now is that you can replace functions at > runtime, so a logging bead would just replace Language.trace(). > > -Alex > > On 7/12/17, 6:44 AM, "Harbs" wrote: > >> Interesting scenarios. I would

Re: [FalconJX] Debugging minified code

Yes. That works too: -js-compiler-option='--debug' -js-compiler-option='--formatting PRETTY_PRINT' Thanks. > On Jul 12, 2017, at 6:11 PM, Alex Harui wrote: > > In theory, you should have been able to use -js-compiler-option more than > once. > > -Alex &g

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

n't re-transpile and > just pass js-debug files to GCC and generate a new js-release output. > > -Alex > > On 7/12/17, 9:11 AM, "Harbs" wrote: > >> That line was what was left of the trace function. >> >> The reason the trace function is no

Multipart

through an ICLA, or can we just bring it in with no fuss? Thanks, Harbs [1]https://github.com/jimojon/Multipart.as/issues/9 <https://github.com/jimojon/Multipart.as/issues/9>

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

dea why my more complex project outputs trace differently… Harbs > On Jul 12, 2017, at 8:11 PM, Harbs wrote: > > Maybe I’m doing something wrong, but I get the following error when I tried > using -skip-transpile: > > [java] ja

FlexJS Yeoman generator

ost on Facebook, that would be awesome. Harbs

Re: FlexJS Yeoman generator

Feel free. You know how I feel about using Facebook. ;-) > On Jul 12, 2017, at 11:03 PM, piotrz wrote: > > Go ahead and post it on our facebook!

Re: FlexJS Yeoman generator

You are full of surprises. :-) I’d love to hear the details. That would make an incredible article. Thanks, Harbs > On Jul 12, 2017, at 11:24 PM, Josh Tynjala wrote: > > I even figured out how to make Travis CI compile with FlexJS (and Travis is > running Linux, by the way)

Re: FlexJS Yeoman generator

Wow. That is pretty cool! Talk about dogfooding. ;-) It’s really nice to see an actual project targeting node. The way you setup the typdefs was very educational for me. I didn’t realize it can be done like that. Thanks! > On Jul 12, 2017, at 11:24 PM, Josh Tynjala wrote: > > Than

Re: Multipart

In our repo with my modifications for FlexJS. > On Jul 13, 2017, at 1:22 AM, Alex Harui wrote: > > What do you mean by "adopt". That the new home for further improvements > is in our repo or that we're using it as a third-party dependency? > > -Alex > &g

Re: [FlexJS] Use of typeof

lex Harui wrote: > > What AS do you want to write and what JS do you want as output? > > -Alex > > On 7/9/17, 12:53 AM, "Harbs" wrote: > >> Checking for window will work for Node, but it will not work for Electron. >> >> I tried adding global to

Re: Multipart

o work on it, then attaching it to a > JIRA would be sufficient documentation of his intent to donate it. > > Either way, it would help if he put the 3rd-party ALv2 header in the file. > > -Alex > > On 7/12/17, 8:59 PM, "Harbs" wrote: > >> In our repo wit

Re: git commit: [flex-asjs] [refs/heads/develop] - Uploads are assumed to be POST

ipped out for release. A @debug comment before the function declaration is probably the simplest solution and fits with the current conventions. I’m not sure what this would all look like for a swf compile. Harbs > On Jul 13, 2017, at 12:35 AM, Alex Harui wrote: > > Bummer. It look

Re: [FlexJS] Use of typeof

ron? Or are you > willing to just try to check for features instead? > > If you can show what JS code you'd want to end up with we can look into > changing the compiler so you can write AS to generate that JS. > > Thanks, > -Alex > > On 7/12/17, 9:03 PM, "Harbs&q

Re: [1/5] git commit: [flex-asjs] [refs/heads/develop] - FLEX-35337 place tool tip anchor point in the centre rather than the bottom right

> On Jul 13, 2017, at 7:21 AM, Justin Mclean wrote: > > Hi, > >> I noticed today that I was actually using ToolTips and your changes make my >> buttons very difficult to use as they are significantly obscured by the >> tooltips. Also, the tooltips are now under the mouse, so the text in not

Re: [FlexJS] Bindable and consts

Thanks. I just (re)read it. I don’t think I quite understood it the first time around. > On Jul 13, 2017, at 9:24 AM, Alex Harui wrote: > > See this background thread if you're > interested [1] > -Alex > > [1] > https://lists.apache.org/thread.html/9802158cb9bf3b3737d7841ff950130d8e7a6e >

Re: [FlexJS] Use of typeof

window/global should be defined in those > SWCs. > > I'm not sure what the test case is supposed to look like. > > Thanks, > -Alex > > On 7/13/17, 12:11 AM, "Harbs" wrote: > >> Electron has both window and global. Node has global and no window. I >

Re: git commit: [flex-asjs] [refs/heads/develop] - added simple positioning to tool tip / make tool tip not react to mouse events

> + positioner.style["pointer-events"] = "none”; I think that should be positioner.style["pointerEvents"] = "none”;

Re: git commit: [flex-asjs] [refs/heads/develop] - added simple positioning to tool tip / make tool tip not react to mouse events

Any reason you didn’t just add this to the constructor? I think all you need is: mouseEnabled = false; In Flash, “element” is a pointer to “this”. Thanks, Harbs > On Jul 13, 2017, at 10:16 AM, jmcl...@apache.org wrote: > > + COMPILE::SWF > + override pub

Re: git commit: [flex-asjs] [refs/heads/develop] - added simple positioning to tool tip / make tool tip not react to mouse events

When specifying css via javascript, the naming is different than specifying using CSS files. I’d be *very* surprised if the code works as-is. > On Jul 13, 2017, at 3:23 PM, Justin Mclean wrote: > > Hi > >>> + positioner.style["pointer-events"] = "none”; >> >> I think that s

Re: git commit: [flex-asjs] [refs/heads/develop] - added simple positioning to tool tip / make tool tip not react to mouse events

I don’t see how this is PAYG. It’s more code for no reason. > On Jul 13, 2017, at 3:25 PM, Justin Mclean wrote: > > Hi, > >> Any reason you didn’t just add this to the constructor? > > PAYG - i.e. no need to do it until it added to the UI. > > Thanks, > Justin

Re: git commit: [flex-asjs] [refs/heads/develop] - added simple positioning to tool tip / make tool tip not react to mouse events

More information here: https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Properties_Reference <https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Properties_Reference> > On Jul 13, 2017, at 4:48 PM, Harbs wrote: > > When specifying css via javascript, the naming is

Re: git commit: [flex-asjs] [refs/heads/develop] - added simple positioning to tool tip / make tool tip not react to mouse events

Here’s a fiddle trying to set pointer-events in various ways. Only one (with dot notation) works: https://jsfiddle.net/Harbs/9c8zezx5/ <https://jsfiddle.net/Harbs/9c8zezx5/> > On Jul 13, 2017, at 5:51 PM, Harbs wrote: > > More information here: > https://developer.mozilla.

Re: [FlexJS] Use of typeof

ndling of that code. "window" > is defined in missing.js so the js.swc knows there is such an entity. Is > there any reason not to add a "global" to node.swc? > > -Alex > > On 7/13/17, 12:29 AM, "Harbs" wrote: > >> Right now, if you have

Re: [FlexJS] Use of typeof

think the correct solution is to add node.swc to the > -external-library-path when you need access to global. You need js.swc on > the -external-library-path when you want to access window. You can't use > window in a SWF-only project, for instance. > > - Josh > > On

Re: [FlexJS] Use of typeof

Adding node.swc makes things like require be recognized, but global is still not. Odd. I thought I saw it in the typedefs. > On Jul 13, 2017, at 8:04 PM, Harbs wrote: > > Are you saying we should add node.swc to Core? > > FWIW, I just tried setting targets to JSNode and glob

Re: git commit: [flex-asjs] [refs/heads/develop] - added simple positioning to tool tip / make tool tip not react to mouse events

It did not work on any Mac browser. Don’t know about Windows. > On Jul 13, 2017, at 8:26 PM, Alex Harui wrote: > > IIRC, style["pointer-events"] works in some browsers but not all.

Re: git commit: [flex-asjs] [refs/heads/develop] - added simple positioning to tool tip / make tool tip not react to mouse events

Something that I keep forgetting to ask: Do [Inspectable] meta tags work in FlexJS? I’m not sure how they worked in classic Flex, but having suggestions of possible values in an IDE was very helpful. Josh, would something like that be possible in VS Code? > On Jul 13, 2017, at 8:26 PM, Alex Ha

Re: git commit: [flex-asjs] [refs/heads/develop] - added simple positioning to tool tip / make tool tip not react to mouse events

Wouldn’t string constants be even clearer? > On Jul 13, 2017, at 8:26 PM, Alex Harui wrote: > > I would also recommend using large numbers for the constants.

Re: FlexJS Yeoman generator

We’re already discussing that problem here: https://www.patreon.com/posts/scaffold-apache-12918005?cid=6126089 It works from the command line, so it seems like it’s an issue that’s connected to the VS Code extension. > On Jul

Re: Multipart

ere other > contributors so we may need to get their permission to make the license > ALv2. > > Of course, I could be wrong,... > -Alex > > On 7/12/17, 9:14 PM, "Harbs" wrote: > >> I don’t think he has plans on modifying it. >> >> Do you mi

Re: git commit: [flex-asjs] [refs/heads/develop] - added simple positioning to tool tip / make tool tip not react to mouse events

I’m not understanding. What worked and what didn’t? In this fiddle: https://jsfiddle.net/Harbs/9c8zezx5/ <https://jsfiddle.net/Harbs/9c8zezx5/> You should get an alert when clicking on every div except div1 (the top left one). Are you seeing something different? > On Jul 14, 2017, at

Bead Lifecycle (was Re: git commit: [flex-asjs] [refs/heads/develop] - Add FileUploaderWithResponseData)

the strand/bead relationships a lot more structure. Thoughts? Harbs > > On Jul 13, 2017, at 7:34 PM, Alex Harui wrote: > > Yes, that's how I think of it. You are right that getting one bead in a > multi bead set to listen to other beads is tricky. UIBase defines a &

Re: git commit: [flex-asjs] [refs/heads/develop] - added simple positioning to tool tip / make tool tip not react to mouse events

Yes. You are right. https://jsfiddle.net/Harbs/9c8zezx5/1/ <https://jsfiddle.net/Harbs/9c8zezx5/1/> I’m not sure how I missed that. My bad… > On Jul 14, 2017, at 1:38 AM, Greg Dove wrote: > > Harbs I think that jsfiddle is not working because of the missing quotes in >

Re: git commit: [flex-asjs] [refs/heads/develop] - added simple positioning to tool tip / make tool tip not react to mouse events

I was wondering why bracket access was not working. I should have opened my eyes. I am surprised that both kinds of bracket access works though. You learn something new all the time. ;-) Either way, camel case “feels” more correct, but whatever… Harbs > On Jul 14, 2017, at 1:46 AM, Ha

Re: git commit: [flex-asjs] [refs/heads/develop] - added simple positioning to tool tip / make tool tip not react to mouse events

One thing I’m curious about: Why does the Google compiler not rename style properties even when we use dot notation? Is it because the object is owned by an external HTMLElement object? I’d like to get a better grasp on when Object typed variables are renamed and when not. I’ve taken to using b

Re: Bead Lifecycle (was Re: git commit: [flex-asjs] [refs/heads/develop] - Add FileUploaderWithResponseData)

. Harbs > On Jul 14, 2017, at 2:48 AM, Alex Harui wrote: > > These are good points. I'm glad I sent my PAYG email earlier today. I'm > not sure I understood points #3 (dependencies) and #5 (cross-referencing) > so apologies if my thoughts below didn't take them into a

Re: Bead Lifecycle (was Re: git commit: [flex-asjs] [refs/heads/develop] - Add FileUploaderWithResponseData)

k and give predictable behavior. The notification vs events question is a separate point to ponder. Thoughts? > On Jul 14, 2017, at 3:38 AM, Harbs wrote: > > 1. I think so, or at most, only slightly. We’d probably save some code by not > adding lots of functions for events and the

Re: Moonshine 1.5.0 Release

+1. > On Jul 14, 2017, at 12:13 PM, piotrz wrote: > > Moonshine is one of the IDE which supports FlexJS - maybe we could make some > shout out about that on fan page ? What do you think guys ? > > Thanks, Piotr > > > > - > Apache Flex PMC > piotrzarzyck...@gmail.com > -- > View this mess

Re: Contribution to Multipart

Perfect. The project owner already gave permission, but we need to get permission from other contributors as well. Thanks, Harbs > On Jul 14, 2017, at 12:05 PM, Norman Xu wrote: > > Hi Harbs, > > Thanks for emailing me, I did made a small contribution but I think I don'

Re: Multipart

those lines of code and replace it? Or, > should our initial check-in not include un-permitted lines of code and the > first commits replace them? > > Of course, I could be wrong... > -Alex > > On 7/13/17, 2:40 PM, "Harbs" wrote: > >> One of them was d

Re: Multipart

Maybe. Not sure. What’s standard practice with this kind of thing? I’ve never done this before. > On Jul 14, 2017, at 6:59 PM, Dave Fisher wrote: > > Hi Harbs, > > If the package naming is kept is there any risk of a user having a classname > collision if they use the origi

Re: [01/10] git commit: [flex-asjs] [refs/heads/refactor-strand] - Core changes to IStrand

> Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/80580936 > Diff: http://git-wip-us.apache.org/repos/asf/flex-asjs/diff/80580936 > > Branch: refs/heads/refactor-strand > Commit: 80580936bf28455f7c3573ca96ee14dff396936c > Parents: dd4672b > Author: Harbs >

Re: Multipart

had > a ton of existing code that referenced those package names. Otherwise, I > think we would have renamed the packages. > > My 2 cents, > -Alex > > On 7/14/17, 9:02 AM, "Harbs" wrote: > >> Maybe. Not sure. >> >> What’s standard practice with t

Re: Bead Lifecycle (was Re: git commit: [flex-asjs] [refs/heads/develop] - Add FileUploaderWithResponseData)

x someone try to load two modules and they might return in different > order and if they had to find each other, they had to create a similar > protocol. Maybe there can be a base class for beads that need to find > each other that has some built-in code that manages this protocol. >

<    1   2   3   4   5   6   7   8   9   10   >