1. 30 Dec, 2012 1 commit
  2. 28 Dec, 2012 3 commits
  3. 09 Aug, 2012 1 commit
  4. 13 Dec, 2011 1 commit
  5. 10 Dec, 2011 1 commit
    • Philip Withnall's avatar
      Bug 665692 — Use constructors correctly · 2247cdd5
      Philip Withnall authored
      In order to allow libfolks to be used from introspected languages (such as
      Python) properly, we need to correctly use the GObject construction process,
      rather than generating code which does all object initialisation inside
      a *_new() function. This involves moving lots of code into construct{} blocks.
      
      There are some complications; mostly the need for various private variables to
      now be exposed as construct-only properties. Most of them should've been
      anyway.
      
      Other complications arose from the fact that moving code to a construct{}
      block can subtly change the execution order of the code if the Object() call
      lists properties which are non-construct properties (e.g. the “alias” property
      of a Persona). The setters for these properties will now be called _after_ the
      construct{} code, whereas previously they would've been called beforehand.
      This rears its head in Tpf.Persona, but hopefully nowhere else.
      
      Closes: bgo#665692
      2247cdd5
  6. 10 Nov, 2011 1 commit
  7. 23 Jun, 2011 6 commits
  8. 30 Dec, 2010 1 commit
  9. 26 Aug, 2010 1 commit
  10. 08 Jul, 2010 1 commit
  11. 30 Jun, 2010 2 commits
  12. 29 Jun, 2010 2 commits