archive-org.com » ORG » C » CPNTOOLS.ORG

Total: 415

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • << CPN Tools Homepage
    are in the cpnet cpntools document and framework directories Another version is the old development track residing mainly in the editor directory The third version is a tagged version of the old CPN Tools frozen at the time of the santa release This version can be used for demos as it is the most stable one and it shows the tool as it was around the beginning of March 2000

    Original URL path: http://cpntools.org/cpn2000/versions (2016-04-26)
    Open archived version from archive


  • Building Releases << CPN Tools Homepage
    Update version number in links from 2 texts or in release Announce the release of a new version Include links to the Obtaining CPN Tools and http www daimi au dk cpntools bin license forgot php Forgotten password pages in the announcement The announcement should always be sent on the CPN Tools announcement mailing list In some cases the announcement should also be sent out on the Petri Nets mailing list Update the CPN Tools announcements page and create an appropriate new page for the new announcement Update the figure in web cpntools public html bin users png Log in to machine with access to license database Run web cpntools bin users sh Update web cpntools public html bin releases dat with a data point for the approximate release date of the Run users sh again Consider whether tool descriptions should be updated in various tool databases Probably only necessary with major changes e g availability on new platform or new analysis tool CPN Tools in http www informatik uni hamburg de TGI PetriNets tools db html Petri Net Tool DB CPN Tools in Formal Methods Europe Some statistics March 2006 There were 3391 licensees at the time version 2 0 was released on March 9th Number of downloads on March 15th 8797 This should have been checked prior to releasing 2 0 Internal Releases Internal releases are primarily meant to be used within the CPN group Internal releases may not be thoroughly tested They generally contain a number bug fixes or feature enhancements that are particularly useful for users who are not programmers of the tool The internal releases are only visible when downloading from within DAIMI Internal releases are indicated by the text development next to the version number e g CPN Tools 1 0 8 development After

    Original URL path: http://cpntools.org/cpn2000/releases (2016-04-26)
    Open archived version from archive

  • Related pages << CPN Tools Homepage
    page from your book Show modify book 18 page s Help Related pages Related pages Timetables Features fixes ver 2 0 what is to be completed for Version 2 0 Timetable feb mar 2005 leading to Version 1 4 Timetable july sept 2004 leading to Version 2 0 not met Timetable july 2004 leading to Version 1 2 not met Timetable mar june 2004 leading to Version 1 2 not

    Original URL path: http://cpntools.org/cpn2000/timetables (2016-04-26)
    Open archived version from archive

  • Upgrading to a new version of BugList << CPN Tools Homepage
    from your book Show modify book 18 page s Help The bug tracking system has been moved away from the CPN Tools project and is now maintained as an Open Source project at http buglist sourceforge net This means that bugs concerning the bug tracking system should now be reported there and not in the CPN Tools bug tracking system As development takes place seperately it is from time to time needed to upgrade to a newer version if the new features are desired of course Upgrading to a new version of BugList You can use the description at http buglist sourceforge net upgrade html but the buglist directory is called bugs for historical reasons Thus you must manually copy the contents of buglist to bugs after doing the required cleanup Links to Support Mailing List Archive A number of bug reports contain links to the archive for the support mailing list In Oct 2008 the support mailing list was moved to a new server This means that the links to the old server will no longer work The archive was moved to the new server so it should be possible to find the correct posting in the archive on

    Original URL path: http://cpntools.org/cpn2000/bug_tracking_system (2016-04-26)
    Open archived version from archive

  • << CPN Tools Homepage
    Much of this information is internal documentation Care has not been made to make links work and make the documentation conprehensible for outsiders Book creator Add this page to your book Book creator Remove this page from your book Show modify book 18 page s Help This explains the different kinds of test that should be conducted and how to do them Consistency test Manual test Unit test Bugfix procedure

    Original URL path: http://cpntools.org/cpn2000/test (2016-04-26)
    Open archived version from archive

  • << CPN Tools Homepage
    code basis to better get the understanding how things are put together When you create or load a net the checker thread will be started The checker thread is responsible for checker the net upon any semantic change this is actually a coded event and send the net to the simulator which runs as seperat process To learn more about the simulator ask Lisa As the name implies is the checker thread a thread which run simultaneously as the main thread and several hmm other gui event related threads Currently there are no mechanism to prevent mutual exclusion from mutual data structures It seems are there are no conflicts when using the tool except for some minor which have been fixed without the use of semaphores The checker thread restarts every time there has been a change in the semantic structure of the net e g a call to semanticChanged When a net is created either a new or loaded we both store the dynamic and the static part of the net The static part of the net is what you usually see e g the places transitions and arc The dynamic part has more to do with how the net is simulated For each place and transition there is their corresponding instance object PlaceInstance and TransitionInstance If you know a little about cp nets then you will also know about instances Operations on nets are performed when the user uses an instrument An instrument is usually kept in the hand meaning that the instrument is active and occupies a mouse cursor Instruments can have figurs which correspond to the mouse cursor When an instrument is applied a command is usually responsible for performing the action the user requested A command sometimes uses a clipping to perform the work A

    Original URL path: http://cpntools.org/cpn2000/introduction (2016-04-26)
    Open archived version from archive

  • << CPN Tools Homepage
    for now A PageElement also has some interesting methods Each object on a page knows which page it is on SetCPNPage GetCPNPage whereby their also know in which net their since a CPNPage has a reference to the net A PageElement can also be cloned the clone method This means that every object on a page can be cloned A PageElement also has a method called postprocessing This method is called right after the net elements has been loaded and it for now called in a specific order See CPNetUnPack This methods ensures that objects which has children i e guidelines gets a reference to the corresponding children objects Besides the interface of PageElement there are also to event related methods which is important for this hierachy namely onChanged and onSemanticChanged These methods should be called when ever something changes graphically a normal changed event or when the semantic changes semanticChanged event Children are normally responsible for probagating the event to their parents Node A Node has only two subpatterns Place and Transition A node has collection of arcs with which it is connected scanable through scanArcs A node also has a name which has a special semantic regarding duplicate names on different nodes Node also has the code that makes inscriptions snap to the node Place A Place holds direct references to its 2 permanent children the InitMark and the PlaceType A place object is born with it s permanent children and always has these meaning that these references never point to NONE This invariant has to be uphold A place can also have other children a PortType or a FusionInfo Place has different methods for hierachical operations these should be clear to interpret directly from the code A place can also be part of a fusionset and has

    Original URL path: http://cpntools.org/cpn2000/pageelements (2016-04-26)
    Open archived version from archive

  • << CPN Tools Homepage
    Add this page to your book Book creator Remove this page from your book Show modify book 18 page s Help Commands Commands are use to perform the actual work in the tool meaning when an instrument is applied a command is usually responsible for doing the actiul work Another purpose of the command is to undo and redo The tool is build so that every action besides some can be undone and redone So in order to do anything one has to create a Command This command is usually first applied when the instrument is applied but it is also registeret usually with a subpattern of WithCommandManager To give an example one could look at the pattern CreatePlace which is such a subpattern and registers a new command The command is here a simple CreateCommand To see the interface of a command look at some commands or look into the framework Clippings Clippings are use to make it simple to use commands I e when one creates a new place and deletes it and then undos it again the placed must always be the same This means that the object identity must be always be the same To give

    Original URL path: http://cpntools.org/cpn2000/commands_and_clippings (2016-04-26)
    Open archived version from archive



  •