pgaval / calipso Goto Github PK

What steps will reproduce the problem?
1. create a field group and include a Greek character in its name
2. create and complete an item
3. view the PDF file

What is the expected output? What do you see instead?
The Greek character is visible only in the html version of the item and it is 
omitted/not shown in the PDF file

Please provide any additional information below.

The following zimlets are needed:

1. Tab zimlet using an iFrame(displaying the "local" Calipso installation), see 
http://wiki.zimbra.com/wiki/ZCS_6.0:Zimlet_Developers_Guide:Examples:Tab_iFrame

2. Panel Item zimlet with Menu items linking to Calipso workflows (e.g. "New 
Order"), see 
http://wiki.zimbra.com/wiki/ZCS_6.0:Zimlet_Developers_Guide:Examples:Panel_Item_
Menus_ActionUrl

What steps will reproduce the problem?
1. Run through installation procedure as described by documentation
2. run "mvn antprops:generate"

What is the expected output? What do you see instead?

Expected to see "build successful"
Got:
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-antprops-plugin' does not 
exist or no valid version could be found

What version of the product are you using? On what operating system?
Checked out from source


Please provide any additional information below.

http://code.google.com/p/flyway

What steps will reproduce the problem?
1. Edit a custom field (e.g. Label)
2. Move to Workflow
3. The custom field permissions is set back to default values 
   (i.e. State "New" >> Mandatory, any other step "Read Only") 

What is the expected output? What do you see instead?
Field level permissions should not change back to default if field is edited.

We already use lucene, so adding apache tika should be easy.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

Looks like this (org.apache.wicket.extensions.wizard) would help us clean up 
the code, the panel example looks good:

http://wicketstuff.org/wicket13/wizard/

as discussed, we need to establish a rough datamodel for geomapping to add the 
appropriate customfields 

When creating a new space:

If "Create new space group" is selected from the "Select or create
space group" drop-down, before correcting the entry by selecting an existing 
group, then the app returns validation errors on the fields "Space group name" 
and "Space group description", which shouldn't be present unless the value 
submitted was "Create new space group".

See [1], this of cource depends on updating spring dependencies.

[1] http://www.springsource.org/spring-social

Codemirror might be a good candidate:

http://codemirror.net/

See subject

The workflow configuration form could use some improovements:

 - buttons should switch to ajax instead of refreshing the page
 - headings should be fixed and only the table body should scroll
 - Descriptions should be added to state/role forms, then added as tooltips in the table

See https://cwiki.apache.org/WICKET/maven-jetty-plugin.html

To latest stable wicket 1.4.x, Spring would be nice too but may need a lot more 
refactoring.

A user may add just too many custom fields for result rendering so the view is 
very easy to break. Refactoring to a grid should be ideal for this as it offers 
a control over the space occupied with both vertical and horizontal scrolling, 
see this example:

http://wicketstuff.org/grid-examples/data-grid/vertical-scrolling.6