: 4400 | 106121 | 11884
|
: 28 : 31 : 3 |
Most developers are used to Lotus-Script. They would not have much of a problem to write scripts in Java. The general syntax can be learned in a few hours and the main knowledge lies actually in the object-modell of the Notes-Classes, which are identical to LotusScript. However what we are missing is a step-by-step code debugger like the one for LotusScript. Once we get this you will see immedialtely a increased usage of Java in LN.
|
1) Curt Stone345 (02 Nov 2007)
You can use third-party debuggers but native would be nice.
2) Axel Janssen4993 (05 Nov 2007)
I've seen very difficult to maintain code when even good Lotus Script developers start to code in Java following the "the class model is the same"-theory mentionedby Hynek. The code has zero (!) unit-tests, all methods have 40 lines or more, the static modifier is used on a random basis, etc.
Me developing a java agent, there must be a proper REASON. We get our money to provide business value, not to script things in randomly chosen programming languages. As reason would qualify: a business case that calls for using nifty open source java libraries as Jexl, jakarta-commons httpClient or the Java Standard Api.
For Java there are allready good IDEs like Eclipse, Netbeans or InteliJ IDEA. Using those we should write unit-tests, follow proven design principles as high cohesion, low coupling. Once the notes access is properly encapsulated we need a debugger only on very rare ocassions, so remote debugging from the ide is enough. Also a Mock Framework for Domino classes can make even the Domino access testable and debugable from inside the IDE.
I see no reason why Lotus should duplicate the effort of the Eclipse, Netbeans or Intellij developers
Me developing a java agent, there must be a proper REASON. We get our money to provide business value, not to script things in randomly chosen programming languages. As reason would qualify: a business case that calls for using nifty open source java libraries as Jexl, jakarta-commons httpClient or the Java Standard Api.
For Java there are allready good IDEs like Eclipse, Netbeans or InteliJ IDEA. Using those we should write unit-tests, follow proven design principles as high cohesion, low coupling. Once the notes access is properly encapsulated we need a debugger only on very rare ocassions, so remote debugging from the ide is enough. Also a Mock Framework for Domino classes can make even the Domino access testable and debugable from inside the IDE.
I see no reason why Lotus should duplicate the effort of the Eclipse, Netbeans or Intellij developers
3) Nick Radov1333 (27 Jan 2008)
For anyone who hasn't seen it yet, this is coming in 8.5.
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
