You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I am not a robot, but I suppose for the purpose of this visit I might as
well be. I just wanted to drop by real quick to check if you are at all
familiar with the jMonkeyEngine project. It seems our projects might have a
thing or two in common.
http://jmonkeyengine.com/blog/blog/2010/02/10/android-support-confirmed-
for-jme3/
http://www.jmonkeyengine.com/forum/index.php?topic=13176.0
http://www.jmonkeyengine.com/forum/index.php?topic=13217.0
We are on the lookout for an Android developer to help us bring jME3's
preliminary Android implementation to a mature, fully functional state.
http://docs.google.com/View?id=dhkt6vsf_251c54bg9hp
Maybe you could be that developer? or, maybe you know someone who might be.
Naturally we'd also appreciate having more testers or plain Android-savvy
people around in our community. Any reason at all for you to contact us,
feel free! Contact information can be found in the docs link above.
Thanks for your time,
~ Erlend Sogge Heggen
Original issue reported on code.google.com by e.so...@gmail.com on 27 Apr 2010 at 6:31
The text was updated successfully, but these errors were encountered:
I'm sorry, I had a similar complaint about this and appreciate the notice. It's
just that I couldn't find any other way of getting in touch with you, at least
not with the time at my disposal. I always checked to see if users had checked
off their 'display e-mail' setting in GoogleCode, which applies the '...'
between my e-mail like you see it above. Besides that, finding an alternative
way of contacting a GoogleCode developers quickly proved surprisingly difficult.
I certainly was not trying to hijack your project, but I do sincerely apologize
for the disruption and promise I won't be bothering you project again.
~ Erlend
Original comment by e.so...@gmail.com on 9 Jun 2010 at 10:20
Original issue reported on code.google.com by
e.so...@gmail.com
on 27 Apr 2010 at 6:31The text was updated successfully, but these errors were encountered: