My favorites | Sign in
Project Logo
                
Details: Show all Hide all

Last 7 days

  • Dec 09, 2009
    Plans (Immediate and long-range plans for PulpCore) Wiki page commented on by odayibasi   -   It's wonderful api. Simple , easy and powerful.
    It's wonderful api. Simple , easy and powerful.

Last 30 days

Earlier this year

  • Nov 09, 2009
    issue 29 (Allow compression level to be passed into PNGWriter) commented on by brackeen   -   This is incorrect because the PNG format specifies "At present, only compression method 0 (deflate/inflate compression with a sliding window of at most 32768 bytes) is defined.". So, 1) the default should use Deflater.DEFAULT_COMPRESSION and 2) the compression method byte should always be 0. Also, the new write() method should throw an exception if the compression level is not 1-9 or -1. Unfortunately, even with compression level 9, the compression won't be as good as the PNG encoder provided in tools/assettools/png which does analysis and optimization.
    This is incorrect because the PNG format specifies "At present, only compression method 0 (deflate/inflate compression with a sliding window of at most 32768 bytes) is defined.". So, 1) the default should use Deflater.DEFAULT_COMPRESSION and 2) the compression method byte should always be 0. Also, the new write() method should throw an exception if the compression level is not 1-9 or -1. Unfortunately, even with compression level 9, the compression won't be as good as the PNG encoder provided in tools/assettools/png which does analysis and optimization.
  • Nov 09, 2009
    issue 29 (Allow compression level to be passed into PNGWriter) reported by daniel.watling   -   It would be nice to allow the setting of the compression level when using PNGWriter instead of defaulting to no compression. I've attached a patch that will add a second (optional) parameter to the PNGWriter.write method. The value for this second parameter can be any of the compression levels found in "Deflater". The default is no compression.
    It would be nice to allow the setting of the compression level when using PNGWriter instead of defaulting to no compression. I've attached a patch that will add a second (optional) parameter to the PNGWriter.write method. The value for this second parameter can be any of the compression levels found in "Deflater". The default is no compression.
  • Nov 08, 2009
    r891 (Buttons can have an optional disabled appearance (Dan Watlin...) committed by brackeen   -   Buttons can have an optional disabled appearance (Dan Watling).
    Buttons can have an optional disabled appearance (Dan Watling).
  • Oct 06, 2009
    r890 (Make it easier for GC to remove memory after an app quits (n...) committed by brackeen   -   Make it easier for GC to remove memory after an app quits (no static fields in Assets)
    Make it easier for GC to remove memory after an app quits (no static fields in Assets)
  • Oct 06, 2009
    r889 (Added root.update(0) when paused (thanks to arya)) committed by brackeen   -   Added root.update(0) when paused (thanks to arya)
    Added root.update(0) when paused (thanks to arya)
  • Oct 06, 2009
    r888 (Workaround for applet.destroy() not called on Safari 4 + Sno...) committed by brackeen   -   Workaround for applet.destroy() not called on Safari 4 + Snow Leopard.
    Workaround for applet.destroy() not called on Safari 4 + Snow Leopard.
  • Sep 29, 2009
    r887 (Moved static field to an instance field in case of a future ...) committed by brackeen   -   Moved static field to an instance field in case of a future muti-threaded renderer.
    Moved static field to an instance field in case of a future muti-threaded renderer.
  • Sep 27, 2009
    r886 (Fixed clipping bug when a Group with a back buffer is rotate...) committed by brackeen   -   Fixed clipping bug when a Group with a back buffer is rotated.
    Fixed clipping bug when a Group with a back buffer is rotated.
  • Sep 27, 2009
    r885 (Fixed two dirty rectangle bugs for moving Groups with a back...) committed by brackeen   -   Fixed two dirty rectangle bugs for moving Groups with a back buffer or filter. This was most notable when the Group was moving diagonally, causing two dirty rectangles to intersect at an angle.
    Fixed two dirty rectangle bugs for moving Groups with a back buffer or filter. This was most notable when the Group was moving diagonally, causing two dirty rectangles to intersect at an angle.
  • Sep 22, 2009
    Donate (Support PulpCore development) Wiki page edited by brackeen   -   Revision r884 Featured Donate page
    Revision r884 Featured Donate page
  • Sep 22, 2009
    WikiSidebar (Wiki Sidebar) Wiki page edited by brackeen   -   Revision r883 Added Donate wiki page.
    Revision r883 Added Donate wiki page.
  • Sep 22, 2009
    Donate (Support PulpCore development) Wiki page added by brackeen   -   Revision r882 Added Donate wiki page.
    Revision r882 Added Donate wiki page.
  • Sep 19, 2009
    r881 (Fixes for simultaneous playback (part 3 - Ogg fix)) committed by brackeen   -   Fixes for simultaneous playback (part 3 - Ogg fix)
    Fixes for simultaneous playback (part 3 - Ogg fix)
  • Sep 19, 2009
    r880 (Fixes for simultaneous playback (forgot the include this fil...) committed by brackeen   -   Fixes for simultaneous playback (forgot the include this file)
    Fixes for simultaneous playback (forgot the include this file)
  • Sep 19, 2009
    r879 (Fixes for simultaneous playback) committed by brackeen   -   Fixes for simultaneous playback
    Fixes for simultaneous playback
  • Sep 15, 2009
    r878 (Moved ImageSprite.setPixelLevelChecks(boolean) to Sprite; Ad...) committed by brackeen   -   Moved ImageSprite.setPixelLevelChecks(boolean) to Sprite; Added pixel-level checks to Label
    Moved ImageSprite.setPixelLevelChecks(boolean) to Sprite; Added pixel-level checks to Label
  • Sep 12, 2009
    r877 ( * API: Added CoreSystem.isMacOSX106() * Core: BufferedSt...) committed by brackeen   -   * API: Added CoreSystem.isMacOSX106() * Core: BufferedStrategy now used on Snow Leopard
    * API: Added CoreSystem.isMacOSX106() * Core: BufferedStrategy now used on Snow Leopard
  • Sep 12, 2009
    r876 (Attempt to fix IllegalStateException) committed by brackeen   -   Attempt to fix IllegalStateException
    Attempt to fix IllegalStateException
  • Sep 12, 2009
    r876 (Attempt to fix IllegalStateException) committed by brackeen   -   Attempt to fix IllegalStateException
    Attempt to fix IllegalStateException
  • Sep 12, 2009
    r876 (Attempt to fix IllegalStateException) committed by brackeen   -   Attempt to fix IllegalStateException
    Attempt to fix IllegalStateException
  • Sep 10, 2009
    r875 (Print stack trace to System.out if there is no uncaughtExcep...) committed by brackeen   -   Print stack trace to System.out if there is no uncaughtExceptionScene
    Print stack trace to System.out if there is no uncaughtExceptionScene
  • Sep 05, 2009
    Plans (Immediate and long-range plans for PulpCore) Wiki page commented on by fvan...@terranovita.com   -   Looking forward to Android development with pulpcore. I currently created a prototype for an mmorpg client in pulpcore. It's the best browser based java engine on the market atm!
    Looking forward to Android development with pulpcore. I currently created a prototype for an mmorpg client in pulpcore. It's the best browser based java engine on the market atm!
  • Aug 24, 2009
    r874 (Group.isPick and Group.isPickEnabledAndVisible return true i...) committed by brackeen   -   Group.isPick and Group.isPickEnabledAndVisible return true if the group is an ancestor of the pick. (Previously, those two methods always returned false for Groups)
    Group.isPick and Group.isPickEnabledAndVisible return true if the group is an ancestor of the pick. (Previously, those two methods always returned false for Groups)
  • Aug 20, 2009
    r873 (Added a looping timeline test) committed by brackeen   -   Added a looping timeline test
    Added a looping timeline test
  • Aug 20, 2009
    Features (Summary of PulpCore features) Wiki page edited by brackeen   -   Revision r872 Added note on browsers' full-page zoom
    Revision r872 Added note on browsers' full-page zoom
  • Aug 20, 2009
    r871 (Fixed browser page zooming issue) committed by brackeen   -   Fixed browser page zooming issue
    Fixed browser page zooming issue
  • Aug 07, 2009
    issue 18 (Port to Desktop/OpenGL) commented on by rajsite   -   Has any headway been made in making pulpcore run in swing, like illustrated in this old thread? http://groups.google.com/group/pulpcore/browse_thread/thread/6d74e7eeded6410e I would have posted in there, but it's a pretty old thread :D @Piotr.Korzuszek I tried the jnlp apps a few months ago and they looked really promising, but I am not able to access your site anymore. Could you post a link to the git repository if you are still making it available?
    Has any headway been made in making pulpcore run in swing, like illustrated in this old thread? http://groups.google.com/group/pulpcore/browse_thread/thread/6d74e7eeded6410e I would have posted in there, but it's a pretty old thread :D @Piotr.Korzuszek I tried the jnlp apps a few months ago and they looked really promising, but I am not able to access your site anymore. Could you post a link to the git repository if you are still making it available?
  • Aug 04, 2009
    Eclipse (Setup in Eclipse) Wiki page commented on by rajsite   -   It might be of interest to note that the newest version of Eclipse ( Eclipse Galileo / Version 3.5 released June 24, 2009) now has the newest version of Ant ( Ant 1.7.1) so pulpcore builds right out of the box! People using older versions of eclipse will have to install Ant 1.7.1 manually.
    It might be of interest to note that the newest version of Eclipse ( Eclipse Galileo / Version 3.5 released June 24, 2009) now has the newest version of Ant ( Ant 1.7.1) so pulpcore builds right out of the box! People using older versions of eclipse will have to install Ant 1.7.1 manually.
  • Aug 02, 2009
    r870 (Updated unit tests) committed by brackeen   -   Updated unit tests
    Updated unit tests
  • Aug 02, 2009
    issue 24 (TimeLine.moveTo takes sprite's base properties) Status changed by brackeen   -   Thanks for the patch. I didn't use the exact code because it didn't include Int or Color properties, or include unit tests. But the fix is based off of the patch.
    Status: Fixed
    Thanks for the patch. I didn't use the exact code because it didn't include Int or Color properties, or include unit tests. But the fix is based off of the patch.
    Status: Fixed
  • Aug 02, 2009
    r869 (Timeline animateTo() methods now animate from the property's...) committed by brackeen   -   Timeline animateTo() methods now animate from the property's value when the tween starts rather than the property's value when the tween is created. ( Issue 24 ). Also added unit tests.
    Timeline animateTo() methods now animate from the property's value when the tween starts rather than the property's value when the tween is created. ( Issue 24 ). Also added unit tests.
  • Aug 02, 2009
    r868 (Added Group mathods: setClippedToBounds(boolean), getClipped...) committed by brackeen   -   Added Group mathods: setClippedToBounds(boolean), getClippedToBounds(), setBackBuffered(boolean), isBackBuffered(). Deprecated removeBackBuffer() and createBackBuffer().
    Added Group mathods: setClippedToBounds(boolean), getClippedToBounds(), setBackBuffered(boolean), isBackBuffered(). Deprecated removeBackBuffer() and createBackBuffer().
  • Aug 02, 2009
    issue 25 (copy constructor "new AnimatedImage(AnimatedImage image)" do...) Status changed by brackeen   -   Added AnimatedImage(AnimatedImage image, boolean copyState) constructor
    Status: Fixed
    Added AnimatedImage(AnimatedImage image, boolean copyState) constructor
    Status: Fixed
  • Aug 02, 2009
    issue 26 (AnimatedImage.isPlaying() returns wrong result just after An...) Status changed by brackeen   -   Clarified JavaDoc on the isPlaying() method
    Status: WontFix
    Clarified JavaDoc on the isPlaying() method
    Status: WontFix
  • Aug 02, 2009
    r867 (Added AnimatedImage(AnimationImage image, boolean copyState)...) committed by brackeen   -   Added AnimatedImage(AnimationImage image, boolean copyState) constructor; clarified isPlaying() JavaDoc
    Added AnimatedImage(AnimationImage image, boolean copyState) constructor; clarified isPlaying() JavaDoc
  • Aug 02, 2009
    issue 28 (A TimelineEvent is *always* executed at the begining of a ch...) Status changed by brackeen   -  
    Status: Fixed
    Status: Fixed
  • Aug 02, 2009
    issue 27 (TimelineEvent in the middle of a Timeline is executed more t...) Status changed by brackeen   -  
    Status: Fixed
    Status: Fixed
  • Aug 02, 2009
    r866 (Adjusted error range for a couple tests) committed by brackeen   -   Adjusted error range for a couple tests
    Adjusted error range for a couple tests
  • Aug 02, 2009
    r865 (Fixed Issue 27 and Issue 28, added unit tests) committed by brackeen   -   Fixed Issue 27 and Issue 28 , added unit tests
    Fixed Issue 27 and Issue 28 , added unit tests
  • Aug 01, 2009
    issue 28 (A TimelineEvent is *always* executed at the begining of a ch...) reported by elazarl   -   1. produce a new scene, in the load() method put the following code: <code> FilledSprite s = new FilledSprite(0,0,30,30,YELLOW); add(s); Timeline tl = new Timeline(); Timeline sec = new Timeline(); tl.after().move(s, 50,0,0,0,2000); sec.move(s, 0,0, 100, 100, 2000); final Int i = new Int(0); sec.after().addEvent(new TimelineEvent(10) { @Override public void run() { i.set(i.get()+1); CoreSystem.print("run"+i.get()); } }); tl.after().add(sec); addTimeline(tl); </code> 2. Execute the scene We expect to see, in the following order: 1) The yellow square moves from (50,0) to (0,0), during 2 seconds. 2) The yellow scene moves from (0,0) to (100,100) during 2 seconds. 3) A "run1" line appears in the console. What we actually see is: 1) The yellow square moves from (50,0) to (0,0), during 2 seconds. 2) A "run1" line appears in the console. 3) The yellow scene moves from (0,0) to (100,100) during 2 seconds. 4) A "run2" line appears in the console. 5) A "run3" line appears in the console. Note that the repetition of run2 and run3 is probably related to issue 27 [1] Also note that this happens only if the child Timeline 'sec' should happen in the middle of the father Timeline 'tl'. This happens with the latest svn version [1] http://code.google.com/p/pulpcore/issues/detail?id=27 Please provide any additional information below.
    1. produce a new scene, in the load() method put the following code: <code> FilledSprite s = new FilledSprite(0,0,30,30,YELLOW); add(s); Timeline tl = new Timeline(); Timeline sec = new Timeline(); tl.after().move(s, 50,0,0,0,2000); sec.move(s, 0,0, 100, 100, 2000); final Int i = new Int(0); sec.after().addEvent(new TimelineEvent(10) { @Override public void run() { i.set(i.get()+1); CoreSystem.print("run"+i.get()); } }); tl.after().add(sec); addTimeline(tl); </code> 2. Execute the scene We expect to see, in the following order: 1) The yellow square moves from (50,0) to (0,0), during 2 seconds. 2) The yellow scene moves from (0,0) to (100,100) during 2 seconds. 3) A "run1" line appears in the console. What we actually see is: 1) The yellow square moves from (50,0) to (0,0), during 2 seconds. 2) A "run1" line appears in the console. 3) The yellow scene moves from (0,0) to (100,100) during 2 seconds. 4) A "run2" line appears in the console. 5) A "run3" line appears in the console. Note that the repetition of run2 and run3 is probably related to issue 27 [1] Also note that this happens only if the child Timeline 'sec' should happen in the middle of the father Timeline 'tl'. This happens with the latest svn version [1] http://code.google.com/p/pulpcore/issues/detail?id=27 Please provide any additional information below.
  • Aug 01, 2009
    issue 27 (TimelineEvent in the middle of a Timeline is executed more t...) reported by elazarl   -   1. produce a scene with the following code in it's load() method: <code> Timeline tl = new Timeline(); final Int i = new Int(0); tl.move(s, 0,0, 100, 100, 2000); tl.after().addEvent(new TimelineEvent(10) { @Override public void run() { i.set(i.get()+1); CoreSystem.print("run"+i.get()); } }); addTimeline(tl); </code> I expect to see in the console output a single line: run1 What I actually see is two lines: run1 run2 Note that this is not related to the fact that the TimelineEvent is residing within a child Timeline, since if you do `tl.at(0).addEvent(...)` the event would occur once only. What version of the product are you using? On what operating system? Please provide any additional information below.
    1. produce a scene with the following code in it's load() method: <code> Timeline tl = new Timeline(); final Int i = new Int(0); tl.move(s, 0,0, 100, 100, 2000); tl.after().addEvent(new TimelineEvent(10) { @Override public void run() { i.set(i.get()+1); CoreSystem.print("run"+i.get()); } }); addTimeline(tl); </code> I expect to see in the console output a single line: run1 What I actually see is two lines: run1 run2 Note that this is not related to the fact that the TimelineEvent is residing within a child Timeline, since if you do `tl.at(0).addEvent(...)` the event would occur once only. What version of the product are you using? On what operating system? Please provide any additional information below.
 
Hosted by Google Code