@Szabolcs @b3m2a1 IIRC, both of you also have a strong opinion about WRI using an open bug tracker. As you might remember, Around pointed out a few days ago that Stephen might want to discuss this. I have prepared a first version of a blog post where I discuss this as open as possible.
Would you, or anyone else, want to read over it or even make substantial edits and act as a co-author?
@b3m2a1 I'm more afraid that I have forgotten some obvious arguments. Szabolcs always has a very clear way of writing and pointing out the important things.
Furthermore, if the post includes opinions from several people, it gives a better overview what the community thinks.
@b3m2a1 Sometimes I also write Arnould for whatever reason :)
@Szabolcs I want to have something like Graphics[{ Dynamic @ image, Dynamic @ line}] but unless I convert image to raster Graphics complains it can't handle images.
Bug introduced in 11.1 and persisting through 11.3
When the first argument of Text is a Graphics, and the third argument (offset) is used, positioning is incorrect in M11.1 and M11.2. Mathematica 11.0 behaves correctly.
Example:
inset = Graphics[{Circle[{0, 0}, 2]}, Frame -> True,
FrameT...
I have an idea but I am not 100% sure this is a good idea and I wanted to get some feedback first. I was thinking about asking the SE community what FEM features should be added next. This question is, due to my work with WRI, a bit different than other questions here, I understand that. I have a draft text that I can post if people here are not completely opposed to the idea.
@halirutan I know, so do I. That is independent of it being off topic :) But again, we have many off topic an highly upvoted threads so at the end meta can be a way to go.
@user21 The above being said, I would very much like to see this on meta although it's not on-topic.
To cite stackexchange policy:
> Meta is for Mathematica Stack Exchange users to communicate with each other about Mathematica Stack Exchange (asking questions about how the websites work, or about policies and community decisions)
I hope we can stretch the interpretation enough to acknowledge that this would be a community discussion, although not specifically about this site. The situation that we as a community get asked about possible features is unique and exciting enough for me.
@halirutan, I am not sure I understand, do you propose that I ask my actual question on meta or that the discussion about such a question should be on meta?
@user21 this is somehow linked with the thoughts being shared on an eventual public list of bugs, isn't it?... public formalized discussion on functionality...
Out[-2] should be the result of the input 2, i.e., 2. It sometimes works with similar input/output.
Once instead of the ToBoxes[Out[-2],..] in the cell expression, the box form of the value Out[-2], which was the symbol x, appeared.
Inconsistent behavior seems like a bug, at least to an ordinary user.
@b3m2a1 Mathematica wrote the DynamicBox expression, so I can't take credit.
BTW, I'm going to try to use your package/paclet dev stuff to create a diff. eq. utility package for a course I'm teaching in the fall. Thanks for putting that together for us. It's looks cool.
@b3m2a1 Thanks! I'm hoping stylesheets will work seamlessly. Years ago, I didn't really understand package structure, except for the .m file. I'd distribute a stylesheet separately to the students; but they wouldn't follow directions, wouldn't put it in the right place, would just ignore the errors and press on without letting me know there was a problem. I just stopped using them.
@b3m2a1 Yeah, sure, but I'm working against the system :(
Not-strictly-related complaint - it feels a lot like they've moved away from writing Tutorials and towards just having loads of guide pages that are essentially just different-ordered lists of functions
Would you expect this to work? SPARQLSelect[ RDFTriple[{SPARQLVariable["country"], EntityProperty["Country", "Name"], SPARQLVariable["countryName"]}]][ EntityList@EntityClass["Country", "GroupOf8"]]
I think there is an interesting set of opportunities if one could use SPARQL to access Entities (especially in conjunction with other knowlegde graphs).
@chuy There certainly is. You can already do this to some extent. They give an example somewhere of linking the Knowledgebase with Wikidata using a "linking set"
It's not clear to me that you can use the SPARQL stuff with entity classes or lists of entities in this way, unfortunately. Your query looks fine though.
@chuy On a simple level this is pretty easy, you create an RDFStore with triples for each part of your dataset. Then you can export it as ttl or whatever
@b3m2a1 @Kuba @C.E. @CarlLange @Szabolcs Can we live with that? I made the spacing between the & a bit larger since I agreed with b3m that this looks a bit clearer
@halirutan There's very little left of the right-alignment now, I wonder if one might not just as well justify the text so that it takes up the whole line. I'd prefer the space to be equally divided between the ampersand and Wolfram and Wolfram and Language.
That will still leave more space after the ampersand, while not disturbing the rhytm.
@C.E. For me this is no solution. The space between two words is important for a good look&fell imo. It looks ripped apart if we distribute the space
So either we keep it like in the initial version, where the ampersand was the same size and had the normal text-flow. Or we go with what I posted above where the ampersand is a bit separated from the rest.
@Kuba @C.E. What I do is that I finalize both the normal and the meta logo. Then I create a new meta post where people can again comment. When we find a compromise that works for everyone, we simply turn this post into a feature request.
And then I can probably talk to our designer if he has further comments.