1. 05 Jul, 2015 5 commits
  2. 04 Jul, 2015 8 commits
  3. 03 Jul, 2015 8 commits
  4. 01 Jul, 2015 6 commits
    • Carlos Garnacho's avatar
      1d59e207
    • Carlos Garnacho's avatar
      tracker-miner-fs: Delete nie:dataSources on update · edf07949
      Carlos Garnacho authored
      Decorators should be updating again all relevant information, so ensure
      their nie:dataSource is deleted for these to kick in again.
      
      This used to be unnecessary because updated items just went to the
      internal decorator queue, without further checks. Now that the decorators
      query the database for the next items missing that dataSource, it is
      crucial to do this somewhere.
      edf07949
    • Carlos Garnacho's avatar
      tracker-extract: tell what the error really means · 331d5753
      Carlos Garnacho authored
      The current one is not really intuitive.
      331d5753
    • Carlos Garnacho's avatar
      libtracker-miner: Reduce TrackerDecorator file cache size · 50ea39fe
      Carlos Garnacho authored
      Instead of keeping all items in memory, a small cache is kept of upcoming
      files to be processed, querying the database again for files missing the
      nie:dataSource when the cache has been flushed. When no further items are
      processed, the miner is stopped. Whenever the prioritized rdf:types list
      changes, the cache is dropped, just to query again with the new order kept
      into account.
      
      This reduces the potential memory usage of tracker-extract, it would
      previously would grow linearly with the number of files left to be
      inspected, which might bring in some memory pressure on certain scenarios.
      
      On the downside, this obviously makes the decorator a little bit slower,
      due to more queries happening (as opposed to a huge one), and at times the
      decorator is idle waiting to know what else to do.
      50ea39fe
    • Carlos Garnacho's avatar
      tracker-extract: Keep ref on recovery files · 5d1f9110
      Carlos Garnacho authored
      The hashtable expects its own ref here, otherwise we get critical
      warnings after processing that item.
      5d1f9110
    • Carlos Garnacho's avatar
      docs: delete xml folder before regenerating ontology docs · 68e4194c
      Carlos Garnacho authored
      Otherwise it simply fails if there happens to be stale data
      68e4194c
  5. 30 Jun, 2015 5 commits
    • Carlos Garnacho's avatar
      distcheck fix · 11eba231
      Carlos Garnacho authored
      11eba231
    • Carlos Garnacho's avatar
      update docs .gitignore · c9ae041d
      Carlos Garnacho authored
      c9ae041d
    • Carlos Garnacho's avatar
      docs: Delete dia diagrams, and pre-generated PNGs · 701810bc
      Carlos Garnacho authored
      Those weren't that much clear nor useful, those are deleted in
      a separate commit in case we want to rescue and rework them
      someday.
      701810bc
    • Carlos Garnacho's avatar
      docs: Delete ontology graph tool · 80f18a67
      Carlos Garnacho authored
      This is now unused, so remove the tool, and the configure.ac check
      for fdp.
      80f18a67
    • Carlos Garnacho's avatar
      docs: Rework ontology docs generation entirely · 60354f20
      Carlos Garnacho authored
      Ontology docs weren't in a much good shape, besides many ontologies
      being seriously underdocumented (something which should improve
      separately), the generated docs were little more than a data dump,
      and the diagrams shown were broken, confusing, or both. This all
      amounts to quite counter-productive developer docs.
      
      So the ontology docs have been refurbished, the per-ontology
      descriptions are still useful, but have been stripped of all images,
      and the docs overall are now completely class-centric, per
      rdfs:Resource subclass we now get:
      
      - Ascii diagram of its local hierarchy, up to all its ancestors and
        down to all its direct children.
      - All properties that affect the specific class. This is notably
        more intuitive now as there's properties defined on one ontology
        that are in the domain of classes in another ontology, something
        which you couldn't get at a glance in the previous docs
      - It clearly states which properties supersede which superproperties,
        which again makes it easier if those apply for the class at hand.
      
      The result feels quite neater, and will indeed be more resembling
      to other gtk-doc generated API docs.
      60354f20
  6. 29 Jun, 2015 1 commit
  7. 23 Jun, 2015 1 commit
  8. 20 Jun, 2015 1 commit
  9. 16 Jun, 2015 1 commit
  10. 31 May, 2015 2 commits
  11. 28 May, 2015 1 commit
  12. 26 May, 2015 1 commit