5 Replies Latest reply on Nov 15, 2006 6:07 AM by Ronald van Kuijk

    behind the scene changes in gpd

    Ronald van Kuijk Master

      I've seen lots of gpd changes comming by in cvs. I know Koen was updating the model behind the designer, but could someone shed some light on the advantages this is going to bring us? e.g. easier implementation of requested features like being able to move transitions, having transitions obey the grid etc...etc...etc... I bet he did not do it for no reason, since it seems to have been a hell of a job.

        • 1. Re: behind the scene changes in gpd
          Koen Aers Master

          The model was a mess really. So the refactoring had to be done in order to accomodate for full JPDL support and also in order to more easily support other languages in the future (BPMN, XPDL, ...).
          While doing the refactoring, I have used inspiration found in the Eclipse GMF project, to split the notation part (the boxes and arrows) from the semantic part (the states, mailnodes, tasks, ...) in the model. Splitting this should make it easier to accomodate for graphical things that don't show up in the semantic model (free text comments e.g.) and for semantic things that have no graphical representation.
          Some of the requested features were already possible with the old model (move transitions) but just didn't make it into the product yet. Some features were not yet possible to support because GEF was not powerful enough (have transition endpoints or bendpoints obey the grid).
          Another goal is to give the SEAM pageflow editor its own plug-in and factor out the commonalities of both plug-ins into a common base plug-in.
          The next release of the GPD will occur in the next couple of weeks if everything goes according to plan and will be 3.1.0 alpha1. I expect it to be reasonably stable but nevertheless contain problems as is not too unexpected after such a major refactoring. Most of the functionality that is available in the last 3.0.x version will also be present. One of the things that will change is that the property dialogs that are brought up by double-clicking on the nodes in the graphical pane or outline will be replaced by tabbed forms in the properties view.

          All feedback is welcome!

          Regards,
          Koen

          • 2. Re: behind the scene changes in gpd
            Ronald van Kuijk Master

            Sounds great, thanks Koen.

            I have one item of feedback on the bringing up of the properties dialogs, especially the tasknode. Would it be possible to have tasks show up in the tasknode dialog as well? That would make them more accessable and not require the treeview...

            • 3. Re: behind the scene changes in gpd
              Koen Aers Master

              Yes, I already experimented with a (collapseable) task compartment a while ago. So this is definitely one of the things I keep in mind. But it should be optional, as some (Tom!) want the graphical view to be as simple as possible.
              For the upcoming new release the tasks should already be available in the 'Tasks' tab of the tabbed property view. So you won't need the treeview for configuring them. I am also thinking of defining a 'jpdl' perspective that positions the outline view below the project/navigation view and making the bird eye view in the outline the default instead of the treeview.
              Thoughts?

              Regards,
              Koen

              • 4. Re: behind the scene changes in gpd
                Ronald van Kuijk Master

                I didn't mean collapsible in the view, but in the proparties dialog in the left. There currently is only general and tasks could be the second one. For me that is good enough (although collapsible in the view would of course be real slick)

                • 5. Re: behind the scene changes in gpd
                  Ronald van Kuijk Master

                  sorry, did not read the second part of your response in detail. That direction sounds great.