This is an automated email from the ASF dual-hosted git repository.

carlosrovira pushed a change to branch feature/vivid-ui-set
in repository https://gitbox.apache.org/repos/asf/royale-asjs.git.


 discard 654aa0c  remove svg not used
 discard 7e2373e  button changes
 discard 7143394  Button initial styles
 discard f004510  initial svg tests, still need 9slice scaling
 discard 1dc03ca  fix vscode config files
 discard 9981f3c  snapshot sdk now works in vscode 0.10.0
 discard 649f0cc  change pom description to conform with "themes"
 discard 83809b1  include assets in theme swc
 discard 1ddb68d  test SVG as background in TextButton, but is not copied to 
final SWC
 discard 119400fe textbutton css in theme
 discard 5492e8d  final dependency from vivid for swf compile
 discard 18d4b6c  Move vivid theme to themes folder and change vivid example to 
dependency "theme"
 discard 50f44b8  add for possible swf comp
 discard b76bd95  Introduce RadioButton
 discard 46aa248  fresh branch with all vivid work, still not work
     add 869b486  Assuming we stick with CSSClassList
     add dc117d2  Switch map co-ords in USStatesMap example so as to fix 
licensing issue.
     new 6958648  fresh branch with all vivid work, still not work
     new ab74a9b  Introduce RadioButton
     new bb892ce  add for possible swf comp
     new 9934d51  Move vivid theme to themes folder and change vivid example to 
dependency "theme"
     new dfef3db  final dependency from vivid for swf compile
     new 820fa8b  textbutton css in theme
     new c2282b7  test SVG as background in TextButton, but is not copied to 
final SWC
     new efefad2  include assets in theme swc
     new b164ce6  change pom description to conform with "themes"
     new 3450203  snapshot sdk now works in vscode 0.10.0
     new 88f164e  fix vscode config files
     new e0bca4f  initial svg tests, still need 9slice scaling
     new 0be29ed  Button initial styles
     new d569727  button changes
     new 5a199f0  remove svg not used

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (654aa0c)
            \
             N -- N -- N   refs/heads/feature/vivid-ui-set (5a199f0)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 15 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 LICENSE                                            |   2 +-
 .../USStatesMap/src/main/royale/MapCoords.as       | 119 ++++++++++++---------
 .../USStatesMap/src/main/royale/USStatesMap.as     |   1 +
 .../main/royale/org/apache/royale/mdl/Button.as    |  29 +++--
 4 files changed, 84 insertions(+), 67 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
[email protected].

Reply via email to