Activity for CODESYS Forge
-
mase created ticket #33
markdown script nullreference exception
-
Ingo modified ticket #32
Create use "step by step" usecase based documentation for CFORGE tool
-
hermsen posted a comment on ticket #32
OOPS.. Please delete this ticket :-(
-
Create use "step by step" usecase based documentation for CFORGE tool
-
Home
-
Android App: Cache handling on Samsung S10 / Android 10
-
Hi! I would be very pleased if someone has the muse to rewrite parts of the script. As far as I remember some design decisions were made because the script should run on windows and linux, as the idea was to use it also in the CI-Jobs. But this is no use case anymore.
-
CFORGE Tool doesn't work with SP16
-
i-campbell created ticket #30
Checkout with cforge not working on large repos
-
It is in fact more an integration issue, as the script didn't work with the newest version. And currently it's hard to test, as codesys-4-linux still doesn't support CODESYS SVN 😞
-
aliazzz modified a comment on ticket #29
Never noticed this... > haven't tested it :-| maybe you should add some unit test for this in the package?
-
Never noticed this... > haven't tested it :-| maybe you should do some unit test for this in the package?
-
Never noticed this... > haven't tested it :-|
-
Home
-
Admin committed [r87]
[#29] CFORGE Tool doesn't work with SP16
-
[#29] CFORGE Tool doesn't work with SP16
-
The Profile names changed in SP16 and can't be found anymore The SVN checkout throws errors (object reference not set...)
-
CFORGE Tool doesn't work with SP16
-
Be more expressive on SVN errors
-
Home
-
Improved installation process
-
Minutes of short meeting: Present: Ingo, i-campbell From the diagram in the above comment we should focus most on the role of the "contributer". And that we should make the start for the potential contributer, who is new to "open source", "version control" and "continous integration", as easy as possible. This indirectly helps the other user types. Make contributing easier cforge tool should provide the "Wizards" for, for example committing your first project. This should build on the "notes" Ian...
-
Minutes of short meeting: Present: Ingo, i-campbell From the diagram in the above comment we should focus most on the role of the "contributer". And that we should make the start for the potential contributer, who is new to "open source", "version control" and "continous integration", as easy as possible. This indirectly helps the other user types. Make contributing easier cforge tool should provide the "Wizards" for, for example committing your first project. This should build on the "notes" Ian...
-
Hi Ian, if it's just us, lets discuss this via teams next week during worktime.
-
Great Idea, I could make any time this long weekend, but after 8pm is easiest.
-
Proposal: We plan a jitsi meeting to discuss and priorize this stuff. What do you think?
-
a. As a test, I setup a slack for collaboration, but I don't think that is optimal for open source use. Looking at other OSS projects, I see irc (specifically irc.freenode.net) as a common "chat". One of the tools for a forge/prj/, could be adding the CODESYS forge bot to their irc, and thus archiving the chat logs. I think it should be made clear that chat is best for "we need to "sit in the same room and discuss this"" whereas [talk] or [tickets] is best for "Please take time to consider and respond...
-
Hi Team! So since February, a lot has happened! 1. forum integration. 2. I made my first forge.codesys.com/prj/ 3. I collaborated with aliazzz on my second forge.codesys.com/prj/ 4. lots of people are working from home. 5. SP16 is sooo close! 6. So many more public and private things for everyone. Some points I have come up with: 1. It took me 4 hours to get my first project from "I have a .project" to "I have a /prj/ people can access". I think I missed a few steps, but it is there. I would like...
-
cforge: .project to markdown converter misses CONSTANT keyword
-
That's right. The reason is, that all special categories in the App are able to trigger push notifications. And the idea was, that the product news would also be of interest for the typical forge user. Despite this, there is no reason why we should duplicate this information on the forge website.
-
Question Why won't place a "Product News" link in the Hamburger menu button? Saves you a custom built place in the app ... plus the hamburger button is by design available on ALL platforms (browser, mobile and android app).
-
Question Why don't place a "Product News" link in the Hamburger menu button? Save you a custom built place in the app ... plus the hamburger button is by design available on ALL platforms (browser, mobile and android app).
-
Cannot find Product News
-
Thanks Ian! Can't reproduce it practically, but in theory this should fix it: https://stackoverflow.com/questions/52707918/webview-showing-err-cleartext-not-permitted-although-site-is-https
-
Android App: can't scroll menu in landscape mode
-
Android: Product News Page opened in App gives errors
-
Tester Note: Hmm, when I used the link on the news feed ( here ), somehow I still get V20200208 If I go to https://forge.codesys.com/tol/cforge/code/ and click through to the cforge.apk I get an error 500 However when I hit the Download Snapshot button, I get a zip file with the correct cforge.apk in it I think as it will be in beta on Play Store soon, the simple fix for now is to say "download snapshot of the repository and unzip to get the APK" RESULT: OK - I now have product news in the app
-
Sorry! Seems, like I forgot to upload the last build.
-
Autoversioning commit: a non-deltaV client made a change to
-
Cannot find Product News
-
ingo <> committed [6880df]
added new category for "product news"
-
ingo <> committed [a9ba7b]
added new category "product news"
-
Upload doesn't work
-
updated app
-
ingo <> committed [5fa9ee]
updated icon
-
ingo <> committed [2a9d44]
[#22] Upload doesn't work
-
Logging out and reopening the app causes to be logged in again
-
fixed in trunk
-
ingo <> committed [4d2034]
updated launcher icon
-
ingo <> committed [75c7cf]
[#24] Logging out and reopening the app causes to be logged in again
-
ingo <> committed [8e6416]
Merge branch 'master' of https://forge.codesys.com/git/tol,cforge,android
-
ingo <> committed [c7736a]
try to make service sticky.
-
ingo <> committed [cd5981]
changed icon
-
ingo <> committed [4c8954]
fixed startup bug in service (app crashed during startup)
-
ingo <> committed [030307]
updated launcher logo
-
Happy reading, ps I ment remote runners (aka remote builders) Jenkins : https://wiki.jenkins.io/display/JENKINS/Jenkins+Runner Drone : https://docs.drone.io/runner/overview/ GitLab : https://docs.gitlab.com/runner/ Plus you can also ask Ingo..
-
Happy reading! Jenkins : https://wiki.jenkins.io/display/JENKINS/Jenkins+Runner Drone : https://docs.drone.io/runner/overview/ GitLab : https://docs.gitlab.com/runner/ Plus you can also ask Ingo..
-
Can you help me find some reading material on Remote Builders? It is new for me.
-
Hi, On point1: Git integration ETA SP16, nice! On point 2: Currently, generating a .pdf output is cumbersome, to say the least, due to frames, latex and python dependencies, etc, etc. This, while generating a .chm file can be generated via a single command. But only if you read the .libdoc documentation carefully, then you can spot that specific command. Maybe documentation has improved over time, I have not checked it since over a year. Anyway, both a themed .chm and a .PDF are high on my bucketlist,...
-
"Git integration for cForge (and a plugin for GIT in CODESYS IDE?)" @aliazzz So the plugin comes with SP16. Do you think any prelim work is needed, ie adding some CODESYS independent GIT things? Sure, this feature with cForge is a must after SP16. For me, I think GIT is fundamental for the collaborative nature of open source, but until SP16, a wiki article is enough so we don't have to start again in May. "Generating .CHM and or .PDF documentation" @aliazzz Yes use of the libdoc tools gets my vote...
-
Another possibility could be to let the cforge executable act as a remote-builder on the system it is installed. Maybe even a platform independent technology suitable for at least Windows and Linux (Mac is debatable for lack of any CODESYS runtimes at this moment). This way the new cForge executable (could still be installed via a .package on windows) bridges the gap between a machine anywhere on the Internet and this web based platform in a secure manner. The executable can interact with any software...
-
Another possibility could be to let the cforge executable act as a remote-builder on the system it is installed. Maybe even a platform independent technology suitable for at least Windows and Linux (Mac is debatable for lack of any CODESYS runtimes at this moment). This way the new cForge executable (could still be installed via a .package on windows) bridges the gap between a machine anywhere on the Internet and this web based platform in a secure manner. The executable can interact with any software...
-
I love the direction! So I think from this: 1. web page can generate an item from a series of templates, maybe call the item type "Worflow instance" or some other well thought out name. "Workpiece" might fit in well with the forge metaphor 2. contributors can make new templates and add them to some central repository (eventually a template for the template workflow ;)) 3. Maybe a "Do" button to start a new workpiece or work on an existing one 4. cforge.exe should not be a .package but a standalone...
-
I love the direction! So I think from this: 1. web page can generate an item from a series of templates, maybe call the item type "Worflow instance" or some other well thought out name. "Workpiece" might fit in well with the forge metaphor 2. contributors can make new templates and add them to some central repository (eventually a template for the template workflow ;)) 3. Maybe a "Do" button to start a new workpiece or work on an existing one 4. cforge.exe should not be a .package but a standalone...
-
I love the direction! So I think from this: 1. web page can generate an item from a series of templates, maybe call the item type "Worflow instance" or some other well thought out name. "Workpiece" might fit in well with the forge metaphor 2. contributors can make new templates and add them to some central repository (eventually a template for the template workflow ;)) [-img src=Screen Shot 2020-02-02 at 20.37.31.png width=25%: missing =-] 3. Maybe a "forge something" button [-img src=Screen Shot...
-
Logging out and reopening the app causes to be logged in again
-
Logging out and reopening the app causes to be logged in again
-
Hi Ian, You crazy guy! ;) Very nice analyzation of the user groups and tasks they want to achieve. I used your lists to try to form use cases and defined even three groups of actors, who want to complete those use cases: Beside the contributer and the consumer, I defined the biggest group of users. Those who only search for informations and tipps to solve their own problem in their proprietary software. My thought is, that we can then sort those use cases into the different user interfaces: web page...
-
Hi Ian, You crazy guy! ;) Very nice analyzation of the user groups and tasks they want to achieve. I used your lists to try to form use cases and defined even three groups of actors, who want to complete those use cases: Beside the contributer and the consumer, I defined the biggest group of users. Those who only search for informations and tipps to solve their own problem in their proprietary software. My thought is, that we can then sort those use cases into the different user interfaces: - web...
-
Notifications aren't fired after reboot
-
Upload doesn't work
-
I have kind of been thinking on this on and off, so haven't until now commented. My view was to look at: 1. what types of cForge users exist, 2. what skills they may have / may lack, 3. and then what tasks each type of cForge users should want to perform. It is my opinion that open source development and its associated workflows are new to many automation engineers. I think the short term development of the cForge tool should focus on guiding the user to complete tasks. Types of users: 1.a admin...
-
Thanks for your input Aliazzz! Thats very valuable. Regarding the webhook: Did you already try them? Allura supports webhooks for the code repositories: https://forge-allura.apache.org/p/allura/wiki/Webhooks/ Or are you missing s.th.?
-
CODESYS Forge needs an icon
-
For me, I am overjoyed with the intricacies of the new cForge logo seen in [r81].
-
- removed .drone.yml to enable default CI build
-
updated cforge package including startup bugfix and sticky service
-
updated app w/ new logo
-
It seems I cannot update the main ticket as requested....
-
Edit: commands from original ticket description show up clarified in the latest installer. But other commands need clarifying as per aliazzz's feedback. @aliazzz is it possible to update the main ticket description with the new requirements?
-
moved posting
-
UPDATE command: Cforge Build package calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\build.py Which does ... ? command: Cforge create package manifest calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\create-package.py Which yields a dialog which asks to creat a package and not a manifest.... Looks like these two commands needs some renaming.
-
@aliazzz Thanks for the help testing and reporting!
-
@Ingo Please accept the change to the Setup.reg file, which puts quotes around the directory paths of shell commands to solve the problem of directories with spaces. https://forge.codesys.com/tol/cforge/tickets/_discuss/thread/4441ef6b6f/32d9/attachment/I-Campbell.2020.01.18.19.50.Setup.reg please see this positive tester note https://forge.codesys.com/tol/cforge/tickets/14/#32d9/4a66
-
UPDATE command: Cforge Build package calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\build.py Which does ... ? command: Cforge create package manifest calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\create-package.py Which yields a dialog which asks to creat a package and not a manifest.... Looks like these two commands needs some renaming.
-
now testing! please wait The registry patch for \"%V\" seems to work !** Aliazzz
-
UPDATE Cforge Build package calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\build.py Which does ... ? Cforge . create package manifest calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\create-package.py Which yields a dialog which asks to creat a package and not a manifest.... Looks like these two commands needs some renaming.
-
UPDATE Cforge Build package calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\build.py Which does ... ? Cforge . create package manifest calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\create-package.py Which yields a dialog which asks to creat a package and not a manifest.... Looks like these two commands needs some renaming as they confuse me.
-
UPDATE Cforge Build package calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\build.py Which does ... ? Cforge . create package manifest calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\create-package.py Which yields a dialog which asks to creat a package and not a manifest.... Looks like these two commands needs some work, as they confuse me.
-
now testing! please wait UPDATE Cforge Build package calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\build.py Which does ... ? Cforge . create package manifest calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\create-package.py Which yields a dialog which asks to creat a package and not a manifest.... Looks like these two commands needs some work, as they confuse me. PS Update, commit and checkout seem correct. PSS On the positive...
-
now testing! please wait UPDATE Cforge Build package calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\build.py Which does ... ? Cforge . create package manifest calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\create-package.py Which yields a dialog which asks to creat a package and not a manifest.... Looks like these two commands needs some work, as they confuse me. PS Update, commit and checkout seem correct. PSS \"%V\" seems to...
-
now testing! please wait UPDATE Cforge Build package calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\build.py Which does ... ? Cforge . create package manifest calls: [INFO] Executing: C:\Program Files\CODESYS 3.5.15.0\CODESYS\CFORGE\Scripts\create-package.py Which yields a dialog which asks to creat a package and not a manifest.... Looks like these two commands needs some work, as they confuse me. PS Update, commit and checkout seem correct. Aliazzz
-
now testing! please wait
-
"... I have seen the renamed commands..." Sounds like a positive tester note to me! @Ingo - candidate for closing the issue?
-
The cForge package 1.0.0.15 in the trunk has not been touched for almost a year? But I have seen the renamed commands but I am still using this year old version. Also, my own knowledge on SVN/Git has increased ever since, still I am in no way an expert yet! ;-)
-
The cForge package in the trunk has not been touched for almost a year? But I have seen the renamed commands but I am still using this year old version. Also, my own knowledge on SVN/Git has increased ever since, still I am in no way an expert yet! ;-)
-
I haven't seen any such postings on any PR workflow, but offcourse it sounds good. A better way, if cforge can handle it, is to clone the project to the users home, then edit it and creat a PR to the original master. That workflow mimics GitHub. Is such a workflow and option? > Ticket idea! see ticket request 78: Github like workflow for PR
-
I haven't seen any such postings on any PR workflow, but offcourse it sounds good. A better way, if cforge can handle it, is to clone the project to the users home, then edit it and creat a PR to the original master. That workflow mimics GitHub. Is such a workflow and option? > Ticket idea! 78 GiIThub like workflow for PR
-
I haven't seen any such postings on any PR workflow, but offcourse it sounds good. A better way, if cforge can handle it, is to clone the project to the users home, then edit it and creat a PR to the original master. That workflow mimics GitHub. Is such a workflow and option? > Ticket idea!
-
File for testing attached Steps to repeat: 1. Download and install cforge 2. Double click this attached file to install to registry 3. Reboot(?) 4. Checkout random repository using its cforge:// link to "D:\folder with a space\" 5. Right click that folder in explorer and "create package manifest" ==>IS: "can't find D:\folder\liscence.txt" ==>SHOULD: create manifest successfully