State and direction of browser changes

[Waldek Hebisch]

As I wrote I would like to replace Hyperdoc code in FriCASsys by
Spad code. Currently large important part still needs fixes
and cleanups, but I merged some parts of new code. In effect,
currently br-op1.boot, br-op2.boot and br-saturn.boot are not
needed when using new code, they are present only so that
old code keeps working. From br-search.boot boot new code
uses only a tiny part (parsing patterns), once there is
replacement in Spad br-search.boot will join to previous 3
files. New code needs only small part of br-util.boot
(144 lines) and ht-util.boot (186 lines) but those parts
are needed by bc-matrix.boot, bc-misc.boot and bc-solve.boot.
If we keep bc-* files in Boot, we will need supporting
parts of br-util.boot and ht-util.boot. Currently new
code need 243 lines from br-con.boot and 434 from br-data.boot.
Setting system variable via Hyperdoc uses htsetvar.boot.

After recent merge to use new code I need tiny patch to
bc-* files, much larger to htsetvar.boot. Also, there
are 191 new line in br_sup.boot, 10 new lines in clam.boot.
And 2808 lines in hypertex.spad.

Anyway, currently br-op1.boot, br-op2.boot, br-saturn.boot
and br-search.boot are legacy files where we still need
to fix bugs, but cleanups and restructurings make no sense
as they will go away before new release. The same
for majority of br-con.boot, br-util.boot and ht-util.boot.

--
Waldek Hebisch