Release a gem? about jrubyfx HOT 10 CLOSED

👍

from jrubyfx.

There are several TODO: flush this outs in jfx_imports and some constants/enums are not properly rubified (some work is on my branch, some I have not pushed but needs cleanup. Aside from that, the gemspec is waiting to be released. I might be able to cleanup the constants I have later today

from jrubyfx.

@byteit101 no huge hurry unless you have the time, but once you say things are cool we can push out a release then.

from jrubyfx.

ok, i just PR'd most of my working tree. There are still some minor TODO's in the code and some missing overrides of conversions, but no deal breakers.

What else is in my working tree? huge speedups by caching all the metaprogramming and reflection by writing it out to a standard .rb file, though it seems kind of hacky. any opinions on this anyone?

from jrubyfx.

Does not sound important in the scheme of putting out a release. Meaning those perf additions should be added after this release.

Better performance is worth it if performance can become a real issue. If it is faster setup of scene versus faster execution of events then added complexity might not be worth it unless people keep complaining about startup (and it is not mostly just jruby startup). If it is something which gets executed like events then it is probably definitely worth the trouble.

from jrubyfx.

I figured. you can push this release then to rubygems.

Currently the huge perf draw is the Enum injection stuff, which obviously must be done before the scene is created. simply by caching all the metaprogramming, I was able to get startup time from 16 second total (10s jrubyfx startup) to 7 seconds total (1.5s average jrubyfx startup). I've also toyed with lazy imports/injections, but have not benchmarked it yet. The current bottleneck is java_import'ing everything takes a full second.

from jrubyfx.

I put out the gem untested and after releasing I noticed homepage was incorrect (committed fix). So hopefully this things will fly high and free! 0.9.2 no doubt will be from feedback from happy users wanting more. Thanks for all the work.

from jrubyfx.

Yea, we need a proper test suite. I currently run samples/test_all_the_samples.rb which just runs all the samples we have and look for any error messages, but its woefully incomplete.

from jrubyfx.

Testing GUI libraries make me shiver, but we should get something going.

-Tom

On Thu, Jan 24, 2013 at 1:07 PM, byteit101 [email protected] wrote:

Yea, we need a proper test suite. I currently run
samples/test_all_the_samples.rb which just runs all the samples we have and
look for any error messages, but its woefully incomplete.

—
Reply to this email directly or view it on GitHubhttps://github.com/nahi/jrubyfx/issues/11#issuecomment-12667475.

blog: http://blog.enebo.com twitter: tom_enebo
mail: [email protected]

from jrubyfx.

my thoughts exactly...

from jrubyfx.