I run another one [1] to align with latest commits and we will see what
happened.
[1]
https://builds.apache.org/view/E-G/view/Flex/job/FlexJS%20Pipeline/job/release0.8.0/18/
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
I see that Maven build [1] of release branch is failing.
[1]
https://builds.apache.org/view/E-G/view/Flex/job/FlexJS%20Pipeline/job/release0.8.0/17/console
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
If targets only has JSFlex, there shouldn't be any SWF compile at all.
The console should spit out what it thinks it needs to do.
Keep in mind that there are now SWCs for SWFs and SWCs for JS. Prior to
dual, there was a main SWC with SWF APIs that the compiler saw, and JS
that it substituted in
As I understand it, the compiler should just take care of differences
between JS and SWF, as long as your targets option is correct. VSCode
shouldn't need to do anything special except to pass in the correct
options.
There's nothing related to dual changes on my to-do list at this time, but
Another weird issue:
> /Users/harbs/Documents/git/PrintUI/printui-flexjs/PortedPrintUI/src/com/printui/dummy/view/Image.as(12):
> col: 15 interface method imageElement in interface IImage not implemented by
> class Image
>
> public class Image extends BinaryImage
>^
>
Josh,
VS Code is now reporting lots of errors in the Problems window. I’m guessing it
does not know how to differentiate between JS and SWF builds using dual?
Is that something on your to-do list?
Thanks,
Harbs
> On Jun 1, 2017, at 5:10 AM, Harbs wrote:
>
> Bingo.
Bingo. Thanks!
SWF output still gets all kinds of errors, but the JS output is pretty error
free. I still have some fixing up to do before I can see how well it actually
works, but at least the compiler is not complaining now.
> On Jun 1, 2017, at 4:45 AM, Josh Tynjala
The examples I see seem to use COMPILE blocks.
I’m not sure how this translates to the app level. Is there a way to define a
single method which overrides a SWF one and implements a new JS one (without
using COMPILE blocks)? That seems to me like a pretty common use case for
migrated apps.
>
Hi,
> I’m using asconfig in VSCode to compile with these settings:
> "config": "flex",
> "compilerOptions": {
> "debug": false,
> "js-output-type": "flexjs",
> "source-map": false,
> "library-path": [
> "lib"
> ],
I’ve not used VSCode but perhaps try
Try replacing the js-output-type compiler option with:
"targets": ["JSFlex"]
- Josh
On May 31, 2017 6:26 PM, "Harbs" wrote:
> I’m using asconfig in VSCode to compile with these settings:
> "config": "flex",
> "compilerOptions": {
> "debug": false,
>
In case I wasn’t clear, I’m not outputting SWF — only JS output.
> On Jun 1, 2017, at 4:26 AM, Harbs wrote:
>
> I’m using asconfig in VSCode to compile with these settings:
> "config": "flex",
> "compilerOptions": {
> "debug": false,
>
I’m using asconfig in VSCode to compile with these settings:
"config": "flex",
"compilerOptions": {
"debug": false,
"js-output-type": "flexjs",
"source-map": false,
"library-path": [
"lib"
],
> On Jun 1, 2017, at 1:04 AM, Justin Mclean
On 5/31/17, 2:38 PM, "Harbs" wrote:
>I just switched to dual and I’m getting lots of errors. These errors seem
>to be exactly what I was afraid of, and I’m not sure how to resolve
>without being restricted by naming of properties and methods.
>
>1. I’m using a mask
Not a CSS property name.
On 5/31/17, 2:49 PM, "Justin Mclean" wrote:
>HI,
>
>What the reason for removing backgroundAlpha?
>
>Thanks,
>Justin
I just switched to dual and I’m getting lots of errors. These errors seem to be
exactly what I was afraid of, and I’m not sure how to resolve without being
restricted by naming of properties and methods.
1. I’m using a mask setter and getter for images it’s now giving override
errors.
2.
Josh is right. There is no way to pass command-line args to an install
command.
What is there right now is the best way to pass args during an npm install.
Thanks,
Om
On Wed, May 31, 2017 at 9:35 AM, OmPrakash Muppirala
wrote:
> I should have something in the next 12
Yishay had some code to handle the cases where it’s not set via MXML which you
removed.
I changed his code to simply intialize the document if it was not set by MXML
like this:
//Needed if the layout is not declared using MXML
private function
I'm still working on this and ran into a couple of issues.
The flexible child layouts no longer provide a way to explicitly set a
child; instead they rely in the child's id being used to retrieve the
child from the document. Unfortunately, a layout that is not referenced in
MXML will not get its
I should have something in the next 12 hours or so.
Thanks,
Om
On May 31, 2017 8:31 AM, "Alex Harui" wrote:
Hi Om,
Command-line sounds great if you can do it. Let us know when you are done
with the NPM stuff so we can move forward with the release.
Thanks,
-Alex
Hi Om,
Command-line sounds great if you can do it. Let us know when you are done
with the NPM stuff so we can move forward with the release.
Thanks,
-Alex
On 5/30/17, 7:15 PM, "Josh Tynjala" wrote:
>I could not find a way to parse extra command line arguments with an
20 matches
Mail list logo