You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by sankar <sa...@gmail.com> on 2016/12/05 10:26:20 UTC
Why there are same files exists in multiple places?
I noticed there are files which exists multiple time with almost no changes.
i.e. DataItemRenderer.
This file exists multiple time in source folders:
1.
https://github.com/apache/flex-asjs/blob/develop/frameworks/projects/Basic/src/main/flex/org/apache/flex/html/supportClasses/DataItemRenderer.as
2.
https://github.com/apache/flex-asjs/blob/develop/frameworks/projects/HTML/src/main/flex/org/apache/flex/html/supportClasses/DataItemRenderer.as
I noticed that the latter link only has a line difference:
> $sprite.addChild(background);
Now what I'm having problem to understand,
1. Why the 'Basic' and 'HTML' folders when holding almost same files?
2. When we call DataItemRenderer in our codes, I noticed it referenced from
/frameworks/libs/HTML.swc - does that mean the swc contains #2 URL file?
3. If above is not, then which file actually imports to our codes?
Thanks!
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Why-there-are-same-files-exists-in-multiple-places-tp56983.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: Why there are same files exists in multiple places?
Posted by sankar <sa...@gmail.com>.
Carlos Rovira-3 wrote
> Hi Sankar
>
> 1. Why the 'Basic' and 'HTML' folders when holding almost same files?
>>
>
> Basic is a deprecated project. When Alex and Harbs made the sprite
> refactor
> it was disconnected from build. I think Alex is working on it and he said
> rest of us could operate with Core, HTML and the rest of projects. So
> don't
> take account on Basic project
>
>
>> 2. When we call DataItemRenderer in our codes, I noticed it referenced
>> from
>> /frameworks/libs/HTML.swc - does that mean the swc contains #2 URL file?
>>
>
> If I understand right, yes, DataItemRenderer comes from HTML.swc (is
> contained in that library swc)
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
Hi Peter, thank you for responding this. This clear my confusion. I was
hoping to have you in discussion in another important subject -
data-binding, and was seeking your view. Can you please take a look in
http://apache-flex-development.2333347.n4.nabble.com/FlexJX-Falcon-Binding-support-fixes-improvements-td54632.html
the last few comments (?) Alex advised that you may have something to say on
this.
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Why-same-files-exists-in-multiple-places-tp56983p56997.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: Why there are same files exists in multiple places?
Posted by Carlos Rovira <ca...@apache.org>.
2016-12-05 16:41 GMT+01:00 Peter Ent <pe...@adobe.com>:
> Maybe we should have HTML just be the <js:DIV>, <js:H1>, etc. components
> that were recently introduced. Have HTML5 product be additional
> HTML5-specific components, and leave Basic to be the original set.
>
> This way you would layer as needed: if you wanted a static-ish HTML page
> that had dynamics created with ActionScript, then you would use the HTML
> project. You could then add in jQuery or whatever to that.
>
> If you wanted to introduce layouts and more complex UI elements, you would
> add in Basic. If you didn't need DIV and H1 at all, then you'd just use
> Basic. I think sorting these into more useful functional groups would help.
>
> ‹
> Peter Ent
> Adobe Systems/Apache Flex Project
>
>
That sounds good to me
--
Carlos Rovira
http://about.me/carlosrovira
Re: Why there are same files exists in multiple places?
Posted by Carlos Rovira <ca...@apache.org>.
2016-12-05 17:17 GMT+01:00 Alex Harui <ah...@adobe.com>:
> We could just fill HTML and HTML5 with the direct wrappers of elements.
> Currently we are using more Flex-familiar names like Container and Label.
> If we can think of a better SWC name for those things that's fine. The
> point of HTML and Basic was that Harbs was finding it easier to work on
> his app with a library that wrapped all Sprites. I want to make sure we
> don't have to wrap all Sprites on the SWF side and am making compiler
> changes to allow for that. Hopefully then we can remove the wrapped
> Sprites, but it is a good exercise to have both just to make sure we don't
> have too many assumptions in the other SWCs. You never know when there
> might be a third platform besides SWF and JS that we want to target.
>
>
If this project is successful, we should expect many additional platforms.
If you see what happen to other projects out there like haxe, it's normal
that people coming would want maybe iOS or Android or whatever and that
people comes to implement this addition.
--
Carlos Rovira
http://about.me/carlosrovira
Re: Why there are same files exists in multiple places?
Posted by Alex Harui <ah...@adobe.com>.
We could just fill HTML and HTML5 with the direct wrappers of elements.
Currently we are using more Flex-familiar names like Container and Label.
If we can think of a better SWC name for those things that's fine. The
point of HTML and Basic was that Harbs was finding it easier to work on
his app with a library that wrapped all Sprites. I want to make sure we
don't have to wrap all Sprites on the SWF side and am making compiler
changes to allow for that. Hopefully then we can remove the wrapped
Sprites, but it is a good exercise to have both just to make sure we don't
have too many assumptions in the other SWCs. You never know when there
might be a third platform besides SWF and JS that we want to target.
-Alex
On 12/5/16, 7:41 AM, "Peter Ent" <pe...@adobe.com> wrote:
>Maybe we should have HTML just be the <js:DIV>, <js:H1>, etc. components
>that were recently introduced. Have HTML5 product be additional
>HTML5-specific components, and leave Basic to be the original set.
>
>This way you would layer as needed: if you wanted a static-ish HTML page
>that had dynamics created with ActionScript, then you would use the HTML
>project. You could then add in jQuery or whatever to that.
>
>If you wanted to introduce layouts and more complex UI elements, you would
>add in Basic. If you didn't need DIV and H1 at all, then you'd just use
>Basic. I think sorting these into more useful functional groups would
>help.
>
>‹
>Peter Ent
>Adobe Systems/Apache Flex Project
>
>On 12/5/16, 6:26 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
><carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>
>>Hi Sankar
>>
>>1. Why the 'Basic' and 'HTML' folders when holding almost same files?
>>>
>>
>>Basic is a deprecated project. When Alex and Harbs made the sprite
>>refactor
>>it was disconnected from build. I think Alex is working on it and he said
>>rest of us could operate with Core, HTML and the rest of projects. So
>>don't
>>take account on Basic project
>>
>>
>>> 2. When we call DataItemRenderer in our codes, I noticed it referenced
>>>from
>>> /frameworks/libs/HTML.swc - does that mean the swc contains #2 URL
>>>file?
>>>
>>
>>If I understand right, yes, DataItemRenderer comes from HTML.swc (is
>>contained in that library swc)
>>
>>--
>>Carlos Rovira
>>http://about.me/carlosrovira
>
Re: Why there are same files exists in multiple places?
Posted by Peter Ent <pe...@adobe.com>.
Maybe we should have HTML just be the <js:DIV>, <js:H1>, etc. components
that were recently introduced. Have HTML5 product be additional
HTML5-specific components, and leave Basic to be the original set.
This way you would layer as needed: if you wanted a static-ish HTML page
that had dynamics created with ActionScript, then you would use the HTML
project. You could then add in jQuery or whatever to that.
If you wanted to introduce layouts and more complex UI elements, you would
add in Basic. If you didn't need DIV and H1 at all, then you'd just use
Basic. I think sorting these into more useful functional groups would help.
‹
Peter Ent
Adobe Systems/Apache Flex Project
On 12/5/16, 6:26 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>Hi Sankar
>
>1. Why the 'Basic' and 'HTML' folders when holding almost same files?
>>
>
>Basic is a deprecated project. When Alex and Harbs made the sprite
>refactor
>it was disconnected from build. I think Alex is working on it and he said
>rest of us could operate with Core, HTML and the rest of projects. So
>don't
>take account on Basic project
>
>
>> 2. When we call DataItemRenderer in our codes, I noticed it referenced
>>from
>> /frameworks/libs/HTML.swc - does that mean the swc contains #2 URL file?
>>
>
>If I understand right, yes, DataItemRenderer comes from HTML.swc (is
>contained in that library swc)
>
>--
>Carlos Rovira
>http://about.me/carlosrovira
Re: Why there are same files exists in multiple places?
Posted by Carlos Rovira <ca...@apache.org>.
Hi Sankar
1. Why the 'Basic' and 'HTML' folders when holding almost same files?
>
Basic is a deprecated project. When Alex and Harbs made the sprite refactor
it was disconnected from build. I think Alex is working on it and he said
rest of us could operate with Core, HTML and the rest of projects. So don't
take account on Basic project
> 2. When we call DataItemRenderer in our codes, I noticed it referenced from
> /frameworks/libs/HTML.swc - does that mean the swc contains #2 URL file?
>
If I understand right, yes, DataItemRenderer comes from HTML.swc (is
contained in that library swc)
--
Carlos Rovira
http://about.me/carlosrovira