You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Carlos Rovira <ca...@apache.org> on 2018/02/24 17:35:00 UTC
How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries
Hi,
the final "environment" problem I've is that SVGs that I put in
src/main/resources/assets are not in
final VividBlueTheme-0.9.2-SNAPSHOT-js.swc
I see it copied to target/classes as usual in maven build, but are not part
of the theme swc file.
it's something missing in the theme implementation? or maybe something I
need to setup in pom.xml?
thanks
--
Carlos Rovira
http://about.me/carlosrovira
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries
Posted by Carlos Rovira <ca...@apache.org>.
Hi Justin,
I think could be ok to have js and swf folders, ...although maybe the most
important thing in structure is the where to copy resources so final
outputs could grab only one copy of them and JS, SWF, WEBASM, and others
techs to come can grab it.
Maybe we should discuss this to find the right structure in output folder
so we get only one copy of resources and the best access to them by JS,
SWF, WEBASM and future outputs
thanks
2018-02-25 0:50 GMT+01:00 Justin Mclean <ju...@classsoftware.com>:
> Hi,
>
> See also this related issue I mentioned some time back. [1] It seems
> inconsistent to be handling swf one way (copies the resources) and JS
> another (it doesn’t).
>
> Thanks,.
> Justin
>
> 1. https://lists.apache.org/thread.html/25d0aaa1bfd73501b363fd2a11fdb4
> f00f3fa7f243758b753ff8d4c4@%3Cusers.royale.apache.org%3E
--
Carlos Rovira
http://about.me/carlosrovira
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc
libraries
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
See also this related issue I mentioned some time back. [1] It seems inconsistent to be handling swf one way (copies the resources) and JS another (it doesn’t).
Thanks,.
Justin
1. https://lists.apache.org/thread.html/25d0aaa1bfd73501b363fd2a11fdb4f00f3fa7f243758b753ff8d4c4@%3Cusers.royale.apache.org%3E
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries
Posted by Carlos Rovira <ca...@apache.org>.
Hi Justin,
we're using resources when using maven. In fact I use it to bundle
resources in theme SWC.
The problem we're discussing now is about for Apps to retrieve "assets"
from inside the theme SWC.
2018-02-25 11:04 GMT+01:00 Justin Mclean <ju...@me.com>:
> Hi,
>
> > OK, just be certain, the compiler will only do this for a folder
> > specifically named "assets". Not every file in the SWC or other folder
> > names. And the destination folder will be "assets" as well.
>
> By default maven looks for “resources” why not support that as well?
>
> Thanks,
> Justin
--
Carlos Rovira
http://about.me/carlosrovira
Re: How to get assets (svg,
png,...) inside *-js.swc and *-swf.swc libraries
Posted by Justin Mclean <ju...@me.com>.
Hi,
> OK, just be certain, the compiler will only do this for a folder
> specifically named "assets". Not every file in the SWC or other folder
> names. And the destination folder will be "assets" as well.
By default maven looks for “resources” why not support that as well?
Thanks,
Justin
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries
Posted by Carlos Rovira <ca...@apache.org>.
ok Alex, maybe not necessary right now. If we start to get some decent
output tied to images in SWF, that could change
thanks
2018-02-28 23:14 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>
>
> On 2/28/18, 1:52 PM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
> <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>
> >Hi Alex,
> >you're right, maybe this deserves more thinking,...in the actual approach,
> >I think that compiler should copy the same assets folder to target so SWF
> >can access it right?
>
> We could do that. Some folks don't think we should copy assets as part of
> the compiler, and that the publisher should be a separate thing. Whatever
> we do here will take time, so I'm probably not going to spend any time on
> it right now. Lots of other bigger fish to fry. At least folks can copy
> from bin/js-debug if they want to. I would recommend copying resources in
> your Maven and Ant scripts for now.
>
> Thanks,
> -Alex
> >
> >2018-02-28 18:13 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> >
> >> We could do that if we get enough complaints, but the nice thing about
> >>the
> >> way it currently works is that the output folder is all-inclusive. You
> >> can deploy (after a Maven build) the target/javascript/bin/js-release
> >> folder and your assets will be in there, and the URLs will be
> >> URL("assets/MyAsset.jpg"). In your proposal, the user has to remember
> >>to
> >> copy the assets folder as well, and the URLs will look like
> >> URL("../../../../assets/MyAsset.jpg") and the layout on the web server
> >> will have to have the same deep folder structure.
> >>
> >> Are you seeing long build times? We could just choose to not overwrite
> >> existing files. That might save time.
> >>
> >> My 2 cents,
> >> -Alex
> >>
> >> On 2/28/18, 8:40 AM, "carlos.rovira@gmail.com on behalf of Carlos
> >>Rovira"
> >> <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
> >>
> >> >Hi, don't know if I understand right since all the things about the
> >> >compiler are beyond my scope, but what I'm suggesting is to realocate
> >> >resources. But don't know if this sounds crazy or not. In this way we
> >>can
> >> >support current outputs (JS and SWF) but prepare for future outputs
> >> >(WEBASM, iOS, Android,...)
> >> >
> >> >so it will end as is:
> >> >
> >> >
> >> >target
> >> > |
> >> > ------ assets (inside this folder all output like css, svg, png,...)
> >> > |
> >> > ------- swf (in this folder the .swf (s) app + modules, but for this
> >>all
> >> >should search for resources in "../assets" for all assets not @Embeded
> >>in
> >> >swf
> >> > |
> >> > ------- js (in this folder will go html and all js files that again
> >> >should look for resources in "../assets"
> >> > |
> >> > -------- webasm
> >> > |
> >> > -------- iOS
> >> > |
> >> > -------- Android
> >> > |
> >> > -------- whatever other output we want to implement
> >> >
> >> >if not I understand that each output should provide its own assets
> >>folder,
> >> >and this will end wasting resources for duplication (n times depending
> >>on
> >> >how many outputs we want to get) and wasting time and CPU process..
> >> >
> >> >does this make sense?
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >2018-02-27 18:11 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> >> >
> >> >> Hi Jason,
> >> >>
> >> >> Actually, I didn't know that. I'm not a compiler guy. Someone else
> >> >>wrote
> >> >> the key pieces. I could see that way back, a compiler might have
> >> >>written
> >> >> out intermediate information for the next step, like having a
> >>separate
> >> >> linker that links the object files. But I don't think I've seen (or
> >> >>maybe
> >> >> I just haven't used) options to output extra information for
> >> >> post-processing after the final output. We could certainly output
> >>extra
> >> >> information, but then that information needs to be parsed again to be
> >> >>used
> >> >> by the publisher.
> >> >>
> >> >> If that's the way folks want to go, all we need is a volunteer to
> >>make
> >> >>it
> >> >> happen. Currently, the publisher does not need the AST so it might
> >>even
> >> >> be possible to write the publisher in ActionScript. But that might
> >>make
> >> >> it harder to integrate with Maven.
> >> >>
> >> >> What do others think?
> >> >> -Alex
> >> >>
> >> >> On 2/27/18, 8:54 AM, "Jason Guild" <ja...@alaska.gov> wrote:
> >> >>
> >> >> >Alex:
> >> >> >
> >> >> >As you probably know, compilers in the old days were implemented in
> >>a
> >> >> >series of stages as separate processes due to memory size
> >>limitations.
> >> >> >The output from the previous stage was fed to the next stage as
> >> >> >compilation proceeded until object files were produced.
> >> >> >
> >> >> >Maybe it makes sense for the compiler to output everything the
> >> >>publisher
> >> >> >needs (final ASTs and/or other metadata, etc) when it exits.
> >> >> >Then a separate publisher process could optionally use that output
> >>to
> >> >>do
> >> >> >all the expected publish-type things without being intermingled with
> >> >>the
> >> >> >compiler itself.
> >> >> >
> >> >> >The publisher would probably be simpler to understand on its own and
> >> >> >maybe more people could be involved with it.
> >> >> >
> >> >> >Jason
> >> >> >
> >> >> >On 2/26/2018 8:49 PM, Alex Harui wrote:
> >> >> >> The only
> >> >> >> downside I've thought of is just that it is weird to have a
> >>publisher
> >> >> >> attached to the compiler. I don't think most compilers have a
> >> >> >>publisher.
> >> >> >
> >> >> >--
> >> >> >Jason Guild
> >> >> >Analyst/Programmer V
> >> >> >State of Alaska - Department of Transportation & Public Facilities
> >> >> >Information Systems and Services Division
> >> >> >820 E. 15th Ave.
> >> >> >Anchorage, Alaska 99501
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >> >--
> >> >Carlos Rovira
> >> >https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Fabout.me%2
> >> >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%
> >> 7C3da558b1a44a46dfc41b08d5
> >> >7ec9fc08%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> 7C636554328342487363&s
> >> >data=aduUVLnj5Q8FYqR9KJ6WZeEoLN1GqSVVbalBmhAwZSA%3D&reserved=0
> >>
> >>
> >
> >
> >--
> >Carlos Rovira
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%2
> >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%
> 7C43a5a6f66b7b4869aa6c08d5
> >7ef597aa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636554515653880312&s
> >data=%2F90VveLbQkI3GLiIaKQbwXWjhrtKilTmxVkoAN0gaLI%3D&reserved=0
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc
libraries
Posted by Alex Harui <ah...@adobe.com.INVALID>.
On 2/28/18, 1:52 PM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>Hi Alex,
>you're right, maybe this deserves more thinking,...in the actual approach,
>I think that compiler should copy the same assets folder to target so SWF
>can access it right?
We could do that. Some folks don't think we should copy assets as part of
the compiler, and that the publisher should be a separate thing. Whatever
we do here will take time, so I'm probably not going to spend any time on
it right now. Lots of other bigger fish to fry. At least folks can copy
from bin/js-debug if they want to. I would recommend copying resources in
your Maven and Ant scripts for now.
Thanks,
-Alex
>
>2018-02-28 18:13 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>
>> We could do that if we get enough complaints, but the nice thing about
>>the
>> way it currently works is that the output folder is all-inclusive. You
>> can deploy (after a Maven build) the target/javascript/bin/js-release
>> folder and your assets will be in there, and the URLs will be
>> URL("assets/MyAsset.jpg"). In your proposal, the user has to remember
>>to
>> copy the assets folder as well, and the URLs will look like
>> URL("../../../../assets/MyAsset.jpg") and the layout on the web server
>> will have to have the same deep folder structure.
>>
>> Are you seeing long build times? We could just choose to not overwrite
>> existing files. That might save time.
>>
>> My 2 cents,
>> -Alex
>>
>> On 2/28/18, 8:40 AM, "carlos.rovira@gmail.com on behalf of Carlos
>>Rovira"
>> <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>>
>> >Hi, don't know if I understand right since all the things about the
>> >compiler are beyond my scope, but what I'm suggesting is to realocate
>> >resources. But don't know if this sounds crazy or not. In this way we
>>can
>> >support current outputs (JS and SWF) but prepare for future outputs
>> >(WEBASM, iOS, Android,...)
>> >
>> >so it will end as is:
>> >
>> >
>> >target
>> > |
>> > ------ assets (inside this folder all output like css, svg, png,...)
>> > |
>> > ------- swf (in this folder the .swf (s) app + modules, but for this
>>all
>> >should search for resources in "../assets" for all assets not @Embeded
>>in
>> >swf
>> > |
>> > ------- js (in this folder will go html and all js files that again
>> >should look for resources in "../assets"
>> > |
>> > -------- webasm
>> > |
>> > -------- iOS
>> > |
>> > -------- Android
>> > |
>> > -------- whatever other output we want to implement
>> >
>> >if not I understand that each output should provide its own assets
>>folder,
>> >and this will end wasting resources for duplication (n times depending
>>on
>> >how many outputs we want to get) and wasting time and CPU process..
>> >
>> >does this make sense?
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >2018-02-27 18:11 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>> >
>> >> Hi Jason,
>> >>
>> >> Actually, I didn't know that. I'm not a compiler guy. Someone else
>> >>wrote
>> >> the key pieces. I could see that way back, a compiler might have
>> >>written
>> >> out intermediate information for the next step, like having a
>>separate
>> >> linker that links the object files. But I don't think I've seen (or
>> >>maybe
>> >> I just haven't used) options to output extra information for
>> >> post-processing after the final output. We could certainly output
>>extra
>> >> information, but then that information needs to be parsed again to be
>> >>used
>> >> by the publisher.
>> >>
>> >> If that's the way folks want to go, all we need is a volunteer to
>>make
>> >>it
>> >> happen. Currently, the publisher does not need the AST so it might
>>even
>> >> be possible to write the publisher in ActionScript. But that might
>>make
>> >> it harder to integrate with Maven.
>> >>
>> >> What do others think?
>> >> -Alex
>> >>
>> >> On 2/27/18, 8:54 AM, "Jason Guild" <ja...@alaska.gov> wrote:
>> >>
>> >> >Alex:
>> >> >
>> >> >As you probably know, compilers in the old days were implemented in
>>a
>> >> >series of stages as separate processes due to memory size
>>limitations.
>> >> >The output from the previous stage was fed to the next stage as
>> >> >compilation proceeded until object files were produced.
>> >> >
>> >> >Maybe it makes sense for the compiler to output everything the
>> >>publisher
>> >> >needs (final ASTs and/or other metadata, etc) when it exits.
>> >> >Then a separate publisher process could optionally use that output
>>to
>> >>do
>> >> >all the expected publish-type things without being intermingled with
>> >>the
>> >> >compiler itself.
>> >> >
>> >> >The publisher would probably be simpler to understand on its own and
>> >> >maybe more people could be involved with it.
>> >> >
>> >> >Jason
>> >> >
>> >> >On 2/26/2018 8:49 PM, Alex Harui wrote:
>> >> >> The only
>> >> >> downside I've thought of is just that it is weird to have a
>>publisher
>> >> >> attached to the compiler. I don't think most compilers have a
>> >> >>publisher.
>> >> >
>> >> >--
>> >> >Jason Guild
>> >> >Analyst/Programmer V
>> >> >State of Alaska - Department of Transportation & Public Facilities
>> >> >Information Systems and Services Division
>> >> >820 E. 15th Ave.
>> >> >Anchorage, Alaska 99501
>> >> >
>> >>
>> >>
>> >
>> >
>> >--
>> >Carlos Rovira
>> >https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fabout.me%2
>> >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%
>> 7C3da558b1a44a46dfc41b08d5
>> >7ec9fc08%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> 7C636554328342487363&s
>> >data=aduUVLnj5Q8FYqR9KJ6WZeEoLN1GqSVVbalBmhAwZSA%3D&reserved=0
>>
>>
>
>
>--
>Carlos Rovira
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2
>Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C43a5a6f66b7b4869aa6c08d5
>7ef597aa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636554515653880312&s
>data=%2F90VveLbQkI3GLiIaKQbwXWjhrtKilTmxVkoAN0gaLI%3D&reserved=0
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex,
you're right, maybe this deserves more thinking,...in the actual approach,
I think that compiler should copy the same assets folder to target so SWF
can access it right?
2018-02-28 18:13 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> We could do that if we get enough complaints, but the nice thing about the
> way it currently works is that the output folder is all-inclusive. You
> can deploy (after a Maven build) the target/javascript/bin/js-release
> folder and your assets will be in there, and the URLs will be
> URL("assets/MyAsset.jpg"). In your proposal, the user has to remember to
> copy the assets folder as well, and the URLs will look like
> URL("../../../../assets/MyAsset.jpg") and the layout on the web server
> will have to have the same deep folder structure.
>
> Are you seeing long build times? We could just choose to not overwrite
> existing files. That might save time.
>
> My 2 cents,
> -Alex
>
> On 2/28/18, 8:40 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
> <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>
> >Hi, don't know if I understand right since all the things about the
> >compiler are beyond my scope, but what I'm suggesting is to realocate
> >resources. But don't know if this sounds crazy or not. In this way we can
> >support current outputs (JS and SWF) but prepare for future outputs
> >(WEBASM, iOS, Android,...)
> >
> >so it will end as is:
> >
> >
> >target
> > |
> > ------ assets (inside this folder all output like css, svg, png,...)
> > |
> > ------- swf (in this folder the .swf (s) app + modules, but for this all
> >should search for resources in "../assets" for all assets not @Embeded in
> >swf
> > |
> > ------- js (in this folder will go html and all js files that again
> >should look for resources in "../assets"
> > |
> > -------- webasm
> > |
> > -------- iOS
> > |
> > -------- Android
> > |
> > -------- whatever other output we want to implement
> >
> >if not I understand that each output should provide its own assets folder,
> >and this will end wasting resources for duplication (n times depending on
> >how many outputs we want to get) and wasting time and CPU process..
> >
> >does this make sense?
> >
> >
> >
> >
> >
> >
> >
> >
> >2018-02-27 18:11 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> >
> >> Hi Jason,
> >>
> >> Actually, I didn't know that. I'm not a compiler guy. Someone else
> >>wrote
> >> the key pieces. I could see that way back, a compiler might have
> >>written
> >> out intermediate information for the next step, like having a separate
> >> linker that links the object files. But I don't think I've seen (or
> >>maybe
> >> I just haven't used) options to output extra information for
> >> post-processing after the final output. We could certainly output extra
> >> information, but then that information needs to be parsed again to be
> >>used
> >> by the publisher.
> >>
> >> If that's the way folks want to go, all we need is a volunteer to make
> >>it
> >> happen. Currently, the publisher does not need the AST so it might even
> >> be possible to write the publisher in ActionScript. But that might make
> >> it harder to integrate with Maven.
> >>
> >> What do others think?
> >> -Alex
> >>
> >> On 2/27/18, 8:54 AM, "Jason Guild" <ja...@alaska.gov> wrote:
> >>
> >> >Alex:
> >> >
> >> >As you probably know, compilers in the old days were implemented in a
> >> >series of stages as separate processes due to memory size limitations.
> >> >The output from the previous stage was fed to the next stage as
> >> >compilation proceeded until object files were produced.
> >> >
> >> >Maybe it makes sense for the compiler to output everything the
> >>publisher
> >> >needs (final ASTs and/or other metadata, etc) when it exits.
> >> >Then a separate publisher process could optionally use that output to
> >>do
> >> >all the expected publish-type things without being intermingled with
> >>the
> >> >compiler itself.
> >> >
> >> >The publisher would probably be simpler to understand on its own and
> >> >maybe more people could be involved with it.
> >> >
> >> >Jason
> >> >
> >> >On 2/26/2018 8:49 PM, Alex Harui wrote:
> >> >> The only
> >> >> downside I've thought of is just that it is weird to have a publisher
> >> >> attached to the compiler. I don't think most compilers have a
> >> >>publisher.
> >> >
> >> >--
> >> >Jason Guild
> >> >Analyst/Programmer V
> >> >State of Alaska - Department of Transportation & Public Facilities
> >> >Information Systems and Services Division
> >> >820 E. 15th Ave.
> >> >Anchorage, Alaska 99501
> >> >
> >>
> >>
> >
> >
> >--
> >Carlos Rovira
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%2
> >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%
> 7C3da558b1a44a46dfc41b08d5
> >7ec9fc08%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636554328342487363&s
> >data=aduUVLnj5Q8FYqR9KJ6WZeEoLN1GqSVVbalBmhAwZSA%3D&reserved=0
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc
libraries
Posted by Alex Harui <ah...@adobe.com.INVALID>.
We could do that if we get enough complaints, but the nice thing about the
way it currently works is that the output folder is all-inclusive. You
can deploy (after a Maven build) the target/javascript/bin/js-release
folder and your assets will be in there, and the URLs will be
URL("assets/MyAsset.jpg"). In your proposal, the user has to remember to
copy the assets folder as well, and the URLs will look like
URL("../../../../assets/MyAsset.jpg") and the layout on the web server
will have to have the same deep folder structure.
Are you seeing long build times? We could just choose to not overwrite
existing files. That might save time.
My 2 cents,
-Alex
On 2/28/18, 8:40 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>Hi, don't know if I understand right since all the things about the
>compiler are beyond my scope, but what I'm suggesting is to realocate
>resources. But don't know if this sounds crazy or not. In this way we can
>support current outputs (JS and SWF) but prepare for future outputs
>(WEBASM, iOS, Android,...)
>
>so it will end as is:
>
>
>target
> |
> ------ assets (inside this folder all output like css, svg, png,...)
> |
> ------- swf (in this folder the .swf (s) app + modules, but for this all
>should search for resources in "../assets" for all assets not @Embeded in
>swf
> |
> ------- js (in this folder will go html and all js files that again
>should look for resources in "../assets"
> |
> -------- webasm
> |
> -------- iOS
> |
> -------- Android
> |
> -------- whatever other output we want to implement
>
>if not I understand that each output should provide its own assets folder,
>and this will end wasting resources for duplication (n times depending on
>how many outputs we want to get) and wasting time and CPU process..
>
>does this make sense?
>
>
>
>
>
>
>
>
>2018-02-27 18:11 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>
>> Hi Jason,
>>
>> Actually, I didn't know that. I'm not a compiler guy. Someone else
>>wrote
>> the key pieces. I could see that way back, a compiler might have
>>written
>> out intermediate information for the next step, like having a separate
>> linker that links the object files. But I don't think I've seen (or
>>maybe
>> I just haven't used) options to output extra information for
>> post-processing after the final output. We could certainly output extra
>> information, but then that information needs to be parsed again to be
>>used
>> by the publisher.
>>
>> If that's the way folks want to go, all we need is a volunteer to make
>>it
>> happen. Currently, the publisher does not need the AST so it might even
>> be possible to write the publisher in ActionScript. But that might make
>> it harder to integrate with Maven.
>>
>> What do others think?
>> -Alex
>>
>> On 2/27/18, 8:54 AM, "Jason Guild" <ja...@alaska.gov> wrote:
>>
>> >Alex:
>> >
>> >As you probably know, compilers in the old days were implemented in a
>> >series of stages as separate processes due to memory size limitations.
>> >The output from the previous stage was fed to the next stage as
>> >compilation proceeded until object files were produced.
>> >
>> >Maybe it makes sense for the compiler to output everything the
>>publisher
>> >needs (final ASTs and/or other metadata, etc) when it exits.
>> >Then a separate publisher process could optionally use that output to
>>do
>> >all the expected publish-type things without being intermingled with
>>the
>> >compiler itself.
>> >
>> >The publisher would probably be simpler to understand on its own and
>> >maybe more people could be involved with it.
>> >
>> >Jason
>> >
>> >On 2/26/2018 8:49 PM, Alex Harui wrote:
>> >> The only
>> >> downside I've thought of is just that it is weird to have a publisher
>> >> attached to the compiler. I don't think most compilers have a
>> >>publisher.
>> >
>> >--
>> >Jason Guild
>> >Analyst/Programmer V
>> >State of Alaska - Department of Transportation & Public Facilities
>> >Information Systems and Services Division
>> >820 E. 15th Ave.
>> >Anchorage, Alaska 99501
>> >
>>
>>
>
>
>--
>Carlos Rovira
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2
>Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C3da558b1a44a46dfc41b08d5
>7ec9fc08%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636554328342487363&s
>data=aduUVLnj5Q8FYqR9KJ6WZeEoLN1GqSVVbalBmhAwZSA%3D&reserved=0
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries
Posted by Carlos Rovira <ca...@apache.org>.
Hi, don't know if I understand right since all the things about the
compiler are beyond my scope, but what I'm suggesting is to realocate
resources. But don't know if this sounds crazy or not. In this way we can
support current outputs (JS and SWF) but prepare for future outputs
(WEBASM, iOS, Android,...)
so it will end as is:
target
|
------ assets (inside this folder all output like css, svg, png,...)
|
------- swf (in this folder the .swf (s) app + modules, but for this all
should search for resources in "../assets" for all assets not @Embeded in
swf
|
------- js (in this folder will go html and all js files that again
should look for resources in "../assets"
|
-------- webasm
|
-------- iOS
|
-------- Android
|
-------- whatever other output we want to implement
if not I understand that each output should provide its own assets folder,
and this will end wasting resources for duplication (n times depending on
how many outputs we want to get) and wasting time and CPU process..
does this make sense?
2018-02-27 18:11 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> Hi Jason,
>
> Actually, I didn't know that. I'm not a compiler guy. Someone else wrote
> the key pieces. I could see that way back, a compiler might have written
> out intermediate information for the next step, like having a separate
> linker that links the object files. But I don't think I've seen (or maybe
> I just haven't used) options to output extra information for
> post-processing after the final output. We could certainly output extra
> information, but then that information needs to be parsed again to be used
> by the publisher.
>
> If that's the way folks want to go, all we need is a volunteer to make it
> happen. Currently, the publisher does not need the AST so it might even
> be possible to write the publisher in ActionScript. But that might make
> it harder to integrate with Maven.
>
> What do others think?
> -Alex
>
> On 2/27/18, 8:54 AM, "Jason Guild" <ja...@alaska.gov> wrote:
>
> >Alex:
> >
> >As you probably know, compilers in the old days were implemented in a
> >series of stages as separate processes due to memory size limitations.
> >The output from the previous stage was fed to the next stage as
> >compilation proceeded until object files were produced.
> >
> >Maybe it makes sense for the compiler to output everything the publisher
> >needs (final ASTs and/or other metadata, etc) when it exits.
> >Then a separate publisher process could optionally use that output to do
> >all the expected publish-type things without being intermingled with the
> >compiler itself.
> >
> >The publisher would probably be simpler to understand on its own and
> >maybe more people could be involved with it.
> >
> >Jason
> >
> >On 2/26/2018 8:49 PM, Alex Harui wrote:
> >> The only
> >> downside I've thought of is just that it is weird to have a publisher
> >> attached to the compiler. I don't think most compilers have a
> >>publisher.
> >
> >--
> >Jason Guild
> >Analyst/Programmer V
> >State of Alaska - Department of Transportation & Public Facilities
> >Information Systems and Services Division
> >820 E. 15th Ave.
> >Anchorage, Alaska 99501
> >
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc
libraries
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Hi Jason,
Actually, I didn't know that. I'm not a compiler guy. Someone else wrote
the key pieces. I could see that way back, a compiler might have written
out intermediate information for the next step, like having a separate
linker that links the object files. But I don't think I've seen (or maybe
I just haven't used) options to output extra information for
post-processing after the final output. We could certainly output extra
information, but then that information needs to be parsed again to be used
by the publisher.
If that's the way folks want to go, all we need is a volunteer to make it
happen. Currently, the publisher does not need the AST so it might even
be possible to write the publisher in ActionScript. But that might make
it harder to integrate with Maven.
What do others think?
-Alex
On 2/27/18, 8:54 AM, "Jason Guild" <ja...@alaska.gov> wrote:
>Alex:
>
>As you probably know, compilers in the old days were implemented in a
>series of stages as separate processes due to memory size limitations.
>The output from the previous stage was fed to the next stage as
>compilation proceeded until object files were produced.
>
>Maybe it makes sense for the compiler to output everything the publisher
>needs (final ASTs and/or other metadata, etc) when it exits.
>Then a separate publisher process could optionally use that output to do
>all the expected publish-type things without being intermingled with the
>compiler itself.
>
>The publisher would probably be simpler to understand on its own and
>maybe more people could be involved with it.
>
>Jason
>
>On 2/26/2018 8:49 PM, Alex Harui wrote:
>> The only
>> downside I've thought of is just that it is weird to have a publisher
>> attached to the compiler. I don't think most compilers have a
>>publisher.
>
>--
>Jason Guild
>Analyst/Programmer V
>State of Alaska - Department of Transportation & Public Facilities
>Information Systems and Services Division
>820 E. 15th Ave.
>Anchorage, Alaska 99501
>
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc
libraries
Posted by Jason Guild <ja...@alaska.gov>.
Alex:
As you probably know, compilers in the old days were implemented in a
series of stages as separate processes due to memory size limitations.
The output from the previous stage was fed to the next stage as
compilation proceeded until object files were produced.
Maybe it makes sense for the compiler to output everything the publisher
needs (final ASTs and/or other metadata, etc) when it exits.
Then a separate publisher process could optionally use that output to do
all the expected publish-type things without being intermingled with the
compiler itself.
The publisher would probably be simpler to understand on its own and
maybe more people could be involved with it.
Jason
On 2/26/2018 8:49 PM, Alex Harui wrote:
> The only
> downside I've thought of is just that it is weird to have a publisher
> attached to the compiler. I don't think most compilers have a publisher.
--
Jason Guild
Analyst/Programmer V
State of Alaska - Department of Transportation & Public Facilities
Information Systems and Services Division
820 E. 15th Ave.
Anchorage, Alaska 99501
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc
libraries
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Forking SVG to its own thread. Thoughts on the asset question below.
On 2/26/18, 1:45 PM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>Hi Alex,
>
>many thanks, just test and this is working fine! :)
>
>One more thing to think about now that we get to this point. In order for
>SWF and JS versions to share the same assets...should we move swf to the
>same folder than "assets"?...or maybe put assets (and maybe CSS) directly
>on "target" folder? So any output could grab a the same assets folder (or
>in other words, to avoid copying 2, 3 or more versions of the same files)
The JS compiler is setup as a bundle with a Compiler and a Publisher. The
compiler outputs a single .js file per .as or .mxml file and then if no
errors are found the Publisher copies the goog files from Google Closure
Library, copies assets from the file system and now, copies assets from
SWC files. It also outputs the final CSS file and handles the HTML
template.
I've been pondering the notion of wrapping the SWF compiler in a Publisher
as well. It would be set up the same way as the JS compiler. If the SWF
compile complete, the Publisher goes to work. A SWF publisher would copy
assets from the file system and SWCs and would know how to fix up the
SWFObject template and AIR -app.xml templates. The upside of a publisher
getting a hand-off from the compiler is that the publisher often wants to
know information discovered during the compile, such as the width and
height of the Application if it is fixed size, and also a background
color. Right now, there is an Ant task that can fix up the SWFObject
template and FlashBuilder knows how as well. I assume the other IDEs know
how to fix up the SWFObject template as well. But building that into the
Publisher would save some configuration hassle for the user. The only
downside I've thought of is just that it is weird to have a publisher
attached to the compiler. I don't think most compilers have a publisher.
Really, though, for now, I'm not sure how essential a SWF-side publisher
really would be. I'm not sure how many people are going to run the SWF
version and how painful it would be to just use Maven or Ant and copy the
asset folder. I think even FB has a post-compile step that could
potentially be used to copy things from bin/js-debug to bin-debug.
Of course, I could be wrong...
-Alex
>
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex,
many thanks, just test and this is working fine! :)
One more thing to think about now that we get to this point. In order for
SWF and JS versions to share the same assets...should we move swf to the
same folder than "assets"?...or maybe put assets (and maybe CSS) directly
on "target" folder? So any output could grab a the same assets folder (or
in other words, to avoid copying 2, 3 or more versions of the same files)
I'm thinking in make JS and SWF version and try to match both, but for this
I need to know how I can load the SVG from Flash. Right now is referenced
in CSS, but don't know if SWF version can handle as well SVGs in CSS. If is
possible that would be great since will make the creation of themes more
easy
Thanks
Ca
2018-02-26 19:36 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> OK, I just pushed a change for this in vivid-ui-set branch. It seemed to
> work for me.
>
> HTH,
> -Alex
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
>
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc
libraries
Posted by Alex Harui <ah...@adobe.com.INVALID>.
OK, I just pushed a change for this in vivid-ui-set branch. It seemed to
work for me.
HTH,
-Alex
On 2/25/18, 4:23 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>Hi Alex
>I think this is perfect
>Go with it
>Thanks!
>
>El El dom, 25 feb 2018 a las 9:37, Alex Harui <ah...@adobe.com.invalid>
>escribió:
>
>> OK, just be certain, the compiler will only do this for a folder
>> specifically named "assets". Not every file in the SWC or other folder
>> names. And the destination folder will be "assets" as well.
>>
>> Everybody ok with that for now?
>> -Alex
>>
>> On 2/24/18, 11:44 PM, "carlos.rovira@gmail.com on behalf of Carlos
>>Rovira"
>> <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>>
>> >Hi Alex,
>> >
>> >2018-02-25 0:12 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>> >>
>> >>
>> >> Any objections to copying EVERY file out of the assets folder?
>> >>
>> >
>> >I think that's completely fine. We should think that a SWC theme should
>> >have only files that are completely needed by the SWF. If not is a
>>task of
>> >the creator to clean it for production. In Flex all was copied and
>> >developers need to do (or not ) maintenance task of removing what's not
>> >needed anymore.
>> >
>> >But the compiler must do that, since the other option seems like a bug
>>to
>> >me.
>> >
>> >thanks
>> >
>> >
>> >--
>> >Carlos Rovira
>> >
>>
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
>>2
>> >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com
>> %7C750dc1559e0d475e935608d5
>>
>>>7c23a2ac%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636551414881836753
>>>&s
>> >data=g64PoGq2CMoNxS8xL64fL6L77FMFaIOGwWkkn1w2wJk%3D&reserved=0
>>
>> --
>Carlos Rovira
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2
>Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C18b9a91b3de74b5bcd3108d5
>7c4a9a28%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636551582253339763&s
>data=3Xrz9OKJOTPoNuL%2FeDWQqXLEfHmEzBBrrk%2BE5%2F1jip8%3D&reserved=0
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex
I think this is perfect
Go with it
Thanks!
El El dom, 25 feb 2018 a las 9:37, Alex Harui <ah...@adobe.com.invalid>
escribió:
> OK, just be certain, the compiler will only do this for a folder
> specifically named "assets". Not every file in the SWC or other folder
> names. And the destination folder will be "assets" as well.
>
> Everybody ok with that for now?
> -Alex
>
> On 2/24/18, 11:44 PM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
> <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>
> >Hi Alex,
> >
> >2018-02-25 0:12 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> >>
> >>
> >> Any objections to copying EVERY file out of the assets folder?
> >>
> >
> >I think that's completely fine. We should think that a SWC theme should
> >have only files that are completely needed by the SWF. If not is a task of
> >the creator to clean it for production. In Flex all was copied and
> >developers need to do (or not ) maintenance task of removing what's not
> >needed anymore.
> >
> >But the compiler must do that, since the other option seems like a bug to
> >me.
> >
> >thanks
> >
> >
> >--
> >Carlos Rovira
> >
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2
> >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com
> %7C750dc1559e0d475e935608d5
> >7c23a2ac%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636551414881836753&s
> >data=g64PoGq2CMoNxS8xL64fL6L77FMFaIOGwWkkn1w2wJk%3D&reserved=0
>
> --
Carlos Rovira
http://about.me/carlosrovira
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc
libraries
Posted by Alex Harui <ah...@adobe.com.INVALID>.
OK, just be certain, the compiler will only do this for a folder
specifically named "assets". Not every file in the SWC or other folder
names. And the destination folder will be "assets" as well.
Everybody ok with that for now?
-Alex
On 2/24/18, 11:44 PM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>Hi Alex,
>
>2018-02-25 0:12 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>>
>>
>> Any objections to copying EVERY file out of the assets folder?
>>
>
>I think that's completely fine. We should think that a SWC theme should
>have only files that are completely needed by the SWF. If not is a task of
>the creator to clean it for production. In Flex all was copied and
>developers need to do (or not ) maintenance task of removing what's not
>needed anymore.
>
>But the compiler must do that, since the other option seems like a bug to
>me.
>
>thanks
>
>
>--
>Carlos Rovira
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2
>Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C750dc1559e0d475e935608d5
>7c23a2ac%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636551414881836753&s
>data=g64PoGq2CMoNxS8xL64fL6L77FMFaIOGwWkkn1w2wJk%3D&reserved=0
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex,
2018-02-25 0:12 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>
>
> Any objections to copying EVERY file out of the assets folder?
>
I think that's completely fine. We should think that a SWC theme should
have only files that are completely needed by the SWF. If not is a task of
the creator to clean it for production. In Flex all was copied and
developers need to do (or not ) maintenance task of removing what's not
needed anymore.
But the compiler must do that, since the other option seems like a bug to
me.
thanks
--
Carlos Rovira
http://about.me/carlosrovira
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc
libraries
Posted by Alex Harui <ah...@adobe.com.INVALID>.
It is true that copying assets is not normally the job of the compiler,
but ignoring SWF output for now, the JS compiler certainly copies lots of
files around.
It should be simple to have the JS compiler copy EVERY asset out of EVERY
theme swc. Harder would be figuring out exactly which assets were needed
by reading the final CSS file.
Any objections to copying EVERY file out of the assets folder?
-Alex
On 2/24/18, 12:44 PM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>Hi Gabe,
>
>since we're talking about a theme feature, it will be very strange that
>the
>implementation of that feature will left things unfinished. I think in
>this
>case is part of the compiler responsibility to provide to the final app
>with the assets the theme needs for its use. I'm talking from a conceptual
>point of view. In the end, users will not understand that the theme only
>manage CSS files.
>
>or at least that's how I understand it.
>
>Carlos
>
>
>
>2018-02-24 21:07 GMT+01:00 Gabe Harbs <ha...@gmail.com>:
>
>> Copying is generally not done by the compiler itself. It’s usually
>>handled
>> by a compiler script or tooling.
>>
>> > On Feb 24, 2018, at 8:53 PM, Carlos Rovira <ca...@apache.org>
>> wrote:
>> >
>> > Hi Alex,
>> >
>> > now the SWCs has all files needed, but when compile VividExample, the
>> > assets are not copied to VividExample target folder.
>> > How this is done?
>> >
>> > Thanks
>> >
>> > Carlos
>> >
>> >
>> >
>> > 2018-02-24 19:48 GMT+01:00 Carlos Rovira
>><carlos.rovira@codeoscopic.com
>> <ma...@codeoscopic.com>>:
>> >
>> >> I get it with:
>> >>
>> >> <include-file>
>> >> <name>assets/*</name>
>> >> <path>../src/main/resources/assets/*</path>
>> >> </include-file>
>> >>
>> >> Thanks!
>> >>
>> >> Carlos
>> >>
>> >>
>> >>
>> >> 2018-02-24 19:28 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>> >>
>> >>> I think any assets need to be listed in the <include-files> in the
>> pom.xml
>> >>> (and for Ant, the src/main/config/compile*.xml files).
>> >>> AFAIK, there is no automatic including. I believe you can use
>> wildcards
>> >>> in the <include-files>.
>> >>>
>> >>> -Alex
>> >>>
>> >>> On 2/24/18, 9:35 AM, "carlos.rovira@gmail.com on behalf of Carlos
>> Rovira"
>> >>> <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org>
>>wrote:
>> >>>
>> >>>> Hi,
>> >>>>
>> >>>> the final "environment" problem I've is that SVGs that I put in
>> >>>> src/main/resources/assets are not in
>> >>>> final VividBlueTheme-0.9.2-SNAPSHOT-js.swc
>> >>>>
>> >>>> I see it copied to target/classes as usual in maven build, but are
>>not
>> >>>> part
>> >>>> of the theme swc file.
>> >>>>
>> >>>> it's something missing in the theme implementation? or maybe
>> something I
>> >>>> need to setup in pom.xml?
>> >>>>
>> >>>>
>> >>>> thanks
>> >>>>
>> >>>> --
>> >>>> Carlos Rovira
>> >>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%
>> >>> 2F%2Fabout.me%2
>> >>>> Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C973b4725a
>> >>> eaf4542d16308d5
>> >>>> 7bacfdd8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63655
>> >>> 0905283794125&s
>> >>>>
>>data=GeImt6g%2FONQJO8aKdkb%2BR8LgspIJ4jimlwrweM%2BCV8M%3D&reserved=0
>> >>>
>> >>>
>> >>
>> >>
>> >> --
>> >>
>> >>
>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.code
>>oscopic.com&data=02%7C01%7Caharui%40adobe.com%7Ccfc781eb803e4e6e379908d57
>>bc76d85%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636551018854655510&s
>>data=UcSVQjR2NGihdeCRBzYyn0yL2QzPnMmDbeNh%2FIQ2Cd8%3D&reserved=0>
>> >>
>> >> Carlos Rovira
>> >>
>> >> Director General
>> >>
>> >> M: +34 607 22 60 05 <607%2022%2060%2005>
>> >>
>> >>
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>>scopic.com&data=02%7C01%7Caharui%40adobe.com%7Ccfc781eb803e4e6e379908d57b
>>c76d85%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636551018854655510&sd
>>ata=UcSVQjR2NGihdeCRBzYyn0yL2QzPnMmDbeNh%2FIQ2Cd8%3D&reserved=0
>> >>
>> >>
>> >> Conócenos en 1 minuto!
>><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.
>>es%2F%23video&data=02%7C01%7Caharui%40adobe.com%7Ccfc781eb803e4e6e379908d
>>57bc76d85%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636551018854655510
>>&sdata=fMcxQzFpFfEkjVvLkysxHKBDiEj8QJkwFaY%2F2Z%2BelDg%3D&reserved=0>
>> >>
>> >>
>> >> Este mensaje se dirige exclusivamente a su destinatario y puede
>>contener
>> >> información privilegiada o confidencial. Si ha recibido este mensaje
>>por
>> >> error, le rogamos que nos lo comunique inmediatamente por esta misma
>> vía y
>> >> proceda a su destrucción.
>> >>
>> >> De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>> >> comunicamos que sus datos forman parte de un fichero cuyo
>>responsable es
>> >> CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la
>> >> prestación del servicio o información solicitados, teniendo usted
>> derecho
>> >> de acceso, rectificación, cancelación y oposición de sus datos
>> dirigiéndose
>> >> a nuestras oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la
>> >> documentación necesaria.
>> >>
>> >>
>> >
>> >
>> > --
>> > Carlos Rovira
>> >
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
>>2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Ccfc781eb803e4e6e379908
>>d57bc76d85%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63655101885465551
>>0&sdata=FH63GlfMgFzaIZA4jTKSCaW3RkZg75CAL1Qeac3EmWY%3D&reserved=0
>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me
>>%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Ccfc781eb803e4e6e37990
>>8d57bc76d85%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365510188546555
>>10&sdata=FH63GlfMgFzaIZA4jTKSCaW3RkZg75CAL1Qeac3EmWY%3D&reserved=0>
>>
>
>
>
>--
>Carlos Rovira
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2
>Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Ccfc781eb803e4e6e379908d5
>7bc76d85%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636551018854655510&s
>data=FH63GlfMgFzaIZA4jTKSCaW3RkZg75CAL1Qeac3EmWY%3D&reserved=0
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries
Posted by Carlos Rovira <ca...@apache.org>.
Hi Gabe,
since we're talking about a theme feature, it will be very strange that the
implementation of that feature will left things unfinished. I think in this
case is part of the compiler responsibility to provide to the final app
with the assets the theme needs for its use. I'm talking from a conceptual
point of view. In the end, users will not understand that the theme only
manage CSS files.
or at least that's how I understand it.
Carlos
2018-02-24 21:07 GMT+01:00 Gabe Harbs <ha...@gmail.com>:
> Copying is generally not done by the compiler itself. It’s usually handled
> by a compiler script or tooling.
>
> > On Feb 24, 2018, at 8:53 PM, Carlos Rovira <ca...@apache.org>
> wrote:
> >
> > Hi Alex,
> >
> > now the SWCs has all files needed, but when compile VividExample, the
> > assets are not copied to VividExample target folder.
> > How this is done?
> >
> > Thanks
> >
> > Carlos
> >
> >
> >
> > 2018-02-24 19:48 GMT+01:00 Carlos Rovira <carlos.rovira@codeoscopic.com
> <ma...@codeoscopic.com>>:
> >
> >> I get it with:
> >>
> >> <include-file>
> >> <name>assets/*</name>
> >> <path>../src/main/resources/assets/*</path>
> >> </include-file>
> >>
> >> Thanks!
> >>
> >> Carlos
> >>
> >>
> >>
> >> 2018-02-24 19:28 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> >>
> >>> I think any assets need to be listed in the <include-files> in the
> pom.xml
> >>> (and for Ant, the src/main/config/compile*.xml files).
> >>> AFAIK, there is no automatic including. I believe you can use
> wildcards
> >>> in the <include-files>.
> >>>
> >>> -Alex
> >>>
> >>> On 2/24/18, 9:35 AM, "carlos.rovira@gmail.com on behalf of Carlos
> Rovira"
> >>> <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> the final "environment" problem I've is that SVGs that I put in
> >>>> src/main/resources/assets are not in
> >>>> final VividBlueTheme-0.9.2-SNAPSHOT-js.swc
> >>>>
> >>>> I see it copied to target/classes as usual in maven build, but are not
> >>>> part
> >>>> of the theme swc file.
> >>>>
> >>>> it's something missing in the theme implementation? or maybe
> something I
> >>>> need to setup in pom.xml?
> >>>>
> >>>>
> >>>> thanks
> >>>>
> >>>> --
> >>>> Carlos Rovira
> >>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%
> >>> 2F%2Fabout.me%2
> >>>> Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C973b4725a
> >>> eaf4542d16308d5
> >>>> 7bacfdd8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63655
> >>> 0905283794125&s
> >>>> data=GeImt6g%2FONQJO8aKdkb%2BR8LgspIJ4jimlwrweM%2BCV8M%3D&reserved=0
> >>>
> >>>
> >>
> >>
> >> --
> >>
> >> <http://www.codeoscopic.com>
> >>
> >> Carlos Rovira
> >>
> >> Director General
> >>
> >> M: +34 607 22 60 05 <607%2022%2060%2005>
> >>
> >> http://www.codeoscopic.com
> >>
> >>
> >> Conócenos en 1 minuto! <https://avant2.es/#video>
> >>
> >>
> >> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> >> información privilegiada o confidencial. Si ha recibido este mensaje por
> >> error, le rogamos que nos lo comunique inmediatamente por esta misma
> vía y
> >> proceda a su destrucción.
> >>
> >> De la vigente Ley Orgánica de Protección de Datos (15/1999), le
> >> comunicamos que sus datos forman parte de un fichero cuyo responsable es
> >> CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la
> >> prestación del servicio o información solicitados, teniendo usted
> derecho
> >> de acceso, rectificación, cancelación y oposición de sus datos
> dirigiéndose
> >> a nuestras oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la
> >> documentación necesaria.
> >>
> >>
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira <http://about.me/carlosrovira>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc
libraries
Posted by Gabe Harbs <ha...@gmail.com>.
Copying is generally not done by the compiler itself. It’s usually handled by a compiler script or tooling.
> On Feb 24, 2018, at 8:53 PM, Carlos Rovira <ca...@apache.org> wrote:
>
> Hi Alex,
>
> now the SWCs has all files needed, but when compile VividExample, the
> assets are not copied to VividExample target folder.
> How this is done?
>
> Thanks
>
> Carlos
>
>
>
> 2018-02-24 19:48 GMT+01:00 Carlos Rovira <carlos.rovira@codeoscopic.com <ma...@codeoscopic.com>>:
>
>> I get it with:
>>
>> <include-file>
>> <name>assets/*</name>
>> <path>../src/main/resources/assets/*</path>
>> </include-file>
>>
>> Thanks!
>>
>> Carlos
>>
>>
>>
>> 2018-02-24 19:28 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>>
>>> I think any assets need to be listed in the <include-files> in the pom.xml
>>> (and for Ant, the src/main/config/compile*.xml files).
>>> AFAIK, there is no automatic including. I believe you can use wildcards
>>> in the <include-files>.
>>>
>>> -Alex
>>>
>>> On 2/24/18, 9:35 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
>>> <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>>>
>>>> Hi,
>>>>
>>>> the final "environment" problem I've is that SVGs that I put in
>>>> src/main/resources/assets are not in
>>>> final VividBlueTheme-0.9.2-SNAPSHOT-js.swc
>>>>
>>>> I see it copied to target/classes as usual in maven build, but are not
>>>> part
>>>> of the theme swc file.
>>>>
>>>> it's something missing in the theme implementation? or maybe something I
>>>> need to setup in pom.xml?
>>>>
>>>>
>>>> thanks
>>>>
>>>> --
>>>> Carlos Rovira
>>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%
>>> 2F%2Fabout.me%2
>>>> Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C973b4725a
>>> eaf4542d16308d5
>>>> 7bacfdd8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63655
>>> 0905283794125&s
>>>> data=GeImt6g%2FONQJO8aKdkb%2BR8LgspIJ4jimlwrweM%2BCV8M%3D&reserved=0
>>>
>>>
>>
>>
>> --
>>
>> <http://www.codeoscopic.com>
>>
>> Carlos Rovira
>>
>> Director General
>>
>> M: +34 607 22 60 05 <607%2022%2060%2005>
>>
>> http://www.codeoscopic.com
>>
>>
>> Conócenos en 1 minuto! <https://avant2.es/#video>
>>
>>
>> Este mensaje se dirige exclusivamente a su destinatario y puede contener
>> información privilegiada o confidencial. Si ha recibido este mensaje por
>> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>> proceda a su destrucción.
>>
>> De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>> comunicamos que sus datos forman parte de un fichero cuyo responsable es
>> CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la
>> prestación del servicio o información solicitados, teniendo usted derecho
>> de acceso, rectificación, cancelación y oposición de sus datos dirigiéndose
>> a nuestras oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la
>> documentación necesaria.
>>
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira <http://about.me/carlosrovira>
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex,
now the SWCs has all files needed, but when compile VividExample, the
assets are not copied to VividExample target folder.
How this is done?
Thanks
Carlos
2018-02-24 19:48 GMT+01:00 Carlos Rovira <ca...@codeoscopic.com>:
> I get it with:
>
> <include-file>
> <name>assets/*</name>
> <path>../src/main/resources/assets/*</path>
> </include-file>
>
> Thanks!
>
> Carlos
>
>
>
> 2018-02-24 19:28 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>
>> I think any assets need to be listed in the <include-files> in the pom.xml
>> (and for Ant, the src/main/config/compile*.xml files).
>> AFAIK, there is no automatic including. I believe you can use wildcards
>> in the <include-files>.
>>
>> -Alex
>>
>> On 2/24/18, 9:35 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
>> <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>>
>> >Hi,
>> >
>> >the final "environment" problem I've is that SVGs that I put in
>> >src/main/resources/assets are not in
>> >final VividBlueTheme-0.9.2-SNAPSHOT-js.swc
>> >
>> >I see it copied to target/classes as usual in maven build, but are not
>> >part
>> >of the theme swc file.
>> >
>> >it's something missing in the theme implementation? or maybe something I
>> >need to setup in pom.xml?
>> >
>> >
>> >thanks
>> >
>> >--
>> >Carlos Rovira
>> >https://na01.safelinks.protection.outlook.com/?url=http%3A%
>> 2F%2Fabout.me%2
>> >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C973b4725a
>> eaf4542d16308d5
>> >7bacfdd8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63655
>> 0905283794125&s
>> >data=GeImt6g%2FONQJO8aKdkb%2BR8LgspIJ4jimlwrweM%2BCV8M%3D&reserved=0
>>
>>
>
>
> --
>
> <http://www.codeoscopic.com>
>
> Carlos Rovira
>
> Director General
>
> M: +34 607 22 60 05 <607%2022%2060%2005>
>
> http://www.codeoscopic.com
>
>
> Conócenos en 1 minuto! <https://avant2.es/#video>
>
>
> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> información privilegiada o confidencial. Si ha recibido este mensaje por
> error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> proceda a su destrucción.
>
> De la vigente Ley Orgánica de Protección de Datos (15/1999), le
> comunicamos que sus datos forman parte de un fichero cuyo responsable es
> CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la
> prestación del servicio o información solicitados, teniendo usted derecho
> de acceso, rectificación, cancelación y oposición de sus datos dirigiéndose
> a nuestras oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la
> documentación necesaria.
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries
Posted by Carlos Rovira <ca...@codeoscopic.com>.
I get it with:
<include-file>
<name>assets/*</name>
<path>../src/main/resources/assets/*</path>
</include-file>
Thanks!
Carlos
2018-02-24 19:28 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> I think any assets need to be listed in the <include-files> in the pom.xml
> (and for Ant, the src/main/config/compile*.xml files).
> AFAIK, there is no automatic including. I believe you can use wildcards
> in the <include-files>.
>
> -Alex
>
> On 2/24/18, 9:35 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
> <carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>
> >Hi,
> >
> >the final "environment" problem I've is that SVGs that I put in
> >src/main/resources/assets are not in
> >final VividBlueTheme-0.9.2-SNAPSHOT-js.swc
> >
> >I see it copied to target/classes as usual in maven build, but are not
> >part
> >of the theme swc file.
> >
> >it's something missing in the theme implementation? or maybe something I
> >need to setup in pom.xml?
> >
> >
> >thanks
> >
> >--
> >Carlos Rovira
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%2
> >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%
> 7C973b4725aeaf4542d16308d5
> >7bacfdd8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636550905283794125&s
> >data=GeImt6g%2FONQJO8aKdkb%2BR8LgspIJ4jimlwrweM%2BCV8M%3D&reserved=0
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conócenos en 1 minuto! <https://avant2.es/#video>
Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.
De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc
libraries
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I think any assets need to be listed in the <include-files> in the pom.xml
(and for Ant, the src/main/config/compile*.xml files).
AFAIK, there is no automatic including. I believe you can use wildcards
in the <include-files>.
-Alex
On 2/24/18, 9:35 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlosrovira@apache.org> wrote:
>Hi,
>
>the final "environment" problem I've is that SVGs that I put in
>src/main/resources/assets are not in
>final VividBlueTheme-0.9.2-SNAPSHOT-js.swc
>
>I see it copied to target/classes as usual in maven build, but are not
>part
>of the theme swc file.
>
>it's something missing in the theme implementation? or maybe something I
>need to setup in pom.xml?
>
>
>thanks
>
>--
>Carlos Rovira
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2
>Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C973b4725aeaf4542d16308d5
>7bacfdd8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636550905283794125&s
>data=GeImt6g%2FONQJO8aKdkb%2BR8LgspIJ4jimlwrweM%2BCV8M%3D&reserved=0
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
but this is not the same problem. I managed something similar to yours when
"introducing assets in theme SWC". Then I use maven to copy assets to SWC.
But the actual problem is "copying the assets inside a theme SWC to final
Royale App (JS or SWF)", so compiler needs to extract from SWC theme and
copy to output folder
in the other hand some CSS rules gives problems. I found various when
tried to make MDLBlogExample. This will become problematic at some time
when people try to enter some advanced selectors in CSS, or maybe even soon
if I need some of that while doing Theme final work on visuals. At some
time will need to start raising bugs to solve it
2018-02-25 0:48 GMT+01:00 Piotr Zarzycki <pi...@gmail.com>:
> I came into similar problem while working on transpiledactionscript
> website. There were some CSS construction like scaleY, rotate etc. which
> simply wasn't accepted by compiler - That is a bug - probably I should
> raise an issue - I forgot about that.
>
> I did workaround - I specified new file under recourse/additional.css -
> where I put all problematic css. I've added link to it in
> "mdl-js-index-template.html". Once I got maven build I had to have that
> file in the bin/js-debug/resources/additional.css.
>
> Compiler won't copy it for me, so I have used maven-resource-plugin in
> order to copy that file [1]. I believe that is some additional approach.
>
> [1] https://goo.gl/mvUd9G
>
> Thanks, Piotr
>
> 2018-02-24 18:35 GMT+01:00 Carlos Rovira <ca...@apache.org>:
>
> > Hi,
> >
> > the final "environment" problem I've is that SVGs that I put in
> > src/main/resources/assets are not in
> > final VividBlueTheme-0.9.2-SNAPSHOT-js.swc
> >
> > I see it copied to target/classes as usual in maven build, but are not
> part
> > of the theme swc file.
> >
> > it's something missing in the theme implementation? or maybe something I
> > need to setup in pom.xml?
> >
> >
> > thanks
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: How to get assets (svg, png,...) inside *-js.swc and *-swf.swc libraries
Posted by Piotr Zarzycki <pi...@gmail.com>.
I came into similar problem while working on transpiledactionscript
website. There were some CSS construction like scaleY, rotate etc. which
simply wasn't accepted by compiler - That is a bug - probably I should
raise an issue - I forgot about that.
I did workaround - I specified new file under recourse/additional.css -
where I put all problematic css. I've added link to it in
"mdl-js-index-template.html". Once I got maven build I had to have that
file in the bin/js-debug/resources/additional.css.
Compiler won't copy it for me, so I have used maven-resource-plugin in
order to copy that file [1]. I believe that is some additional approach.
[1] https://goo.gl/mvUd9G
Thanks, Piotr
2018-02-24 18:35 GMT+01:00 Carlos Rovira <ca...@apache.org>:
> Hi,
>
> the final "environment" problem I've is that SVGs that I put in
> src/main/resources/assets are not in
> final VividBlueTheme-0.9.2-SNAPSHOT-js.swc
>
> I see it copied to target/classes as usual in maven build, but are not part
> of the theme swc file.
>
> it's something missing in the theme implementation? or maybe something I
> need to setup in pom.xml?
>
>
> thanks
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*