I"m not sure I understand the question. This looks like a dump of the
main Application. What does that have to do with ADG and
XMLListCollection?
On 12/21/15, 11:00 PM, "dhwanishah85" wrote:
>Hello Alex,
>
>I am getting result after sending following command to fdb:
>send("print this.");
>
>an
Hello Alex,
I am getting result after sending following command to fdb:
send("print this.");
and i am getting following snippet of result in return:
data = "$2 = this = [Object 156627105, class='TestFlexAIR']
$alpha = 1 (0x1)
$blendMode = "normal"
$blendShader = [Setter 1582,
name='http://www.
>The release manager would take care of it.
Makes sense ;-)
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/4-15-0-Update-FontAwesome-icon-lib-to-4-5-tp50737p50761.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
On Mon, Dec 21, 2015 at 10:41 PM, OK wrote:
> >-Fork off of the 4.15.0 branch on github
> >...
> Thanks for help!
> I'll do this in the evening.
>
> >However the release branch can be merged back into develop or vice versa
> if
> needed.
> Who takes care of it?
>
The release manager would take c
>-Fork off of the 4.15.0 branch on github
>...
Thanks for help!
I'll do this in the evening.
>However the release branch can be merged back into develop or vice versa if
needed.
Who takes care of it?
Olaf
--
View this message in context:
http://apache-flex-development.247.n4.nabble.co
Github user ok-at-github closed the pull request at:
https://github.com/apache/flex-sdk/pull/38
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Okay, Justin responded at the same time as I sent mine.
Here are the correct instructions:
- Fork off of the 4.15.0 branch on github
- Clone the fork onto your local computer
- Apply the fixes in your local computer (no need to create a new branch)
- Commit and push your changes to your fork on g
I am guessing that the new branch + merging caused this issue
Here is the most straightforward way I would recommend:
- Fork off of the dev branch on github
- Clone the fork onto your local computer
- Apply the fixes in your local computer (no need to create a new branch)
- Commit and push your c
Hi,
If you want it in the release i'd make the pull request on the 4.15 branch.
However the release branch can be merged back into develop or vice versa if
needed.
Thanks,
Justin
Github user ok-at-github commented on the pull request:
https://github.com/apache/flex-sdk/pull/38#issuecomment-166530832
I've just seen that my pull request contains 12 commits instead of 2.
Seems that other commits from other users are included in this pull request
cause I target
I've just seen that my pull request contains 12 commits instead of 2.
Seems that other commits from other users are included in my pull request
cause I target the 4.15.0 branch for merging.
Should I target the develop branch instead of the 4.15.0 branch?
Olaf
--
View this message in context:
It looks like someone turned on the download cache and the default
directory is not writeable. So the answer may be for you to set the
Installer download cache to a writeable folder.
The default appears to be the ApplicationStorageDirectory. Seems like
that should be writeable. I don't know if
yes,your are right.
but i am said,
it is will lost of a lot of great lib(starling,away3d).
use this lib,must do a lot of rebuild.
but if the flexjs,support the cdd,it will good for as3 lib.
helpful this same code,gen as and js.
--
View this message in context:
http://apache-flex-development
So, here`s a solution, but I think we have to review the installer.
When I try to copy the file app/Contents/Resources/tmp/air/mac/
download/19.0/AdobeAIRSDK.tbz2
This folder app/Contents/Resources/tmp/air/mac/download/... needs user
permission manually to make it work.
After doing that problem
flex-sdk_release-candidate - Build #138 - Successful
Changes since last build:
No changes
For more information, check the console output at
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/138/.
Here's part of the error
check-sum:
Validating download: /Users/mikolajdebowski/Desktop/4.14.1 (AIR
19)/in/AdobeAIRSDK.tbz2
put-in-cache:
[copy] Copying 1 file to /Applications/Apache Flex/Apache Flex SDK
Installer.app/Contents/Resources/tmp/air/mac/download/19.0/AdobeAIRSDK.tbz2
fileWriteRe
For some reason, the installer can't write to some folder. Right-click
and enable verbose logging to get more details on which folder.
On 12/21/15, 4:42 PM, "Igor Costa" wrote:
>Hi there Guys
>
>I`m getting this error when I try to install flex sdk on a mac with Flex
>sdk installer.
>
>Installe
Hi there Guys
I`m getting this error when I try to install flex sdk on a mac with Flex
sdk installer.
Installer version 3.2.0 (mac)
Using Locale: en_PL
Fetched the SDK download mirror URL from the CGI.
SDK version Apache Flex SDK 4.14.1
AIR version 19.0
Flash Player version 19.0
Creating Apache F
I've just created a pull request that contains the update to FontAwesome 4.5.
I'm not sure if I've done it all right. If somebody could merge it I'll test
it by using te latest dev build.
Thanks,
Olaf
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/4-15-0-
GitHub user ok-at-github opened a pull request:
https://github.com/apache/flex-sdk/pull/38
Update to FontAwesome 4.5
Currently only FontAwesome 4.2 is included in the SDK.
This pull request contains the updated font itself and the updated
AwesomeUtils.as.
If somebody co
Well garbage is relative. I didn't mean it in a derogatory way, only that
the original authors were the ones that could understand it.
As far as FlaconJX, I wrote that as a prototype based off of my prior
experience with AST traversing and the visitor pattern. That was almost 3
years ago now so as
OK. I think we have a plan.
My goal for the holiday break is to fix as many bugs as I can. If I get
through the ones I know about, then I'll start on this. I'll probably
just do the Core and HTML folders and get your ok before doing the rest.
I'll also look at the BlazeDS ant script.
Thanks,
@Harbs,
I don't know enough about Git and branching to know if this is the right
way to "archive" stuff before deleting, but I would think that branch
would need special handling after it is created because any attempt to
merge with that branch might result in the deletion of that code.
@Mark & M
Hi Fabrice,
Apache projects are run by volunteers. Feel free to start your own survey
via this mailing list. Personally, I'm not worried about AIR since with
FlexJS we are trying to remove our hard dependencies on AIR. But a
similar wish list for Flex and FlexJS would be interesting.
-Alex
On
On 12/20/15, 1:36 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
wrote:
>
>Should we be trying to copy falcon-flexTasks.jar instead?
Yes, makes sense. Not sure what that will break though.
-Alex
That's what I would do, though I hate git with a fair level of passion :-)
Tom
On 21/12/15 13:40, OK wrote:
Is it the right way to fork the github develop branch, create a new brunch,
make the changes and create a pull request for the 4.15.0 branch?
Hi,
it would be nice if we could update the great FontAwesome icon lib to the
recent version 4.5.
To do this it seems that the .otf file itself has to be replaced and the
AwesomeUtils.as has to be modified:
flex-sdk/frameworks/projects/flatspark/src/flatspark/assets/fonts/awesome/FontAwesome.otf
f
Yup, I agree, it doesn't really need to be deleted but it needs to be so
far away from FalconJX that a common dev wouldn't mistake it for anything
other than archived history.
The code is garbage, another reason why FalconJX even exists, I hated that
code with a passion. :)
Mike
On Mon, Dec 21,
Might as well make an archive folder that's generic and we can put anything
else we want to keep but don't want in the main source areas.
-Mark
I would suggest putting it in a branch called falconjs_archive (or something
like that to make it clear that it’s archived code) and removing it from
develop branch. That way if there’s ever any reason to use code from there, it
should be easy to pull it in.
On Dec 21, 2015, at 10:26 AM, Alex H
+1
that kind of code makes people confused (so it did for me in the past). So
better delete it and if someone needs he/she can download from the history
2015-12-21 10:22 GMT+01:00 Christofer Dutz :
> +1
>
> I think I lost track how often, during my maven-deploy efforts I processed
> that stuff a
+1
I think I lost track how often, during my maven-deploy efforts I processed that
stuff and was a little frustrated after finding out it's actually not used.
I would generally suggest to move dead and experimental code to some place you
don't confuse it with real parts of Falcon or FlexJS (es
>>src/main/resources/compile-asjs-config.xml and
>>src/main/resources/compile-config.xml are build scripts too and should
>>reside in the root of the module alongside the build.xml.
>
>These -config files aren't Ant scripts, but rather more like
>flex-config.xml. Should they still go in src/main/r
I thought FB only showed the this pointer and variables local to the
function.
IIRC, for any object, FB only shows its immediate properties and leaves
the bigger and slower "inherited properties" for on-demand.
-Alex
On 12/21/15, 12:07 AM, "dhwanishah85" wrote:
>Hello Alex,
>
>Thanks for your
Hello Alex,
Thanks for your response.
I need to update variables which are getting changed during debug process.
Like how it is working in Flash builder, same way I want my debug view to
get updated with changing values without hurting the execution time of "f6".
I dont get any useful info in in
Hi,
It has been a long time since I've looked at the FalconJS code that was
donated by Adobe. The FalconJX code seems to be working fine. The
FalconJS code seems to be confusing some people who are trying to help
find bugs in FalconJX, so I think it might be time to just delete the
whole FalconJ
On 12/19/15, 3:37 AM, "Christofer Dutz" wrote:
>Ok .. so the build.xml shouldn't be in src/test/flex as ist's not
>test-code, but the ant script running the tests ... it should be in the
>root of the module.
That build.xml is the Ant script for the tests. It gets called by the
root build.xml
That thread seems to be about Flash Builder compatibility. This is just
Ant stuff, isn't it? I don't know if folks explicitly list which SWCs
they want or just point to the whole set of FlexUnit swcs. If the answer
is to explicitly list the SWCs, that should be straightforward to do.
-Alex
On
Do you want local variables or variables in scope?
Local variables are available as "info local" and parameters are available
via "info stack". I don't know of any easy way to get all of the scope
variables. You might want to just get a few and use scrolling to get more.
-Alex
On 12/20/15, 11
> I don't know FlexUnit very well. Is it normal to have both the as3 and
> flex version in the library-path so their definitions compete or is it
> normal to only have one or the other? I'm trying to understand whether
> the current situation where both are in the library-path is the default
> an
Please file a JIRA.
Thanks,
-Alex
On 12/20/15, 8:33 PM, "lizhi" wrote:
>parseint
>parsefloat
>
>addeventlistener
>
>use
>
>parseint("10") error
>
>must
>parseint("10",10);
>
>
>
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/flexjs-0-6-js-defargs
>-tp50
41 matches
Mail list logo