State and direction of browser changes

23 views
Skip to first unread message

Waldek Hebisch

unread,
May 16, 2026, 10:49:44 AMMay 16
to fricas...@googlegroups.com
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

Waldek Hebisch

unread,
May 28, 2026, 5:39:22 PMMay 28
to fricas...@googlegroups.com
A little update: after recent commit new browser code is indepenedent
from br-search.boot. Also, parts of br-util.boot which are needed
by new code are moved to ht-util.boot. So, as of today the
following files are only needed by old HyperDoc: br-op1.boot,
br-op2.boot, br-saturn.boot, br-search.boot, br-util.boot
and match.boot.

--
Waldek Hebisch

Qian Yun

unread,
May 28, 2026, 6:41:32 PMMay 28
to fricas...@googlegroups.com
What happens to the old boot code? Will they be replaced by
new code via SPADCALL or will they co-exist?

- Qian

Waldek Hebisch

unread,
May 28, 2026, 10:13:38 PMMay 28
to fricas...@googlegroups.com
My plan is to remove the files above before the next release.
Also, most of br-con.boot, large part of ht-util.boot and
about 1/3 of br-data.boot should be removed. Together this
is about 5000 lines of Boot code to remove. Other removals
are possible, but I think it is better to replace the above
by Spad code relatively quickly, then to delay replacement
or relase waiting for bigger change.

Some replacement parts are already in the trunk, but one big
part (single package having 2800 lines) still needs work.
As of today diff between my private version where HyperDoc
uses new code and trunk is 275 kB. Biggest single part
is the package that I mentioned above (126 kB), removals
take some tens of kilobytes, I also need extensive changes
in htsetvar.boot and in remaining part of ht-util.boot.

At peak diff between my private version and the trunk
were about 500 kB, but during last two months diff is
going down.

--
Waldek Hebisch

Qian Yun

unread,
May 29, 2026, 8:14:38 AMMay 29
to fricas...@googlegroups.com
Corner case:

(3) -> search_documentation ""

>> Error detected within library code:
index out of range

- Qian

On 5/29/26 5:39 AM, Waldek Hebisch wrote:
Reply all
Reply to author
Forward
0 new messages