Proof of Concept

[Glenn Wilson]

I have published a test for an initial proof of concept for a ChessFlash chess publishing tool based on jangaroo at:

http://www.glennwilsonchess.com/2013/03/test-iframe-2.html

based on 0.9.9.  It is looking promising to supplement in the near term and possibly replace the Flash version in the long term.

One concern is the the speed of the initial load; I know it needs a lot of stuff to replace much of the flash framework. Any thoughts on how that can be made faster?

Thanks,

Glenn 

[Dennis Homann]

> One concern is the the speed of the initial load; I know it needs a lot of stuff to replace much of the flash framework. Any thoughts on how that can be made faster?

It looks like your Apache server is not configured to compress application/x-javascript.

It does compress your text/html and text/css, indicated by the "Content-Encoding: gzip" response header, which is missing for your JavaScript files.

You may want to follow instructions on http://httpd.apache.org/docs/2.2/mod/mod_deflate.html to configure mod_deflate to compress application/x-javascript as well.

Hope this helps,

Dennis 

[Glenn Wilson]

I'll check that out.  Thanks!

[Frank]

If you want to reduce requests, you can use jangaroo-application-
all.js instead of jangaroo-application.js.
Although jangaroo-application-all.js already contains no comments an
(almost) no removable white-space, it will still become a bit smaller
by running it through a JavaScript minifier like Uglify or Google
Closure Compiler (do not use ADVANCED_OPTIMIZATIONS, it won't work).
If you want to invest a bit of work, you can optimize by including
only the classes that are loaded in debug mode (#joo.debug).
Another option is to try out Jangaroo 3, of which I'll do a preview
release soonish. It uses RequireJS for script loading and linking.
RequireJS comes with a static optimizer tool and leads to much more
concise Jangaroo applications.

Greetings
-Frank-

[Glenn Wilson]

Much better with the compression enabled.   Thanks!

On Wednesday, March 13, 2013 6:13:51 PM UTC-5, Dennis Homann wrote:

[Glenn Wilson]

This option is now live and available to my ChessFlash users.  They can publish their chess games and they will display using flash where supported and will publish with a subset of the full flash functionality using jangaroo where flash is not supported.  If you are interested there are some sample posts at:

http://www.glennwilsonchess.com/

The FAQ mentions Jangaroo:

http://chessflash.com/pgnviewerfaq.html

And the publishing page mentions the Jangaroo license:

http://chessflash.com/chessflash.html

It has been less than a week since I stumbled across Jangaroo.   Pretty awesome tool! Thanks!

[Dennis Homann]

Congratulations, that's super fast for a migration like this!

Works great on iPhone and iPad.

On Nexus 10, I get the "loading-forever behavior". It's probably only some minor issue, but I cannot debug the tablet browser right now.

Cool stuff!

[Frank]

That's awesome! What a reference for Jangaroo!

To solve the remaining issues with JooFlash 1.0.1, I'd like to retest
fixes by building your application. Is the source code for the
Jangaroo variant already in your SVN repo?

Another question: how do you dynamically switch between Flash and
JooFlash (if no Flash available)? Are you aware of my patched version
of swfobject that is meant for exactly this task? Probably not,
because it is totally undocumented...

Greetings,
-Frank-

[Frank]

On Mar 15, 10:25 am, Frank <frank.wienb...@coremedia.com> wrote:
> Another question: how do you dynamically switch between Flash and
> JooFlash (if no Flash available)? Are you aware of my patched version
> of swfobject that is meant for exactly this task? Probably not,
> because it is totally undocumented...

This option has been applied successfully for switching Open Flash
Charts
between Flash and JooFlash version. Please have a look at this (very
long) thread:
http://groups.google.com/group/jangaroo-users/browse_thread/thread/73da89267dd6a743

[Glenn Wilson]

It is now.  I figure it is easier for me to juggle the flash vs. joo differences so the Jangaroo version is the trunk.

Currently the trunk is set to build with 0.9.9 and is the V1.00 Jangaroo version.  The only "trick" is that I use build.bat to build.  It calls maven and also copies over images that I could not figure out how to with with maven :-(.

Well, I guess the other trick is knowing how to use it.  Something like:

XXX/target/chessflashJS-0.1/index.html?pgndata=1.e4%20e5&dark=cc6666

(adjusted for where index.html is located)
Should do something "interesting."
Regards,

Glenn

[Frank]

I guess I just fixed the "vanishing canvas" issue:
http://jangaroo.myjetbrains.com/youtrack/issue/LIBS-50
But the fix is not yet released. I better retest with your application
first.
I should get this working based on your infos...

[Glenn Wilson]

I did notice that with 1.0.1 you can use left and right arrow keys to navigate through the game.  That  did not work in 0.9.9.

The current trunk should work for Flash or Jangaroo 0.9.9.  

I've cleaned up the code some, especially buttons, while trying to isolate the 1.0.1 issue(s).  No real progress on that except I have noticed that for the buttons the click events get registered and clicking does fire click events.  But they never get to the registered listeners?

[Frank]

I just fixed three more bugs:
http://jangaroo.myjetbrains.com/youtrack/issues?q=Fix+versions%3A+1.0.2+Subsystem%3A+jooflash
...and ChessFlash now runs perfectly with JooFlash 1.0.2-SNAPSHOT (at
least as far as I can tell).
I'm gonna do some more QA with other JooFlash applications and then
release jangaroo-libs 1.0.2!
Stay tuned...

I also added a solution that copies the images from the lib folder to
pom.xml.
I admit it is not easy to figure out.
Just use this maven-war-plugin configuration:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1.1</version>
<configuration>
<webResources>
<resource>
<directory>src/main/webapp</directory>
</resource>
<resource>
<directory>lib</directory>
<targetPath>joo/lib</targetPath>
</resource>
</webResources>
<failOnMissingWebXml>false</failOnMissingWebXml>
</configuration>
</plugin>

Also, you use the wrong property for the jangaroo-maven-plugin:
instead of jangaroo_libs_version, it should use jangaroo_version,
which will stay on 1.0.1 when you move to jangaroo-libs 1.0.2.

Greetings
-Frank-

[Glenn Wilson]

That's great!  Thanks.