1. 11 Jan, 2016 4 commits
  2. 29 Jul, 2015 2 commits
  3. 13 May, 2015 1 commit
  4. 15 Apr, 2015 1 commit
  5. 30 Jan, 2015 1 commit
  6. 26 Sep, 2014 1 commit
  7. 10 Sep, 2014 1 commit
    • David Thompson's avatar
      Progress on remote bridge via Remus and miscellany. · 5d4cb8a3
      David Thompson authored
      Remus remote bridge
      -------------------
      
      You must run your own Remus server and manually
      start an smtk-remote-model process, but if you do
      then the new unitRemusBridgeConnection test will
      not fail immediately.
      Remus "mesh type" names are used to advertise specific bridge
      types (e.g., "smtk::model[cgm{OpenCascade}]" instead of
      "cgm" with the default engine set to OpenCascade).
      
      It is possible to start a remote bridge session.
      The request is made and the resulting session ID is
      included in the response.
      
      Base SMTK changes in support of Remus
      -------------------------------------
      
      1. Add method to import local bridge sessions.
      2. Fix documentation for remote operators.
      3. Move registration of bridges into its own class, BridgeRegistrar.
         This class will not be wrapped or even parsed by shiboken.
      4. Add a CGM read operator. This is currently only tested if you
         run the remus unit test, but that must be done manually for now
         because a remus server and worker must be run separately.
         The code that actually reads the model is taken mostly
         from `smtk/cgm/ImportSolid.cxx`.
      5. Add a way to force model associations to be copied.
         SMTK's model expects to be able to copy model associations
         and ModelEntityItem attribute items between attribute managers
         even when they do not have a common model manager (such as
         when temporary attribute managers are constructed for bridges
         to use when copying operators and their results).
         Because UUIDs are unique (not in a verified way, but highly
         likely), these copies should not cause issues.
      
      Miscellany
      ----------
      
      1. Expose Vertex coordinates.
      2. Report cells of a model even when it has no arrangements.
      3. Remove the `CellEntity::shellEntities()` method as it would only return things for naughty cells in any event.
      4. Ignore CGM warnings. (Use pragmas to ignore warnings generated by CGM.)
      5. Ignore warnings generated inside boost headers.
      6. Ignore shiboken warnings.
      7. Clarify docs for ImportJSON.
      5d4cb8a3