-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/03/15 15:26, Nusenu wrote:
Nusenu:
I figured it might make sense to discuss this in a separate thread.
And just in case you were wondering, if you ever have a feature request for Onionoo, I'd be happy to discuss that. In contrast to some of its clients, Onionoo itself is actively maintained.
Actually I came to the conclusion that it would make sense to move the myfamily grouping to the backend since any other compass grouping is based on onionoo data and not on data "generated" by compass itself (grouping key).
The MyFamily grouping takes also a bit CPU time. So "computing" families once per generated details document make a lot more sense than recalculating them in every compass query again.
Actually it is be a lot easier then I tough and does not require a backend change at all, so you can ignore this one.
Okay, just in case you change your mind, let's talk more about integrating this into Onionoo. There's already the `family` parameter which I specifically added for Virgil's thing. Though for Compass (or its successor), you'd probably want a new field in details documents, not a parameter. Just let me know. All the best, Karsten -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJVECt4AAoJEJD5dJfVqbCrKAUH+gK9pOThFkS70gidRV5PpmFJ ZmtlQzVBrq9iGdB/IxczKbTer5a3P81Moy8Y6S9K6fwAMasWVyfxOOq078iVnjly n1rhc1kaDRqlyo8oSAlzZDC5mW2MhOcloFJsMUOLryWkjPDGTUC8VpTMhKv1YWWs BPlhTeNBQjbtWYZbGbkVeCSbheT0amSJokfvOdAcxoIX++9WZRLG9L1IhDodo89i v8IU952Q7x7Qg8Cs67f7wQy1MjIqXavmu2zxMffUPVtaqXunG8zkDYdJYzNVfrOl O5gjv/oi96dawh8/f4FXJL9n0gRzNl5clV1LVTo2aUV9nAVvqTyuNuOfOQgmug0= =IlKR -----END PGP SIGNATURE-----