translate-swf-updates — News on releases, bugs and patches for Translate SWF for Java

[translate-swf-updates] List replaced by new forum

[News on r. b. a. p. f. T. S. f. J. <tra...@li...>]

This mailing was primarily used to post news about releases, bug reports 
and patches. With the repository moving to GitHub this list is shutting 
down.

All new releases will still be announced on the Flagstone Announcements 
forum, http://www.flagstonesoftware.com/phpBB3/viewforum.php?f=1

All reports of bugs and patches to fix them will be posted on the new 
Flagstone Bugs & Patches forum, 
http://www.flagstonesoftware.com/phpBB3/viewforum.php?f=8

Regards,

Stuart
--
Flagstone Software Ltd.

[translate-swf-updates] Status report for week ending Oct 15th

[News on r. b. a. p. f. T. S. f. J. <tra...@li...>]

  Progress This Week.

The decision was that Translate 3.0 will be released when profiles 
DEFAULT_1_5 through to DEFAULT_1_10 are fully supported since this gives 
the largest coverage when compiling existing scripts. Support for 
DEFAULT_1_4 will be added latest since this involves a reasonable amount 
of work. Profiles for Flash Lite will be added after this since the work 
for DEFAULT_1_4 forms a basis for this.

No release date is currently set buy regular updates will be provided as 
support for each profile is completed. This will allow a decision to be 
taken on when you can start successfully using version 3.0 in your projects.

Planned for Next Week:

Continue with testing.

Regards,

Stuart MacKay
Flagstone Software Ltd.

[translate-swf-updates] Status report for week ending Oct 8th

[News on r. b. a. p. f. T. S. f. J. <tra...@li...>]

  Completed This Week:

Started writing up the errors reported during integration testing. Each 
profile is being tested in turn which makes it easier to fix bugs 
incrementally and give a level of actionscript support that is 
increasingly useful.

Of the profiles tested so far:

DEFAULT_1_2 - 100% of tests passing
DEFAULT_1_3 - 100% of tests passing
DEFAULT_1_4 - 289 out of 557 testing passing (52%)
DEFAULT_1_5 - 955 out of 1013 tests passing (94%)
DEFAULT_1_6 - 1225 out of 1349 tests passing (91%)

The tests that are failing for profiles DEFAULT_1_5 and DEFAULT_1_6 can 
be summarised as follows, in decreasing importance:

1. The directive #include is not supported.
2. Global (built-in) functions loadMovieNum(), loadVariablesNum() and 
the deprecated mblength() are not supported.
3. The typeof operator is not supported.
4. There is an issue with fscommand() that needs further investigation.
5. Deprecated operators: eq, gt, lt, not are not compiled correctly.

Detailed description of the bugs can be found at:

DEFAULT_1_4 profile. See 
http://sourceforge.net/tracker/?func=browse&group_id=123003&atid=695166&category=1553351
DEFAULT_1_5 profile. See 
http://sourceforge.net/tracker/?func=browse&group_id=123003&atid=695166&category=1553352

The bugs for profile, DEFAULT_1_6 appear to largely be the same as for 
profile DEFAULT_1_5 so the bug lists will be updated after profile, 
DEFAULT_1_5 is passing 100% of tests.

Planned For Next Week:

1. Fix all the bugs in profile DEFAULT_1_5.
2. Retest profile DEFAULT_1_6 and start fixing bugs.
3. Continue testing the remaining profiles.

Based on the favourable results from testing profile DEFAULT_1_5 it is 
likely that a decision will be taken on when to release Translate SWF 
3.0 at the end of October. Profile, DEFAULT_1_5 provides a level of 
functionality that would satisfy a large number, if not the majority of 
reasonably complex applications. So the compiler could be released as a 
viable piece of software then incremental improvements made as a series 
of minor releases.

Regards,

Stuart MacKay
Flagstone Software Ltd.

[translate-swf-updates] Status report for week ending Oct 1st

[News on r. b. a. p. f. T. S. f. J. <tra...@li...>]

  Last week's work (and status report) got interupted on Sept23rd by the 
arrival of Mariana, 3.6 kilos and doing very well, though I have to 
admit to being sleep-deprived as I type this.

Progress this week:

1. Completed the comparison of the YAML reference files with an 
Actionscript 1.0 language reference guide. Now we have a complete 
description of all the language features and which version of Flash they 
are applicable.

The bonus of having this is that all the YAML files can be used for 
assessing language coverage for Actionscript 2.0 as well. All that needs 
to be added are the keywords used for defining classes.

2. Added the missing unit tests so now we have 100% test coverage of all 
the language features.

3. Ran the first suite of integration tests covering all the different 
versions of Flash (2 to 10) that support Actionscript 1.0. Roughly 80% 
of the tests are passing. Some of the output from the compiler is 
functionally correct but fails a test because it does match 100% the 
actions generated by the Flash Authoring tool. This means that for a lot 
of scripts, Translate SWF as it stands today, can be used for useful work.

Planned for next week:

1. Start assessing some of the errors to determine whether support for 
language features should be prioritised.

2. Start writing up tickets for the root causes of failed tests.

Regards,

Stuart MacKay
Flagstone Software Ltd.

[translate-swf-updates] Status report for week ending Sept 17th

[News on r. b. a. p. f. T. S. f. J. <tra...@li...>]

  Progress This Week:

API Changes:

1. Simplified the interface to ASCompiler so a Profile is used to set 
the target Flash Player, Actionscript version and Flash version rather 
than setting the parameters individually. This makes it easier to catch 
unsupported versions.

Integration Testing:

1. Simplified ActionscriptGenerator and process for generating and 
compiling actionscript files used for testing so all publish profiles 
can be compiled in a single step.

2. Added TestCoverageReport which compares the identifiers in the 
actionscript reference YAML files with the references in the model YAML 
files used for generating the scripts used in integration testing. If an 
identifier for a language feature does not have at least one test that 
covers it then the identifier is logged in the test coverage report so 
new tests can be added.

Planned For Next Week:

1. Compare the YAML files that describe all the Actionscript features 
with an official Adobe Actionscript reference guide. This will identify 
whether the implementation of Actionscript 1.0 is 100% complete or not.

2. Once the YAML reference files have been updated new tests will be 
added so there is 100% test coverage of the language features.

3. In the unlikely event that #2 gets completed the next step will be to 
run the integration tests and start fixing the bugs.

Regards,

Stuart
--
Flagstone Software Ltd.

[translate-swf-updates] Status report for week ending Aug 6th

[News on r. b. a. p. f. T. S. f. J. <tra...@li...>]

  Progress this week:

Still refactoring the existing suite of actionscript files into YAML. 
The work is taking longer than expected and might need another week or 
two to complete. The good news is that the new format is great for 
adding lots of different tests which, if presented in a single 
actionscript file, would be very difficult to track and debug. So the 
extra effort is going to be worth it.

Planned For Next Week:

1. More work on refactoring the scripts.
2. Vacation.

Regards,

Stuart
--
Flagstone Software Ltd.

[translate-swf-updates] Status report for week ending July 30th

[News on r. b. a. p. f. T. S. f. J. <tra...@li...>]

Progress This Week:

Lots of work on the code and scripts used for testing:

1. Reorganised the tests so the actionscript files that are used to 
verify that ASCompiler generates the same code as the Flash Authoring 
tool are now generated from YAML files. This allows complete suites of 
scripts for each supported profile (actionscript version, flash version 
and runtime platform) to be generated from the same set of YAML files 
rather than maintaining the suites separately.

2. In addition a reference YAML file for the Actionscript 1.x language 
was created. Each language feature - an operator or class and a method, 
e.g.  a + b; or a = Math.cos(b); is assigned a unique identifier. Each 
test in the YAML test files uses the same identifier so test coverage 
for the language can be tracked. This can also be used for a variety of 
reports - assessing language coverage or listing all the tests and hence 
language features that are not currently implemented or the tests are 
failing.

Although this appears to be quite an involved approach it is expected to 
have significant benefits when all the different profiles (one for each 
Flash version, plus Flash Lite 1, Flash Lite 1.1, Flash Lite 2.0, Flash 
Lite 2.1, Flash Lite 3.0, Flash Lite 3.1, etc.) implemented.

3. Started porting the current suite of actionscript test over to yaml. 
About half the scripts have been converted with the work expected to be 
complete by the end of next week.

4. Added tools for generating the actionscript resources used in testing 
from the YAML based test files.

5, Added a simple tool for debugging individual scripts.

6. Added utility functions as static class methods to simplify the test 
classes.


API Changes:

1. Added Profile so combinations of actionscript version, flash version 
and runtime platform can be referenced by a single name.


Planned For Next Week:

Complete porting the scripts to YAML so the complete support for 
Actionscript 1.x can be assessed.


Regards,

Stuart
--
Flagstone Software Ltd.

[translate-swf-updates] Status report for week ending July 23rd

[News on r. b. a. p. f. T. S. f. J. <tra...@li...>]

Progress This Week:

A lot of progress, though not all the changes have been committed yet. 
More in the next status report-


API Changes:

1. Added PlayerType enum to distinguish between the different runtime 
platforms, specifically to target the different Flash Lite versions that 
are used on mobile platforms and set-top boxes.

Code Changes:

1. Cleaned up ASCompiler interface and oither classes to support both 
the existing  and new refactored codebases.

2. Moved all the code generation code in ASNode over to NodeGenerator - 
a default generator class that will then be refactored into smaller 
generator classes.


Planned For Next Week:

1. The actionscript used to test the compiler is currently started as 
suite of scripts. For each script there is a Flash file generated by 
Flash CS3 that acts as a reference to compare the output of the code 
generated by the ASCompiler against. A new suite is needed for each 
profile (a combination of actionscript version, flash player version and 
target rumtime) as the code can vary according to the Flash Player 
environment - there are particular differences between the browser 
plugin and the player on mobile phones for example. The result is a 
large number of identical scripts which will be complicated to mantain. 
The solution is to store the parameters in YAML files and generate the 
actionscript files.

This means that a version of the Flash authoring tool is needed to 
generate the reference flash files but this disadvantage will be offset 
by the large reduction in effort needed to maintain  the scripts. 
Probably a small reference set of scripts and Flash files will be 
retained in the repository so the compiler can be tested without needing 
a copy of the Flash Authoring tool.

Regards,

Stuart
--
Flagstone Software Ltd.

[translate-swf-updates] Status report for week ending July 16th

[News on r. b. a. p. f. T. S. f. J. <tra...@li...>]

Progress This Week:

Refactoring the code to split the functionality into smaller classes and 
allow parsers to be added for Actionscript 2 and 3 and perhaps also a 
parser for Flash Lite.

Actionscript Changes:

The following tickets were completed:

Newline now delimit statements (Ticket #1).

on() and onclipevent() statements are now interchangeable. This was 
fixed largely for historical / compaitbility reasons - older versions of 
Flash allowed on() and onClipEvent() to be used interchangeably but this 
appears to have been restricted in newer releases. (Ticket #2)

Function names are case sensitive, gotoandplay(), gotoAndPlay() and 
GOTOANDPLAY() all compile to the same code. (Ticket #3)

API Changes:

A new class ASCompiler now hosts the public API for the compiler. It has 
methods for setting the version of Actionscript used as well as the 
target Flash version which the code will be compiled to. ASNode is no 
longer visible. (Ticket #6).

Code Changes:

Complete integration with Transform. In the current release there are 
private copies of classes representing actions etc. These have been 
replaced with thier equivalents from Transform so libraries are tightly 
integrated. (Ticket #7)

Testing Changes:

Refactored actionscript test files so it maps to the Maven way or 
organising test resources. (Ticket #5)

Separate suites of test files were created for each Flash version 
allowing the code generated to accurately support the features hosted in 
each version of the Flash Player.

Updated testing to replace TableIndex objects with the actual strings. 
This makes it possible to easily compare the code generated by the Flash 
editor against the code generated by Translate even though the strings 
table may have strings in different orders making a pure diff impossible.

Commented out test cases that currently do not pass (or at least need 
verification) so that all the remaining tests pass and so make it easier 
to refactor the code.

Planned For Next Week

Finish the refactoring of the code so the API is stable and the 
libraries passes the current suite of tests.

Release a SNAPSHOT build to the Sonatype Maven repository (and also to 
the Flagstone web site if tests are passing).

Regards,

Stuart
--
Flagstone Software Ltd.

[translate-swf-updates] Status report for week ending July 9th

[News on r. b. a. p. f. T. S. f. J. <tra...@li...>]

Progress This Week:

Added test suites and methods that allow scripts written in different 
actionscript versions to be parsed and the code generation phase to 
target the different features supported in each version of Flash.

API Changes:

Added attributes for actionscript and flash versions to ASCompile so 
scripts can be compiled for specific Flash versions (not just default, 
actionscript 1) and targetted towards different Flash versions.

Testing:

Wrote a script to use the Javascript Flash API to generate .swf files 
from the actionscript test files. Most importantly this means that 
scripts can be compiled for different versions of actionscript and 
different versions of Flash. This means that the compiler can be tested 
with specific version profiles verifying that it can be used to compile 
code for different versions of Flash Lite for example.

Restructed the actionscript files used for testing. Now the scripts are 
grouped according to actionscript version and flash version. That allows 
a reference suite for each release of Flash to be created.

Added an actionscript suite for Flash 5 to complement the existing set 
for  Flash 7.

Planned For Next Week:

More work on resolving the current set of issues.

Regards,

Stuart
-- 
Flagstone Software Ltd.

[translate-swf-updates] ERRATA: Early release of Translate SWF 3.0 is now available

[News on r. b. a. p. f. T. S. f. J. <tra...@li...>]

The previous announcement of the snapshot release of Translate 3.0 
contain an error in the POM dependency. It should, of course, be:

  <dependencies>
      ....
      <dependency>
          <groupId>com.flagstone</groupId>
          <artifactId>translate</artifactId>
          <version>3.0-SNAPSHOT</version>
          <scope>compile</scope>
      </dependency>
  </dependencies>

Apologies for any confusion.

Stuart
-- 
Flagstone Software Ltd.

[translate-swf-updates] Early release of Translate SWF 3.0 is now available:

[News on r. b. a. p. f. T. S. f. J. <tra...@li...>]

A SNAPSHOT of Translate SWF 3.0 (for Java) is now available. Planned for 
Version 3.0 is tight integration with Transform 3.0 and support for 
Actionscript 2.0.


If you are using Maven:

All snapshot releases are deployed to the Sonatype public repository: 
https://oss.sonatype.org/content/groups/public/

Add the following entry to your POM

   <dependencies>
       ....
       <dependency>
           <groupId>com.flagstone</groupId>
           <artifactId>transform</artifactId>
           <version>3.0-SNAPSHOT</version>
           <scope>compile</scope>
       </dependency>
   </dependencies>

Add the Sonatype public repository to your settings.xml:

<profiles>
   ...
   <profile>
       <repositories>
           <repository>
               <id>FlagstoneSnapshots</id>
               <name>Flagstone Software Snapshots</name>
               <releases>
                   <enabled>false</enabled>
                   <updatePolicy>always</updatePolicy>
                   <checksumPolicy>fail</checksumPolicy>
               </releases>
               <snapshots>
                   <enabled>true</enabled>
                   <updatePolicy>always</updatePolicy>
                   <checksumPolicy>fail</checksumPolicy>
               </snapshots>
               <url>https://oss.sonatype.org/content/groups/public</url>
               <layout>default</layout>
           </repository>
       </repositories>
   </profile>
 </profiles>


If you are not using Maven, you can still download the latest snapshot 
from the Flagstone web site:

http://www.flagstonesoftware.com/downloads/index.html

The snapshot files are not timestamped, e.g. 
translate-3.0-SNAPSHOT-dist.tar.gz rather than 
transform-3.0-20100705.115554-1-dist.tar.gz. This should make it simple 
to drop in new releases though at the risk of getting snapshots mixed up 
if there is a breaking change.

Regards,

Stuart
-- 
Flagstone Software Ltd.

[translate-swf-updates] Release Date for Version 3.0

[News on r. b. a. p. f. T. S. f. J. <tra...@li...>]

Translate SWF 3.0 now has a planned release date of Sept 15th 2010. 
Planned for this release:

1. Integration with Transform SWF 3.0 - which is also planned for this 
date.
2. Support for Actionscript 2.0.
3. Project will be based on Maven.

A full list of issues and tasks planned for this release can be found at 
https://sourceforge.net/apps/trac/translate-swf/report/3

Regular project reports will be posted to this list.

Regards,

Stuart
-- 
Flagstone Software Ltd.