Recherche avancée

Sur d’autres sites (3915)

• phplondon conference 2008

  9 juin 2010, par Mikko Koppanen — Everything else, Imagick, PHP stuff, phplondon08

  To summarize it : I had fun My conference preparations started about two weeks before the conference. The PHPLondon fellows (Paul, Matt and Richard) asked me to do a small presentation about Imagick at the pre-conference social event. The presentation I assembled ended up being a little over two hours, give or take. The hardest part was to trim down from two hours to about 40 minutes (I didn’t want to bore the people with too many code examples). The slides are available at http://valokuva.org/talks if you need them for some reason.

  My conference day was pretty hectic from the beginning to the end. I gave a few demos about the products that we represent and the moment I opened my mouth for the first time people started leaving the room. I hope that it had something to do with the “My Framework is better than yours ?” talk starting at the same time

  I met quite a lot of new people at the conference and of course it was nice to see the familiar faces from other conferences and PHPLondon meetings. I was especially happy that I was able to answer the questions Nigel James had

  A huge thanks to the organizers for making this day possible !

• Creating buttons with Imagick

  9 juin 2010, par Mikko Koppanen — Imagick, PHP stuff

  A fellow called kakapo asked me to create a button with Imagick. He had an image of the button and a Photoshop tutorial but unfortunately the tutorial was in Chinese. My Chinese is a bit rusty so it will take a little longer to create that specific button

  The button in this example is created after this tutorial http://xeonfx.com/tutorials/easy-button-tutorial/ (yes, I googled “easy button tutorial”). The code and the button it creates are both very simple but the effect looks really nice.

  Here we go with the code :

  php

  < view plain text >

  1. < ?php
  2.  
  3. /* Create a new Imagick object */
  4. $im = new Imagick() ;
  5.  
  6. /* Create empty canvas */
  7. $im->newImage( 200, 200, "white", "png" ) ;
  8.  
  9. /* Create the object used to draw */
  10. $draw = new ImagickDraw() ;
  11.  
  12. /* Set the button color.
  13.   Changing this value changes the color of the button */
  14. $draw->setFillColor( "#4096EE" ) ;
  15.  
  16. /* Create the outer circle */
  17. $draw->circle( 50, 50, 70, 70 ) ;
  18.  
  19. /* Create the smaller circle on the button */
  20. $draw->setFillColor( "white" ) ;
  21.  
  22. /* Semi-opaque fill */
  23. $draw->setFillAlpha( 0.2 ) ;
  24.  
  25. /* Draw the circle */
  26. $draw->circle( 50, 50, 68, 68 ) ;
  27.  
  28. /* Set the font */
  29. $draw->setFont( "./test1.ttf" ) ;
  30.  
  31. /* This is the alpha value used to annotate */
  32. $draw->setFillAlpha( 0.17 ) ;
  33.  
  34. /* Draw a curve on the button with 17% opaque fill */
  35. $draw->bezier( array(
  36.           array( "x" => 10 , "y" => 25 ),
  37.           array( "x" => 39, "y" => 49 ),
  38.           array( "x" => 60, "y" => 55 ),
  39.           array( "x" => 75, "y" => 70 ),
  40.           array( "x" => 100, "y" => 70 ),
  41.           array( "x" => 100, "y" => 10 ),
  42.          ) ) ;
  43.  
  44. /* Render all pending operations on the image */       
  45. $im->drawImage( $draw ) ;
  46.  
  47. /* Set fill to fully opaque */
  48. $draw->setFillAlpha( 1 ) ;
  49.  
  50. /* Set the font size to 30 */
  51. $draw->setFontSize( 30 ) ;
  52.  
  53. /* The text on the */
  54. $draw->setFillColor( "white" ) ;
  55.  
  56. /* Annotate the text */
  57. $im->annotateImage( $draw, 38, 55, 0, "go" ) ;
  58.  
  59. /* Trim extra area out of the image */
  60. $im->trimImage( 0 ) ;
  61.  
  62. /* Output the image */
  63. header( "Content-Type : image/png" ) ;
  64. echo $im ;
  65.  
  66.  ?>

  And here is a few buttons I created by changing the fill color value :

  

  

  

• Monster Battery Power Revisited

  28 mai 2010, par Multimedia Mike — Python, Science Projects

  So I have this new fat netbook battery and I performed an experiment to determine how long it really lasts. In my last post on the matter, it was suggested that I should rely on the information that gnome-power-manager is giving me. However, I have rarely seen GPM report more than about 2 hours of charge ; even on a full battery, it only reports 3h25m when I profiled it as lasting over 5 hours in my typical use. So I started digging to understand how GPM gets its numbers and determine if, perhaps, it’s not getting accurate data from the system.

  I started poking around /proc for the data I wanted. You can learn a lot in /proc as long as you know the right question to ask. I had to remember what the power subsystem is called — ACPI — and this led me to /proc/acpi/battery/BAT0/state which has data such as :

  present :                 yes
  capacity state :          ok
  charging state :          charged
  present rate :            unknown
  remaining capacity :      100 mAh
  present voltage :         8326 mV
  

  "Remaining capacity" rated in mAh is a little odd ; I would later determine that this should actually be expressed as a percentage (i.e., 100% charge at the time of this reading). Examining the GPM source code, it seems to determine as a function of the current CPU load (queried via /proc/stat) and the battery state queried via a facility called devicekit. I couldn’t immediately find any source code to the latter but I was able to install a utility called ’devkit-power’. Mostly, it appears to rehash data already found in the above /proc file.

  Curiously, the file /proc/acpi/battery/BAT0/info, which displays essential information about the battery, reports the design capacity of my battery as only 4400 mAh which is true for the original battery ; the new monster battery is supposed to be 10400 mAh. I can imagine that all of these data points could be conspiring to under-report my remaining battery life.

  Science project : Repeat the previous power-related science project but also parse and track the remaining capacity and present voltage fields from the battery state proc file.

  Let’s skip straight to the results (which are consistent with my last set of results in terms of longevity) :

  
  
  

  So there is definitely something strange going on with the reporting— the 4400 mAh battery reports discharge at a linear rate while the 10400 mAh battery reports precipitous dropoff after 60%.

  Another curious item is that my script broke at first when there was 20% power remaining which, as you can imagine, is a really annoying time to discover such a bug. At that point, the "time to empty" reported by devkit-power jumped from 0 seconds to 20 hours (the first state change observed for that field).

  Here’s my script, this time elevated from Bash script to Python. It requires xdotool and devkit-power to be installed (both should be available in the package manager for a distro).
  

  PLAIN TEXT

  PYTHON :

  1. # !/usr/bin/python
  2.  
  3. import commands
  4. import random
  5. import sys
  6. import time
  7.  
  8. XDOTOOL = "/usr/bin/xdotool"
  9. BATTERY_STATE = "/proc/acpi/battery/BAT0/state"
  10. DEVKIT_POWER = "/usr/bin/devkit-power -i /org/freedesktop/DeviceKit/Power/devices/battery_BAT0"
  11.  
  12. print "count, unixtime, proc_remaining_capacity, proc_present_voltage, devkit_percentage, devkit_voltage"
  13.  
  14. count = 0
  15. while 1 :
  16.   commands.getstatusoutput("%s mousemove %d %d" % (XDOTOOL, random.randrange(0,800), random.randrange(0, 480)))
  17.   battery_state = open(BATTERY_STATE).read().splitlines()
  18.   for line in battery_state :
  19.     if line.startswith("remaining capacity :") :
  20.       proc_remaining_capacity = int(line.lstrip("remaining capacity : ").rstrip("mAh"))
  21.     elif line.startswith("present voltage :") :
  22.       proc_present_voltage = int(line.lstrip("present voltage : ").rstrip("mV"))
  23.   devkit_state = commands.getoutput(DEVKIT_POWER).splitlines()
  24.   for line in devkit_state :
  25.     line = line.strip()
  26.     if line.startswith("percentage :") :
  27.       devkit_percentage = int(line.lstrip("percentage :").rstrip(’\%’))
  28.     elif line.startswith("voltage :") :
  29.       devkit_voltage = float(line.lstrip("voltage :").rstrip(’V’)) * 1000
  30.   print "%d, %d, %d, %d, %d, %d" % (count, time.time(), proc_remaining_capacity, proc_present_voltage, devkit_percentage, devkit_voltage)
  31.   sys.stdout.flush()
  32.   time.sleep(60)
  33.   count += 1