TODO List

[kalmarek]

• parser (waiting for the JSON from Polymake) (Added first test version of parser. #29, new one: Enh/new codegen #119 )
• Exception on the Polymake execution (Enh/error handling #48 )
• Methods (DO NOT MERGE - Methods #27, WIP: More temporary method defs #34)
• tab completion (big object list and application list helpers #45 ,add Base.propertynames(::pm_perl_Object) #46)
• Build system (via Binarybuilder #76)
• polymake> REPL mode (WIP: add repl, access via $ key #47)
• c++lib independent typenames in PropertyValue (WIP: restructure propertyvaluehelper and add is_boolean #38)
• Wrappers for BigObjects (add objects with help and params to json #178)
• Document our wrapper
• Documentation (in an automated way from Polymake):
  • functions (Enh/new codegen #119)
  • objects: (add objects with help and params to json #178);
  • methods (is it even possible???) (expose help strings in json files #192)
• Most commonly used SmallObjects:
  • [ ] BitSet
  • IncidenceMatrix (Types/incidencematrix #184),
  • SparseVector (Types/sparsevector #208)
  • SparseMatrix (Types/sparsematrix #181)
  • Polynomial-types? (Types/polynomial #216)
  • TropicalNumber (Types/tropicalnumber #182)
  • QuadraticExtension (Quadratic Extension #221)
  • [ ] Graph
  • [ ] Map*-types
  • [ ] Pair
• solve 0-1 based indexing (is this even a realistic goal? we need to know the intention how the object is going to be used later...) (we have to_(zero|one)_based_indexing functions)

[sebasguts]

Methods work.
Parser still needs work, but waiting for input from Eugen

[sebasguts]

I am going to take care of the build system and the parser.

By wrappers you mean Julia structs that encapsulate different kinds of pm_perl_Object?

[kalmarek]

yes, the order is not random: if we want to have some meaningful tab completion, we need to make it selective based on the PerlObject/BigObject we complete for.

[saschatimme]

After my discussion with Michael, here are the things he suggested we should add:

• Add a "How to add a new small type" guide
• Add an explanation for the static_cast<long> stuff
• Document the functions in polymake_caller.cpp
• Write done something regarding the CxxWrap inference problems (everything is just inferred as Any)
• Simplify the plenty of type mappings. An idea of Michael was to have a separate txt file from which we can auto generate these type maps.

[sebasguts]

Okay, how should we split this up?

I would guess I am the natural choice for 2. Maybe @saschatimme or @kalmarek can do 1, and @saschatimme should do 3 (because he is the guy with the mac ;)).

[kalmarek]

there is also documentation of "getting Polymake.jl going" where we're waiting for a release of polymake with all the necessary changes (3.2.1?)
and I can do "How to add a new small type"

[saschatimme]

Lars is currently preparing a snapshot of the latest master which will be put on the polymake github repo. For a stable release we have to wait on polymake 3.3

[saschatimme]

I will write something to the static cast stuff

[kalmarek]

have a look:
https://gist.github.com/kalmarek/c5a38f733903753a72abedf1dcd63ebb

m