@b3m2a1 OK, enough fiddling.. One of the easiest solutions I have found is to skip the edges all together and make them zero thickness. Then, simply making an heptagon behind the whole drawing which has a mean/similar color to all colors reduces the artifacts and doesn't introduce any edge-clutter
Here is what we have to decide between based on what people have suggested: * With or without "the" * "and", "&", "/" and no conjunction, "Powered by Wolfram Language" * centered, right-aligned * smaller or larger font size
@C.E. Yes, and I'm a bit lost when I think about how we want to vote for all the possible permutations. One point though: Fontsize won't be up for much discussion. Depending on what comes in the second line, there isn't much room when we want to have a nice proportion of space between the parts.
@halirutan Personally I'm not sure it's necessary to have the community vote exactly about how the text should be displayed. Make your best judgement and if people are unhappy they will ask for a change. No need to design by committee on this one :)
@CarlLange What the native speakers among us could decide is if "the" sounds better in combination with "Wolfram Language". My feeling tells me yes but I'm not sure how much difference it makes.
@halirutan if you want an & or Powered by I’d say you probably want it. If you go with / that reads as Mathematica “slash” Wolfram Language which somehow feels more palatable
On the other hand it’s the kind of thing that’s not worth obsessing over given how little anyone is really apt to be bothered by whatever the community goes with
What I think looks best is having "the" when there is no conjunction and not having "the" when there is a conjunction.
I feel the same about right-aligned or not. I prefer right-aligned except when there is no conjunction.
"/" and "Powered by Wolfram Language" I don't think convey the right thing. "/" makes it sounds like Mathematica and Wolfram Language are synonymous and "Powered by Wolfram Language" makes it sound like Mathematica is built in Wolfram Language.
"and" makes it sound like they are two separate things, which I think is right.
@C.E. I agree. I would like to have it right aligned with "and" and without "the". I don't like the symbols "&" or "/" in this. It feels like a playground then. "Powered by" sounds awesome but it just doesn't feel right.
It's safe to say that after quite a discussion, the general consensus is that we should add "Wolfram Language" as sub-text to our header image. Now, the question is what exactly should we put there. I prepared 3 versions of things I like the most, where "Mathematica and Wolfram Language" is my fa...
@halirutan to my eyes the & just looks more correct than "and" here, especially since we're not putting the Wolfram Language on the same footing. One possible variant that could be even nicer would be to put the conjunction in yet a different color. Like you could have a lightish-gray & there
That's how Unix & Linux do it, although in their logo the two are treated as equals
The benefit of graying out the conjunction is that it is clearly distinct from the Wolfram Language in a way that it's not entirely here. On the other hand it might feel wrong given the columnar layout.
@b3m2a1 have you managed to put dynamic module variable's controller in an attached cell? even with InheritScope -> True it does not seem to work. It works for global variables though
@halirutan @b3m2a1 and others thanks for taking care about Wolfram Language header thing. If you need any help from my side let me know, I was not interfering because I don't have strong opinion on this subject and you are doing well anyway.
@halirutan What about this for the logo? Dropbox link. Looks like this on different zoom-levels:
The idea is to first merge everything with the same color into one shape, and to "merge-accumulate" them with the previous one, going from the inside out. This way, there are no edges between shapes, just overlapping shapes, so you get away with no edge colors at all
@LukasLang Visually, there doesn't seem to be much difference to my latest version
Except that the outer red in my version appears to be a bit darker.
@LukasLang Can you share your implementation?
@LukasLang However, since I drew additional lines on the edges and you only merged existing shapes, your version is smaller in size and I would prefer this.
When using SPARQLSelect on Entity Types the entire entity store is downloaded to the local cache.
For example,
SPARQLSelect[
{
RDFTriple[SPARQLVariable["city"], EntityProperty["City", "Name"],
SPARQLVariable["cityName"]]
} /;
SPARQLEvaluation["CONTAINS"][SPARQLVariable[...
More SPARQL fun. These functions feel very experimental; which is why they are.
Still, though, it seems odd not to have an easily accessible SPARQL endpoint for entity queries considering SPARQL on entities have been showcased numerous times leading up to the release and within the release videos.
@chuy The SPARQL functions can take entities (and list of entities) as the graph store.
It seems okay for operations on a single entity graph. However, because it is downloading the values in the query for all of the entities supplied to the query you can quickly run out of memory when the Cartesian product of the entity count of the entities in the query are created
@chuy If it didn't download everything locally then the advantage is being able to perform entity queries that span entities. Like the one in my post that queries both "City" and "Airport" entities.
I'd like some help in identifying a function that works will work similarly to this, but w/o the periodicity (so there is one "peak" so to say") `Manipulate[ Plot3D[Sin[x + w]^2 Sin[y + z]^2, {x, 0, Pi}, {y, 0, Pi}], {w, -1, 1}, {z, -1, 1}]` My limited mathematical function literacy is not up to the job.
One thing I will never get about Mathematica is how the language is seemingly designed to stunt independence in its user base. Like it seems designed to be a toy language with functions that do lots of cool things but rarely generalize well which means that you could know how to use all the fancy built-in functions but still not be particularly good at composing them into targeted use cases for what you really care about...
When using SPARQLSelect on Entity Types the entire entity store is downloaded to the local cache.
For example,
SPARQLSelect[
{
RDFTriple[SPARQLVariable["city"], EntityProperty["City", "Name"],
SPARQLVariable["cityName"]]
} /;
SPARQLEvaluation["CONTAINS"][SPARQLVariable[...
