PlayN 1.2 release

[Michael Bayne]

Hello cross-platform gaming enthusiasts,

I'm pleased to announce the 1.2 release of the PlayN libraries.
There's a lot of exciting new stuff in there, along with a great many
smaller improvements. The release notes tell the whole tale:

http://code.google.com/p/playn/wiki/ReleaseNotes

(Well, really the commit logs tell the whole tale, but the release
notes provide a nice summary.)

Because I know your time is valuable, I'll provide highlights of the
summary right here in this email. Some exciting new things in PlayN
1.2 include:

- You can now listen for mouse and pointer events directly on layers.
- Ray brought the Flash backend up to date. Christopher &co at
King.com shipped an awesome Facebook game using it.
- There's an experimental GL20 interface that allows you to make
OpenGL calls directly. It works on Android and WebGL.
- Image.subImage relieves you from having to roll your own image tiling code.
- The iOS backend is almost entirely done. There's an ios submodule in
the new Maven archetype. A getting started guide is still needed.
- Check the release notes for all the other awesome improvements, both
large and small.

In addition to playn-1.2, I have also released tripleplay-1.2 for your
user interface creating pleasures (along with a grab bag of other
useful things). In a shocking turn of events, I have also prepared
release notes for TriplePlay:

https://github.com/threerings/tripleplay/wiki/ReleaseNotes

I have also published an ugly, disorganized, widget demo for
TriplePlay that does a mediocre job of demonstrating some of its
capabilities:

http://threerings.github.com/tripleplay/widgetdemo.html

If anyone wanted to make a proper TPUI "showcase" I would greatly
welcome the contribution. You can make much nicer UIs using TPUI than
my horrible programmer art demonstrations would suggest.

The 1.2 versions of both libraries were published to SonaType about an
hour ago, and will hopefully show up on Maven Central in the next 12
hours or so. Remember that last time we discovered that the PlayN
Maven archetype doesn't get updated until Sunday, so it will take a
few days before you can easily create new project skeletons that
include the new iOS submodule.

-- m...@samskivert.com

[Joseph Spandrusyszyn]

A quick bug report for the TriplePlay widget demo... the "Disabled text" input in is not disabled (at least not using Chrome 19 beta in Ubuntu).

Also, double-clicking on any of the buttons causes the "It's" text below the demo to be selected.

- Joe

[Michael Bayne]

On Fri, Apr 20, 2012 at 1:10 PM, Joseph Spandrusyszyn
<illa...@illandril.net> wrote:
> A quick bug report for the TriplePlay widget demo... the "Disabled text"
> input in is not disabled (at least not using Chrome 19 beta in Ubuntu).

Ha! It looks pretty disabled though. :)

> Also, double-clicking on any of the buttons causes the "It's" text below the
> demo to be selected.

That's just because I embedded the PlayN game in a normal HTML page
and didn't go to great lengths to disable the ability to select text
on the page. There's nothing PlayN or TPUI can do about that.

Thanks for the feedback!

-- m...@samskivert.com

[noblemaster]

Great work :D

[Stefa]

Hi,
with the 1.2 release the play-samples demo "1 -Sprites"
does not work anymore in Android.

Stefa

[Michael Bayne]

On Sun, Apr 22, 2012 at 12:00 PM, Stefa <aci...@gmail.com> wrote:
> with the 1.2 release the play-samples  demo "1 -Sprites"
> does not work anymore in Android.

Can you give more details?

Anyway, I commit all the changes to the samples that I've made along
the way that bring them up to date.

-- m...@samskivert.com

[Mickael Barbeaux]

Hi Michael,

Great work indeed !

But I found a bug which were introduced when you've rewrote the setSourceRect method using the newly ImageRegion class (inside ImageLayerGL) :

public void setSourceRect(float sx, float sy, float sw, float sh) {

setImage(img.subImage(sx, sy, sw, sh));

}

It works only the first time, because the Image property is initialy a Image object and is set to be a Image.Region, but next time you call the method, it makes a Image.Region from the precedently created Image.Region, etc etc...

Shouldn't it be something like :

public void setSourceRect(float sx, float sy, float sw, float sh) { final Image image = img instanceof Image.Region ? img.parent() : img;

setImage(image.subImage(sx, sy, sw, sh));

}

like it's already done inside clearSourceRect() method ?

Mickael

[Michael Bayne]

On Sun, Apr 22, 2012 at 11:12 PM, Mickael Barbeaux <mbar...@gmail.com> wrote:

Shouldn't it be something like :

public void setSourceRect(float sx, float sy, float sw, float sh) { final Image image = img instanceof Image.Region ? img.parent() : img;

setImage(image.subImage(sx, sy, sw, sh));

}

like it's already done inside clearSourceRect() method ?

You are correct sir.

I'll make the change in trunk and after allowing a few more days for other bugs to crop up, issue a 1.2.1 release with the fix.

-- m...@samskivert.com

[Mickael Barbeaux]

Thanks Michael ! :-)

[Michael Bayne]

On Mon, Apr 23, 2012 at 10:20 AM, Carsten
<carsten...@googlemail.com> wrote:
> It throws some exception at the end. I am a complete Maven beginner so
> I blame it on Maven ;)

Are you sure you ran "mvn package" first? It looks like you didn't and
it's freaking out because you're trying to run a webapp and the webapp
was not created.

-- m...@samskivert.com

[Carsten]

First I tried http://code.google.com/p/playn/wiki/GettingStarted#Running_via_Ant

run-java did work, run-html did not.

You are right. I forgot to package it :(

Executing mvn package resulted in the following Error but I guess this
is expected. Now executing mvn test -Ptest-html did work :D

[ERROR] Failed to execute goal
com.jayway.maven.plugins.android.generation2:android-maven-plugin:
3.1.1:generate-sources (default-generate-sources) on project playn-
showcase-android: Execution default-generate-sources of goal
com.jayway.maven.plugins.android.generation2:android-maven-plugin:
3.1.1:generate-sources failed: Invalid SDK: Platform/API level 11 not
available. This command should give you all you need:
[ERROR] D:\android-sdk-windows\tools\android update sdk --no-ui --
obsolete --force
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with
the command
[ERROR] mvn <goals> -rf :playn-showcase-android

On Apr 23, 7:24 pm, Michael Bayne <m...@samskivert.com> wrote:
> On Mon, Apr 23, 2012 at 10:20 AM, Carsten
>

[Michael Bayne]

On Mon, Apr 23, 2012 at 11:00 AM, Carsten
<carsten...@googlemail.com> wrote:
> [ERROR] Failed to execute goal
> com.jayway.maven.plugins.android.generation2:android-maven-plugin:
> 3.1.1:generate-sources (default-generate-sources) on project playn-
> showcase-android: Execution default-generate-sources of goal
> com.jayway.maven.plugins.android.generation2:android-maven-plugin:
> 3.1.1:generate-sources failed: Invalid SDK: Platform/API level 11 not
> available. This command should give you all you need:
> [ERROR] D:\android-sdk-windows\tools\android update sdk --no-ui --
> obsolete --force

This is because the Android development team and the Maven Android
plugin authors are engaged in a conspiracy to waste the time of as
many developers as possible. No one is immune to their sinister
machinations.

I'll update the getting started instructions to include arguments that
tell Maven only to build exactly what is needed for the test in
question. That way people who are not trying to build Android and thus
who may not have an Android SDK installed on their machine, or who may
have an Android SDK installed that does not meet the stringent
requirements of the aforementioned time-wasting cabal, can still make
forward progress. At least until the men in black come for them.

-- m...@samskivert.com

[Carsten]

Somehow it doesn't work to run the showcase on my Android phone. Now I
followed all instructions but get this error (see below)

[INFO] --- android-maven-plugin:3.1.1:generate-sources (default-
generate-sources
) @ playn-showcase-android ---
[INFO] ANDROID-904-002: Found aidl files: Count = 0
[INFO] ANDROID-904-002: Found aidl files: Count = 0
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] PlayN Showcase Metaproject ........................ SUCCESS
[4.536s]
[INFO] PlayN Showcase Core ............................... SUCCESS
[3.868s]
[INFO] PlayN Showcase Java ............................... SUCCESS
[1.296s]
[INFO] PlayN Showcase HTML ............................... SUCCESS
[57.402s]
[INFO] PlayN Showcase Android ............................ FAILURE
[0.877s]
[INFO] PlayN Showcase iOS ................................ SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1:09.929s
[INFO] Finished at: Mon Apr 23 20:02:49 CEST 2012
[INFO] Final Memory: 10M/50M
[INFO]
------------------------------------------------------------------------

[ERROR] Failed to execute goal
com.jayway.maven.plugins.android.generation2:andr

oid-maven-plugin:3.1.1:generate-sources (default-generate-sources) on

D:\git\playn-samples\showcase>mvn -f android/pom.xml android:deploy
[INFO] Scanning for projects...
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building PlayN Showcase Android 1.0-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- android-maven-plugin:3.1.1:deploy (default-cli) @ playn-
showcase-andr
oid ---
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1.941s
[INFO] Finished at: Mon Apr 23 20:03:17 CEST 2012
[INFO] Final Memory: 5M/15M
[INFO]
------------------------------------------------------------------------

[ERROR] Failed to execute goal
com.jayway.maven.plugins.android.generation2:andr

oid-maven-plugin:3.1.1:deploy (default-cli) on project playn-showcase-
android: E
xecution default-cli of goal
com.jayway.maven.plugins.android.generation2:androi
d-maven-plugin:3.1.1:deploy failed: Invalid SDK: Platform/API level 11

not avail
able. This command should give you all you need:
[ERROR] D:\android-sdk-windows\tools\android update sdk --no-ui --
obsolete --for
ce
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutio
nException

On Apr 23, 8:00 pm, Carsten <carsten.schm...@googlemail.com> wrote:
> First I triedhttp://code.google.com/p/playn/wiki/GettingStarted#Running_via_Ant

>
> run-java did work, run-html did not.
>
> You are right. I forgot to package it :(
>
> Executing mvn package resulted in the following Error but I guess this
> is expected. Now executing mvn test -Ptest-html did work :D
>
> [ERROR] Failed to execute goal
> com.jayway.maven.plugins.android.generation2:android-maven-plugin:
> 3.1.1:generate-sources (default-generate-sources) on project playn-
> showcase-android: Execution default-generate-sources of goal
> com.jayway.maven.plugins.android.generation2:android-maven-plugin:
> 3.1.1:generate-sources failed: Invalid SDK: Platform/API level 11 not
> available. This command should give you all you need:
> [ERROR] D:\android-sdk-windows\tools\android update sdk --no-ui --
> obsolete --force
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:

> [ERROR] [Help 1]http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionExcep...

[Esteban Montero]

Hi all!

I think I am experiencing the same error, only that in my case it got it when I created a Maven Project in Eclipse and the Android Project displays an error with com.jayway.maven.plugins.android.generation2:android-maven-plugin.

I have no idea how to solve it.

Thanks,

Esteban M.

--
Esteban Montero Ureña
Flex/Flash Developer
mail: esteban...@gmail.com
skype: esteban.montero

[Michael Bayne]

On Mon, Apr 23, 2012 at 11:26 AM, Carsten
<carsten...@googlemail.com> wrote:
> [ERROR] Failed to execute goal
> com.jayway.maven.plugins.android.generation2:andr
> oid-maven-plugin:3.1.1:deploy (default-cli) on project playn-showcase-
> android: E
> xecution default-cli of goal
> com.jayway.maven.plugins.android.generation2:androi
> d-maven-plugin:3.1.1:deploy failed: Invalid SDK: Platform/API level 11
> not avail
> able. This command should give you all you need:
> [ERROR] D:\android-sdk-windows\tools\android update sdk --no-ui --
> obsolete --for
> ce

I know all that gibberish spat out by Maven looks like it should just
be ignored by any civilized person, but in this case there is actually
a meaningful error message buried deep down amid the refuse:

Invalid SDK: Platform/API level 11 not available. This command
should give you all you need:

D:\android-sdk-windows\tools\android update sdk --no-ui --obsolete --force

My advice is that when something says it will "give you all you need,"
you should take it up on the offer. That's practically like getting
three wishes!

-- m...@samskivert.com

[Carsten]

I did. It still complains:

[INFO] Reactor Summary:
[INFO]
[INFO] PlayN Showcase Metaproject ........................ SUCCESS

[1.048s]

[INFO] PlayN Showcase Core ............................... SUCCESS

[5.667s]

[INFO] PlayN Showcase Java ............................... SUCCESS

[1.578s]

[INFO] PlayN Showcase HTML ............................... SUCCESS

[57.178s]
[INFO] PlayN Showcase Android ............................ SUCCESS
[1:03.827s]
[INFO] PlayN Showcase iOS ................................ FAILURE
[1.762s]

[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------

[INFO] Total time: 2:12.588s
[INFO] Finished at: Mon Apr 23 21:06:16 CEST 2012
[INFO] Final Memory: 12M/48M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-
plugin:2.3
.1:install (default-install) on project playn-showcase-ios: The
packaging for th
is project did not assign a file to the build artifact -> [Help 1]

[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please rea
d the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE

xception
[ERROR]
[ERROR] After correcting the problems, you can resume the build with
the command

[ERROR] mvn <goals> -rf :playn-showcase-ios

On Apr 23, 8:31 pm, Michael Bayne <m...@samskivert.com> wrote:
> On Mon, Apr 23, 2012 at 11:26 AM, Carsten
>

[Michael Bayne]

On Mon, Apr 23, 2012 at 12:25 PM, Carsten
<carsten...@googlemail.com> wrote:
> I did. It still complains:

Oops, I forgot to enable some jiggery pokery that allows the ios build
to NOOP even if you try to install its artifact.

If you git pull playn-samples, it should work now.

-- m...@samskivert.com