Gliffy Online

Improve integration with Confluence

Details

Description

Currently the integration between gliffy and confluence is a bit clunky.

When adding a diagram, one has to create what looks like a diagram placeholder and only then an option to start gliffy is offered. In balsamiq the first step is not needed.

Once a diagram is created, a gliffy renders the image via a servlet whereas balsamiq uses pre-generated image stored as an attachment alongside with with source xml.

Also the fact that gliffy uses spacekey, page title and pageid in the markup by default puts extra constraints on the portability of the content.

Any chance that you could learn some stuff from what balsamiq does and bring it to gliffy?

Issue Links

This issue is duplicated by:
GLIFFY-1672 Copying Confluence Pages causes user confusion when they then edit diagrams Major Code Complete
This issue is related to:
GLIFFY-1614 Creating diagram doesn't work when confluence isn't hosted at root context Blocker Code Complete

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Shannon Krebs added a comment -

@Chris what do you actually want me to do with this one?

We could probably jump from the create diagram page, to the editor, but it would be even better if you could just create a new diagram straight in the editor without the first step like you can in the Jira plugin.

Storing an image file along with the gliffy xml file would allow you to use the normal confluence tools for inserting images etc. That would be a large change to implement though and could impact on a lot of things.

I agree about the default macro markup point, we probably don't need to include anything more then the attachment name in the gliffy tag by default.

Show
Shannon Krebs added a comment - @Chris what do you actually want me to do with this one? We could probably jump from the create diagram page, to the editor, but it would be even better if you could just create a new diagram straight in the editor without the first step like you can in the Jira plugin. Storing an image file along with the gliffy xml file would allow you to use the normal confluence tools for inserting images etc. That would be a large change to implement though and could impact on a lot of things. I agree about the default macro markup point, we probably don't need to include anything more then the attachment name in the gliffy tag by default.
Hide
Permalink
Chris Kohlhardt added a comment -

We're not going to make any big workflow changes in the client editor at this time. As such, please implement:

  • jump from the create diagram page, to the editor
  • don't include anything more then the attachment name in the gliffy tag by default.
Show
Chris Kohlhardt added a comment - We're not going to make any big workflow changes in the client editor at this time. As such, please implement:
  • jump from the create diagram page, to the editor
  • don't include anything more then the attachment name in the gliffy tag by default.
Hide
Permalink
Shannon Krebs added a comment - - edited

One problem with jumping straight to the editor from the add diagram action is that we can't create the editor in a new window anymore. :-/

edit: can't is the wrong word, more difficult I should say.

Show
Shannon Krebs added a comment - - edited One problem with jumping straight to the editor from the add diagram action is that we can't create the editor in a new window anymore. :-/ edit: can't is the wrong word, more difficult I should say.
Hide
Permalink
Shannon Krebs added a comment - - edited

@Chris The macro inserted into the page will now only have the diagram name and alignment/size info. Not page or space params.

I've updated (and refactored a bit) the AddDiagram action so now after hitting the Create Diagram button it jumps straight to the editor if you have the open in new window set to false. If that setting is set true, it displays the same page as before with a link to launch the editor in the new window. Will need to investigate options for opening the editor in a new window.

(I was hopeful we could copy the way the link from the attachment page is done, with different web-ui items, but that doesn't seem to work in my testing in confluence 3.0 atm, will need to investigate)

Show
Shannon Krebs added a comment - - edited @Chris The macro inserted into the page will now only have the diagram name and alignment/size info. Not page or space params. I've updated (and refactored a bit) the AddDiagram action so now after hitting the Create Diagram button it jumps straight to the editor if you have the open in new window set to false. If that setting is set true, it displays the same page as before with a link to launch the editor in the new window. Will need to investigate options for opening the editor in a new window. (I was hopeful we could copy the way the link from the attachment page is done, with different web-ui items, but that doesn't seem to work in my testing in confluence 3.0 atm, will need to investigate)
Hide
Permalink
Shannon Krebs added a comment -

Resolving this issue as fixed for now as this is all we are going to do in this release. If there is further integration improvements they will need to go in new issues.

Show
Shannon Krebs added a comment - Resolving this issue as fixed for now as this is all we are going to do in this release. If there is further integration improvements they will need to go in new issues.

People

Vote (0)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved:
Bug tracking and project tracking for software development powered by Atlassian JIRA (v4.4#649-r158309) | Report a problem