• We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      We need this documentation.

      This has been discussed by mail so far, but didn't get actioned yet. Please schedule for this week.


      Yes, that sounds all very reasonable, let's please do it like this. It can't take that long to write down a page for this, can it (asking Matt and Chris)? Even if we wouldn't use the hover for other products, we should still provide this kind of documentation even for "just" plugin developers, and for our future selves (e.g. if someone else on the team wants to reuse the hover in another context)

      Cheers,
      Per

      > The implement guide should describe everything that a product needs to do to implement user hover, answering questions like:
      >
      > * What JavaScript code should I use to display the hover? * How should the server-side action display the hover information?
      > * What web-items section should I use for links
      > * What content should be in the main panel of the hover?
      > * What content should be in the main buttons and how should it be determined?
      >
      > Yes, these are things that could be conveyed by having Charles sit down with the developer and walk through, but I've found a document, shared between teams, promotes consistency, simplifies interactions, and is a nice reference guide for estimation and planning. Without things like this being spelled out, if it is possible for products to do things differently, they'll do it in ways you can't imagine.
      >
      > Don
      >
      > Adnan Chowdhury wrote:
      >> Sorry, wrong Don.
      >>
      >> a
      >>
      >> On 16/03/2009, at 11:00 AM, Adnan Chowdhury wrote:
      >>
      >>> Hey guys,
      >>>
      >>> It was mentioned in the integration meeting that we should produce an 'implementation guide' for the user hover that other teams can use when they are implementing the user hover in their products. I don't know what that is, or what should be in it, but I think you two should get together to work out what's required and whether only Charles is required or someone else to write it.
      >>>
      >>> @Don: do you have an example in mind for what's required? Or should this be worked out in a meeting?
      >>>
      >>> a
      >>>
      >>
      >

            [CONFSERVER-14967] No developer documentation for user hover popup

            Jacob Kjeldahl added a comment - - edited

            Just for reference.

            To add links to the dropdown use section system.user.hover it is further sectioned in primary and secondary

            Jacob Kjeldahl added a comment - - edited Just for reference. To add links to the dropdown use section system.user.hover it is further sectioned in primary and secondary

            There is no documentation for the Confluence implementation but there is for the AUI implementation here:
            https://studio.atlassian.com/wiki/display/AJS/InlineDialog

            Created CONF-17208 to facilitate the upgrade.

            m@ (Inactive) added a comment - There is no documentation for the Confluence implementation but there is for the AUI implementation here: https://studio.atlassian.com/wiki/display/AJS/InlineDialog Created CONF-17208 to facilitate the upgrade.

            I guess now is the time! Can we get this done now?

            Per Fragemann [Atlassian] added a comment - I guess now is the time! Can we get this done now?

            AudraA added a comment -

            could be deferred to after 3.0 releases

            AudraA added a comment - could be deferred to after 3.0 releases

            This actually turned out to be more work than just documenting. Spent a fair bit of time migrating the hover code into AJS (https://studio.atlassian.com/browse/AJS-26) and when AUI 1.0-rc1 is released (and confluence updated to use it) we can write some documentaiton.

            m@ (Inactive) added a comment - This actually turned out to be more work than just documenting. Spent a fair bit of time migrating the hover code into AJS ( https://studio.atlassian.com/browse/AJS-26 ) and when AUI 1.0-rc1 is released (and confluence updated to use it) we can write some documentaiton.

              mjensen m@ (Inactive)
              pfragemann Per Fragemann [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: