@acer Thanks. I find that the following codes are more or less convenient: 

[`$`](''parse(DocumentTools:-Tabulate([sprintf("%ld", i)], 'exterior' = 'none'), 'noeval', 'statement'), ifactors(2^i - 1)[-1]'', 'i' = 190 .. 200); DocumentTools:-Tabulate([[]]): 

@lcz SVG is an XML-based text format. So the connection between .svg and .xml is, in effect, closer.

In this question, @Carl Love posted an example of finding one shortest possible tour through several 3D points. His code only took he around four minutes, and just took @dharr about six minutes. Unexpectedly, executing it takes me nigh on 9 min! Well, these may be determined by one's computer. But how about Steam Deck's performance?
 

Download testTSP.mws (Sorry for a typo in it.) 

The selection works for sets as well.

@mmcdara For a small problem, minimizing the unsquared sum of actual distances (something like perpendicular offsets) remains possible in practice.

But it seems that Maple haven't collected this method yet, so one has to implement these by hand!

@lcz Replace "\n" and/or "\t" between term and datum with " ". For example, 

fontName	"Dialog"

is replaced by 

fontName "Dialog"

and 

LabelGraphics
		[

is replaced by 

LabelGraphics [

@acer Thanks again. It's what I want.

@sand15 Cheers. I believe the "smooth" means "antialiased", but I'm unfamiliar with these technical terms, and don't know how to define them.

@lcz Thanks. Maybe Maple is more geared towards graph computations rather than graph representations. I'm not familiar with Gephi, but it looks superb. At present, if I really wanna plot a graph emphasizing layered structure in Maple, I have to specify the co-ordinates of the vertices manually only after obtaining vertex placement in Mathematica (using GraphEmbedding). This vexed matter is very irritating.

@sand15 I think that the third line is with(ComputationalGeometry):. Also, the boundary is less smooth, but this is a constructive approach indeed. Thanks!

@acer This time the boundary is very rough (in contrast to Mathematica's default output). However, these approaches are not so easy-to-use. (What about other possible ways?) It is often alleged that there exists an inverse relationship between the power of the tool and how easy it is to use. Still, I wish there to be a more intelligent Maple functionality in this respect.

@mmcdara Thanks as well. It seems that if we hope to transform a complicated plot, this approach may fail. Am I correct in saying this?

@acer Thanks very much. I never knew these before. But I wonder why plottools[transform] works in the first example instead. Any distinctions?

Are your codes correct? An error is issued at last:  By the way, running these on my computer takes about 32 minutes!

@C_R Thanks. It's very strange indeed—It appears that using the standard plot is always recommended.