[opencms-dev] Is it possible to publish control in resourcetypeand get resource type's own property method in 6.2.0?

[Shi Yusen]

Thank you Alex!

Your method is perfect. And I must tell you: you are my HERO.

I think I have got the spirit of your approach:
* The new lock type is not at the same level as other lock types because the
resources should be unlocked when flow from reporters to editors and
multi-language-publish or multi-channel-publish may happen.
* The "workflow project" cannot be seen in the workplace by Users.

Am I right?

For my second question, we create a new type extended from xmlpage. So we
can use the DHTML editor to edit the type. When press the property button in
the editor, ../common/property.jsp is called rather than a property.jsp we
set in opencms-workplace.xml for the resource type. In some cases such as
multi-language-publish or multi-channel-publish, the editors cannot change
template and other properties in the DHTML editor conveniently. This is not
a bug. It would be perfect if this can be changed.

Thank you for your adding our requirements to 6.2.0's TODO list!

I'm very glad OpenCMS almost have a 3-year roadmap now. Great work!

Best Regards,

Shi Yusen/Beijing Langhua Ltd.



-----邮件原件-----
发件人: Alexander Kandzior [mailto:alex at opencms.org] 
发送时间: 2005年10月22日 17:40
收件人: shiys at langhua.cn; 'The OpenCms mailing list'
主题: RE: [opencms-dev] Is it possible to publish control in resourcetypeand
get resource type's own property method in 6.2.0?

Dear Yusen,

First, thank you very much for your effort on the Workflow integration.
While I did not check out your module yet, I really appreciate that
contribution.

Regarding your questions about 6.2.0 extensions.

> During the osworkflow integration, we find A_CmsResourceType 
> should have a method to check if a resource can be published. 
> If a resource is in a publish approval procedure, no matter 
> whether it's new, it should not be published.

I understand what you mean. However, I would like to change the
I_CmsresourceType interface only if absolutly required. My ideas in that
direction are like this:

* In order to better integrate workflows, we the lock status information is
extended. A new lock type is introduced that indicates that the locked
resource is part of a workflow. Special treatment for the lock status is
added to the explorer to prevent "lock stealing". Moreover, some sort of new
lock icon is displayed in the Explorer front end to visually indicate that
this item is part of a workflow. Unlocking resources for a project publish
won't affect locks of this special type.

* All Resources that are part of a workflow set are bundled in a project.
For each set of workflow resources, a new project with a new type ("workflow
project") is automatically created. A final "approval" für the workflow
items is equal to a publish of this project. 

This approach would generate a number of benefits, and would be well
integrated in the current core. 

For example:

- Several resources can be easily bundled in one project and published
together, using existing mechanisms.
- Since the resources would be part of one "workflow project", they would
not be published anyway since only resources in the current selected project
are published (the workflow projects would not appear in the project select
box).
- The explorer view would give a visual indication of the workflow status of
individual resources.

While this may sound like a big deal of work, it actually is not.

TODO items:

+ Define new lock type in org.opencms.lock.CmsLock (e.g. TYPE_WORKFLOW).
+ Add logic to "force unlock" operations in order to prevent lock stealing
on locks of new type in CmsDriverManager
+ Define new project type in org.opencms.file.CmsProject (e.g.
PROJECT_TYPE_WORKFLOW)
+ Add code to org.opencms.workplace.explorer.CmsExplorer to indicate
resources are in workflow state (special lock type)
+ Extend JavaScript for explorer to display special infos for workflow
resources (use space of lock and/or "red flag" symbols)

Please note that this approach cleanly separates the workflow itself from
the state of resources. Creation of workflow projects, as well as moving
resources into workflow projects and publishing of such projects is left to
the individual workflow implementation.

Let me know what you think.

> Another method is on the property jsp's url. Is it possible 
> to get it from the resource type's setting? Currently the 
> xmlpage's url is hardcoded in the CmsPropertyAdvanced. All 
> other types use the same jsp.

I don't quite understand what you mean. There is a special property handler
you can use to exchange the property page. Have a look at the "templateone"
demo which uses that feature. If you mean something else, please provide
more information.

Kind Regards,
Alex.

Alexander Kandzior
Alkacon Software - The OpenCms Experts
http://www.alkacon.com

 

> -----Original Message-----
> From: opencms-dev-bounces at opencms.org 
> [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Shi Yusen
> Sent: Friday, October 21, 2005 6:32 PM
> To: 'The OpenCms mailing list'
> Subject: [opencms-dev] Is it possible to publish control in 
> resource typeand get resource type's own property method in 6.2.0?
> 
> Hi Alexander,
> 
> During the osworkflow integration, we find A_CmsResourceType 
> should have a method to check if a resource can be published. 
> If a resource is in a publish approval procedure, no matter 
> whether it's new, it should not be published.
> 
> Another method is on the property jsp's url. Is it possible 
> to get it from the resource type's setting? Currently the 
> xmlpage's url is hardcoded in the CmsPropertyAdvanced. All 
> other types use the same jsp.
> 
> Is it possible to make these changes in 6.2.0?
> 
> Have a nice weekend,
> 
> Shi Yusen/Beijing Langhua Ltd.
> 
> PS: I'll keep my promise to offer a osworkflow module on 
> 6.0.2 at the end of this month.
> 
> 
> 
> 
> 
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list To 
> change your list options, or to unsubscribe from the list, 
> please visit http://mail.opencms.org/mailman/listinfo/opencms-dev
> 
>