Two examples, just for illustration: eval is built-in, but can call to `eval/piecewise` a Library routine, and `*` is built-in but can call `rtable/Product` to do elementwise multiplication of two Arrays.

acer

Lots of suggestions have been made in the past.

• Ratings of posts/responses by the reader. (This was done for apps on the Maple-Applications site, and is even more potentially useful here on account of the range of quality.)
• Readership stats. For example, Blog posts on mapleprimes used to be dynamically marked with their number of views. Why not bring that back?
• Favourites. The ability to mark, store locally, and view posts as favourites. There are lots of gems on mapleprimes, and managing browser bookmarks is out of vogue.
• Fix the small things, and every now and then mention what's fixed. For example, the "profile" links were recently fixed, but who would have guessed since they were broken for 3 years? Eg, here.
• Encourage maplesoft staff to post.
• Encourage content (tips,techniques,blogs,whatever). Technical content can be very useful even if it does not have all the final polish of what gets on the Apps Centre.
• Update the FAQ of what gets asked here, frequently. Make it more visible for readers (top menubar, beside forums/blogs/...?) and more easily linked-to by responders.
• Add a mode to the top menubar's Search box, for the Online help.

It might be nice if some level of meta-tagging of threads could be done. Sometimes a question is asked and answered, and it relates to a topic with a common technical name -- say "quadrature". Now, it often happens that, unfortunately, neither the original poster or the responders will use that particular term. But such a term might be typical of what would get used to do a relevant search. So, if a new Search facility could search meta-tags, and if some subset of admins/experts/world could add salient metatags to threads, then the ability to search for a given topic would be so much better.

acer

It wasn't entirely clear (to me) that the OP wanted to do interactive things (typing, entering commands, editing, etc) while the component was being constant refreshed by the background Thread. I originally interpreted the query as being about having Maple's kernel (quietly) do other computations at the same time.

If a new, second Worksheet/Document were opened using a new (not shared) "engine", then would'nt updates to the MathContainer in the first sheet occur even while one was interacting in the second sheet? That seems to work OK, although granted continuous updates in one sheet are not so useful if one has to temporarily switch tabs in order to view results.

I'd likely just start two Maple GUI instances, if I wanted to use Maple to run a tickertape as a sideshow.

acer

It wasn't entirely clear (to me) that the OP wanted to do interactive things (typing, entering commands, editing, etc) while the component was being constant refreshed by the background Thread. I originally interpreted the query as being about having Maple's kernel (quietly) do other computations at the same time.

If a new, second Worksheet/Document were opened using a new (not shared) "engine", then would'nt updates to the MathContainer in the first sheet occur even while one was interacting in the second sheet? That seems to work OK, although granted continuous updates in one sheet are not so useful if one has to temporarily switch tabs in order to view results.

I'd likely just start two Maple GUI instances, if I wanted to use Maple to run a tickertape as a sideshow.

acer

Thanks, Robert. Yes, I did indeed do that crucial step, but forgot to mention it.

acer

Thanks, Robert. Yes, I did indeed do that crucial step, but forgot to mention it.

acer

This is Maple 13.01, Standard GUI, Worksheet mode, 1D Maple input.

> restart:

> 'LinearAlgebra:-Norm(<3,4>)';
                         LinearAlgebra:-Norm(<3, 4>)

> op(Norm);
                                    Norm

> (1);  # equation label, using Ctl-l
                                      4

> op(Norm);
                             LinearAlgebra:-Norm

The name `Norm` has not been rebound, but it prints wrongly.

Now, if I subsequently issue,

> Norm(<1,17>);
                LinearAlgebra:-Norm(<1,17>)

> (5);  # equation label of last command
                                17

acer

So that the TTY/commandline Maple interface people don't feel left out...

`\e[00m\e[03;31mThis is my text.\e[00m`;

It's the Thursday afternoon before the Friday before a long weekend.

acer

ps.

`\e[00m\e[05;35mTTY rules.\e[00m`;

So that the TTY/commandline Maple interface people don't feel left out...

`\e[00m\e[03;31mThis is my text.\e[00m`;

It's the Thursday afternoon before the Friday before a long weekend.

acer

ps.

`\e[00m\e[05;35mTTY rules.\e[00m`;

I don't know of any help on this.

Here's what I did. I took your text and entered it as 2D Math input, surrounded by left-ticks in order to enter it as a name. I did not hit <Enter>. For example,

`this is my text`

Then I used my mouse to left-click-select the whole name, including the quotes. Then I used the top-menubar's Format->Character choice to change the color. I did this to that 2D Math input. Then I hit <Enter>, which returned output (which I ignored).

Then I entered the command lprint(%). I copied the output of that lprint call which was,

`#mi("\`this is my text\`",mathcolor = "red")`

What else can be changed in this way? I am not sure. One can add fontweight="bold" to get a bold look. I don't know whether the font, or its size, can also be changed.

There doesn't seem to be much available on programmatic typesetting. You could roll your own procedure that constructed such typeset-enhanced names by simply concatenating your input string/name with the decorating information.

acer

I don't know of any help on this.

Here's what I did. I took your text and entered it as 2D Math input, surrounded by left-ticks in order to enter it as a name. I did not hit <Enter>. For example,

`this is my text`

Then I used my mouse to left-click-select the whole name, including the quotes. Then I used the top-menubar's Format->Character choice to change the color. I did this to that 2D Math input. Then I hit <Enter>, which returned output (which I ignored).

Then I entered the command lprint(%). I copied the output of that lprint call which was,

`#mi("\`this is my text\`",mathcolor = "red")`

What else can be changed in this way? I am not sure. One can add fontweight="bold" to get a bold look. I don't know whether the font, or its size, can also be changed.

There doesn't seem to be much available on programmatic typesetting. You could roll your own procedure that constructed such typeset-enhanced names by simply concatenating your input string/name with the decorating information.

acer

That is nicely explained, and better laid out than a previous similar suggestion of mine.

Darin, would you be able to explain Joe's questions?

acer

That is nicely explained, and better laid out than a previous similar suggestion of mine.

Darin, would you be able to explain Joe's questions?

acer

This doesn't relate to the OP, but... names of type local can be assigned to variables and then be saved, but the localness can get lost.

> restart:

> t:=`tools/gensym`(x);
                                    t := x
 
> type(t,`local`);
                                     true
 
> save t, "temp.m":

> restart:

> t;
                                       t
 
> read "temp.m";
> t;
                                       x
 
> type(t,`local`);
                                     false

So I would not say that such locals are successfully saved.

I suspect that the inability of ".m" format to handle such locals might be why they do not work properly when conveyed along the context-menu system. See here.

acer

This doesn't relate to the OP, but... names of type local can be assigned to variables and then be saved, but the localness can get lost.

> restart:

> t:=`tools/gensym`(x);
                                    t := x
 
> type(t,`local`);
                                     true
 
> save t, "temp.m":

> restart:

> t;
                                       t
 
> read "temp.m";
> t;
                                       x
 
> type(t,`local`);
                                     false

So I would not say that such locals are successfully saved.

I suspect that the inability of ".m" format to handle such locals might be why they do not work properly when conveyed along the context-menu system. See here.

acer