: 4400 | 106119 | 11884
|
: 4 : 4 : 0 |
1. In the present implementation the document is locked when double-click, that is, before the commencement of Querymodechange! This is wrong - on Querymodechange there are some conditions for which are not permitted to translate the document into edit mode.
I propose to block the document between Querymodechange and Postmodechange, while in edit mode, the document should be translated only if the document was blocked! If suddenly you need to block the document before, it can be done elementarily programmatically by calling notesDocument.Lock() on Querymodechange. 2. If the document has been blocked by the current user and will re-lock (an attempt to translate the document into edit mode), then the document should not explicitly blocked and translated into edit mode, rather, it is not true, because document at the same time could be changed by another process from the same user, such as background agent. If you give to save the document, the data entered by another process will be replaced by the current instance.
Ideally, there should be a link with this idea, or should warn you that "the document is changed by another process..." 3. Lock indicators:
This is all seen in the debugger and flies in the runtime...
|
1) Peter Presnell26400 (10 Jun 2010)
I agree. Documentlocking was one of those features that was never fully implemented and a number of issues with its use often prevent it from being used in applications. unfortunately I don't see much chance IBM of devoting too much time to this unless it ties into locking of Xpage documents.
2) Vlad Sh10122 (10 Jun 2010)
Thank you for your vote and comment, Peter.
1. If IBM will not support the UI, based on the Forms, you have officially reported this state, then we will not spend time with each other.
2. If XPages will work in the Notes client, and interface documents will be built on XPages, then the above problems are also possible, because mechanism, one(?) What meaning to write a second mechanism for XPages? In my opinion, better to refine the mechanism so that it worked in Forms and in XPages.
1. If IBM will not support the UI, based on the Forms, you have officially reported this state, then we will not spend time with each other.
2. If XPages will work in the Notes client, and interface documents will be built on XPages, then the above problems are also possible, because mechanism, one(?) What meaning to write a second mechanism for XPages? In my opinion, better to refine the mechanism so that it worked in Forms and in XPages.
3) Bruce Lill6677 (12 Jun 2010)
With the distributed state of Domion, it's hard to make a real document lock. I would rather see the ability to merge change and to realtime show updates on the form when content changes,. Similar to what flex can do.
4) Vlad Sh10122 (15 Jun 2010)
Welcome to IdeaJam™
You can run IdeaJam™ in your company. It's easy to install, setup and customize. Your employees, partners and customers will immediately see results.
Use IdeaJam to:
- Collect ideas from employees
- Solicit feedback and suggestions from employees and customers
- Run innovation contests and competitions
- Validate concepts
- Use the power of "crowd-sourcing" to rank ideas and allow the best ideas to rise to the top
IdeaJam™ works with:
- IBM Connections
- IBM Lotus Quickr
- Blogs and Wikis
- Websphere Portal
- Microsoft Sharepoint
- and other applications.
IdeaJam has an extensive set of widgets and API's that allow you to extend and integrate IdeaJam™ with other applications.
Learn more about IdeaJam >>
IdeaJam developed by
