user_guide:extend:extensions

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
user_guide:extend:extensions [2019/05/30 20:05] – [Configuring an extension] configure.pl resides in support folder now oroehriguser_guide:extend:extensions [2021/01/12 15:38] (current) – external edit 127.0.0.1
Line 26: Line 26:
  
 To create a really new application from scratch, execute the command\\ ''%%found_application "~/my_ext", "APP_NAME";%%'' \\ To create a really new application from scratch, execute the command\\ ''%%found_application "~/my_ext", "APP_NAME";%%'' \\
-Again, it will create a folder hierarchy rooting at ''my_ext/apps/APP_NAME''.  After having composed the rules and/or clients, you may include the ''APP_NAME'' in the custom variable ''@start_applications'' stored in ''prefer.pl'' in your polymake settings directory (usually ''~/.polymake'') so that you'll have your new application at hand in every interactive session.+Again, it will create a folder hierarchy rooting at ''my_ext/apps/APP_NAME''.  After having composed the rules and/or clients, you may add the ''APP_NAME'' to the [[:user_guide:howto:shell_custom#custom_variables|custom variable]] ''@start_applications'', so that you'll have your new application at hand in every interactive session.
  
 ===== Configuring an extension ===== ===== Configuring an extension =====
Line 114: Line 114:
 ===== Writing testcases ==== ===== Writing testcases ====
  
-It is always a good idea - especially if your extension is large - to write unit tests for your code. Those are essentially small examples which test individual rules and functions. One advantage of this is that you will quickly notice if a change in your code (or in a new polymake release) breaks something in your extension. Polymake offers a convenient set of tools for this, you can find a full description [[dev_corner:testcases|here]].+It is always a good idea - especially if your extension is large - to write unit tests for your code. Those are essentially small examples which test individual rules and functions. One advantage of this is that you will quickly notice if a change in your code (or in a new polymake release) breaks something in your extension. Polymake offers a convenient set of tools for this, you can find a full description [[user_guide:extend:unit_tests|here]].
 ===== Using other people's extensions ===== ===== Using other people's extensions =====
  
Line 149: Line 149:
  
 If you later try to load a data file referring to the URI of the obliterated extension, polymake will ask you, as usual, to enter its installation directory.  If you are sure that in the meanwhile all the stuff has migrated into the standard distribution and/or other (already loaded) extensions, you should respond with the magic word ''ignore'' . If you later try to load a data file referring to the URI of the obliterated extension, polymake will ask you, as usual, to enter its installation directory.  If you are sure that in the meanwhile all the stuff has migrated into the standard distribution and/or other (already loaded) extensions, you should respond with the magic word ''ignore'' .
 +
  • user_guide/extend/extensions.1559246755.txt.gz
  • Last modified: 2019/05/30 20:05
  • by oroehrig