Activity for CODESYS Forge
-
i-campbell posted a comment on ticket #15
Seems these two are already in Trunk https://forge.codesys.com/tol/cforge/code/HEAD/tree/trunk/cforge/cforge/Package/CFORGE/Setup.reg#l41 aliazzz, are you satisfied with the slightly modified "Create Package Manifest"? Also noting here, I looked at the other commands and think they are self explanatory if you are familiar with SVN, or Google the SVN concepts. If you are happy with that text, I will test this also next week and post here if the change made works. (Or, if someone else has the latest...
-
I think the "pull request" workflow at the moment is as follows: 1. create a ticket 2. Checkout 3. Make changes 4. Test changes 5. Upload the changed files to the ticket and say "dear maintainer, please accept this change because...". It's in the documentation somewhere. OK, I will make the change and test. Will have to wait until next week.
-
aliazzz posted a comment on ticket #14
Why don't you do the change and test? I haven't got write-access
-
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
-
I never recognised it until you finally revealed it.
-
Hi, just some thoughts: GIT integration for cForge (and a plugin for GIT in CODESYS IDE?) would be very very favourable! Extend cForge with Webhooks to let any builder (arbitrairly which or where) start a job very cool! Generating .CHM and or .PDF documentation (with choice of a few cool prefab documentation frames) from the reSructured text in a project or Library Letting cForge Tool run a custom user made script from windows explorer with a right click (an "execute custom" command). What the script...
-
I cannot try it out any more, but in hindsight, without even trying your suggestion I'd say point 2 is valid. Whenever spaces are present in a windows path, one must open and close the entire string with surrounding quotes. So It should be: "%V".
-
Without even trying your suggestion I'd say point 2 is valid. Whenever spaces are present in a windows path, one must open and close the entire string with surrounding quotes. So It should be: "%V"
-
Without even trying your suggestion I'd say point 2 is valid. Whenever spaces are present in a windows path, on must open/close the entire string with quotes. So It should be: "%V"
-
Without even trying your suggestion I'd say point 2 is valid. Whenever spaces are present in a windows path, on must open/close the entire string with ". So It should be: "%V"
-
Ingo created ticket #21
Future of cforge package
-
Haha, it is a flux compensator (back to future). ;) But I think we change this after we get the App Logo from marketing. Then the direction becomes more clear.
-
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.
-
CWD is Current Working Directory as seen by the cforge c# application. This is where the context menu is setup for the create package https://forge.codesys.com/tol/cforge/code/HEAD/tree/trunk/cforge/cforge/Package/CFORGE/Setup.reg#l62 So it will be calling : cmd /C cforge.exe --create-package C:\Users\user\Desktop\I2C mcp7941x Code for cforge.exe is here: https://forge.codesys.com/tol/cforge/code/HEAD/tree/trunk/cforge/cforge/Program.cs So it can be seen it then passes those two arguments to the...
-
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 221 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.
-
The button status should follow the URL
-
Click on notification should lead to the corresponding page
-
updated cforge package
-
ingo <> committed [7e660b]
[#18] Click on notification should lead to the corresponding page
-
Form data is lost in mobile view
-
Form data is lost in mobile view
-
fixed it wrote this ... pressed back button ... and clicked on this ticket again ... => Works ;)
-
updated cforge package
-
ingo <> committed [567601]
- update currentURL when back button is pressed
-
History is wrong when back button is used
-
History is wrong when back button is used
-
Form data is lost in mobile view
-
Forn data is lost in mobile view
-
Click on notification should lead to the corresponding page
-
The button status should follow the URL
-
ingo <> committed [8adee1]
removed diaplay of version toast
-
updated app w/ changes to versioning and fix in notification handling
-
ingo <> committed [080df0]
corrected parsing of news status
-
ingo <> committed [e91c54]
[#16] merged changes from erichspitzweg
-
codesys.com modified ticket #16
Where can I find the version number for Android app?
-
Merged changes from erichspitzweg. Version number is the build date, and it is shown in the app-info as well as a short message at startup.
-
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...
-
Suggestion: why don't you borrow idea's from the Codesys web view app? Sideswipe menu etc etc.
-
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 ;)
-
erichspitzweg modified ticket #16
Where can I find the version number for Android app?
-
PS looking forward to see more advanced features like notifications! ;-)
-
Where can I find the version number for Android app?
-
ingo <> committed [94fecf]
corrected feed urls
-
corrected notification feed urls
-
added notification mechanism
-
ingo <> committed [33c326]
- added service for long polling (every hour) for changes
-
ingo <> committed [bfdae0]
fixed bug by rotating the device
-
fixed bug while rotating the device
-
first alpha of the android app
-
ingo <> committed [f71d5b]
initial import
-
pointed image to local
-
Autoversioning commit: a non-deltaV client made a change to
-
Autoversioning commit: a non-deltaV client made a change to
-
Autoversioning commit: a non-deltaV client made a change to
-
corrected name of build and commit module, when they are included in cforge.exe
-
I understand it to be interfaces hooked together I guess.
-
What do you think about the one in the project? (didn't scale it for the package, yet)
-
Merge Request on branch "13-jobs". Sample JSON, which needs to be passed via a file as the first argument to the command "job": { "project" : "tol/cforge", "user" : "test", "pass" : "test", "actions" : [ { "cmd" : "build", "repo" : "tol,cforge,code"} ] }
-
Automatic Build
-
Merge Request on branch "13-jobs". Sample JSON, which needs to be passed via a file as the first argument to the command "job": { "project" : "tol/cforge", "user" : "test", "pass" : "test", "actions" : { "cmd" : "build", "repo" : "tol,cforge,code"} }
-
Load JSON commands from file, instead as an argument.
-
Autoversioning commit: a non-deltaV client made a change to
-
Hi Aliazzz, sure! That sounds great!
-
renaming cforge commands
-
create Package bug
-
[#13] Automatic Build
-
[#13] automatic build branch
-
Automatic Build
-
Home
-
Home
-
You didn't step on any toes! Really not! ;) Honestly the reaction of our marketing regarding the hammer was similar ;) Regarding the copyright thing: I care mich about licenses and copyrights. Therefore I will only use 3rd party material when the copyright is clear. Another idea is to use simply the black wires CODESYS Logo.
-
Hi, I did not know the hammer was the package icon until I installed the the update you posted today. I just thought the the "swiss army knife" image was kind of fitting after our last exchange. About the rights, I just plucked the images via google while searching for "swiss army knife icon". I dont think this icon has right because it's not the real "swiss army knife" emblem but a generic one. Anyway, I did not intend to infringe copyrights or to step on any toes in regards of the hammer. Alia...
-
Hi Aliazzz, what's wrong with the hammer? ;) What are the licenses of those images? BR, Ingo
-
CODESYS Forge needs an icon
-
Support new commands from the Projects website
-
Honestly? The swiss army knife is my first intend ;) But you are right. There are new ideas around for a better integration. After a proof of concept, and a decision, you are right, we can illustrate the goal or roadmap. For now: My current Vision is a similar usability as Crossover office is giving the users. You have a set of tools, which can be used by their own. And then you have a frontend, which gives you easy access to the tools for your personal projects.
-
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...
-
The idea is good. But two things: 1) I would not mix bootstrapping (or maybe better "prerequisit check") with the libdoc exe detection 2) FindExePath tries to expand the exe name with environment variables. That makes IMHO not much sense. Maybe this function needs to be reworked before it can be integrated But another idea: svn.exe is needed only necessary for a few python scripts. But on the other hand, there might be some more prerequisits to check. What's if we don't check it in C# at time of...
-
Draft for better bootstrapping and checking prerequisits
-
attachments to ticket 9
-
Seems like all is already attached.
-
cForge installation on latest Win10 x64
-
I added the hint with TortoiseSVN to the prerequisits.
-
Home
-
add
-
adding a "generate-chm.py" command to CFORGE
-
attachments to ticket 9
-
To make life easier I added the files and the output as attachments
-
add
-
This issue is resolved, this ticket can be closed.
-
.
-
I found the issue on my devbox: Turtoise SVN cmd tools were not installed, which your tool uses, as you said: "You will need to install a command line SVN client." I have added a screenshot of the mandatory selection in svn installer.
-
"You will need to install a command line SVN client."
-
I found the issue on my devbox: Turtoise SVN cmd tools were not installed, which your tool uses. I have added a screenshot of the mandatory selection in svn installer.
-
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?
-
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.
-
OK, and sadly I was not able to reproduce the issue. I used SP14 64Bit on a Win10 VM from here. Everything worked. Except, that the package download in IE was a bit anoying. It always renamed my package to *.zip ;) BTW: I didn't need to change the Setup.bat. It doesn't contain any path information. What did you change there?
-
Extra feedback; I have had Turtoise SVN installed before I installed the CODESYS cForge & SVN package (!) Still, I will check the windows environment variables (paths) and your other tips.
-
Hi Aliazzz! At least the last error message sounds clear to me. Sorry that the prerequisits checks are not good enough, yet. You will need to install a command line SVN client. I usually install Tortoise SVN and check the "add to path"-Option during the installation. But you can also just install the svn tools from somewhere else. They just need to be found in the path. You can check that by opening the the windows command line and enter "svn -h". This command should succeed. I will try to reproduce...
-
cForge installation on latest Win10 x64