@kirma Ah but I already have a bunch of keys on the keyboard that I hardly ever press. I would much rather work on making the computer do more interesting and useful things (automatic game design) when I press the keys.

For all the non-native speakers here I need to share an excellent tool. It's called Grammarly, and it is just unbelievable what mistakes and grammar mistakes they find and highlight. It works in almost all website input fields. The basic version is free and can be installed as browser plugin.

(And I always thought I'm not that bad at English)

@halirutan: Interesting. I think I'm going to try it. The premium version is seriously expensive, though.

@MichaelHale Well, point of the touch bar is not to replace existing functionality, but rather to provide an alternative method of interaction.

Given a simple open discretized region in 3D. A 2D region in 3D. How to find the z where {x, y} == {2., 3.} for example?

I still haven't bumped into a magic working compination of Solve, RegionIntersection and those

@Rojo Welcome back!

I see the obvious doesn't work. Worth a main site question.

reg = DiscretizeRegion@Sphere[];
RegionIntersection[reg, InfiniteLine[{0.2, 0.3, 0}, {0, 0, 1}]]

^ doesn't work.

@Szabolcs thanks :)

RegionIntersection[#, InfiniteLine[{0.2, 0.3, 0}, {0, 0, 1}]] & /@ Flatten[MeshPrimitives[reg, All]] // RegionUnion

Not particularly pretty...

@kirma ok, in some cases it seems to work, though slow. Thanks!

I was very skeptical when I first saw the new region functionality ... It is so insanely general. It can express just about any possible region operation on any possible combination of region representations. There is no way that all this can work seamlessly together. It is expected that many operations that are easy to express will fail.

I am actually quite impressed with what it can do in version 11.

The disadvantage of the generality is that people will get annoyed when stuff doesn't work, and many won't realize how much functionality there is already ...

Another disadvantage is that it isn't 100% clear what I should expect to work and what I shouldn't, what I should expect to be fast and what I shouldn't. In some specific situations I would rather have a much more limited function with a very clearly defined scope.

But I see the advantages of the generality too.

I wish they exposed the specific implementations in addition to the general interface ... and not just for regions.

I really like how Oliver put together the FEM stuff and how he documented parts of it. The completely general approach would give us one function that can solve PDEs fully automatically with minimal user control. We do have something like that in NDSolve. But we can also access the details, and there are tutorials which show us how the solution works step by step. We can build our own solver, and we have access the toolbox that the high level functions use internally (NDSolve`FEM` ).

Interesting question on Wolfram Community: community.wolfram.com/groups/-/m/t/969924 How to set up extension mappings for custom import formats?

Hey @Szabolcs by any chance you have any clue of what is going wrong with SQLInsert for me? When I try to insert a mma integer expression in a SQL table on a particular column that hasint8 type assigned, my mma integer is converted to something else. For example an integer 20161102135641 in mma becomes 545533010 when inserted. Any idea what might be going wrong?

@PlatoManiac Sorry, I have never used these functions and I am not very familiar with SQL :) Haven't used it in many years.

I see..trying to figure out who is the DatabaseLink guy here..

may be I will post a question @Szabolcs

Just find a bug of the document. The 1st example on this page no longer works:

reference.wolfram.com/language/ref/format/Directory.html

Now one needs to explicitly set the 2nd argument it Import i.e. Import[$InstallationDirectory, "Directory"] // Length

I guess it's because KML format is supported since v8

@xzczd Use the Give Feedback link at the bottom of the page.

@Szabolcs Done :)

@PlatoManiac I'm seeing a similar issue. I haven't used SQLInsert before. I just use SQLExecute with raw SQL strings. The following works properly.

SQLExecute[db, "
 insert into test..test
 values (20161102135641)
 "]

Any help with this project will be appreciated:

Let's try to figure out what we can do with PacletInfo.m

There are many guesses about what might work, which I don't have time to personally verify. If you feel like trying out any of them, please edit the community wiki answer.

If you feel that it's appropriate, also feel free to post a new answer.

@Searke Do you know if there is anyone from WRI who is familiar with this stuff who we could ask nicely to contribute? I understand that many of these are probably irrelevant for users and are strictly internal. But some are clearly extremely useful, and even essential for cerating our own applications. I am interested in these useful ones.

E.g. the FrontEnd extension is very useful.

I think I figured out Loading and the Symbols argument of the Kernel extension, but some confirmation would be welcome ... updated the answer.

@halirutan and everyone else: I just added the following note to the post. Spelunking help will be most welcome!

> Look at the contents of First[PacletFind["PacletManager"]]["Location"]. This contains at least a partial implemention of the PacletManager. The code is well commented.

Extensions.m has most of the stuff I wrote up in the post ... if only I found it earlier!!! (@halirutan)