<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd">
	<channel>
<title>PLCEdit News</title><link>http://www.plcedit.org/index.html</link><description>News of PLCEdit development</description><dc:language>(null)</dc:language><dc:creator>PLCEdit.org</dc:creator><dc:rights>Copyright 2005-2010 M. Rehfeldt</dc:rights><dc:date>2010-12-12T18:11:17+01:00</dc:date><admin:generatorAgent rdf:resource="http://www.realmacsoftware.com/" />
<admin:errorReportsTo rdf:resource="mailto:PLCEdit.org" /><sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
<lastBuildDate>Sun, 12 Dec 2010 18:31:52 +0100</lastBuildDate><item><title>Dev Report No. 11</title><dc:creator>PLCEdit.org</dc:creator><category>PLCEdit News</category><dc:date>2010-12-12T18:11:17+01:00</dc:date><link>http://www.plcedit.org/blog/files/7ee6b5dfbdccb4fc68a2adbb2f3ab9dd-33.php#unique-entry-id-33</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/7ee6b5dfbdccb4fc68a2adbb2f3ab9dd-33.php#unique-entry-id-33</guid><content:encoded><![CDATA[After working some months with version 2.2.1 I saw some bugs which 


should be fixed.   Especially the CAL converter did not work as expected


in every case.   Now I tried to use a regular expression comparison to


enforce a correct detection of real CAL blocks in IL source code.


I have some more small improvements in mind and a new release will


come during next month.   Just ask me if you need a preliminarily release 


with the current fixes ask me.]]></content:encoded></item><item><title>Release v2.2.1</title><dc:creator>PLCEdit.org</dc:creator><category>Announcements</category><dc:date>2010-07-11T09:59:56+02:00</dc:date><link>http://www.plcedit.org/blog/files/ee6aa606fea0e928fbaa0eb4f0b35463-32.php#unique-entry-id-32</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/ee6aa606fea0e928fbaa0eb4f0b35463-32.php#unique-entry-id-32</guid><content:encoded><![CDATA[Today we see a minor update of PLCEdit - Version 2.2.1.   It comes with some


bug fixes and also some nice to have features.   Implementations of bigger key


features will not placed this year, maybe.   So, also the support of OpenPCS is


not yet included as separate entry in the open and save dialogs.


Ok, what&rsquo;s changed in v2.2.1?


First of all the session manager can now redirected to a user defined path.


Use the Default button at the preferences dialog if any problem occurs with


the session manager or the selected path.


Next PLCEdit contains now an update function to inform about updates of


the application.


I tried again to fix the tab/file list bug which occurs by saving a file if some


more files are opened.
]]></content:encoded></item><item><title>Release v2.2.0</title><dc:creator>PLCEdit.org</dc:creator><category>Announcements</category><dc:date>2010-03-14T18:00:00+01:00</dc:date><link>http://www.plcedit.org/blog/files/b7b4c3f3889e8de0daba122962ddda32-31.php#unique-entry-id-31</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/b7b4c3f3889e8de0daba122962ddda32-31.php#unique-entry-id-31</guid><content:encoded><![CDATA[After a couple of month I proudly present the new major version of 


PLCEdit.   Version 2.2.0 comes with a lot of new features and got some 


good enhancements under the surface.


The new key features are:


- support for Mitsubishi MELSFOT IEC files


- the function block call model converter


Next the support for infoteam&rsquo;s OpenPCS has started.   First files


of OpenPCS will be accepted as plain text POUs.   Later seperated


entries in the file open and save dialogs will be added.   The sources 


are very clean, so there is only something to do regarding the file


extension management in PLCEdit. 
]]></content:encoded></item><item><title>Dev Report No. 10</title><dc:creator>PLCEdit.org</dc:creator><category>PLCEdit News</category><dc:date>2009-12-18T17:39:19+01:00</dc:date><link>http://www.plcedit.org/blog/files/aecf102f9bd4e05a904306e7ba81e5f8-30.php#unique-entry-id-30</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/aecf102f9bd4e05a904306e7ba81e5f8-30.php#unique-entry-id-30</guid><content:encoded><![CDATA[I know, I said we will see a new version until end of October.   Now we&rsquo;ve 


mid of December.   I&rsquo;m sorry but I had a joyous occasion in private. 


And next I&rsquo;ve  found some problems in using the beediff source for the file 


differencing function.   I think I have to rewrite a lot of routines to hold the 


promise &bdquo;never create any registry entries&ldquo; and to make the differencing


really work. 


So, for the moment I&rsquo;ve canceled the file differencing function and will only 


have a look to the function block call conversion functionality and the new


Mitsubishi Melsoft support. 


Hopefully I&rsquo;m able to release version 2.2.0 during the next week or better


before the new year is there...]]></content:encoded></item><item><title>Dev Report No. 9</title><dc:creator>PLCEdit.org</dc:creator><category>PLCEdit News</category><dc:date>2009-10-04T17:15:00+02:00</dc:date><link>http://www.plcedit.org/blog/files/5bd9830bd937127a90cdf5c22fda2a11-28.php#unique-entry-id-28</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/5bd9830bd937127a90cdf5c22fda2a11-28.php#unique-entry-id-28</guid><content:encoded><![CDATA[The release v2.1.2 is nearly two and a half month old and during the last


time PLCEdit got some changes according to the announced ToDo list.


But the work would take a few month in addition if we want to leave the 


list unchanged.   The current feature improvements have reached a status


which allows a speedy release.   So, what are the selected features?


- file comparision and differencing utility:


&nbsp; a dialog window which shows two POUs side by side with in


&nbsp; color highlighted differences; implemented as context menu


&nbsp; of each page; comes with optional file open dialog


- function block call conversion: 


&nbsp; enhanced POU compatibility by converting function block calls 


&nbsp; into the appointed IDE call model; can be used as setting for 


&nbsp; the file save routines and as option for the batch processing


- support for Mitsubishi MELSOFT: 


&nbsp; support for .asc export files; supported CONFIGURATION files/sections


- updates:


&nbsp; enhanced support of TYPE definitions; 


&nbsp; FUNCTION dialog with user defined data types


The upcomming release will not yet include the PLCOpen XML support.


The implementation takes to much time and would delay the release 


until 2010. 


For now there must be some points fixed regarding the file diff utility. 


So, I hope we have 2.2.0 ready this month.
]]></content:encoded></item><item><title>Dev Report No. 8</title><dc:creator>PLCEdit.org</dc:creator><category>PLCEdit News</category><dc:date>2009-08-17T06:00:00+02:00</dc:date><link>http://www.plcedit.org/blog/files/4a8212589c33cd8d79f6010a98c6dc29-27.php#unique-entry-id-27</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/4a8212589c33cd8d79f6010a98c6dc29-27.php#unique-entry-id-27</guid><content:encoded><![CDATA[I think it is once again the time to give a report about the development 


status of PLCEdit.   Now we have version 2.1.x and I think PLCEdit is a


well featured editor.   But the development remains fully active to fit the 


requirements of the daily work.


Regarding to the latest ToDo list I&rsquo;ve started to include a file differencing


dialog.   Therefore I&rsquo;ve added code from beediff, a Qt based opensource 


project.   Thanks to Piotr Pszczolkowski!   A first quick and dirty setup works 


pretty cool. 


I&rsquo;ve also started to include a functionblock call convert function which will 


be part of the batch routine and file ave routine as well.   It should help to 


make POU ouputs more compatible to the appointed IDE.   I think it will be 


a lot of work and maybe some conversions will not supported.


Both features will be part of the next release.   If you have some other ideas, 


something new ore any regarding the new features please let me know.
]]></content:encoded></item><item><title>Release v2.1.2</title><dc:creator>PLCEdit.org</dc:creator><category>Announcements</category><dc:date>2009-07-27T20:02:00+02:00</dc:date><link>http://www.plcedit.org/blog/files/1405169b4d0d5d97b229f4cbc4e1d99a-25.php#unique-entry-id-25</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/1405169b4d0d5d97b229f4cbc4e1d99a-25.php#unique-entry-id-25</guid><content:encoded><![CDATA[22 Days later - the second update for version 2.1 is out - v2.1.2.


This time I tried to clean the code base of PLCEdit and to include


smart enhancement - a unsaved file notification.   I know it took a 


while to include this, but I don&rsquo;t like to get annoyed by a message 


&bdquo;You forgot to save one or more files&ldquo;.   And so there is an option


in the preferences to disable such bitchily nags ;)


The asterisk in the file list and on the tabs is maybe more useful.


I&rsquo;ve also fixed some issues regarding the recent files list and the


print output.   But I suppose that some more things could be done 


to make the printout more acceptable.


If I remember correctly we had a todo list for a nexe major release.


Maybe it needs to be revised but in general it seems to be ok.


The actual todo list:


- file comparison and differencing utility


- PLCopen support


- enhancement of the batch processing + including a CAL-converter 


- enhancement of the TYPE defintion support
]]></content:encoded></item><item><title>Release v2.1.1</title><dc:creator>PLCEdit.org</dc:creator><category>Announcements</category><dc:date>2009-07-05T20:02:31+02:00</dc:date><link>http://www.plcedit.org/blog/files/86a06a2774c2ea985065a7346fe8dd6c-24.php#unique-entry-id-24</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/86a06a2774c2ea985065a7346fe8dd6c-24.php#unique-entry-id-24</guid><content:encoded><![CDATA[This version 2.1.1 is a much needed bug fix release.


There were some small but bad bugs in the former version 2.1.0, which 


hinder effective working, for example the file save as function.   It did not 


save the correct content, because of changes in the last version :( 


I&rsquo;ve found the problem and solved it.   So please update to version 2.1.1.]]></content:encoded></item><item><title>Versiontracker is horrible</title><dc:creator>PLCEdit.org</dc:creator><category>General</category><dc:date>2009-06-27T08:25:16+02:00</dc:date><link>http://www.plcedit.org/blog/files/64fae4240c23bf56c981cab91569500d-23.php#unique-entry-id-23</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/64fae4240c23bf56c981cab91569500d-23.php#unique-entry-id-23</guid><content:encoded><![CDATA[I tried to update the version information for the PLCEdit Windows version 2.1.0.


A lot of days they did nothing and now they have changed v2.0.4 with the new


changelog of v2.1.0.   What a bad service :(


Actually, I wanted to release a new version today, which solves a small issue


in the function block dialog.   The closing sign gets lost if the data type and/or 


the I/O comments are deselected.   But now I want to wait until versiontracker


has revised the version.   I suppose otherwise they get totaly confused...
]]></content:encoded></item><item><title>Release v2.1.0</title><dc:creator>PLCEdit.org</dc:creator><category>Announcements</category><dc:date>2009-06-14T13:00:00+02:00</dc:date><link>http://www.plcedit.org/blog/files/d74976f898a177260daf22ee0ea12227-22.php#unique-entry-id-22</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/d74976f898a177260daf22ee0ea12227-22.php#unique-entry-id-22</guid><content:encoded><![CDATA[The next larger version step is done and version 2.1.0 is available for download.


I had a look in the source and found a lot of small issues. 

...In total, this represents a new version. :)


The Import/Export routines were revised to be more faster and better in file 


...Especially CoDeSys users will be happy about this update, because 


comments at the declaration section will now accpeted at this position.


A default POU extension for new files can be selected at the preferences dialog.


Next the jumping of the pages element is solved.   If Qt4.5.x is used the tab bar


looks a litle bit more professional (close Button in every tab, movable tabs).


But on Mac OS X the metal tool bar gets lost because this option is switched off


by using Qt 4.5, to prevent a fixed minimum size of 1000px for the main window.


The function block call dialog has now an option to include existing comments 


of the block I/Os into the call model.   This was a very good feature suggestion. 


It helps a lot for source documentation.


I hate replace all functions, but yo&rsquo;ve annoyed me enough at this point and now


...It starts at the current position in the active window. 

...window it tells you that it is ready to do it on the opposite window, but waits 


...At least I&rsquo;ve prepared the support for TYPE definitions.   It is experimental and


works for CoDeSys export files only.


And what will be next?


Here is the new todo list:


- enhancement of the batch processing + including a CAL-converter 


...- enhancement of the TYPE defintion support


...The CAL-convert function could help to make POUs more compatible to other


...It would be a great upgrade for the batch routine.


Maybe the adaption of an existing opensource file diff project could be done


...At least file diff tools are very useful for professional 


...For now have a look at this page.


The PLCopen support is a nice to have but it would fit well the basic idea of 


PLCEdit - to be the missing link between the PLC IDEs.]]></content:encoded></item><item><title>Release v2.0.4</title><dc:creator>PLCEdit.org</dc:creator><category>Announcements</category><dc:date>2009-05-16T11:45:00+02:00</dc:date><link>http://www.plcedit.org/blog/files/f57d5e81f29664a42f5ed02dd8496490-21.php#unique-entry-id-21</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/f57d5e81f29664a42f5ed02dd8496490-21.php#unique-entry-id-21</guid><content:encoded><![CDATA[Version 2.0.4 is released.   It contains some essential fixes.


The file save dialog is now working exclusively with the selected file extension 


on all platforms.   Also the session save dialog, the current lines highlighter and 


the recent files list were revised.
]]></content:encoded></item><item><title>Release v2.0.3</title><dc:creator>PLCEdit.org</dc:creator><category>Announcements</category><dc:date>2009-05-01T13:15:00+02:00</dc:date><link>http://www.plcedit.org/blog/files/17c57b41657463d8fe80fbe4f4e5ad67-20.php#unique-entry-id-20</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/17c57b41657463d8fe80fbe4f4e5ad67-20.php#unique-entry-id-20</guid><content:encoded><![CDATA[An update is available - having fun again, by using PLCEdit! :)


I&rsquo;ve fixed a small but horrible bug.   The lines highlighter and the printable 


area routine causes the app to repaint the editor windows permanently 


- at least the CPU load swings up to maximum :( 


Next I&rsquo;ve solved some wrong handlings of the class PrefDialog.   A window


resizing and a repeated opening of the POUs from the file autoSession.dat 


should gone now.


Because my free time is limited, I&rsquo;ll slow down the development of PLCEdit.


Hopefully version 2.1 can be released at the end of summer 2009.]]></content:encoded></item><item><title>CPU eater</title><dc:creator>PLCEdit.org</dc:creator><category>PLCEdit News</category><dc:date>2009-04-29T19:53:11+02:00</dc:date><link>http://www.plcedit.org/blog/files/34058d5ce3ef225be17f94745c070a6b-19.php#unique-entry-id-19</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/34058d5ce3ef225be17f94745c070a6b-19.php#unique-entry-id-19</guid><content:encoded><![CDATA[PLCEdit is slowing down my PC :(


I&rsquo;m sorry about this bad behaviour!   PLCEdit uses an update routine for


the current line and printable area indicators, which is permanently called.


I&rsquo;ve fixed this issue and the update is already uploaded to the repository. 


The packages for Win, Linux and Mac will be available during the next days.]]></content:encoded></item><item><title>Release v2.0.2</title><dc:creator>PLCEdit.org</dc:creator><category>Announcements</category><dc:date>2009-03-21T19:05:00+01:00</dc:date><link>http://www.plcedit.org/blog/files/5f56c1ab8334461478162cc4410c6015-18.php#unique-entry-id-18</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/5f56c1ab8334461478162cc4410c6015-18.php#unique-entry-id-18</guid><content:encoded><![CDATA[The next verison is there.   It contains only some minor, 


but nice to have editor improvements:


- recent files list


- lines highlighter


- print area indicator


I thought the sessions function was a very good thing.


But I have completely  understimated the significance


of a recent files menu, although I use it every day with


my internet browser...   You did requested it - here it is :)


At least I&rsquo;ve noticed, that the Mac OS X app was not


able to run on OS 10.4.   I have corrected this issue. 


What&rsquo;s next?   I don&rsquo;t know!   Of course, I have a ToDo list,


but the items on it will take a lot of development time


and currently my free time is limited.   I think to improve 


the import/export routine is a good next step.]]></content:encoded></item><item><title>Release v2.0.1</title><dc:creator>PLCEdit.org</dc:creator><category>Announcements</category><dc:date>2009-02-26T20:25:00+01:00</dc:date><link>http://www.plcedit.org/blog/files/ba515d0e32be1356d87aaa2c6d2e021e-17.php#unique-entry-id-17</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/ba515d0e32be1356d87aaa2c6d2e021e-17.php#unique-entry-id-17</guid><content:encoded><![CDATA[Today version 2.0.1 is released, caused from some


small bugs, mostly regarding the user interface.


Only the CoDeSys enahncement is a significant 


innovation.   Existing VISU sections will now readed


and included to the page.]]></content:encoded></item><item><title>Final Release v2.0.0</title><dc:creator>PLCEdit.org</dc:creator><category>Announcements</category><dc:date>2009-02-23T20:05:29+01:00</dc:date><link>http://www.plcedit.org/blog/files/84cc21955779892674b843a3fe132c79-16.php#unique-entry-id-16</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/84cc21955779892674b843a3fe132c79-16.php#unique-entry-id-16</guid><content:encoded><![CDATA[Today I proudly present the final release of PLCEdit v2.0.0


It was a long way to develop the codebase for version 2 of


this great application.   In summer 2007 I&rsquo;ve started to rewrite


the source by using Trolltech&rsquo;s Qt GUI toolkit. 


Now it is February 2009 and only the GUI structure of the


codebase for version 1 is nearly the same.   The rest is more


or less completely new.   At least I&rsquo;ve created a svn repository 


at sourceforge.net, for a more transparent development.


What are the highlights of codebase v2? 


--> PLCEdit is platform independent!


--> PLCEdit got some great functions in addition to v1!


--> PLCEdit is more compatible to the supported file types!


--> ...and PLCEdit is opensource!


Some bugs are still alive, but there should be nothing to make


PLCEdit unusable for you.


At least, thanks to all people who helped me with Qt and who


have tested & used PLCEdit over the last years! :)


The actual todo list:


- spend some time with my wife


- visit my motorcycle


- dedusting my camera
]]></content:encoded></item><item><title>v2.0b Dev Report No. 7</title><dc:creator>PLCEdit.org</dc:creator><category>PLCEdit News</category><dc:date>2009-02-08T13:57:36+01:00</dc:date><link>http://www.plcedit.org/blog/files/1729d4b2ad6fd8a1ea159f2891a1afff-15.php#unique-entry-id-15</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/1729d4b2ad6fd8a1ea159f2891a1afff-15.php#unique-entry-id-15</guid><content:encoded><![CDATA[The items of the last ToDo list are finished and now we have 


a feature freeze and a code freeze.   The freeze will be testet 


the following weeks.   So, hopefully v2.0 can be released at the 


beginning of March 2009.


Some words about the current source:


1. 


PLCEdit seems to have some problems with Siemens Step7 


sources.   I&rsquo;ll try to fix it, but it would be nice to get some help.


2. 


Sometimes PLCEdit&rsquo;s open routine is very slow for big or 


many files.   Regarding this I have add a progressbar, which 


will be shown during the file open process and if the batch


routine runs, too.


3.


An often asked feature was a possibility to insert function 


blocks with its call model into a page.   The answer is the


new class FBDialog :) 


The dialog allows to insert opened function blocks from a list, 


by using a page-correct call model for all supported sources.


The actual todo list:


- testing the current source


- fixing Siemens Step7 bugs (done)


- preparing the app and the docu for the release
]]></content:encoded></item><item><title>v2.0 Release Candidate 2</title><dc:creator>PLCEdit.org</dc:creator><category>Announcements</category><dc:date>2008-12-27T15:20:00+01:00</dc:date><link>http://www.plcedit.org/blog/files/2c1bf806ce88d717345826e9262ac1b3-14.php#unique-entry-id-14</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/2c1bf806ce88d717345826e9262ac1b3-14.php#unique-entry-id-14</guid><content:encoded><![CDATA[PLCEdit v2.0 release candidate 2 is released today.


Today we try it again.   I&rsquo;m sorry for the last release.


It was very flawed and I&rsquo;ve disabled the download. :(


Some minor changes in the class PageCtrl causes 


a lot of painful bugs.   With the current fixes in the file


opening and file storge routines it should be done. 


The new version was tested very hard and with all


sorts of nonsens - hopefully it was enough this time.


It seems there is a problem with Qt 4.x and the Mac


metal styled toolbar on Mac OS 10.5.x systems. 


If PLCEdit crashes on your system, please contact 


me - you&rsquo;ll get a version without the metal toolbar.


The actual todo list:


- enable POU info dialog for KW-Soft description section (done)


- fixing some minor bugs, wich are still hiding


- preparing the app and the docu for the release]]></content:encoded></item><item><title>v2.0 Release Candidate 1</title><dc:creator>PLCEdit.org</dc:creator><category>Announcements</category><dc:date>2008-12-23T18:59:31+01:00</dc:date><link>http://www.plcedit.org/blog/files/956a6ecd10004314a41fd561966d8fa9-12.php#unique-entry-id-12</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/956a6ecd10004314a41fd561966d8fa9-12.php#unique-entry-id-12</guid><content:encoded><![CDATA[PLCEdit v2.0 release candidate 1 is released today.


:) it&rsquo;s cristmas time... :)


I think it is time to freeze the current development status 


after two betas.   PLCEdit has reached the same amount 


of functionality as v0.9.9 with the old development toolkit. 


Some new features are also included.   The handling of 


CoDeSys v2.3.x .  EXP files was improved - I think it was 


a knock-out criterion for this version.


What's left or missing in this version? 


The crc checksum support for Sucosoft POU files gives me


a headache.   I don&rsquo;t know if it will be done for version 2.0.


Next, I have some ideas about translating the Moeller function 


block calls into CoDeSys (and other distributions) compliant 


calls.   A menu to include/call function blocks wich are opened


in PLCEdit is one of my favorites.   At least it would be nice to


have a file comparison function.


I think this are good milestones for version 2.1 and up.


The actual todo list:


- fixing some minor bugs, wich are still hiding]]></content:encoded></item><item><title>v2.0b Dev Report No. 6</title><dc:creator>PLCEdit.org</dc:creator><category>PLCEdit News</category><dc:date>2008-12-10T20:15:58+01:00</dc:date><link>http://www.plcedit.org/blog/files/c66d4ed6cbe780290679490517a776a3-11.php#unique-entry-id-11</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/c66d4ed6cbe780290679490517a776a3-11.php#unique-entry-id-11</guid><content:encoded><![CDATA[A lot of work was done.   And there is only one


open issue from the last ToDo list.


Now its around christmas time and maybe the<br />


CoDeSys problem is to much to solve it during<br />


the last days of this year.   I want to include the 


fix in RC1 ...   I&rsquo;m sorry, but you have to wait.


If you want a fixed batch convert I would please


you to download the linux file.   It includes the 


latest  stable source, which could be compiled 


easily &bdquo;at home&ldquo; or ask me for an executable.


I have updated the project website.   It shows


now a docs menu, which contains a changelog


and holds links for the FAQ and the Help. 


The actual todo list:


- better CoDeSys support  	(done)


- disabled menu items greyed out (done)


(- Sucosoft checksum support (n/a))]]></content:encoded></item><item><title>v2.0b Dev Report No. 5</title><dc:creator>PLCEdit.org</dc:creator><category>PLCEdit News</category><dc:date>2008-11-16T20:35:00+01:00</dc:date><link>http://www.plcedit.org/blog/files/08da6f1638f33302673e4ab8e5ac4801-10.php#unique-entry-id-10</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/08da6f1638f33302673e4ab8e5ac4801-10.php#unique-entry-id-10</guid><content:encoded><![CDATA[Oh, my last entry is from june.   I&rsquo;m sorry but there 


were some private things to to.   Now I&rsquo;m working


on the next enhancements and some bug fixes,


eg. the batch converter bug, which causes same


content for all converted files :(


I&rsquo;ll try to publish the release candidate at the end 


of december 2008. 


At the moment I think about to use Scintilla as


the editor back-end.   It could solve some basic


problems with the syntax highlighter and the


line numbers.   But it would be a lot of work.


We will see... maybe in v2.1.


The actual todo list:


- new settings file handling  	(done)


- better CoDeSys support  	(v2rc1)


- timer based autosave		(done)


- fix batch converter bug		(done)


- syntax highlighter updates 	(done)


- interface enhancements		(done)


- Help files				(done, english)]]></content:encoded></item><item><title>Public Beta Release v2b2</title><dc:creator>PLCEdit.org</dc:creator><category>Announcements</category><dc:date>2008-06-05T14:17:00+02:00</dc:date><link>http://www.plcedit.org/blog/files/7820c202e1154be9bcb7b1a02bd264f8-9.php#unique-entry-id-9</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/7820c202e1154be9bcb7b1a02bd264f8-9.php#unique-entry-id-9</guid><content:encoded><![CDATA[I have decided to release the second public beta with one


open issue of the latest ToDo list.   The needed revision of


the  CoDeSys import and export function needs more time, 


but I think you want to see the new version with its nice


improvements.   The work on the release candidate will go


on starting at the end of june.


Please report all bugs of the actual beta version.


The new todo list:


- new settings file handling  	(v2rc1)


- better CoDeSys support  	(v2rc1)


- timer based autosave		(v2rc1)


- Help files				(v2rc1)]]></content:encoded></item><item><title>v2.0b Dev Report No. 4</title><dc:creator>PLCEdit.org</dc:creator><category>PLCEdit News</category><dc:date>2008-05-29T20:59:51+02:00</dc:date><link>http://www.plcedit.org/blog/files/0ba1a428b60573e0c27aea00ef13af13-8.php#unique-entry-id-8</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/0ba1a428b60573e0c27aea00ef13af13-8.php#unique-entry-id-8</guid><content:encoded><![CDATA[My time for working on PLCEdit is limited, but I try my


best to ensure that development does'nt stop now.


Some points of the new ToDo list were already done.


I also plan to support another PLC-software provider.


We will see what's happen until v2b2 ;).


The actual todo list:


- interface enhancements	 	(done)


- language translations  		(done)


- fix file-extension-save bug  	(done)


- save sessions as project  	(done)


- export as PDF			(done)


- better CoDeSys support	


- new POU files support		(done)


- timer based autosave		(v2rc1)


- Help files				(v2rc1)
]]></content:encoded></item><item><title>Breaking News</title><dc:creator>PLCEdit.org</dc:creator><category>PLCEdit News</category><dc:date>2008-05-18T10:59:37+02:00</dc:date><link>http://www.plcedit.org/blog/files/47bd51c4bd9390148e46dfc487bf0f31-7.php#unique-entry-id-7</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/47bd51c4bd9390148e46dfc487bf0f31-7.php#unique-entry-id-7</guid><content:encoded><![CDATA[The last weeks were not really productive.   There were some 


user interface enhancements made.   On Mac OS the App looks


now more mac-like.   And the Toolbar icon size is now 22px.


You can see it on the Home and Features pages.


I have also found a bug.   If an already open document needs


to be saved, next to the name a broken filename extension 


will be shown and later used by the export routine.


As a work around please erase the extension first, before 


editing the file name.   The next version contains a bugfix.


And how long will it take until the next beta-release?


I'll try to release the next beta until the beginning of june.]]></content:encoded></item><item><title>openSPS&#x2c; versiontracker</title><dc:creator>PLCEdit.org</dc:creator><category>General</category><dc:date>2008-04-24T21:03:03+02:00</dc:date><link>http://www.plcedit.org/blog/files/5af263d5865e7f830d0da2d29b27ea4f-6.php#unique-entry-id-6</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/5af263d5865e7f830d0da2d29b27ea4f-6.php#unique-entry-id-6</guid><content:encoded><![CDATA[Today I've found a great program, which follows the nice idea


to bring an IDE with integrated plc runtime environment to your


PC, including a simple and easy to build process connection.


To get more information visit http://www.eilers.net/ .


Versiontracker.com has updated the description for PLCEdit 


with the right file link.   I've seen that many other download 


pages has included the new version of PLCEdit, too.   Thanks.]]></content:encoded></item><item><title>Broken link on versiontracker.com</title><dc:creator>PLCEdit.org</dc:creator><category>General</category><dc:date>2008-04-09T21:37:49+02:00</dc:date><link>http://www.plcedit.org/blog/files/9ca5db4a122891030e2e4183d08b25be-5.php#unique-entry-id-5</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/9ca5db4a122891030e2e4183d08b25be-5.php#unique-entry-id-5</guid><content:encoded><![CDATA[I've seen that versiontracker.com do not use a correct link to


the new Windows&reg; version of PLCEdit.   An information was


already sent to versionracker.com, but it seems that they 


don't find time to update the link.   I'm sorry.


As a bonus I have early updated the Windows&reg; version to 


build 006, which contains now an "open with..." function.]]></content:encoded></item><item><title>Public Beta Release v2b1</title><dc:creator>PLCEdit.org</dc:creator><category>Announcements</category><dc:date>2008-04-05T21:50:14+02:00</dc:date><link>http://www.plcedit.org/blog/files/707fb35515543560c65bd63aa46c5962-4.php#unique-entry-id-4</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/707fb35515543560c65bd63aa46c5962-4.php#unique-entry-id-4</guid><content:encoded><![CDATA[PLCEdit public beta v2b1 is released today.


After a couple of month in development I'm pleased to present 


the first public beta of PLCEdit v2.   Version 2 offers not really 


new features.   This version is primarily a rewritten version 0.9.9.


But the new code base offers some enhancements and opens


up the way for new ideas.   As a great point the new code base


is platform independent.   Now it works on Windows as well as


on Mac OS X and Linux.


What's left or missing in this version?


The actual todo list:


- language translations


- Help files


- CoDeSys .exp files enhancements


- timer based autosave of opened files


- save sessions as project option


- export as PDF file


- interface enhancements


- fixing some minor bugs]]></content:encoded></item><item><title>v2.0b Dev Report No. 3</title><dc:creator>PLCEdit.org</dc:creator><category>PLCEdit News</category><dc:date>2008-04-05T09:55:37+02:00</dc:date><link>http://www.plcedit.org/blog/files/99b4c1aa6c17012055f2c1fc8f5b3d47-3.php#unique-entry-id-3</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/99b4c1aa6c17012055f2c1fc8f5b3d47-3.php#unique-entry-id-3</guid><content:encoded><![CDATA[Today it looks very well.   All work for v2b1 was done. :)


Now I'm going to prepare the application for distributing.


The public beta will be released maybe today or tomorrow.
]]></content:encoded></item><item><title>v2.0b Dev Report No. 2</title><dc:creator>PLCEdit.org</dc:creator><category>PLCEdit News</category><dc:date>2008-03-27T19:08:46+01:00</dc:date><link>http://www.plcedit.org/blog/files/cc979b568c18b5f3d6aedd562f62409b-2.php#unique-entry-id-2</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/cc979b568c18b5f3d6aedd562f62409b-2.php#unique-entry-id-2</guid><content:encoded><![CDATA[As you see we have some open issues and maybe some small bugs, too.


However, I've decided that the first beta version will miss some features.


So, the help files and the translation functionality are planned for v2.0b2.


Now let us tell about the development progress:


In the last days the batch converter, the POU information dialog and the 


print dialog were implemented.   With this the core class named PageCtrl


was revised.   Now the file import/export functions have its own class,


which makes it easier to write functions like the batch converter or the 


prototype function and many other features which needs acces to the 


prepared POU file content.


Now some bugs in the POU info dialog needs to be fixed.   The find and


replace dialogs will be the last steps on the way to the public beta.
]]></content:encoded></item><item><title>v2.0b Dev Report No. 1</title><dc:creator>PLCEdit.org</dc:creator><category>PLCEdit News</category><dc:date>2008-03-20T08:36:10+01:00</dc:date><link>http://www.plcedit.org/blog/files/d98d170ecac8fb1c3e94b91758219a75-1.php#unique-entry-id-1</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/d98d170ecac8fb1c3e94b91758219a75-1.php#unique-entry-id-1</guid><content:encoded><![CDATA[The development of PLCEdit is still in full activity.   But today it seems that 


I could not hold the promise to release a 2.0b1version at the end of March.


Some issues needs more concentration, so it could take some more days.


The actual todo list:


- printing				(done)


- POU info dialog		(done)


- batch converter 		(done) 


- find & replace dialogs	(done)


- drag & drop			(done)


- translation			(v2b2)


- Help files			(v2rc1)]]></content:encoded></item><item><title>New Home</title><dc:creator>PLCEdit.org</dc:creator><category>General</category><dc:date>2008-03-15T15:09:21+01:00</dc:date><link>http://www.plcedit.org/blog/files/048c9c65272051e6021665432a65f5f9-0.php#unique-entry-id-0</link><guid isPermaLink="true">http://www.plcedit.org/blog/files/048c9c65272051e6021665432a65f5f9-0.php#unique-entry-id-0</guid><content:encoded><![CDATA[Welcome at the new PLCEdit website with its new adress www.  PLCEdit.org


The home of PLCEdit has changed, preparative to the next mayor release.


The new website contains now a blog, which will be used to announce new 


versions and also to inform about the development progress of PLCEdit. 


In the next weeks the site will be enhanced more and more. 


So, stay tuned.]]></content:encoded></item></channel>
</rss>
