follow-up to variable row Height

[gbarbosa]

Hi Royale,

I read this thread  /Issue-with-rowHeight-and-big-amount-of-data-in-cells

  

and was wondering if any progress or decisions were made for this. Is there
a branch with a partially built bead for variable row height that can be
used with mx:AdvancedDataGrid? 

Side question is there an easy way to hide the headers on
mx:AdvancedDataGrid?

Thanks!
-Gabriel Barbosa



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Royale_Release_Step_008 - Build # 17 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_008 - Build # 17 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_008/17/
 to view the results.

Royale_Release_Step_008 - Build # 16 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_008 - Build # 16 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_008/16/
 to view the results.

Royale_Release_Step_008 - Build # 15 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_008 - Build # 15 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_008/15/
 to view the results.

Royale_Release_Step_008 - Build # 14 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_008 - Build # 14 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_008/14/
 to view the results.

Royale_Release_Step_008 - Build # 13 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_008 - Build # 13 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_008/13/
 to view the results.

Royale_Release_Step_008 - Build # 12 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_008 - Build # 12 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_008/12/
 to view the results.

Royale_Release_Step_008 - Build # 11 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_008 - Build # 11 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_008/11/
 to view the results.

Royale_Release_Step_008 - Build # 10 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_008 - Build # 10 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_008/10/
 to view the results.

Royale_Release_Step_008 - Build # 9 - Failure!

[apacheroyaleci]

Royale_Release_Step_008 - Build # 9 - Failure:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_008/9/
 to view the results.

Release Step 007 Succeeded

[apacheroyaleci]

>From the royale-typedefs repo:
1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.8 
-DskipTests=true
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign 
-Drelease.version=0.9.8
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_007_Upload 
-Drelease.version=0.9.8
This will upload the signed artifacts to Maven Release Staging. Do not "Close" 
the staging repository until the other repos have been added.

Royale_Release_Step_007 - Build # 17 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_007 - Build # 17 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_007/17/
 to view the results.

Royale_Release_Step_007 - Build # 16 - Failure!

[apacheroyaleci]

Royale_Release_Step_007 - Build # 16 - Failure:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_007/16/
 to view the results.

Release Step 006 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands:
git push
git push origin org.apache.royale.typedefs-0.9.8-rc2

You will need your Apache/Github username and 2FA token.

Release Step 005 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_005 and run the
following commands:
git push

You will need your Apache/Github username and 2FA token.

Release Step 004 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands:
git push
git checkout release/0.9.8
git push -u origin release/0.9.8

You will need your Apache/Github username and 2FA token.

Royale_Release_Step_004 - Build # 22 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_004 - Build # 22 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/22/
 to view the results.

Royale_Release_Step_004 - Build # 21 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_004 - Build # 21 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/21/
 to view the results.

Royale_Release_Step_004 - Build # 20 - Failure!

[apacheroyaleci]

Royale_Release_Step_004 - Build # 20 - Failure:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_004/20/
 to view the results.

Release Step 003 Succeeded

[apacheroyaleci]

>From the royale-compiler repo:
1. Run:
  ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign 
-Drelease.version=0.9.8
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload 
-Drelease.version=0.9.8
This will upload the signed artifacts to Maven Release Staging. If you are 
getting 401 responses from Nexus (permission denied) please be sure to have 
your apache creedentials configured in your .m2/settings.xml file. 

Feel free to use this template if you haven't got a settings.xml yet:


http://maven.apache.org/SETTINGS/1.1.0 
http://maven.apache.org/xsd/settings-1.1.0.xsd; 
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
  


  apache.releases.https
  {your apache user id}
  {your apache user password}

  


(Be sure to replace the placeholders with your actual apache committer id and 
your Apache password)

If you already have a settings.xml, just be sure the "server" block containing 
your credentials is added to a servers block in that file.

Do not "Close" the staging repository until the other repos have been added.

Royale_Release_Step_003 - Build # 30 - Failure!

[apacheroyaleci]

Royale_Release_Step_003 - Build # 30 - Failure:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_003/30/
 to view the results.

Release Step 003 Succeeded

[apacheroyaleci]

>From the royale-compiler repo:
1. Run:
  ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign 
-Drelease.version=0.9.8
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload 
-Drelease.version=0.9.8
This will upload the signed artifacts to Maven Release Staging. If you are 
getting 401 responses from Nexus (permission denied) please be sure to have 
your apache creedentials configured in your .m2/settings.xml file. 

Feel free to use this template if you haven't got a settings.xml yet:


http://maven.apache.org/SETTINGS/1.1.0 
http://maven.apache.org/xsd/settings-1.1.0.xsd; 
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
  


  apache.releases.https
  {your apache user id}
  {your apache user password}

  


(Be sure to replace the placeholders with your actual apache committer id and 
your Apache password)

If you already have a settings.xml, just be sure the "server" block containing 
your credentials is added to a servers block in that file.

Do not "Close" the staging repository until the other repos have been added.

RE: META-INF/DEPENDENCIES Diff (was RE: [Discuss] What to do with SWF target now that Adobe removed Flash Player in 2021 (Re: How to build from now on?))

[Yishay Weiss]

Thank you josh! Will upgrade CI server to 3.6.3.

From: Josh Tynjala
Sent: Thursday, April 8, 2021 1:31 AM
To: Apache Royale Development
Subject: Re: META-INF/DEPENDENCIES Diff (was RE: [Discuss] What to do with SWF 
target now that Adobe removed Flash Player in 2021 (Re: How to build from now 
on?))

I was able to find binaries for Maven 3.6.0, and I compared the output
between 3.6.0 and 3.6.3 (which is, coincidentally, the version that I have
installed on my computer too). Maven 3.6.0 omits playerglobal.swc from
flex-compiler-oem.jar's META-INF/DEPENDENCES and Maven 3.6.3 includes it.
So it appears that you either need to switch to Maven 3.6.0 locally, or you
need to upgrade Maven on the CI server.

If it helps, here's where I downloaded Maven 3.6.0:

https://archive.apache.org/dist/maven/maven-3/3.6.0/binaries/

--
Josh Tynjala
Bowler Hat LLC 


On Wed, Apr 7, 2021 at 1:43 AM Yishay Weiss  wrote:

> Running  ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
> succeeds on the CI server but fails my local pc because of this difference
> in DEPENDENCIES. So it’s the same command being run with different results,
> which means we can’t release.
>
> The only differences I can think of are the mvn version (mine is 3.6.3,
> CI’s is 3.6.0), and the java version (mine is 1.8.0_281, CI’s is 1.8.0_201).
>
> I tried removing the playerglobal.swc from CI server’s .m2 repo and
> letting mvn download it but it’s the same result.
>
> From: Josh Tynjala
> Sent: Tuesday, April 6, 2021 7:42 PM
> To: Apache Royale Development
> Subject: Re: [Discuss] What to do with SWF target now that Adobe removed
> Flash Player in 2021 (Re: How to build from now on?)
>
> I have tested locally and confirmed that playerglobal.swc is listed in
> flex-compiler-oem's META-INF/DEPENDENCIES only when using -P
> option-with-swf. That makes sense. So I guess you didn't use -P
> option-with-swf on one of the computers.
>
> --
> Josh Tynjala
> Bowler Hat LLC 
>
>
> On Tue, Apr 6, 2021 at 9:23 AM Josh Tynjala 
> wrote:
>
> > Yeah, that could be where it comes from. By why would that affect one
> > computer, but not another? That doesn't make sense to me. Unless maybe a
> > slightly different command is being run on the two computers. Are both
> > using option-with-swf?
> >
> > --
> > Josh Tynjala
> > Bowler Hat LLC 
> >
> >
> > On Tue, Apr 6, 2021 at 1:58 AM Yishay Weiss 
> > wrote:
> >
> >> Not sure if this is related, but I found this in
> >> royale-compiler/compiler/pom.xml
> >>
> >> 
> >>   option-with-swf
> >>   
> >> 
> >> 
> >>   com.adobe.flash.framework
> >>   playerglobal
> >>   ${flash.version}
> >>   swc
> >>   runtime
> >> 
> >>   
> >> 
> >>
> >> From: Josh Tynjala
> >> Sent: Monday, April 5, 2021 7:26 PM
> >> To: Apache Royale Development
> >> Subject: Re: [Discuss] What to do with SWF target now that Adobe removed
> >> Flash Player in 2021 (Re: How to build from now on?)
> >>
> >> I wouldn't expect a compiler .jar file to have a dependency on any .swc
> >> files. That doesn't really make any sense to me. Chris might know, since
> >> he
> >> did the Maven stuff, but he may or may not be around to help anymore.
> >>
> >> --
> >> Josh Tynjala
> >> Bowler Hat LLC 
> >>
> >>
> >> On Mon, Apr 5, 2021 at 4:14 AM Yishay Weiss 
> >> wrote:
> >>
> >> > One more thing, perhaps related. I’m getting a different in the
> >> > flex-compiler-oem-0.9.8.jar between my local system and the CI server
> >> > because of this line
> >> >
> >> > +  - playerglobal  com.adobe.flash.framework:playerglobal:swc:20.0
> >> >
> >> > In META-INF/DEPENDENCIES
> >> >
> >> > which only exists in one of the systems. Any ideas on how to get
> around
> >> > that?
> >> >
> >> > Thanks.
> >> >
> >> > From: Yishay Weiss
> >> > Sent: Monday, April 5, 2021 10:36 AM
> >> > To: dev@royale.apache.org
> >> > Subject: RE: [Discuss] What to do with SWF target now that Adobe
> removed
> >> > Flash Player in 2021 (Re: How to build from now on?)
> >> >
> >> > Hi Josh,
> >> >
> >> > I’m running release ant script which has
> >> >
> >> >  >> > failonerror="true" >
> >> > 
> >> > 
> >> > 
> >> > 
> >> >
> >> > This results in
> >> >
> >> >  [exec] [INFO] Installing
> >> >
> >>
> C:\temp2\sources\compiler-playerglobalc\target\compiler-playerglobalc-0.9.8-tests.jar
> >> > to C:\Users\yisha\.m2\repository\org\apache\royale\compile
> >> > r\compiler-playerglobalc\0.9.8\compiler-playerglobalc-0.9.8-tests.jar
> >> >  [exec] [INFO]
> >> >  [exec] [INFO] <
>