I apologize for that misinterpretation of mine.

Writing

M := <<m1|m2>,<m3|m4>>;

is just the same as writing

M := Matrix([[m1,m2],[m3,m4]]);

which, see my former mail in this thread, I would expect to mean a 2x2 matrix consisting of 2x3 matrices, not a 4x6 matrix consisting of scalars. My afterthought was in relation to the post by Tim Van Dusen in which he seems to think that the way Maple now works is somehow needed in order to easily create larger matrices from smaller ones. The intention of my post was just to point out a relatively easy way of creating a larger matrix from smaller ones even if Maple behaved as I would expect it to do.

Note that creating larger matrices from smaller ones can be performed using the following way of embedding, so to speak, smaller matrices into the larger one (using again the example from above):

m1 := Matrix([[1.1,2.1,3.1],[4.1,5.1,6.1]]):
m2 := Matrix([[1.2,2.2,3.2],[4.2,5.2,6.2]]):
m3 := Matrix([[1.3,2.3,3.3],[4.3,5.3,6.3]]):
m4 := Matrix([[1.4,2.4,3.4],[4.4,5.4,6.4]]):
M := Matrix(4,6):
M[1..2,1..3] := m1:
M[1..2,4..6] := m2:
M[3..4,1..3] := m3:
M[3..4,4..6] := m4:

You are so very welcome, but I wonder whether my answer was useful to you. Here are some packages which are related to Quantum Field Theory:

• The Feynman Graphs Package, by Dr. Marvin Weinstein.
• The Package for the calculation of trace of Dirac gamma matrices, by Andrea Siver.
• The package TENSORS OF RELATIVISTIC ELECTRODYNAMICS WITH MAPLE, by Dr. Alexei V. Tikhonenko.

However, having had a short look at them, I do not expect them to be quite what you are looking for, but maybe you can get inspired by them.

One place to look is at the MapleSoft application center where you could enter, say, "Quantum" in the "Keyword or phrase" box to search for any useful application. However, I do not expect your search to be entirely successful because Quantum Field Theory is a very complex beast.

Thank you for saying that.

Thanks for your suggestion on using the Classic interface, but I think I have closed completely the door on Maple 11 for two reasons:

• I have quite simply come to dislike the product, because it have made me feel frustrated for so long.
• I have lost confidence in the product, because it have made me loose control over my documents.

So, I suppose, no future upgrade on my behalf will be undertaken, unless MapleSoft can give me a money-back-guarantee that these XML generated nuisances have been removed.

Thanks for this concrete post. I have just downloaded and installed tsWebEditor, written a short test-module, saved it as a text-file, and imported it into Maple. And it works :-). I have never before imported anything into Maple, probably quite a surprise to you guys. So these issues are quite new to me, which, I suppose, is the reason that I have felt quite overwhelmed by the content of previous posts in this thread. Maybe I am becoming a bit to demanding now, but how do I turn on Maple specific highlighting? For instance, I cannot find "Maple" under the list of Languages in Editor Settings -> Code Insight.

No, not as default. But Will might give you the privilege to do so. Needless to say, a blog entry should only be considered removed if no one has posted any comments to it, as the opposite would presumably be viewed as rude.

So, the conclusion seems to be that there is no simple solution to a simple problem. What a down.

To me aesthetics is part of any thing I strive for. Without it any achievement of mine becomes just cold to me, like a machine having made something that works, but without the soul of beauty. Our world today is overwhelmingly replete with this ugliness of streamlined efficiency. Apart from the question of maintainability, that is why indentation in codes is of imperative importance to me, which again is the reason why the present indentation problem in Maple is such a frustration to me.

Thanks for all your info concerning how to work outside the Maple editor. But, please forgive me, it just seems too overwhelming. I just want to carry on writing some packages of mine, checking some physical equations of mine, etc., without having to learn about shells and editors originating, as far as I have understood, from another operating system such as Unix, just because Maple 11 cannot figure out something as completely trivial as tab indentation.

I have just skimmed trough the page Functional programming, as provided by you, and the related page Imperative programming. You are quite right; I do use the imperative programming style. The reason for that, I suppose, is that in the field of programming I am almost completely self-taught (the only exception, I believe, being a Fortran course back in 1987, at the first year of my university study). But maybe I should give the functional programming style a try, because, after all, being a theoretical physicist mathematics should not be a complete stranger to me :-).

Honestly to say, I am disappointed with MapleSoft (but maybe it is just me being naive concerning the way software development is done!?), because this, maybe to MapleSoft insignificant, tabbing misbehaviour is a source of daily frustration to me. Actually, since my update from 9.5 to 11 my research activity using Maple has significantly reduced; all my programs written in 9.5 are no longer readily editable because of this tabbing misbehaviour. As a direct result of that, I have kind of lost the feeling of fun working with Maple because it feels like it is working against me, in a certain sense analogous to the worst parts of Word's auto-substitutions, etc. Having also spend a lot of money on updating I think you can understand my frustration.

Thanks for your suggestion. I have looked a bit at VIM, Emacs, and jEdit (the latter suggested by Will in another thread), but it seems to me, that there are too much Unix hocus-pocus (tar- and gz files, I am lost!). Of course, I might be completely mistaken, and if affirmative, please correct me. Anyway, I do not think that working in a text editor would really suit me. You see, the way I work is very iteratively, hitting Enter in Maple very often to check that small changes work as intended. This would entail having to copy-paste back and forth very often between the text editor and Maple.