1. 24 Aug, 2010 1 commit
  2. 12 Aug, 2010 1 commit
  3. 10 Aug, 2010 12 commits
  4. 04 Jul, 2010 1 commit
  5. 26 May, 2010 1 commit
  6. 28 Oct, 2009 1 commit
  7. 15 Sep, 2009 1 commit
  8. 23 Jun, 2009 1 commit
  9. 29 Jan, 2009 1 commit
    • Nigel McNie's avatar
      (#3063) Make blocktype configuration forms change if they are in a template. · d9f2144b
      Nigel McNie authored
      Now they do things like not making it compulsory to choose an artefact
      if it's a template (as the creator might just want to put the block
      there), and removing some options that only make sense in Views.
      There's a parameter for instance_config_form and artefactchooser_element
      to allow the Blocktype to detemine whether it's in a template easily.
  10. 17 Dec, 2008 1 commit
    • Nigel McNie's avatar
      (#3063) Remove copy_allowed in favour of allowed_in_view. Also remove · 099dc5b3
      Nigel McNie authored
      copy_artefacts_allowed is unnecessary as it's only called if the copy
      type is 'full', and there's now no way that you would want to fully
      copy a block and not copy the artefacts inside it.
      Some other API tidyups have been done - default_artefact_config has been
      renamed to rewrite_blockinstance_config and had a method signature
      change to be a bit more flexible.
      The copyconfig field of the View object is gone too, no longer required.
  11. 16 Dec, 2008 1 commit
    • Nigel McNie's avatar
      (#3063) part 2: Hide blocktypes that don't make sense when making a · 7599ec0c
      Nigel McNie authored
      This means that blog/profile/resume blocktypes don't show up in
      group/institution/site Views.
      This is controlled through a new Blocktype method - allowed_in_view.
      Various code had to be changed to listen to this method, mostly around
      the display of the category browser.
      When making a template, all blocktypes are available.
      Part 3 is to change the configuration forms to be more sensible when
      editing a template, and then testing what happens when blocktypes are
      rendered somewhere that they "shouldn't" be - e.g. a My Friends block in
      a group View.
  12. 18 Nov, 2008 1 commit
  13. 15 Sep, 2008 3 commits
  14. 12 Sep, 2008 1 commit
  15. 15 Aug, 2008 1 commit
  16. 13 Jul, 2008 1 commit
  17. 21 Apr, 2008 1 commit
    • Nigel McNie's avatar
      Make most blocktype titles editable. · 8b400358
      Nigel McNie authored
      This patch makes most blocktypes have no title set by default when created. For those that used to set their own titles, if no title is set after the configuration form is submitted, then they get the chance to set the title.
      So for example, the RSS block will start with an empty title, but if the user doesn't set it, the title will be the title of the feed that is being syndicated.
      Blocks like 'textbox' still keep their defaults, because they don't have any special case way of setting their own titles.
  18. 16 Feb, 2008 2 commits
  19. 04 Dec, 2007 1 commit
  20. 21 Nov, 2007 1 commit
  21. 20 Nov, 2007 1 commit
    • Nigel McNie's avatar
      First shot at entireresume blocktype. · 0f1c8d9d
      Nigel McNie authored
      One suggestion for improvement is to have several layout templates and allow the user to pick one.
      For now, it makes sure that all resume fields a user has are displayed in the block at all times (excluding goals and skills)