Last modified by Ecaterina Moraru on 2013/11/13 12:49
  • Marta Girdea
    Marta Girdea, 2010/04/28 14:53

    This looks great emoticon_smile

    It would be nice to have some options for the HTML Export too, not just because the HTML tab looks lonely, but also because some customization is useful and people have been asking for it. For example, allow to export with/without the menus, panels, annotations, comments, allow to export only the comments, etc. Unfortunately, there's no support for such things yet...

  • Sergiu Dumitriu
    Sergiu Dumitriu, 2010/05/02 12:02
    • The "tick" and "cross" images look pretty, but, at least in a first implementation, I'd rather use classic checkboxes, since they will work without JavaScript. The styling with images can be part of the JS enhancements after the Export is functional, but with lower priority.
    • "Restore one of the Saved Packages" should be "Reuse..."
    • "Description" is only valid for XAR export, and maybe "License" should also be included for XAR.
    • Maybe the two trees should have a max height (dependent on the window size), so that the important controls are always available on the screen (controls = search filter, select all/remove all, export options, "Export" button)
    • Indeed, being able to customize the HTML export is a good idea
    • Ecaterina Valica
      Ecaterina Valica, 2010/05/03 08:28

      My main disappointment if you gonna use the "classic" checkboxes is that then we will need some link from "Select"/"Remove" actions and the whole thing of making the selection/removal simpler and obvious is gone. 

      Also the "classic checkbox" as a remove action (without a remove link action) is not gonna be very intuitive (cause check is positive metaphor)

  • Marta Girdea
    Marta Girdea, 2010/05/02 22:51

    Here's a "live" document tree prototype: SpaceTree (also works without javascript! emoticon_smile )

    • Ecaterina Valica
      Ecaterina Valica, 2010/05/03 08:36

      This works great and beautiful.

      About the style modifications, I like the ones from the proposal better, because:

      - Indentation: the icon is enough IMO to state that the folder is the parent. When they are on the same grid, the scanability is better and also consistent with the Import UI. 

      - Bold for Space names increased separation of the hierarchical relation, and eased again the readability;

      - You have bold + highlightColor for the location of the query result. I think one is sufficient (and that is highlight color). If you thing the highlight color is not readable enough, then that is a ColorTheme problem.  

      • Marta Girdea
        Marta Girdea, 2010/05/03 09:05

        Sure, I'll make them look like the proposal, I don't have a strong opinion about these aspects. Basically:

        • I just didn't pay enough attention at the proposed indentation, sorry
        • the whole list of collapsed bold spaces on an empty page looked a bit strong to me, but in a context this should be less problematic; respecting the item spacing in the proposal also helps
        • I had trouble seeing the highlighted text on search (that's the color theme's issue, though)
  • Marta Girdea
    Marta Girdea, 2010/05/03 09:44

    When searching in the tree, how should matching space names be handled? (I ask because there is no illustrative example for this in the proposal.) In the current implementation I don't check the space name, but I intend to display the matching spaces collapsed by default in the results. Is this OK? I don't see the reason to expand them initially, since it will only make the response time much longer and it will crowd the resulted tree with information that is not really useful. 

    • Ecaterina Valica
      Ecaterina Valica, 2010/05/03 12:35

      yes - they need to be collapsed. The user is looking for the space's name, not it's content. 

      The advantage of this tree is that after you find what you need you can further explore and expand.