Changelog for diagrams-core-1.1.0.3
1.1.0.3 (15 May 2014)
- Allow semigroups-0.14
1.1.0.2 (10 April 2014)
- Allow semigroups-0.13
1.1.0.1 (19 March 2014)
- Allow lens-4.1
1.1 (8 March 2014)
-
New features
- New
basisfunction - New
determinantfunction for computing the determinant of aTransformation - Add
Typeableconstraint onPrims, making it possible to extract things back out of aPrimwrapper usingcast - Raw
Traces now return a sorted list of intersections, instead of only the smallest. This is used to implement a new family of functionsrayTraceV,rayTraceP,maxRayTraceV,maxRayTraceP, which work similarly to the parallel versions withoutRay, but return the first intersection in the positive direction from the given point, rather than the smallest in absolute terms. - New
Annotationtype and correspondingapplyAnnotationfunction, for attaching uninterpreted annotations at specific points in a diagram tree. Currently this is used for hyperlinks; more annotation types will be added in the future.
- New
-
Dependency/version changes
- Require
lens-4.0 - Allow
vector-space-points-0.2
- Require
-
Bug fixes
- Looking up a subdiagram by name now results in a diagram which still has that name (#43)
1.0.0.1 (27 November 2013)
- Allow semigroups-0.12
1.0 (25 November 2013)
-
New features
-
Delayed subtrees: instead of a primitive, one can now also have a delayed subtree at a leaf, containing a continuation which generates a
QDiagramwhen given the accumulated d-annotation at that point in the tree. Useful for things which need to know the final transformation applied to them before deciding what diagram to generate. The prototypical use case is arrows: see https://github.com/diagrams/diagrams-lib/issues/112 . However, this may be useful for other things as well: for example, diagrams which scale normally until hitting some maximum or minimum size, at which point they refuse to scale any further (or more generally diagrams which scale as some non-linear function of the transformation applied to them).The only downside is that the u-annotation must be fixed ahead of time---doing otherwise requires a more general solution for constraint solving.
-
New function
lookupNamefor doing a simple lookup of a named subdiagram -
New module
Diagrams.Core.Compile, containing a framework for compilingQDiagramsinto a simpler tree typeRTree, which may be used by backends for rendering.
-
-
New instances
-
Qualifiableinstances for(,),(,,),[],Set,Map k, and(->) e. -
(->) einstance forJuxtaposable(thanks to Carlos Scheidegger)
-
-
API changes
-
Export
pointDiagramfunction, which creates an otherwise empty diagram with a point (not empty) envelope -
A bunch of stuff now uses machinery from the
lenslibrary.envelope,trace, andsubMapare nowLens'esWrappedinstances forTrace,TransInv,QDiagram,SubMap,Envelope,Style,Query, andName(replacesNewtypeinstances)Isos forQuery,Envelope,QDiagram,SubMap,TransInv
-
0.7.0.1 (26 September 2013)
allow semigroups-0.11
0.7: 9 August 2013
-
New features
- new function
onBasis, to extract the matrix equivalent of aTransformation SubMaps are nowDeletable- new function
localizefor hiding/deleting names from scope - new
IsPrimclass, containingtransformWithFreezefunction. This is primarily intended to support scale-invariant primitives (e.g. arrowheads) but may be useful for other stuff as well. The default implementation ofrenderDianow usestransformWithFreeze. - optimized
Transformableinstance forTransInv
- new function
-
New instances
-
Eq,Ord,Enveloped,Traced, andQualifiableinstances forTransInv -
Transformableinstance for functions, which acts by conjugation
-
-
API changes
namedandnamePointhave moved to thediagrams-libpackage.
-
Dependency/version changes
- allow
base-4.7 - upgrade to
monoid-extras-0.3
- allow
0.6.0.2: 5 March 2013
- bug fix: the 'diameter' and 'radius' functions now work correctly.
0.6.0.1: 7 January 2013
- allow
semigroups-0.9
0.6: 11 December 2012
-
New features
-
Proper support for subdiagrams: previous versions of diagrams-core had a mechanism for associating names with a pair of a location and an envelope. Now, names are associated with actual subdiagrams (including their location and envelope, along with all the other information stored by a diagram).
See
Diagrams.Core.Types. -
Traces: in addition to an envelope, each diagram now stores a "trace", which is like an embedded raytracer: given any ray (represented by a base point and a vector), the trace computes the closest point of intersection with the diagram along the ray. This is useful for determining points on the boundary of a diagram, e.g. when drawing arrows between diagrams.
See
Diagrams.Core.Trace.
-
-
API changes
-
The modules have all been renamed to be more consistent with the module naming scheme in the rest of the diagrams universe. In particular:
Graphics.Rendering.Diagrams-->Diagrams.CoreGrahpics.Rendering.Diagrams.Core-->Diagrams.Core.TypesGraphics.Rendering.Diagrams.*-->Diagrams.Core.* -
Graphics.Rendering.Diagrams.UDTreehas been split out into a separatedual-treepackage (which has also been substantially rewritten). -
Graphics.Rendering.Diagrams.{Monoids,MList}have been split out into a separatemonoid-extraspackage. -
The
namesfunction now returns a list of names and their associated locations, instead of the associated subdiagrams. In particular the output is suitable to be rendered to aStringusingshow. -
The new
subMapfunction fills a similar role thatnamesused to play, returning the entire mapping from names to subdiagrams. -
New functions
envelope[VP]MayenvelopeVandenvelopePreturn the zero vector and origin, respectively, when called on an empty envelope. However, sometimes it's useful to actually know whether the envelope was empty or not (the zero vector and the origin are legitimate outputs from non-empty envelopes). The new functions have their return type wrapped inMaybefor this purpose. -
New functions
envelopeSandenvelopeSMayLike
envelope[VP](May), but returning a scalar multiple of the input vector. -
The
Graphics.Rendering.Diagrams.Utilmodule has been removed, along with thewithLengthfunction. Calls towithLengthcan be replaced usingwithLength s v = s *^ normalized v -
Add needed constraints
(InnerSpace v, OrderedField (Scalar v), Monoid' m)to the type of therenderDiasmethod in theMultiBackendclass. -
Generalized
Transformableinstances for pairs and tuplesPreviously, the components of the tuples were required to have the same type; but everything still works as long as they all share the same vector space. This is actually useful in practice: say, if we wanted to pair a diagram with a path and then apply the same transformation to both.
-
-
Improvements
- More efficient implementation of
diameter
- More efficient implementation of
-
Dependency/version changes
- Tested with GHC 7.6.1
- allow
base-4.6 - allow
containers-0.5.* - allow
MemoTrie-0.6.1
-
Bug fixes
-
juxtaposeDefault now correctly handles empty envelopes (#37)
juxtaposeDefaultis now the identity on the second object if either one has an empty envelope. In particular this means thatmemptyis now an identity element forbesideand friends.
-
0.5.0.1: 11 May 2012
- Update
MemoTrieupper bound to allowMemoTrie-0.5
0.5: 9 March 2012
-
New features:
- New
Juxtaposableclass - New
NullBackendandDtypes, for conveniently giving a monomorphic type to diagrams when we don't care which one it is. - #27: Change type of
adjustDiato return a new options record (with an explicitly filled-in size)
- New
-
New instances:
Enveloped,HasOrigin,Juxtaposable,HasStyle, andTransformableinstances forSets and tuplesV Double = DoubleJuxtaposableandBoundableinstances forMap
-
API changes
AnnDiagramrenamed toQDiagram- #61: terminology change from "bounds" to "envelope"
boundary->envelopeP- "bounding region" -> "envelope"
Bounds->EnvelopeBoundable->EnvelopedgetBounds->getEnvelope- etc.
- Split out definition of
Pointinto separate package (vector-space-points) - The
PointconstructorPis no longer exported fromGraphics.Rendering.Diagrams. See theDiagrams.TwoD.Typesmodule fromdiagrams-libfor new tools for working with abstract 2D points. If you really need thePconstructor, importGraphics.Rendering.Diagrams.Points. - Name-related functions now return "located bounding functions" instead of pairs of points and bounds, to allow for future expansion.
-
Dependency/version changes:
vector-space0.8 is now required.- Bump base upper bound to allow 4.5; now tested with GHC 7.4.1.
-
Bug fixes:
- Bug fix related to empty envelopes
0.4: 23 October 2011
- improved documentation
- a few new instances (Newtype Point, Boundable Point)
- new functions (value, clearValue, resetValue) for working with alternate query monoids
0.3: 18 June 2011
- big overhaul of name maps:
- allow arbitrary types as atomic names
- carry along bounding functions as well as names in NameMaps
- additional functions for querying information associated with names
- fix for issue #34 (fix behavior of setBounds)
- Transformable and HasOrigin instances for Transformations
0.2: 3 June 2011
- bounding regions can now be overridden
- new namePoint function for more flexibly assigning names to arbitrary points
- add HasStyle, Boundable, and HasOrigin instances for lists
- add a "trivial backend"
- transformable attributes
0.1.1: 18 May 2011
- link to new website
0.1: 17 May 2011
- initial preview release