[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/feed.php on line 173: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/feed.php on line 174: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
CAPE-OPEN Discussions about use and implementation of the CAPE-OPEN standard 2017-06-29T08:39:56+00:00 http://cape-open-forum.org/feed.php?f=39 2017-06-29T08:39:56+00:00 2017-06-29T08:39:56+00:00 http://cape-open-forum.org/viewtopic.php?t=555&p=1868#p1868 <![CDATA[Interop SIG • June 29, 2017 conference call]]>
Insight from Michael HALLORAN on current points discussed with COBIA Phase 2, namely threading model and persistence, was gathered to be handed over to the Methods & Tools Special Interest Group after some further checks on use of multiple threads in COLTT. Following earlier discussion with CO-LaN Management, work in the Interop SIG will be focused again on COLTT development and especially on further support of 64-bit versions of PMEs and PMCs.

Already CO-LaN is capable to provide separate installers of COLTT for its 32-bit and 64-bit versions It consequently provides for separate COLTT Controllers in 32-bit and 64-bit. This arrangement has been tested for example with COFE () 32-bit and 64-bit versions. Next step in COLTT developement could be a single controller which identifies 32-bit and 64-bit PMCs separately. Once user has selected which PMC is to be used, COLTT selects the appropriate logger (32-bit or 64-bit). There are issues around getting both 32-bit and 64-bit components displayed simultaneously. Your feedback is welcome on how you see use of COLTT, and especially COLTT controller, in the context of 32-bit and 64-bit software tools.

Next conference call to review actions is scheduled for August 4, 2017.

Statistics: Posted by colancto — 29 June 2017, 08:39

]]> 2017-03-16T16:06:50+00:00 2017-03-16T16:06:50+00:00 http://cape-open-forum.org/viewtopic.php?t=517&p=1757#p1757 <![CDATA[Interop SIG • March 2017 review of actions]]>
On the agenda was the debriefing of the conference call held on February 24, 2017 about the CAPE-OPEN Type Libraries and Primary Interop Assemblies installers. For those who did not attend the Feb 24 web seminar, it can be replayed from the . Some minor adjustments to the Developer Guide will be done soon and additional files pertaining to the example demonstrated will be provided, presumably in the since the demo pertains to the .

The Interop SIG also discussed the next steps in the development of the . While a 64-bit version of COLTT has now been developed, it remains to figure out if a single COLTT controller is necessary. Insight from software vendors regarding their strategy in the interoperability of a 64-bit Process Modelling Environment and Process Modelling Components of either 32-bit or 64-bit architecture is needed: the Interop SIG will define a suitable way to gather input on this.

The Interop SIG commented also on Phase II of the COBIA project run by the .

The next review of actions will be conducted on April 24, 2017.

Statistics: Posted by colancto — 16 March 2017, 16:06

]]>