Post by ingo on #17 The button status should follow the URL
CODESYS Forge
tickets
(Post)
labels: App --> status: open --> closed
Last updated: 2020-01-11
Post by i-campbell on #14 create Package bug
CODESYS Forge
tickets
(Post)
So we need someone to change setup.reg.. Replace: %V With: \"%V\" And then test if the problem is solved. If still doesn't work, further investigation of how the C# program calls the python program
Last updated: 2020-01-18
Post by ingo on #19 Form data is lost in mobile view
CODESYS Forge
tickets
(Post)
summary: Forn data is lost in mobile view --> Form data is lost in mobile view
Last updated: 2020-01-04
Post by ingo on #30 Checkout with cforge not working on large repos
CODESYS Forge
tickets
(Post)
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.
Last updated: 2020-08-25
Post by ingo on #25 Cannot find Product News
CODESYS Forge
tickets
(Post)
status: open --> closed
Last updated: 2020-02-21
Post by aliazzz on #15 renaming cforge commands
CODESYS Forge
tickets
(Post)
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.
Last updated: 2020-01-18
Post by ingo on #5 Implement checkout
CODESYS Forge
tickets
(Post)
status: open --> closed
Last updated: 2018-05-09
Post by erichspitzweg on #1 Implement URL Handler and framework for actions
CODESYS Forge
tickets
(Post)
status: accepted --> closed
Last updated: 2018-04-11
Post by ingo on #8 cForge installation on latest Win10 x64
CODESYS Forge
tickets
(Post)
status: open --> closed
Last updated: 2019-01-13
Post by aliazzz on #14 create Package bug
CODESYS Forge
tickets
(Post)
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
Last updated: 2020-01-18
Post by ingo on #12 CODESYS Forge needs an icon
CODESYS Forge
tickets
(Post)
Hi Aliazzz, what's wrong with the hammer? ;) What are the licenses of those images? BR, Ingo
Last updated: 2019-01-25
Post by aliazzz on #9 Draft for better bootstrapping and checking prerequisits
CODESYS Forge
tickets
(Post)
1) okay, but I only hope that the documentation generation toolchain, at least some commands of it, can be integrated into the cForge tool via some python scripts as this is relatively simple to achieve. 2) findexepath was merely intended as a proof of concept and is by no means a fully finished function. However your idea about "prerequisits.py" is more flexible/extensible then an integrated bootstrapper as you suggested. 3) I now see where your cForge tool will be headed towards. It is a good idea to add a small development-roadmap to this project in order to streamline the idea's towards the intent. Otherwise you might end up with a "swiss army knife" application without a clear goal or purpose. This unless the "swiss army knife" tool is your goal ;-)
Last updated: 2019-01-13
Post by ingo on #20 History is wrong when back button is used
CODESYS Forge
tickets
(Post)
labels: App --> status: open --> closed
Last updated: 2020-01-11
Post by ingo on #24 Logging out and reopening the app causes to be logged in again
CODESYS Forge
tickets
(Post)
labels: --> App
Last updated: 2020-02-02
Post by ingo on #16 Where can I find the version number for Android app?
CODESYS Forge
tickets
(Post)
Makes fully sense. But all at its time. And all only when it's needed. So I don't think, that there is any use for a side menu with the current feature set. At the monent an info button in the bottom menu, or even built into the menu of the website makes more sense. While side swiping is desirable. But when we do it, the whole handling of histories becomes more complex. Think of, that you swipe accidently to the side. When you swipe back again, you want to be on the same page, scroll position and you don't want to lose form data. (Just to name a few things we need to consider ;) ). So step by step.
Last updated: 2019-12-30
Post by erichspitzweg on #2 commit: Implement the action 'commit'
CODESYS Forge
tickets
(Post)
status: open --> accepted assigned_to: erichspitzweg
Last updated: 2018-04-12
Post by ingo on #16 Where can I find the version number for Android app?
CODESYS Forge
tickets
(Post)
Actually I prepared the notifications already. Mainly the compatible handling between Android Oreo and the versions before is a bit tricky and not working, yet. The versioning is not prepared, yet. Looking forward to the ideas of Erich ;)
Last updated: 2019-12-30
Post by ingo on #9 Draft for better bootstrapping and checking prerequisits
CODESYS Forge
tickets
(Post)
summary: add --> Draft for better bootstrapping and checking prerequisits
Last updated: 2019-01-13
Post by aliazzz on #8 cForge installation on latest Win10 x64
CODESYS Forge
tickets
(Post)
I added the "full path to cForge between quotes" in the bat file, which should be seen by windows as a valid path. The quotes are mandatory because the full path contains spaces. I think the problem lies in admin rights or so?
Last updated: 2018-12-31
Post by i-campbell on #12 CODESYS Forge needs an icon
CODESYS Forge
tickets
(Post)
For reference, the hammer can be seen here. https://forge.codesys.com/tol/cforge/code/HEAD/tree/branches/13-jobs/cforge/cforge/icon.ico Is the black and white 2x2x1 array-of-cubes logo just for forge, or? If so it gets my vote. I don't understand the logo of this project. Maybe an electrical 3 phase star connection point? But it's animated? I don't think it will scale well to a small icon size. And the machine designer in me feels that things don't flash when they don't need my attention.
Last updated: 2020-01-18
Post by ingo on #21 Future of cforge package
CODESYS Forge
tickets
(Post)
Hi Ian, if it's just us, lets discuss this via teams next week during worktime.
Last updated: 2020-04-12
Post by ingo on #19 Form data is lost in mobile view
CODESYS Forge
tickets
(Post)
labels: App --> status: open --> closed
Last updated: 2020-01-11
Post by ingo on #15 renaming cforge commands
CODESYS Forge
tickets
(Post)
Hi Aliazzz, sure! That sounds great!
Last updated: 2019-04-06
Post by i-campbell on #21 Future of cforge package
CODESYS Forge
tickets
(Post)
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 role for forge. 1.b Contribute new projects intending others to contribute. 1.c Contribute new projects with no intent to seek contributions. 1.d Contribute code to existing projects. 1.e Contribute non-code to existing projects, such as documentation or issue management. 1.f Take some existing code and modify it but don't contribute. 1.g Wanting to spend as little time in forge as possible, just wanting to grab the driver or lib they want. 1.h Just wanting to talk on the forum. Skill/Experience I think that some people will have varying levels of each of these skills: 2.a Computer programming 2.b Version control systems 2.c Testing 2.d CODESYS 2.e PLCs 2.f open source communities and issues 2.g Electronics 2.h Physical applications Tasks and workflows So for me the cForge tool should be aimed at users 1.b through 1.e (hereafter referred to as contributors). The main goal is to help contributors to make their projects as accessible as they want it to be for users 1.f through 1.g (hereafter referred to as audience). A secondary goal is to help the contributors make their projects easier to contribute to. So we have the documentation [forge:wiki:Home] which describes some workflows. Should CODESYS be a prerequisite? Well, what if the project doesn't have any CODESYS code? for example an open source python script to test modbus comms or something? So I think the very first getting started step is install cforge.exe. Then I would like cforge to have a developer readiness checklist: - Install CODESYS IDE (link to https://store.codesys.com/codesys.html, or maybe link to a forge page with some installation tips and tricks? both?) - Install SVN (link to store or forge) - Install Tortise SVN - Install cforge.package (will be seperate to cforge.exe) - Set path variables - Link to OAuth credentials - etc. The checkboxes can be marked by the contributor as TO DO, WON'T DO, NOT PLANNED, DONE etc. Maybe a bonus if we can autodetect some of them like isCODESYSInstalled. Then there will be some workflows, once the developer is satisfied with their PC's readiness: * Start new forge project - Driver project, lib project, hack? - Just under my user page for now? or on the main directory? - do you have files already, or do you want a blank folder to start with? Link existing forge project Then there will be a project readiness checklist, similar to the development machine readiness checklist. * SVN or Git repository created * If you're at work, do you have permission from your boss to open source this? * used external libs correctly (link to info on maintaining copyright etc) * extended someone else's work correctly (link to info) * License selected and added (link to help on selecting a license) * Is there a readme.md (button to create one and open in text editor) * Is there contrib guidelines * Package Manifest exist (button to create one) * Package exist (button to create one) * package uploaded to forge.codesys.com * Wiki exists on forge.codesys.com * Link exists on the Project Home page of project to download package * Link exists on the Project Home page to discuss project in forum (or maybe search forum for discussions related to the project) * etc. Perhaps a button to initiate a check for some of these things. For instance it could check if the manifest is up to date, or if the package installs successfully. Each task could have a "search for topic in forge docu / forge forum / help.codesys.com / google". A "Discuss topic in forum" button could create a Nicely formatted Discussion topic, with some key info already filled in, eg. cForge version, codesys version, cForge workflow item, Developer readiness %?. It may even have a template such as some subheadings [Background] [Question] Anyway thanks for listening to my rambling. If this direction for cForge is of interest I am happy to contribute further.
Last updated: 2020-02-02
Post by ingo on #21 Future of cforge package
CODESYS Forge
tickets
(Post)
Proposal: We plan a jitsi meeting to discuss and priorize this stuff. What do you think?
Last updated: 2020-04-09