New Gideros Library of Classes!

Comments

• hgvyas123 Guru

  November 2013

  kool Thnx for sharing

  +1 -1Share on Facebook
• keszegh Member

  November 2013

  thanks for sharing.

  Longtitle Productions, creator of
  Fragmenter - animated loop machine and IKONOMIKON - the memory game

  +1 -1Share on Facebook
• ar2rsawseen Maintainer

  November 2013

  @amaximov wow that looks awesome.
  It reminds me the framework I started:
  http://www.giderosmobile.com/forum/discussion/1780/extending-gideros/p1
  
  So you can also peak some stuff from there

  Likes: phongtt

  http://appcodingeasy.com/Gideros-Mobile

  +1 -1 (+1 / -0 )Share on Facebook
• amaximov Member

  November 2013

  @ar2rsawseen pretty cool I'll look into it!

  http://intoitgames.com/
  
  https://play.google.com/store/apps/developer?id=Into-It+Games
  
  http://appstore.com/LidiaMaximova

  +1 -1Share on Facebook
• amaximov Member

  November 2013 edited November 2013

  Update! Added new feature: TTFont caching
  
  Imagine doing this with regular Gideros.

  local f1 = TTFont.new("Fonts.ttf", 25, "Text", true)   local t1 = Text.new(f1, "Text")   print(application:getTextureMemoryUsage())   local f2 = TTFont.new("Fonts.ttf", 25, "Text", true)   local t2 =Text.new(f2, "Text")   print(application:getTextureMemoryUsage())

  You would first get a printout of "x" followed by "2x" showing a doubling of texture memory usage despite using the same font with the same constructor properties.
  
  With the added features in Display lib texture memory usage will NOT increase and will simply reuse the cached font. In fact f1 and f2 will point to the exact same object.
  
  Now you might say, why would you need this? Why not just do:

  local f1 = TTFont.new("Fonts.ttf", 25, "Text", true)   local t1 =Text.new(f1, "Text")   local f1 =Text.new(f1, "Text")   print(application:getTextureMemoryUsage())

  This is in fact the most logical approach but would involve global variables if you were using similar fonts in different .lua files!
  
  This feature basically allows you to avoid global entirely and reuse fonts across modules.
  
  There is a catch however, you MUST provide cache characters to your font constructor or you will not experience these texture memory savings.
  
  Small explanation available in the DOCS: https://bitbucket.org/IntoItGames/gideros-display/overview
  
  Small feature, maybe unnecessary, but I plan on using it

  http://intoitgames.com/
  
  https://play.google.com/store/apps/developer?id=Into-It+Games
  
  http://appstore.com/LidiaMaximova

  +1 -1Share on Facebook