Re: Streaming video to FMS?

Unfortunately, they don't expose the APIs to be able to fake the camera input, so there really isn't any way to do it. There are drivers that exist at the OS level that allow you to do this (TechSmith used to make one, but it wasn't updated to W10 and later OSX versions) -- and they essentially al

Re: [07/13] git commit: [flex-asjs] [refs/heads/release0.8.0] - give up on trying to use FlexBox for full-screen 3-pane views. FlexBox seems more happy stretching to content size instead of clipping a

That’s probably it. It really needs bracket access. Alex, if you are looking for a task in the compiler, here’s a suggestion that would drastically reduce bugs in minified apps: 1. For all untyped objects, dot notation should be rewritten to bracket notation: var myObj:Object = myArr[idx]; do

Re: [07/13] git commit: [flex-asjs] [refs/heads/release0.8.0] - give up on trying to use FlexBox for full-screen 3-pane views. FlexBox seems more happy stretching to content size instead of clipping a

You can grab the JSON files from the Jenkins server, but the Ant build should also build them. My guess is that the code isn't finding properties from the JSON objects because GCC renamed the properties. -Alex On 9/26/17, 2:25 PM, "Harbs" wrote: >I can’t test because I’m missing the json files

Re: [07/13] git commit: [flex-asjs] [refs/heads/release0.8.0] - give up on trying to use FlexBox for full-screen 3-pane views. FlexBox seems more happy stretching to content size instead of clipping a

I can’t test because I’m missing the json files and I’m not sure how to generate them. Looks like some binding problem probably due to renaming. The json files appear to be loading correctly from the web. > On Sep 26, 2017, at 11:41 PM, Alex Harui wrote: > > Feel free to take a investigate.

RE: Streaming video to FMS?

Thank you, Nick and Peter. Yeah, the FFMPEG option was my backup in case this didn't work. So, if we could fake the mp4 stream to appear like a camera stream then this should work wouldn't it? I tried exploring the NetStream instance but there doesn't seem to be anything obvious enough to do th

Re: [07/13] git commit: [flex-asjs] [refs/heads/release0.8.0] - give up on trying to use FlexBox for full-screen 3-pane views. FlexBox seems more happy stretching to content size instead of clipping a

Feel free to take a investigate. Peter's old ASDoc page points to the js-debug version. It loads slowly some times, but at least it is functional. I'd rather work on other things right now than chasing down a js-release problem. -Alex On 9/26/17, 1:36 PM, "Harbs" wrote: >FWIW, the debug vers

Re: [07/13] git commit: [flex-asjs] [refs/heads/release0.8.0] - give up on trying to use FlexBox for full-screen 3-pane views. FlexBox seems more happy stretching to content size instead of clipping a

FWIW, the debug version is working, but the release version does not appear to work: http://apacheflexbuild.cloudapp.net:8080/job/FlexJS_ASDoc_Example/lastSuccessfulBuild/artifact/examples/flexjs/ASDoc/bin/js-release/index.html

Re: [07/13] git commit: [flex-asjs] [refs/heads/release0.8.0] - give up on trying to use FlexBox for full-screen 3-pane views. FlexBox seems more happy stretching to content size instead of clipping a

If I understand the problem (which I'm not sure, since the fix you posted runs code if not Safari), you could create a OneFlexibleChildLayoutWithSafariXSupport and put your fixes with browser sniffing in there. That way folks who don't need it, don't pay for the sniffing. There might be a version

Re: [07/13] git commit: [flex-asjs] [refs/heads/release0.8.0] - give up on trying to use FlexBox for full-screen 3-pane views. FlexBox seems more happy stretching to content size instead of clipping a

I’m showing how to fix the “non-ForOverflow” layouts. The problem is that Safari handles flex layouts differently than other browsers. I’d like to use the flexbox layouts and AFAICT, they need browser sniffing to work across the board. Ideally, the browser sniffing should be included in the lay

Re: [07/13] git commit: [flex-asjs] [refs/heads/release0.8.0] - give up on trying to use FlexBox for full-screen 3-pane views. FlexBox seems more happy stretching to content size instead of clipping a

I'm not sure if you have the exact same problem as ASDoc, but the ASDoc example is working fine with the "ForOverflow" layouts and no extra code in the app. Or are you saying ASDoc isn't working for you on some browser? IMO, that's the whole point of having many different flavors of layouts. Folk

Re: [DISCUSS} Fork FlexJS from Apache Flex

JS version is working again. You'll see that it isn't very pretty. Volunteers are welcome to make it look better. Thanks, -Alex On 9/26/17, 12:15 PM, "Alex Harui" wrote: >I just fixed the SWF version. Working on the JS version now. > >-Alex > >On 9/26/17, 6:55 AM, "yishayw" wrote: > >>The a

Re: [07/13] git commit: [flex-asjs] [refs/heads/release0.8.0] - give up on trying to use FlexBox for full-screen 3-pane views. FlexBox seems more happy stretching to content size instead of clipping a

I ran into the Safari problem in my app. I needed to add code like this: var info:BrowserInfo = BrowserInfo.current(); if(info.browser != "Safari" && info.formFactor.indexOf("iP") == -1){ outerContainer.percentHeight = 100; leftResizeThumb.percentHeight = 100; } The components lo

Re: [07/13] git commit: [flex-asjs] [refs/heads/release0.8.0] - give up on trying to use FlexBox for full-screen 3-pane views. FlexBox seems more happy stretching to content size instead of clipping a

I just reverted ASDoc back to the "ForOverflow" layouts. ASDoc was not showing up correctly for me (Safari). Maybe flex-basis is handled differently on different browsers. We can look into it more later. Looking into this did make me glad we are changing over to "Royale" so "Flex" and "FlexJS"

Re: [DISCUSS} Fork FlexJS from Apache Flex

I just fixed the SWF version. Working on the JS version now. -Alex On 9/26/17, 6:55 AM, "yishayw" wrote: >The address is ok but tags.json isn't found... > > > > > >-- >Sent from: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle >x-development.247.n4.nabble.com%2

Re: [Discuss] Pros and Cons of Using Royale to Build Websites

Harbs has to request the repos and mailing lists, and then Infra will hookup GitPubSub and we'll be able to set up royale.apache.org. And when we do, I suggest that we stick in some static pages just for now. I can do it, but will look ugly if I do, so best if someone else can do it. But over ti

Re: FlexJS element setter

Harbs, Give me couple of days and I will pick up that branch and try it out. I will also review those changes and give the feedback. Thanks! 2017-09-26 20:50 GMT+02:00 Harbs : > I think I’m done. Any reason to not merge into develop? > > > On Sep 26, 2017, at 7:01 PM, Piotr Zarzycki > wrote: >

Re: FlexJS element setter

I think I’m done. Any reason to not merge into develop? > On Sep 26, 2017, at 7:01 PM, Piotr Zarzycki wrote: > > Harbs, > > Please push those changes into separate branch "feature/" no matter how non > serious it look. I hope your changes will simplify things. > > Thank you! > > > 2017-09-26

Re: FlexJS element setter

No. I just used it because it’s the simplest UI component. I don’t remember off hand what I needed it for. > On Sep 26, 2017, at 8:59 PM, Alex Harui wrote: > > You aren't the only one, but why did you do it? Is there some subclass of > UIBase missing from the component set? ScratchPad? Space

Re: FlexJS element setter

You aren't the only one, but why did you do it? Is there some subclass of UIBase missing from the component set? ScratchPad? Spacer? On 9/26/17, 10:53 AM, "Harbs" wrote: >I’ve used it. > >> On Sep 26, 2017, at 8:41 PM, Alex Harui >>wrote: >> >> IMO, the first question is, do we really need

Re: FlexJS element setter

I’ve used it. > On Sep 26, 2017, at 8:41 PM, Alex Harui wrote: > > IMO, the first question is, do we really need to support "new UIBase()"?

Re: FlexJS element setter

Funny you mention that. I added addElementToWrapper() as a top level function which attaches elements to UIBases. I have just finished implementing this in all Basic and MDL components. That pretty much removes the need to call super. I’m committing my changes soon (to a branch). > On Sep 26,

Re: FlexJS element setter

IMO, the first question is, do we really need to support "new UIBase()"? I remember being surprised in regular Flex when folks did "new UIComponent()". There aren't abstract classes in ActionScript, but I would have made UIComponent and UIBase abstract if I could. But if the answer is that we wan

Re: FlexJS element setter

Huh? Why would the subclass call super.createElement() and assume the element will not be created? FWIW, super.createElement() is barely called, and when it is (from all the cases I’ve found so far in the whole Basic and MDL), it’s expecting the default div element. > On Sep 26, 2017, at 8:15

Re: FlexJS element setter

IIRC, UIBase has that code so if you do "new UIBase()" you will get an element, but if subclasses call super.createElement() by habit, we won't overwrite anybody's element. It isn't truly PAYG, it depends on how folks feel about "requiring" that you know not to call super.createElement() on UIBase

Re: FlexJS element setter

FYI: TableRowItemRenderer in MDL has a separate positioner. > On Sep 26, 2017, at 7:01 PM, Piotr Zarzycki wrote: > > Harbs, > > Please push those changes into separate branch "feature/" no matter how non > serious it look. I hope your changes will simplify things. > > Thank you! > > > 2017-0

Re: FlexJS element setter

Harbs, Please push those changes into separate branch "feature/" no matter how non serious it look. I hope your changes will simplify things. Thank you! 2017-09-26 17:54 GMT+02:00 Harbs : > I’m working on refactoring this. > > Is there a reason for the null check in UIBase.createElement()? > >

Re: FlexJS element setter

I’m working on refactoring this. Is there a reason for the null check in UIBase.createElement()? Why would createElement be called if the element is already created? None of the subclasses have this null check. if (element == null) element = document.createElement('div') as WrappedHTMLEleme

Re: FlexJS element setter

I believe there are components where more than one HTMLElement is created but only one is (and can be) assigned as "element" but all have flexjs_wrapper assigned to the wrapping IUIBase. If in fact no components need a separate positioner, it is fine to remove it. But if we keep it, even as a get

Re: [DISCUSS} Fork FlexJS from Apache Flex

The address is ok but tags.json isn't found... -- Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: FlexJS element setter

@Harbs: yes on get positioner returning element. This way someone could override the getter and return something else if it suited their needs. —peter On 9/26/17, 9:25 AM, "Harbs" wrote: >I looked at MDL and I don’t see any problem there. > >I’m talking about simplifying things across the board

Re: FlexJS element setter

I looked at MDL and I don’t see any problem there. I’m talking about simplifying things across the board. I don’t see how it could effect anything. @Peter I think removing positioner might not be a bad idea, but keeping it and using it as a pointer to element is basically just as cheap. > On S

Re: FlexJS element setter

I should also have addressed "cloneNode". I keep operating in the twilight world between SWF and HTML/JS. The main guiding principle is to make it work for HTML/JS as simply as possible and then replicate it for SWF. I think since the Flash announcement, this should really be the defining principle

Re: FlexJS element setter

The original intent of positioner was to allow the element to be different. The NumericStepper was the use case. The positioner was to be the enclosing div or DisplayObjectContainer. The element was to be the input or TextField. We thought there might be more complex components that would benefit f

Re: FlexJS element setter

Hi Harbs, If you will do such changes like moving to set flexjs_wrapper in the setter of element - please make it on the separate branch. Let me test with my app whether MDL will not breaking up. I hope that we could avoid this one, even if I think that it seems to be quite reasonable to do that.

Re: FlexJS element setter

Yishay and I were working on drag/drop today and we were modifying one of the classes you wrote for generating the drag image. The code can be simplified by using cloneNode() and stuffing the results into the element. The thing is, it does not work until you assign the flexjs_wrapper to the ele

Re: FlexJS element setter

The setter for element is in HTMLElementWrapper, the super class for UIBase. The setter for flexes_wrapper is in UIBase. So if the element setter were to also set the flexjs_wrapper, it would have to be an override in UIBase to do it. At least that¹s how I understand it. Could you elaborate a litt

FlexJS element setter

Currently, setting the element of a IUIBase will not work correctly because the flexjs_wrapper is not set. This makes it error prone when there’s a need to work with the underlying DOM elements for HTML output. I cannot think of a reason why the wrapper should not be set when calling the elemen

Re: [DISCUSS} Fork FlexJS from Apache Flex

Thanks for your reply! But there is a problem, I can not open the two links in: http://people.apache.org/~pent/asdoc-flexjs/index.html Are these docs moved to another new place, so it can not be opend now? Or is it just my network problem? If the address has been updated, please tell me where it is

Re: [Discuss] Pros and Cons of Using Royale to Build Websites

Hi, when I tried to replicate an MDL web page example (from MDL official samples). I found I was at maybe 90% to get the same results with our Royale MDL library, the problems at that time was from CSS processed by Royale that was not prepared for all uses cases. About the CSS problems, most of th