Ticket #8: Snapshots are not working
CODESYS Forge
support
(Ticket)
Snapshots are not created. The process never finishes2020-02-08 02:19:34.045000 Ticket #8: Snapshots are not working CODESYS Forge forge tickets support False /forge/support/8/ Ticket Snapshots are not working False 2 2018-02-19 22:39:25.449000 8 Snapshots are not working closed Snapshots are not created. The process never finishes False False 0 0 0 None ingo None
Last updated: 2020-02-08
Ticket #9: Duplicated "Projects in same catagories"
CODESYS Forge
support
(Ticket)
The projects are listed multiple times when they are both in the same catagories (which is not seldom ;) )2020-02-08 02:19:34.057000 Ticket #9: Duplicated "Projects in same catagories" CODESYS Forge forge tickets support False /forge/support/9/ Ticket Duplicated "Projects in same catagories" False 2 2018-02-20 08:19:49.584000 9 Duplicated "Projects in same catagories" closed The projects are listed multiple times when they are both in the same catagories (which is not seldom ;) ) False False 0 0 0 None ingo ingo
Last updated: 2020-02-08
Ticket #10: Tracker Import
CODESYS Forge
support
(Ticket)
Tracker Import is not working2020-02-08 02:19:34.021000 Ticket #10: Tracker Import CODESYS Forge forge tickets support False /forge/support/10/ Ticket Tracker Import False 2 2018-02-22 20:20:47.847000 10 Tracker Import closed Tracker Import is not working False False 0 0 0 None ingo None
Last updated: 2020-02-08
Ticket #11: Overlapping text in title on small screens
CODESYS Forge
support
(Ticket)
For example: https://forge.codesys.com/tol/wharfie/wiki/Home/2020-02-08 02:19:34.022000 Ticket #11: Overlapping text in title on small screens CODESYS Forge forge tickets support False /forge/support/11/ Ticket Overlapping text in title on small screens False 2 2018-03-31 21:31:25.891000 11 Overlapping text in title on small screens closed For example: https://forge.codesys.com/tol/wharfie/wiki/Home/ False False 0 0 0 None ingo ingo
Last updated: 2020-02-08
Ticket #12: Some functions are not working on mobile devices
CODESYS Forge
support
(Ticket)
I encountered currently two functions, that are simply showing no effect when clicking on them on mobile browsers (tested with chrome): Edit Button on Support Tickets Reply Button in Forums / Discussions Maybe there are more...2020-02-08 02:19:34.034000 Ticket #12: Some functions are not working on mobile devices CODESYS Forge forge tickets support False /forge/support/12/ Ticket Some functions are not working on mobile devices False 2 2018-05-06 06:09:29.169000 12 Some functions are not working on mobile devices closed I encountered currently two functions, that are simply showing no effect when clicking on them on mobile browsers (tested with chrome): Edit Button on Support Tickets Reply Button in Forums / Discussions Maybe there are more... False False 0 0 0 None ingo ingo
Last updated: 2020-02-08
Ticket #13: Ticket tool in mobile view has some issues
CODESYS Forge
support
(Ticket)
search is not linked Bulk Edit is not labeled result table is not horizontally scroll width is sometimes not limited e.g. https://forge.codesys.com/tol/cforge/tickets/5/2020-02-08 02:19:34.051000 Ticket #13: Ticket tool in mobile view has some issues CODESYS Forge forge tickets support False /forge/support/13/ Ticket Ticket tool in mobile view has some issues False 3 2018-05-08 19:50:02.491000 13 Ticket tool in mobile view has some issues closed - search is not linked - Bulk Edit is not labeled - result table is not horizontally scroll - width is sometimes not limited e.g. https://forge.codesys.com/tol/cforge/tickets/5/ False False 0 0 0 None ingo ingo
Last updated: 2020-02-08
Ticket #14: Width in sourcebrowser is too small on mobile devices
CODESYS Forge
support
(Ticket)
Example: https://forge.codesys.com/tol/cforge/code/HEAD/tree/trunk/cforge/cforge/Package/CFORGE/Scripts/import.py2020-02-08 02:19:34.065000 Ticket #14: Width in sourcebrowser is too small on mobile devices CODESYS Forge forge tickets support False /forge/support/14/ Ticket Width in sourcebrowser is too small on mobile devices False 2 2018-05-12 14:36:19.738000 14 Width in sourcebrowser is too small on mobile devices closed Example: https://forge.codesys.com/tol/cforge/code/HEAD/tree/trunk/cforge/cforge/Package/CFORGE/Scripts/import.py False False 0 0 0 None ingo admin
Last updated: 2020-02-08
Ticket #15: Source code is not indexed
CODESYS Forge
support
(Ticket)
For example cforge_usage should be found with global search. Google is indexing this. So why should we only find it on google, but not locally2020-02-08 02:19:34.041000 Ticket #15: Source code is not indexed CODESYS Forge forge tickets support False /forge/support/15/ Ticket Source code is not indexed False 2 2018-05-12 14:39:53.111000 15 Source code is not indexed closed For example cforge_usage should be found with global search. Google is indexing this. So why should we only find it on google, but not locally False False 0 0 0 None ingo ingo
Last updated: 2020-02-08
Ticket #16: Overflows in mobile view
CODESYS Forge
support
(Ticket)
Here starts a list of Overflows in mobile view: - https://forge.codesys.com/forge/wiki/Project%20Maintenance/ Sadly I need to push the author of wikipages to the top again, as the display: table-footer-group had side effects.2020-02-08 02:19:34.049000 Ticket #16: Overflows in mobile view CODESYS Forge forge tickets support False /forge/support/16/ Ticket Overflows in mobile view False 2 2018-05-21 04:44:00.977000 16 Overflows in mobile view closed Here starts a list of Overflows in mobile view: - https://forge.codesys.com/forge/wiki/Project%20Maintenance/ Sadly I need to push the author of wikipages to the top again, as the display: table-footer-group had side effects. False False 0 0 0 None admin None
Last updated: 2020-02-08
Ticket #17: Markdown is not well editable on small screens
CODESYS Forge
support
(Ticket)
This is an Accident of: [#12] Some functions are not working on mobile devices Now those functions are working as we implemented a wrapper for codemirror, but the field is now too small and not scrollable. You can type a sequential text (like I do now), but you can't navigate and modify a larger text.2020-02-08 02:19:34.027000 Ticket #17: Markdown is not well editable on small screens CODESYS Forge forge tickets support False /forge/support/17/ Ticket 12 Markdown is not well editable on small screens False 4 2018-05-23 17:52:39.248000 17 Markdown is not well editable on small screens closed This is an Accident of: [#12] Some functions are not working on mobile devices Now those functions are working as we implemented a wrapper for codemirror, but the field is now too small and not scrollable. You can type a sequential text (like I do now), but you can't navigate and modify a larger text. False False 0 0 0 None admin ingo
Last updated: 2020-02-08
Ticket #18: Attaching files to blog posts doesn't work
CODESYS Forge
support
(Ticket)
2020-02-08 02:19:34.040000 Ticket #18: Attaching files to blog posts doesn't work CODESYS Forge forge tickets support False /forge/support/18/ Ticket Attaching files to blog posts doesn't work False 2 2018-07-04 22:34:35.787000 18 Attaching files to blog posts doesn't work closed False False 0 0 0 None ingo None
Last updated: 2020-02-08
Ticket #19: Source Browser: revisioned content is not shown
CODESYS Forge
support
(Ticket)
It is somehow related to the double slashes in the URL. "merge_slashes on" doesn't help. e.g.: https://forge.codesys.com/drv/spi-temperature/code/10/tree/trunk/ ... works, while: https://forge.codesys.com/drv/spi-temperature/code/10/tree//trunk/ ... doesn't. 2020-02-08 02:19:34.017000 Ticket #19: Source Browser: revisioned content is not shown CODESYS Forge forge tickets support False /forge/support/19/ Ticket Source Browser: revisioned content is not shown False 3 2018-07-28 18:25:28.465000 19 Source Browser: revisioned content is not shown closed It is somehow related to the double slashes in the URL. "merge_slashes on" doesn't help. e.g.: https://forge.codesys.com/drv/spi-temperature/code/10/tree/trunk/ ... works, while: https://forge.codesys.com/drv/spi-temperature/code/10/tree//trunk/ ... doesn't. False False 0 0 0 None ingo None
Last updated: 2020-02-08
Ticket #20: Cookie confirmation doesn't work in IE
CODESYS Forge
support
(Ticket)
The style of the cookie confirmation doesn't work in IE. See attachment.2020-02-08 02:19:34.023000 Ticket #20: Cookie confirmation doesn't work in IE CODESYS Forge forge tickets support False /forge/support/20/ Ticket Cookie confirmation doesn't work in IE False 2 2018-09-13 09:20:45.560000 20 Cookie confirmation doesn't work in IE closed The style of the cookie confirmation doesn't work in IE. See attachment. False False 0 0 0 None ingo codesys-com
Last updated: 2020-02-08
Ticket #21: Edit / create a new wiki for "Developer guide & tips"
CODESYS Forge
support
(Ticket)
Hi Ingo, Can you create a freely editable wiki for named "Developer guide & tips" ? Also, someone (you ;-) ) should have the ultimate rights to lock/unlock it whenever appropriate so that it will not be edited all year around. I suspect it will be edited a lot because it is still young and new tips will be added frequently or current content gets revised. According to suggestion; We can start a WIKI in cforge called "Developer guide & tips" which can contain a compendium of good practices like versioning tips, coding style tips etc etc. Versioning tips; -All developers should stick to one version of the development environment to avoid any confusion (not only for libraries). Offcourse, users can use any version.In any case, the user must know project (library) format before download. This format must be one for target device (RPi3, ...). - "used compiler version" and "project file format" are different things. You can e.g. use 3.5.10.0 version as compiler but e.g. 3.5.11.0 version for the project file format. - As long as your project is not finished, stick to the chosen version of compiler and project format; - ; etc. Coding tips; - for RTS_IEC_HANDLE and RTS_IEC_RESULT types need to add SysTypes2 Interfaces (3.5.4.0); - if possible, use standard error codes (CmpErrors or CmpErrors2 Interfaces); - avoid using dynamic memory (the usage of NEW operator); - use the ST language whenever possible (ST is by far the most versatile language, in which all operations, manipulations and functions are possible); - document the source code (add meaningful comments); - for modern coding style advice: read the Codesys v3 library development tips as provided in codesys help - guidelines for creating libraries, They are pretty good but, but not as thorough as "code complete" but provide a very good starting point. Further reading: e.g. Steve McConnell "Code Complete"; -; etc.2020-02-08 02:19:34.032000 Ticket #21: Edit / create a new wiki for "Developer guide & tips" CODESYS Forge forge tickets support False /forge/support/21/ Ticket Edit / create a new wiki for "Developer guide & tips" False 3 2018-09-22 19:46:41.790000 21 Edit / create a new wiki for "Developer guide & tips" closed Hi Ingo, Can you create a freely editable wiki for named "Developer guide & tips" ? Also, someone (you ;-) ) should have the ultimate rights to lock/unlock it whenever appropriate so that it will not be edited all year around. I suspect it will be edited a lot because it is still young and new tips will be added frequently or current content gets revised. According to suggestion; We can start a WIKI in cforge called "Developer guide & tips" which can contain a compendium of good practices like versioning tips, coding style tips etc etc. Versioning tips; -All developers should stick to one version of the development environment to avoid any confusion (not only for libraries). Offcourse, users can use any version.In any case, the user must know project (library) format before download. This format must be one for target device (RPi3, ...). - "used compiler version" and "project file format" are different things. You can e.g. use 3.5.10.0 version as compiler but e.g. 3.5.11.0 version for the project file format. - As long as your project is not finished, stick to the chosen version of compiler and project format; - ; etc. Coding tips; - for RTS_IEC_HANDLE and RTS_IEC_RESULT types need to add SysTypes2 Interfaces (3.5.4.0); - if possible, use standard error codes (CmpErrors or CmpErrors2 Interfaces); - avoid using dynamic memory (the usage of NEW operator); - use the ST language whenever possible (ST is by far the most versatile language, in which all operations, manipulations and functions are possible); - document the source code (add meaningful comments); - for modern coding style advice: read the Codesys v3 library development tips as provided in codesys help - guidelines for creating libraries, They are pretty good but, but not as thorough as "code complete" but provide a very good starting point. Further reading: e.g. Steve McConnell "Code Complete"; -; etc. False False 0 0 0 None *anonymous ingo
Last updated: 2020-02-08
Ticket #22: Wiki permissions can't be edited
CODESYS Forge
support
(Ticket)
Opening the permissions page of a wiki leads to a routing error.2020-02-08 02:19:34.026000 Ticket #22: Wiki permissions can't be edited CODESYS Forge forge tickets support False /forge/support/22/ Ticket Wiki permissions can't be edited False 2 2018-09-23 21:10:29.745000 22 Wiki permissions can't be edited closed Opening the permissions page of a wiki leads to a routing error. False False 0 0 0 None ingo ingo
Last updated: 2020-02-08
Ticket #23: Logout not working correct
CODESYS Forge
support
(Ticket)
Logout not working properly if authenticated with https://account.codesys.com.2020-02-08 02:19:34.020000 Ticket #23: Logout not working correct CODESYS Forge forge tickets support False /forge/support/23/ Ticket login logout account Logout not working correct False 2 2018-09-24 14:37:08.715000 23 Logout not working correct closed Logout not working properly if authenticated with https://account.codesys.com. False False 1 0 1 None ferag-com codesys-com
Last updated: 2020-02-08
Ticket #24: Link to home on codesys logo
CODESYS Forge
support
(Ticket)
On 3S Sites the company logo is linked to the home site (e.g. click on the Codesys Logo in the Store leads to https://store.codesys.com/). But this is not working in this site. Is that on purpose? 2020-02-08 02:19:34.047000 Ticket #24: Link to home on codesys logo CODESYS Forge forge tickets support False /forge/support/24/ Ticket usability Link to home on codesys logo False 2 2018-09-26 18:34:01.123000 24 Link to home on codesys logo closed On 3S Sites the company logo is linked to the home site (e.g. click on the Codesys Logo in the Store leads to https://store.codesys.com/). But this is not working in this site. Is that on purpose? False False 0 0 0 None heinzf codesys-com
Last updated: 2020-02-08
Ticket #25: Send message to user not working
CODESYS Forge
support
(Ticket)
On click on send message button in the user view, the following error occours: Error 500 We're sorry but we weren't able to process this request. 2020-02-08 02:19:34.034000 Ticket #25: Send message to user not working CODESYS Forge forge tickets support False /forge/support/25/ Ticket bug Send message to user not working False 3 2018-09-27 18:06:04.620000 25 Send message to user not working closed On click on send message button in the user view, the following error occours: Error 500 We're sorry but we weren't able to process this request. False False 0 0 0 None heinzf codesys-com
Last updated: 2020-02-08
Ticket #26: List of latest additions/mutaions of pages in cForge
CODESYS Forge
support
(Ticket)
Hi, I'd like to request a functionality which shows a summary of the latest additions/mutations/deletions within cforge. In short, a list with pages which have been updated most recently ands shows what, where, when and by who, etc, etc.. Currently it's rather difficult to find out if anythings has been added/edited. Maybe such a functionality is allready available, but I have not discovered it (yet)?2020-02-08 02:19:34.078000 Ticket #26: List of latest additions/mutaions of pages in cForge CODESYS Forge forge tickets support False /forge/support/26/ Ticket new cforge functionality List of latest additions/mutaions of pages in cForge False 2 2018-09-27 18:39:24.731000 26 List of latest additions/mutaions of pages in cForge closed Hi, I'd like to request a functionality which shows a summary of the latest additions/mutations/deletions within cforge. In short, a list with pages which have been updated most recently ands shows what, where, when and by who, etc, etc.. Currently it's rather difficult to find out if anythings has been added/edited. Maybe such a functionality is allready available, but I have not discovered it (yet)? False False 0 0 0 None aliazzz codesys-com
Last updated: 2020-02-08
Ticket #27: Delete of Projects
CODESYS Forge
support
(Ticket)
Is it possible to remove/delete a project?2020-02-08 02:19:34.025000 Ticket #27: Delete of Projects CODESYS Forge forge tickets support False /forge/support/27/ Ticket usability Delete of Projects False 2 2018-09-28 18:02:50.536000 27 Delete of Projects closed Is it possible to remove/delete a project? False False 0 0 0 None heinzf codesys-com
Last updated: 2020-02-08
Ticket #28: Collaboration possibilitieswith other board members
CODESYS Forge
support
(Ticket)
Hi there, After some try-outs on cforge I am beginning to see a communication issue in usage of this portal that could be needs to be addresed (fine-polished over time). I tried various ways to contact other board members personally (incl Ingo, but anwser yet). Contacting other members should be made as easy as possible by cforge as this will enable us to collaborate better. => How do we contact each other personally (if opted in) in a transparant easy way and and how do we get feedback of this proces? => If I post a question or remark under a wiki (or project etc), how do I know for sure someone will find it and respond within a reasonable timelimit if that is asked for? => How do I check if something has been added changed within the entire CMS? (this is an earlier ticket) Also, a request with personal high importance! Can someone please post a proper working open source IO driver example with the devdescr? A small driver/wrappare around an fb with some in/output parameters to a user program as BOOL/REAL or so would be enough to mimick the mechanism, as I am not getting mine to work with the currently provided hints! As I want to build a proper IO driver for a raspberry pi HAT that interacts with the user program via parameters, the demonstrated mechanic is not working (at least I am not getting that to work). As far as my knowledge goes the FB in question should EXTENDS IoDrvBase IMPLEMENTS ICmpIoDrvParameter. I wrote this kind of a driver half a year ago, but it was no walk in the park without proper documentation/guidance! :-( So, I am hoping with help of this platform I can revisit it and learn to make my driver leaner and meaner!... So, the wiki is currently sadly still incomplete (but I found it very useful ;-) ) about this specific mechanic. At the moment the wiki only tells very little about the actual used methods for the IO driver FB, but does not show code/examples on how to properly achive this. So, examples wanted, because what is currently is shown in the posted I2c /SPI driver (r10) is how to write a static value from the parameters into into an FB. Offcourse, this can be mimicked and expanded upon, but as far as I know this will not be enough for my needs. If I am mistaking on the IO driver, please forgive and show me the proper way! PS I can show working code/results on where I am now! With kind regards! Aliazzz2020-02-08 02:19:34.015000 Ticket #28: Collaboration possibilitieswith other board members CODESYS Forge forge tickets support False /forge/support/28/ Ticket Collaboration possibilitieswith other board members False 2 2018-09-30 20:44:36.996000 28 Collaboration possibilitieswith other board members closed Hi there, After some try-outs on cforge I am beginning to see a communication issue in usage of this portal that could be needs to be addresed (fine-polished over time). I tried various ways to contact other board members personally (incl Ingo, but anwser yet). Contacting other members should be made as easy as possible by cforge as this will enable us to collaborate better. => How do we contact each other personally (if opted in) in a transparant easy way and and how do we get feedback of this proces? => If I post a question or remark under a wiki (or project etc), how do I know for sure someone will find it and respond within a reasonable timelimit if that is asked for? => How do I check if something has been added changed within the entire CMS? (this is an earlier ticket) Also, a request with personal high importance! Can someone please post a proper working open source IO driver example with the devdescr? A small driver/wrappare around an fb with some in/output parameters to a user program as BOOL/REAL or so would be enough to mimick the mechanism, as I am not getting mine to work with the currently provided hints! As I want to build a proper IO driver for a raspberry pi HAT that interacts with the user program via parameters, the demonstrated mechanic is not working (at least I am not getting that to work). As far as my knowledge goes the FB in question should EXTENDS IoDrvBase IMPLEMENTS ICmpIoDrvParameter. I wrote this kind of a driver half a year ago, but it was no walk in the park without proper documentation/guidance! :-( So, I am hoping with help of this platform I can revisit it and learn to make my driver leaner and meaner!... So, the wiki is currently sadly still incomplete (but I found it very useful ;-) ) about this specific mechanic. At the moment the wiki only tells very little about the actual used methods for the IO driver FB, but does not show code/examples on how to properly achive this. So, examples wanted, because what is currently is shown in the posted I2c /SPI driver (r10) is how to write a static value from the parameters into into an FB. Offcourse, this can be mimicked and expanded upon, but as far as I know this will not be enough for my needs. If I am mistaking on the IO driver, please forgive and show me the proper way! PS I can show working code/results on where I am now! With kind regards! Aliazzz False False 0 0 0 None aliazzz codesys-com
Last updated: 2020-02-08
Ticket #29: Attachments on Hacks Blog don't work
CODESYS Forge
support
(Ticket)
Attachments on the CODESYS Hacks Blog don't work. When clicking on the "attach" link after selecting the file, nothing happens.2020-02-08 02:19:34.031000 Ticket #29: Attachments on Hacks Blog don't work CODESYS Forge forge tickets support False /forge/support/29/ Ticket Attachments on Hacks Blog don't work False 2 2018-10-01 05:44:47.561000 29 Attachments on Hacks Blog don't work closed Attachments on the CODESYS Hacks Blog don't work. When clicking on the "attach" link after selecting the file, nothing happens. False False 0 0 0 None ingo None
Last updated: 2020-02-08
Ticket #30: favicon.ico
CODESYS Forge
support
(Ticket)
Hi There, It would be very nice if cforge gets its own favicon (website icon). Thank you!2020-02-08 02:19:34.027000 Ticket #30: favicon.ico CODESYS Forge forge tickets support False /forge/support/30/ Ticket favicon.ico favicon.ico False 2 2018-10-19 11:15:27.982000 30 favicon.ico closed Hi There, It would be very nice if cforge gets its own favicon (website icon). Thank you! False False 0 0 0 None aliazzz codesys-com
Last updated: 2020-02-08
Ticket #31: Script language Python in CODESYS V3 wiki
CODESYS Forge
support
(Ticket)
Dear Ticketmaster =) Lately I have used the Python Script Engine in CODESYS to automate various things like auto-edit the Project Information etc. I have found that Help.Codesys.Com is not providing nearly enough codesnippers, and searching the forum was a tedious task (more like stumble upon!). For sure, you at CODESYS have a large compendium of know-how in this area! Its just that the know-how is very scattered (just like my previous experience on writing IO drivers before using cForge). So, as (iron)Python scripting in CODESYS will definatly add a new dimension it at least deserves its owncorner in within cForge! What I would like to see is more information on list of external tools can be used to write Python scripts. * Notepad++ * - Does not provide sufficient intellisense help * +Small installation footprint http://eric-ide.python-projects.org/ Provides sufficient intellisense help Large and complex installation footprint: composed of several independant but mandatory tools (Qt, Python, etc etc) Visual Studio .NET 2015 with a python plugin (I am interested in this flavour but have not tried it yet) Provides sufficient intellisense help (I assume!) Large installation footprint (VS.NET + Python plugin) And offcourse more background information on the CODESYS scriptengine objects and for every member within the scriptengine some small code example of how to use this member; from __future__ import print_function from scriptengine import * for member in dir(scriptengine): print(member) I know this is a lot on the first go, but heck, rome wasn't built in one day either! With kind regards Aliazzz 2020-02-08 02:19:34.038000 Ticket #31: Script language Python in CODESYS V3 wiki CODESYS Forge forge tickets support False /forge/support/31/ Ticket Script language Python in CODESYS V3 wiki False 2 2018-10-27 10:36:33.832000 31 Script language Python in CODESYS V3 wiki closed Dear Ticketmaster =) Lately I have used the Python Script Engine in CODESYS to automate various things like auto-edit the Project Information etc. I have found that Help.Codesys.Com is not providing nearly enough codesnippers, and searching the forum was a tedious task (more like stumble upon!). For sure, you at CODESYS have a large compendium of know-how in this area! Its just that the know-how is very scattered (just like my previous experience on writing IO drivers before using cForge). So, as (iron)Python scripting in CODESYS will definatly add a new dimension it at least deserves its owncorner in within cForge! What I would like to see is more information on list of external tools can be used to write Python scripts. * Notepad++ * - Does not provide sufficient intellisense help * +Small installation footprint http://eric-ide.python-projects.org/ Provides sufficient intellisense help Large and complex installation footprint: composed of several independant but mandatory tools (Qt, Python, etc etc) Visual Studio .NET 2015 with a python plugin (I am interested in this flavour but have not tried it yet) Provides sufficient intellisense help (I assume!) Large installation footprint (VS.NET + Python plugin) And offcourse more background information on the CODESYS scriptengine objects and for every member within the scriptengine some small code example of how to use this member; from __future__ import print_function from scriptengine import * for member in dir(scriptengine): print(member) I know this is a lot on the first go, but heck, rome wasn't built in one day either! With kind regards Aliazzz False False 0 0 0 None aliazzz codesys-com
Last updated: 2020-02-08
Ticket #32: LibDocScripting corner
CODESYS Forge
support
(Ticket)
Hi Ingo, As you allready guessed, I'd like to suggest a Tools/LibDocScripting corner in cForge. I actually have used reStructeredText allready in several professional Libraries I wrote for my employer. This corner could give some extra insights /tips/tools on how to produce self documenting libraries/applications and how to autogenerate .chm's or pdf (or html). My personal experience is that beginners will have a tough understanding of the toolchain in place to generate the documentation out of the libraries/projects because the documentation on this point is somewhat "tough". Beginners difficulties could be: Understanding of the workflow in the toolchain in general (the picture helps a lot in the documentation, but I foresee beginners will still have trouble), Adding CODESYS LibDocSctripting to PATH environment of windows (how to with pictures missing), Mandatory third party installation of HTMLWorkshop to generate .chm's (not explained that well) Mandatory third party installalion of "Sphinx" and /or "rst2pdf" python tools to generate .pdf out of either latex or .rst files (not explained well). * Providing a "workflow" example for all the above points, which goal is to more straightforward then the help files examples (which are not that clear for newcommers) . The workflow examples in documentation (especially generating .pdf) will fail if one follows it to the letter. This has to do with assumptions in directories. Hope you pick this up2020-02-08 02:19:34.037000 Ticket #32: LibDocScripting corner CODESYS Forge forge tickets support False /forge/support/32/ Ticket LibDocScripting corner False 2 2018-11-01 22:35:33.360000 32 LibDocScripting corner closed Hi Ingo, As you allready guessed, I'd like to suggest a Tools/LibDocScripting corner in cForge. I actually have used reStructeredText allready in several professional Libraries I wrote for my employer. This corner could give some extra insights /tips/tools on how to produce self documenting libraries/applications and how to autogenerate .chm's or pdf (or html). My personal experience is that beginners will have a tough understanding of the toolchain in place to generate the documentation out of the libraries/projects because the documentation on this point is somewhat "tough". Beginners difficulties could be: Understanding of the workflow in the toolchain in general (the picture helps a lot in the documentation, but I foresee beginners will still have trouble), Adding CODESYS LibDocSctripting to PATH environment of windows (how to with pictures missing), Mandatory third party installation of HTMLWorkshop to generate .chm's (not explained that well) Mandatory third party installalion of "Sphinx" and /or "rst2pdf" python tools to generate .pdf out of either latex or .rst files (not explained well). * Providing a "workflow" example for all the above points, which goal is to more straightforward then the help files examples (which are not that clear for newcommers) . The workflow examples in documentation (especially generating .pdf) will fail if one follows it to the letter. This has to do with assumptions in directories. Hope you pick this up False False 0 0 0 None aliazzz codesys-com
Last updated: 2020-02-08