Hi Alex,
maybe, if you detect some pages are out-of-date, to avoid confussion, you
could move those ones to some folder that could serve as a intermediate
state before deletion?. So in this way, we could always go to that info and
reuse things as needed. What do you think?
btw, I was readiing the
I have a related question here. I can test, but if someone knows off-hand,
it’ll save some work:
How are conflicts in externs handled?
For example, Adobe’s CEP library has an RGBColor class which has four
attributes (including alpha), but the FlexJS js.swc has an RGBColor class which
is missin
Thanks Harbs, Chris and Josh for the kindly word :)
I'll try to make some more 1920x1080 wallpapers with different styles and
motivs, and post the links here to showcase.
Then we could proceed as people consider, maybe voting to see if we should
include as a downloadable asset in the website, or
Well, I’ll definitely post them to the Facebook page.
On Apr 18, 2016, at 2:18 PM, Carlos Rovira
wrote:
> Thanks Harbs, Chris and Josh for the kindly word :)
>
> I'll try to make some more 1920x1080 wallpapers with different styles and
> motivs, and post the links here to showcase.
>
> Then w
Slightly off topic, but if someone is kind enough to give you a gift, the
proper response is to say thank you and accept it. What you do after you
accept it is another story.
The Apache process of discussing if we should accept said gift is kind of a
dick move. No offence, but IMHO this behaviour
Hi Jude,
I couldn't refrain from commenting this:
1) We have a responsibility to our customers/users that we deliver stuff that
is safe to use. Safe doesn't only mean, that it works well, but also that all
legal issues have been set aside. If we were to accept anything without
checking that al
We should never just accept anything automatically. Apache is a business
that has to meet legal requirements. The PMC for each project are entrusted to
help protect the organization while looking out for the best interest for their
project. While in a perfect world we could just absorb ev
Hi,
I'm currently working on migrating the build of the framework projects in the
flex-asjs project to build with the flexjs-maven-plugin. I noticed one thing,
that most of our config files don't have a single namespace declaration. Is
this just because of lazyness, or don't we have schemas fo
There was discussion on the topic in the past. IIRC, it was a conscious
decision to not use namespaces. I don’t remember the reason.
Harbs
On Apr 18, 2016, at 3:47 PM, Christofer Dutz wrote:
> Hi,
>
>
> I'm currently working on migrating the build of the framework projects in the
> flex-asj
Very impressive!
On Mar 25, 2016, at 1:11 AM, OmPrakash Muppirala wrote:
> On Thu, Mar 24, 2016 at 12:59 PM, wrote:
>
>> under 100 errors
>>
>
> woohoo!
>
>
>>
>>
>> Project: http://git-wip-us.apache.org/repos/asf/flex-asjs/repo
>> Commit: http://git-wip-us.apache.org/repos/asf/flex-asjs
While I can understand Jude’s frustration, I do think it’s clear that we need
to properly vet donations.
I’d like to try to bring this discussion back on-topic.
I would like to see Lizhi’s code accepted. I think it’s really useful. If not
actual “core”, it’s pretty close to it.
So the question
Would be interested in a pointer to that discussion ... cause the only benefit
of leaving them away is that it makes less fuss in writing the files, but on
the downside there is a large amount of downsides:
- No tool support (IntelliJ can't help you detect things that are wrong)
- Makes writing p
I’m not sure if you were talking about the same thing, but this is the
discussion I was thinking of:
http://mail-archives.apache.org/mod_mbox/flex-dev/201511.mbox/browser
On Apr 18, 2016, at 4:29 PM, Christofer Dutz wrote:
> Would be interested in a pointer to that discussion ... cause the only
Hi,
> Slightly off topic, but if someone is kind enough to give you a gift, the
> proper response is to say thank you and accept it.
We’re willing to accept it, but as part of our PMC responibilities we do need
to know about it’s contents. I’m sure you know about he story of the Trojan
horse.:-
I think this is not what I'm talking about.
In Falcon and ASJS we have a lot of xml config files. Unfortunately most of
them (if not even none) use an XML Schema to define their content. This makes
it difficult to write tools and maintain content. So my question was:
1) Is there a schema for mani
hi 2 all,
just need concrete info to create custom flexSDK stuff with latest airSDK.
In my daily base as3 dev, I have sometime to test some features or try to
fix air regressions, e.g. 22sdk 0.97 seems to fix x86_64 ane extension in
osx, @see: https://forums.adobe.com/thread/2129529
furthermore,
The generated JavaScript always includes the full package. If they're in
different packages, there won't be a conflict.
- Josh
On Mon, Apr 18, 2016 at 3:25 AM, Harbs wrote:
> I have a related question here. I can test, but if someone knows off-hand,
> it’ll save some work:
>
> How are conflicts
On 4/18/16, 1:37 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
wrote:
>Hi Alex,
>
>maybe, if you detect some pages are out-of-date, to avoid confussion, you
>could move those ones to some folder that could serve as a intermediate
>state before deletion?. So in this way, we could alwa
On 4/18/16, 3:25 AM, "Harbs" wrote:
>I have a related question here. I can test, but if someone knows
>off-hand, it’ll save some work:
>
>How are conflicts in externs handled?
I think first-in-wins, but I'm not sure. The compiler might also throw an
error. I know for -library-path SWCs it is
On 4/18/16, 4:34 AM, "jude" wrote:
>Slightly off topic, but if someone is kind enough to give you a gift, the
>proper response is to say thank you and accept it. What you do after you
>accept it is another story.
>
>The Apache process of discussing if we should accept said gift is kind of
>a
>d
On 4/18/16, 6:24 AM, "Harbs" wrote:
>
>2. Assuming we accept it, what should the package naming be? I think
>there’s a strong case for leaving it as-is.
IMO, I would rename "flash" to "flex". I'd like our FlexJS code to not
mention Flash at all, regardless of whether there is some legal/copyri
On 4/18/16, 7:01 AM, "Christofer Dutz" wrote:
>I think this is not what I'm talking about.
>In Falcon and ASJS we have a lot of xml config files. Unfortunately most
>of them (if not even none) use an XML Schema to define their content.
>This makes it difficult to write tools and maintain conten
Jude,
First off, I am truly sorry that you had a bad experience at Apache Flex,
especially when you were trying to do good to the community by donating
something that you had put your heart and soul into.
We are all learning here. Instead of saying let's not do this at all,
perhaps you can propo
ok, good. I think mark it as you proposed is a better idea so people notice
that is old content and the new is in other location
Thanks Alex
2016-04-18 17:15 GMT+02:00 Alex Harui :
>
>
> On 4/18/16, 1:37 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>
> wrote:
>
> >Hi Alex,
> >
> >ma
On Apr 18, 2016, at 6:44 PM, Alex Harui wrote:
>
>
> On 4/18/16, 6:24 AM, "Harbs" wrote:
>>
>> 2. Assuming we accept it, what should the package naming be? I think
>> there’s a strong case for leaving it as-is.
>
> IMO, I would rename "flash" to "flex". I'd like our FlexJS code to not
> me
I’m not sure how to work this out with Alex’s response that the first one wins.
If I’m reading this correctly, I think I have a problem. The javascript does
not have qualified class names. RGBColor is just RGBColor in Javascript, and
not com.adobe.RGBColor, so the Javascript will not run as it s
Well, all HTML APIs are supported, so RGBColor, for example should work.
On Apr 18, 2016, at 6:24 PM, Alex Harui wrote:
> The key question for you is whether you need js.swc in the project that
> uses your new CSInterface.swc. There might need to be a CEF.swc subset
> from js.swc that represent
On 4/18/16, 11:01 AM, "Harbs" wrote:
>
>On Apr 18, 2016, at 6:44 PM, Alex Harui wrote:
>
>>
>>
>> On 4/18/16, 6:24 AM, "Harbs" wrote:
>>>
>>> 2. Assuming we accept it, what should the package naming be? I think
>>> there’s a strong case for leaving it as-is.
>>
>> IMO, I would rename "fla
On 4/18/16, 11:16 AM, "Harbs" wrote:
>Well, all HTML APIs are supported, so RGBColor, for example should work.
So Adobe is effectively overriding RGBColor and expecting CEF to ignore
extra fields on it?
-Alex
Good question. I’m not really sure.
On Apr 18, 2016, at 9:21 PM, Alex Harui wrote:
>
>
> On 4/18/16, 11:16 AM, "Harbs" wrote:
>
>> Well, all HTML APIs are supported, so RGBColor, for example should work.
>
> So Adobe is effectively overriding RGBColor and expecting CEF to ignore
> extra fie
My point is that if someone is using a swf-first workflow, they can’t just use
flex.* packages.
If we do some magic depending on whether it’s JS or AS, that might work.
On Apr 18, 2016, at 9:17 PM, Alex Harui wrote:
>
>
> On 4/18/16, 11:01 AM, "Harbs" wrote:
>
>>
>> On Apr 18, 2016, at 6:
On 4/18/16, 11:23 AM, "Harbs" wrote:
>Good question. I’m not really sure.
It is technically legal to do that in JS, and when libraries do that, that
makes it harder to emulate in AS because they are not really doing
object-oriented support with sealed classes. To allow it would require
more c
If the only reason to not use the flash namespace is because it has a
pejorative term to some ignorant media types and competing web developers
than that's not a good case.
If someone doesn't want to use FlexJS because they see the term "flash"
somewhere then they can go find another tool.
But if
I appreciate it. I think just rewording it might fix some issues. An
example response I would have liked to hear would have been,
We appreciate the offer you are making to donate or maintain your project
at Apache Flex. We know you've worked hard on your project and know your
desire is for it to b
On 4/18/16, 3:04 PM, "jude" wrote:
>
>So the components Tink donated years ago IIRC weren't completely finished
>(from what I read at the time they were still in progress) or that he may
>not even be part of the community anymore to maintain it. I still would
>have liked to have his and others
On 4/18/16, 2:29 PM, "jude" wrote:
>If the only reason to not use the flash namespace is because it has a
>pejorative term to some ignorant media types and competing web developers
>than that's not a good case.
For me, it is about expectations. If you claim to have a
flash.display.Sprite, fol
FWIW, I created this organization some time back: https://github.com/flex-extras
The idea was to have a place to put code that does not strictly belong on ASF
repos.
Harbs
On Apr 19, 2016, at 1:16 AM, Alex Harui wrote:
>
>
> On 4/18/16, 3:04 PM, "jude" wrote:
>
>>
>> So the components Ti
everytime I read "flex-extras", my brain thinks Flextras instead lol.
-Mark
On Mon, Apr 18, 2016 at 6:44 PM, Harbs wrote:
> FWIW, I created this organization some time back:
> https://github.com/flex-extras
>
> The idea was to have a place to put code that does not strictly belong on
> ASF rep
no need some fork.no need extends,it just the final.
now the code and get a.swf and a.js from one code.
and can get starling.js.
if chang the package name.
we can not get a.swf,and starling.js
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Discuss-Acce
I vote for keeping the package names same, i.e. flash.*.* The proposed
package name swapping seems to confusing. And could be error-prone.
We already have package names like jquery.*.* and createjs.*.* where we are
using the same package names for consistency. Are we proposing to change
all tho
yes,the spriteflexjs not the flexjs core,
it just a framework baseon flexjs.
it not the only drawing apis.
it is just help some "old" *.as code(swf),get the *.js
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Discuss-Accept-donation-of-drawing-APIs-tp52429
if somebody from apache do some code of spriteflexjs will good thing
it missing a lot of function
movieclip,textfiled multiline ,etc,now
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Discuss-Accept-donation-of-drawing-APIs-tp52429p52489.html
Sent from th
Warning: I can't decide if I'm just playing devil's advocate or am truly
concerned about this, but below are some worst-case scenarios, which may
need to be taken with a grain of salt.
My latest proposal is that we rename packages from "flash.* to "webgl.*"
and teach the compiler how to map thing
43 matches
Mail list logo
