Hi, all:
I want to start upgrading the very useful documentation we have that
currently refers to FlexJS [1]. At the very least every document needs
edits to make sure it refers to Royale.
However, there are some other considerations:
- Is there material that needs to be rewritten because
This is great. I have verified all the fixes and have updated the tracking
document. This task is complete...for now!
a
On Tue, Jan 16, 2018 at 6:12 PM, Carlos Rovira
wrote:
> Thanks Andrew, I did all changes except one. The one about the digest, I
> took this tables
Well if the Above example of usage is not working, we need to figure out
how to have it working. I can of course copy everything what is inside
DynamicDataGrid style and add my things, but this is not the solution.
Thanks!
2018-01-17 22:10 GMT+01:00 Peter Ent :
> I'm not
I'm not sure; it is a good question. I will have to experiment.
The DataGridModel works with ArrayList now. What I would do is change it
to work with Array and then make a new model for the ArrayList or
ICollectionView, which to me, is a better choice over ArrayList since its
an interface and
Hi Peter,
To me it is a good change. I was always wondering why DG is working with
ArrayList default. However let's say that I wanted to switch some of the
beads for that DataGrid or add some custom class. How am I supposed to add
second css class ?
If I have this: and I have
something in my
Hi,
> Are you now claiming this content is under CC-BY-SA instead of just CC-BY?
> I did not see that. Where did you get that? Share-Alike (SA) has more
> restrictions than just CC-BY, AIUI.
Sorry my mistake it’s CC-BY not CC-SA. Full name "Creative Commons Attribution
International 4.0
Here is the relevant license text:
=
All code in any directories or sub-directories that end with *.html or
*.css is licensed under the Creative Commons Attribution International
4.0 License, which full text can be found here:
IMO, the DataGrid in Basic should work with Arrays and a different set of
beads allow it to work with ArrayList and another set of beads provides
detection of changes to the ArrayList. As long as we have those beads
(and maybe some tests/examples to prove it all works), the default set of
beads
The legal email is here:
https://lists.apache.org/thread.html/22458fb5e7e73adaff5345744ba16842c57352
eab72fd89ae0423327@%3Clegal-discuss.apache.org%3E
-Alex
On 1/17/18, 11:30 AM, "Piotr Zarzycki" wrote:
>Hi Alex,
>
>Thanks for the explanation. Can you share link to
Hi,
I'm proposing a change to DataGrid default configuration. Right now DataGrid is
designed to work with ArrayList; its does not work with Array. I propose that
the default configuration for DataGrid is to use Array as its dataProvider and
provide no dynamic abilities.
We would include in
Hi Alex,
Thanks for the explanation. Can you share link to the legal email/jira - I
cannot find it. Legal-VP - It means that you have asked one person ?
Option 1) I personally don't have enough free time to make such changes in
those examples.
Option 2) If Legal answer that because of current
On 1/16/18, 9:16 PM, "Justin Mclean" wrote:
>Hi,
>
>> Royale is not going to operate like Flex. We want to be more responsive
>> to our users. So instead of conducting detailed searches for IP issues
>>at
>> release time, they should be done at commit time or at
Piotr, Carlos,
Please read and respond. Others are welcome to give their thoughts as
well.
Just to be clear, MDLBlogExample is an attempt to exactly replicate an
example from Google's MDL repo. Google's example contains HTML and CSS
files and the example uses text content from the HTML files
We have to also exclude MDLBlogExample from ANT build, because ANT is
producing distribution package for IDE usage not Maven.
Thanks for explanation, so by deprecation you mean rather recommendation to
the users some other UI module instead of MDL. Not removing it completely
from the framework
Hi Piotr
2018-01-17 13:29 GMT+01:00 Piotr Zarzycki :
> Hi Carlos,
>
> I think removing MDLBlogExample completely will be better, cause we don't
> need to remember in every release about exclusion of that example.
>
exclusion in maven is only not to list in modules
Hi Carlos,
I think removing MDLBlogExample completely will be better, cause we don't
need to remember in every release about exclusion of that example.
What do you mean by "deprecate that library" in terms of open source
project ?
Thanks, Piotr
2018-01-17 13:24 GMT+01:00 Carlos Rovira
Hi,
I think MDLExample is one of the most referred examples out there. I
couldn't follow all the discussion since I was busy with work and other
task in this project, but I read that we had some problems with images. We
can change the images for place holders. If there's some more problem I
don't
Olaf,
I'm against even for that. MDLExample should be always in release package.
If I understand Alex's idea the things should be fixed in the commit time,
so now we have release time. We had that issue for several releases, we can
leave with it one more release.
Thanks, Piotr
2018-01-17 10:24
Hi Piotr,
just to make sure you don't get it wrong:
The idea is to just remove it from the RC2 (So from the first Royale release
at the end) just in order to have some more time to fix the IP/license
issues and so don't delay the release any longer.
This does not mean that those examples aren't
If there is unresolvable license issue which do not allow us to keep those
examples - I will get them to my private repository, than we can remove
from this project.
2018-01-17 10:02 GMT+01:00 Piotr Zarzycki :
> Hi Guys,
>
> I'm definitely against of removing MDL
Hi Guys,
I'm definitely against of removing MDL examples. I could agree only on
removing MDLBlogExample, because it's not finished and I'm not going to
invest time to finish it. Unless Carlos have such pans. If we cannot
resolve something now let's resolve it for the next release. Let's start
21 matches
Mail list logo