January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (GPD-146) improve feedback when creating self referencing transitions

by Koen Aers (JIRA)

improve feedback when creating self referencing transitions ----------------------------------------------------------- Key: GPD-146 URL: http://jira.jboss.com/jira/browse/GPD-146 Project: JBoss jBPM GPD Issue Type: Feature Request Affects Versions: jBPM JPDL Designer 3.1.0.GA Reporter: Koen Aers Assigned To: Koen Aers Priority: Minor At the moment creating self referencing transitions is done by clicking twice on the source/target node. In the future some feedback (a dummy transition) should make this proces more obvious -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (GPD-150) In-place label edit box offset in scrolled editor

by David Good (JIRA)

In-place label edit box offset in scrolled editor ------------------------------------------------- Key: GPD-150 URL: http://jira.jboss.com/jira/browse/GPD-150 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.CR Environment: Eclipse 3.3, Windows XP SP2, JDK 6 Reporter: David Good Assigned To: Koen Aers Priority: Minor When editing a diagram larger than the editor window, clicking on a node label causes the edit box to appear in an offset position (see attachment) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBPM-1051) The GPD does not generate task forms correctly

by James Baxter (JIRA)

The GPD does not generate task forms correctly ---------------------------------------------- Key: JBPM-1051 URL: http://jira.jboss.com/jira/browse/JBPM-1051 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.1 Reporter: James Baxter Assigned To: Tom Baeyens Tasks can have variables specified as 'required'. This is not built into the taskform, the forms are missing the following attribute from the h:input tag: [code] required="true" [/code] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (GPD-167) Diagram should not scroll after adding nodes from palette

by John Ruud (JIRA)

Diagram should not scroll after adding nodes from palette --------------------------------------------------------- Key: GPD-167 URL: http://jira.jboss.com/jira/browse/GPD-167 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM jPDL Designer 3.1.0.SP1 Reporter: John Ruud Assigned To: Koen Aers Priority: Minor After adding nodes from the palette to diagrams where the scroll-bars are not in the top left corner position, the diagram will automatically scroll (to the top-left position). This is not desirable IMO, as it makes it easy to loose track of just-added nodes for large diagrams. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (GPD-151) entries in mail node subject and body elements disappear depending on click order before save

by Ross McDonald (JIRA)

entries in mail node subject and body elements disappear depending on click order before save --------------------------------------------------------------------------------------------- Key: GPD-151 URL: http://jira.jboss.com/jira/browse/GPD-151 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.CR Environment: os x, eclipse 3.3.0, Reporter: Ross McDonald Assigned To: Koen Aers Priority: Critical when I enter text in a mail node 'subject' input box, if I just click straight on the save button in eclipse, I lose the text entered... the same is true of the 'body' input box on the mail node to get this process to work I need to enter my text in the 'subject' input box, then click on the body input box, then click on the save button on the toolbar, this ensures my entry is in fact saved -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (GPD-134) form file names generated from the task dialogue are unstable

by Ross McDonald (JIRA)

form file names generated from the task dialogue are unstable ------------------------------------------------------------- Key: GPD-134 URL: http://jira.jboss.com/jira/browse/GPD-134 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.beta1 Environment: osx macbook pro, eclipse 3.3.0 Reporter: Ross McDonald Assigned To: Koen Aers Priority: Minor the form names generated from the task dialogue are sensitive to content... 'fbm-rejects.xhtml' is ok, and is stored in the DB fine when deployed, 'fbm-rejects-psr.xhtml' is not stored in the DB when deployed and therefore the form does not display within the jbpm-console the DB schema says the name field is varchar(255), which suggests that perhaps the second hyphen in the name is causing a problem somewhere -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (GPD-67) GPD support for editing non-files (any IEditorInput, not just FileEditorInput)

by John Ruud (JIRA)

GPD support for editing non-files (any IEditorInput, not just FileEditorInput) ------------------------------------------------------------------------------ Key: GPD-67 URL: http://jira.jboss.com/jira/browse/GPD-67 Project: JBoss jBPM GPD Issue Type: Feature Request Reporter: John Ruud Assigned To: Koen Aers Priority: Minor We need to edit process defs that are stored in a DB, as opposed to the processdefinition.xml, gpd.xml files stored in the workspace. There are currently many dependencies to FileEditorInput/File throughout GPD (as is the case for a lot of other Eclipse editors BTW). It would be very helpful if it would be feasible to separate out the code that deals with a particular type of IEditorInput from the rest of the editor, possibly into a separete delegate class. For FileEditorInput the delegate would deal with reading, writing, and syncronizing the view (resource listeners), plus whatever else I may have forgotten. We could then replace the default "file" delegate with our own that knows how to deal our DB (by subclassing of the editor would be fine). Probably not the #1 GPD issue for many other users, but hopefully something you would keep in mind... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (GPD-184) gpd.xml incorrect with non-ascii characters like Chinese

by Ryan Wong (JIRA)

gpd.xml incorrect with non-ascii characters like Chinese -------------------------------------------------------- Key: GPD-184 URL: http://jira.jboss.com/jira/browse/GPD-184 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM jPDL Designer 3.1.0.SP1 Environment: Eclipse WTP 1.5 with JDK 1.6 Windows XP Home SP2 Reporter: Ryan Wong Assigned To: Koen Aers When named the node with non-ascii character like 节点 the generated gdp.xml is human unreadable. (not proper UTF-8 file) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (GPD-35) enhancement drawing transitions

by Koen Aers (JIRA)

enhancement drawing transitions ------------------------------- Key: GPD-35 URL: http://jira.jboss.com/jira/browse/GPD-35 Project: JBoss jBPM GPD Issue Type: Feature Request Components: jpdl Reporter: Koen Aers Assigned To: Koen Aers When the mousepointer is in the outer area of a node/state/task/.... but within it's boundaries, it should be possible to draw a transition. This is makes using the gpd a lot faster (not switching in the toolbar) Maybe it should only be in the 'middle areas' of top, bottom, left and right and not the corners -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (GPD-193) Add the ability to drag new components into the workflow

by Gunnar Hillert (JIRA)

Add the ability to drag new components into the workflow -------------------------------------------------------- Key: GPD-193 URL: http://jira.jboss.com/jira/browse/GPD-193 Project: JBoss jBPM GPD Issue Type: Feature Request Reporter: Gunnar Hillert Assigned To: Koen Aers In the workflow designer it would be nice if I could simply drag a new workflow component into the main workflow. Right now you have to select the component from the component palette and then click again in the main workflow area to place the component. This seems to be slightly less intuitive than just drag-and-drop the new component into the workflow. Also, it would be great if I could then drag a component from the palette onto an existing 'transition line' and the transition will automatically connect to the newly placed component. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008