Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
inkface
Home
+ new post
About this group
Join this group
inkface pygame v0.2.2
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Jayesh Salvi  
View profile  
 More options Mar 12 2009, 12:54 pm
From: Jayesh Salvi <jayeshsa...@gmail.com>
Date: Thu, 12 Mar 2009 22:24:45 +0530
Local: Thurs, Mar 12 2009 12:54 pm
Subject: inkface pygame v0.2.2
Print | Individual message | Show original | Report this message | Find messages by this author

Hi,

I just uploaded inkface-pygame v0.2.2 tarball. Here are some highlights of
changes:

1. Important changes were made to improve the performance of drawing the
elements to the pygame backend, . This involved use of pygame's advanced
facilities (special pygame sprite groups - LayeredDirty). In short, inkface
can flag only selective surfaces as dirty and only the parts of the screen
occupied by those surfaces are refreshed. Before this change the
animation.py test used to take constant ~40% CPU (irrespective of changes in
the component surfaces). With this change the CPU consumption remains around
~5% during no GUI activities and consumes higher CPU only when parts of the
GUI need redrawing (for animation.py it peaks at ~25%). This changes how
animation are programmed (fo better). Check tests/animation.py and
tests/twt.py for example. Soon I plan to release API docs to explain this
better.

2. Using the SVG elements, higher level widgets can be coded. A sample
application twitter-inkface (under apps/ directory), shows how textbox
widgets can be created. They have usual qualities of textbox (blinking
cursors, self adjusting text), but they can be themed easily y changing
corresponding SVG files. Check out the video demo mentioned below for more
details.

3. The text elements now can be drawn with colors.

4. The use of RGB24 surfaces was causing problem while running in Maemo SDK.
All cairo surfaces are now changed to ARGB32 so that this works in Maemo
diablo SDK.

5. The callback handler signatures - onKeyPress, onDraw - have been changed
slightly to be more like traditional event handler signatures. They will be
clear once API docs are ready.

To demonstrate above features, I have coded a twitter client. It is under
the apps directory in source tree. It runs with two separate themes. Each
theme consists of 2 SVG files, yet the difference in GUI's look is huge.
Here is the demo video that shows the same.

http://blip.tv/file/1869874

The performance improvement effort - as mentioned in 1 above - has made
inkface-pygame incompatible with Maemo diablo SDK. This is because the
pygame features like LayeredDirty are available only in 1.8.x while diablo
has pygame version 1.7.x. I am trying to fix this by making use of old
pygame features instead of LayeredDirty.

Comments are welcome.
--
Jayesh


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google