1. 08 Eki, 2010 1 kayıt (commit)
  2. 04 Eki, 2010 1 kayıt (commit)
  3. 15 Eyl, 2010 1 kayıt (commit)
  4. 21 Haz, 2010 1 kayıt (commit)
  5. 15 Haz, 2010 2 kayıt (commit)
  6. 11 Haz, 2010 1 kayıt (commit)
  7. 09 Haz, 2010 1 kayıt (commit)
  8. 04 Haz, 2010 1 kayıt (commit)
  9. 31 May, 2010 1 kayıt (commit)
  10. 06 May, 2010 1 kayıt (commit)
  11. 05 May, 2010 1 kayıt (commit)
  12. 21 Nis, 2010 1 kayıt (commit)
  13. 17 Nis, 2010 1 kayıt (commit)
  14. 16 Nis, 2010 2 kayıt (commit)
  15. 14 Nis, 2010 1 kayıt (commit)
  16. 09 Nis, 2010 1 kayıt (commit)
  17. 07 Nis, 2010 1 kayıt (commit)
  18. 31 Mar, 2010 2 kayıt (commit)
  19. 30 Mar, 2010 1 kayıt (commit)
  20. 13 Nis, 2010 1 kayıt (commit)
  21. 23 Mar, 2010 2 kayıt (commit)
  22. 11 Mar, 2010 1 kayıt (commit)
  23. 04 Mar, 2010 1 kayıt (commit)
  24. 03 Mar, 2010 1 kayıt (commit)
  25. 25 Şub, 2010 1 kayıt (commit)
  26. 19 Şub, 2010 1 kayıt (commit)
  27. 17 Şub, 2010 1 kayıt (commit)
  28. 15 Şub, 2010 2 kayıt (commit)
  29. 12 Şub, 2010 2 kayıt (commit)
  30. 08 Şub, 2010 1 kayıt (commit)
  31. 04 Şub, 2010 1 kayıt (commit)
  32. 01 Şub, 2010 1 kayıt (commit)
    • Frank Schoenheit [fs]'s avatar
      autorecovery: more sophisticated configuration data for interaction handlers · 6a35ea72
      Frank Schoenheit [fs] yazdı
      The generic css.task.InteractionHandler implementation in module uui is now able to instantiate "sub handlers", i.e.
      components to delegate a request to, based on the type of the request, and some configuration data.
      
      The "old" (and now deprecated) configuration scheme at org.openoffice.ucb.InteractionHandler did not contain type
      information, so any handlers registered there were always called when no default implementation for a given request
      was available.
      
      The "new" configuration scheme at org.openoffice.Interaction contains UNO type information. That is, a given handler
      implementation can declare itself responsible for an arbitrary set of UNO types, and for each of those types, whether
      it is also responsible for sub types.
      The generic interaction handler implementation uses this configuration data, when it encounteres an interaction
      request it cannot fullfill itself, to instantiate a component to delegate the request to.
      
      As with the "old" data, such a component is required to support the css.task.XInteractionHandler2 interface. Also,
      if it supports css.lang.XInitialization, then it will be initialized with a name-value pair, the name being
      "Parent", the value being the XWindow interface of the parent window for any message boxes.
      
      As an examplary implementation for this feature, the css.sdb.InteractionHandler has been deprecated. Now the
      css.sdb.DatabaseInteractionHandler is reponsible for database-related interactions, and the new configuration scheme
      is pre-filled with data assigning this responsibility.
      
      Consequently, a lot of places previously creating an css.sdb.InteractionHandler have been modified to create the
      default css.task.InteractionHandler.
      6a35ea72
  33. 26 Ock, 2010 1 kayıt (commit)
  34. 22 Ock, 2010 1 kayıt (commit)