Ticket search results

renaming cforge commands

aliazzz — Sun, 19 Jan 2020 09:37:37 -0000

Hi, While using cForge to create a Package some questionmarks arose with me. Only after reading the wiki I understood the workflow. Therefore I would like to suggest some renaming in the context menu command's aso they will become more intuitive; 1) "Create Package" into => "Create Manifest for package" 2) "Build" into => "Build Package" Hope my suggestion will be picked up

create Package bug

aliazzz — Sat, 18 Jan 2020 22:33:32 -0000

Hi, I found a bug in the "create package" command in cForge. Apperently spaces in the CWD are not permitted. See the following output; ~~~ ---------------------------------------------------------------------------- cforge started Build date: $WCNOW$ Revision based: $WCREV$ ---------------------------------------------------------------------------- Easy attach enabled. Now attach with debugger, and then press Enter here! CWD: C:\Users\user\Desktop\I2C mcp7941x User elevated: False default case: --create-package [INFO] Executing: C:\Program Files\CODESYS 3.5.14.0\CODESYS\CFORGE\Scripts\create-package.py [Exception] command create-package.py caused an exception: Traceback (most recent call last): File "C:\Program Files\CODESYS 3.5.14.0\CODESYS\CFORGE\Scripts\create-package.py", line 145, in IOError: [Errno 2] Could not find a part of the path 'C:\Users\user\Desktop\I2C\license.txt'.: C:\Users\user\Desktop\I2C\license.txt ---------------------------------------------------------------------------- cforge finished. ---------------------------------------------------------------------------- ~~~ As clearly seen, the original path is "C:\Users\user\Desktop\I2C mcp7941x" But the output is being written to "C:\Users\user\Desktop\I2C\" which fails.

Automatic Build

Ingo — Sat, 20 Apr 2019 09:54:02 -0000

Support an automated build system by implementing a meta command, which executes several others, based on a configuration passed to it. (like passing a build job to cforge)

Avoid warnings from URL handlers

Ingo — Thu, 09 Aug 2018 19:28:40 -0000

There are two warnings produced when clicking on an URL handler: 1. Warning from the browser, that an external App is launched. This needs to be disabled per browser: [IE](https://stackoverflow.com/questions/37702082/internet-explorer-or-edge-how-to-display-the-warning-that-appear-if-you-open-c) 2. Execute as Admin This needs to be avoided in the tool, which doesn't need to have admin rights.

support context menu entry for common use cases in windows explorer

erichspitzweg — Thu, 09 Aug 2018 19:29:35 -0000

It is simple to add context menu entries (even with sub-menu and icons). So it would be very convenient to use cforge directly from windows explorer.

Implement checkout

Ingo — Tue, 15 May 2018 22:22:30 -0000

Implementierung a basic cforge checkout action, which checks out CODESYS libraries and projects, and can be used in combination with the links on the website

commit: Implement the action 'commit'

Ingo — Thu, 09 Aug 2018 20:24:11 -0000

The commit action does several at once: # Export Documentation The script uses the PLCopen Export to get the content out of the project. Then it transforms the result into Markdown, using XSLT. First, it is more than enough to support ST. # Commit with CODESYS SVN Commit the changes in the project with CODESYS SVN to the repository that is connected with it (no changes done). # Commit with local SVN Add / commit the project file and exported documentation, using external SVN client.