Hey Lourens, sounds like you want to the query functions: Try to get <http://package.elm-lang.org/packages/elm-community/graph/2.0.0/Graph#get> the node whose siblings (neighbors, adjacency, ...) you want know and use incoming and outgoing Adjacencies <http://package.elm-lang.org/packages/elm-community/graph/2.0.0/Graph#Adjacency> of the NodeContext <http://package.elm-lang.org/packages/elm-community/graph/2.0.0/Graph#NodeContext> (for undirected graphs, incoming = outgoing).
Also you probably want to use the actual released and up to date version at https://github.com/elm-community/graph resp. http://package.elm-lang.org/packages/elm-community/graph/2.0.0 Have fun, Sebastian On Saturday, 21 January 2017 20:32:19 UTC+1, Lourens Rolograaf wrote: > > Hi Sebastian, > > After some deep thinking I concluded my world is modelled best in a graph > datastructure. > What is in elm-community/graph the way to get the only the siblings of a > node? > When I use breadth-first traveling with `ignorepath` it gives me far too > many nodes. > probably due to "ignoring distance parameters" > It seems I need an example for `BfsNodeVisitor`, any chance for a tutorial > with some more examples to get me started? > > Or are you far gone from this project? it is almost half a year old now.... > > thanks anyway! > Lourens > > Op vrijdag 7 augustus 2015 11:56:47 UTC+2 schreef Sebastian Graf: >> >> Hi, >> >> today I'd like to open my developments of a graph library in Elm >> <https://github.com/sgraf812/elm-graph/tree/develop> to a broader >> public. >> It's not quite there yet, but most of the stuff for a 1.0 is in there >> except for BFS (which won't take that long). >> I would really appreciate some short code review and help with what is >> seemingly a bug in elm-make (or myself): >> >> Trying to compile the Graph module with elm-make results in module >> documentation errors for every single export ('The module exports `export` >> but it is not in the module documentation'), except that I really have >> supplied documentation. >> I don't know what this is about, documentation generation worked for some >> other packages I published earlier. >> >> So, some questions regarding code organization: >> >> 1. Should I leave the Foci in the main module? Should I even supply >> them in an extra library? >> 2. I feel a little partial wrt. having most of the code in one >> module, but love the name spacing that way. Should I split up e.g. >> traversals into their own module anyway? That might help with the >> elm-make >> bug. >> >> I really enjoyed the neatness of Elm, although somewhat verbose. Every >> library I released gives me a warm cozy gut feeling :) >> >> Thanks for your time! >> > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
