I'd like to suggest a new mailing list be created for all the CI and
other build related emails. I'm suggesting this to keep the dev
mailing clean from these automated emails.
--
Chris
--
Chris Velevitch
m: 0415 469 095
y" seems not very
> appropriate.
> We try to respect as much as possible, the work and proposals from others.
> You can disagree, but please maintain a level of respect since that way
> will make others not want to enter the conversation.
>
> Thanks in advance.
>
> El
There doesn't seem to be an all-encompassing document describing, MX,
Spark and Jewel components and as well as the pros and cons of each
nor is there a discussion on using third party web components,
creating custom web components and how to the material design
components.
>
> I think the term component is right in most cases and accomplish a meaning
> purpose, but strand/beads concept comes to give another subset of meaning
>
> just my opinion about this.
>
> Carlos
>
>
>
> El mar., 8 oct. 2019 a las 9:23, Chris Velevitch ()
>
If the whole point of PAYG is to eliminate unused code from being
included in the final app distribution, then I'd like to suggest that
we take advantage of the tools the JavaScript ecosystem already has
for eliminating unused code.
I think we should take a look at Webpack [1] and create a
When I was going through the documentation and code to get my head
around this silly notation of "beads" and "strands", I realised the
component plugins are very similar to the concept of skinning
components that Adobe Flex talks about. And there doesn't seem to be
any discussions on how to skin a
The use of the terms "strands" and "beads" still doesn't make sense to
me because they are concepts I have never heard before and it is
creating a barrier to acceptance and deepens the learning curve. As
far as I can tell, it's something to do with visual/UI components.
The section "Strands and
should work [1]
>
> For Jewel the page is this [2]
>
> [1] https://www.w3schools.com/js/js_versions.asp
> [2] https://apache.github.io/royale-docs/component-sets/jewel.html
>
>
> El jue., 29 ago. 2019 a las 7:19, Chris Velevitch (<
> chris.velevi...@gmail.com>) escri
*, (released, *2014*) , although I think Android devices can be
> very different between manufactures, so maybe is not as easy, I tried with
> Samsung Galaxy different models and versions)
>
> I'll put this info on the wiki
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
--
Chris
--
Chris Velevitch
m: 0415 469 095
On Wed, 28 Aug 2019 at 16:12, Carlos Rovira wrote:
> Where did you find those links? maybe google (maybe bots already didn't
> notice the change?
I found those links by going to the main docs page [1]
[1] https://apache.github.io/royale-docs/
Chris
--
Chris Velevitch
m: 0415 469 095
the correct working links (just remove the
"/welcome" from the URL).
Chris
--
Chris Velevitch
m: 0415 469 095
On Tue, 27 Aug 2019 at 16:34, Carlos Rovira wrote:
> maybe the actual way compiler deal with this is a bit restricted, and we
> can update that part including the
Where is the value of "${body}" defined? When I build a javascript app, the
following code is inserted there:-
new MyApp().start();
I want to be able to insert additional code there like:-
royaleCompatibility = new RoyaleCompatibility();
if
So that line is shown in blue and with a bit more size to
> match the web style. That line should help a user to quickly understand
> what's that page about, since just "Externs" probably will not be of much
> help for a beginner.
>
> many pages are still without subtitle, but as we go over all docs, we
> should add this lines to help users reaching that pages.
>
> Thanks
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Chris
--
Chris Velevitch
m: 0415 469 095
14 matches
Mail list logo
