On Thu, Jul 17, 2025 at 09:41:57AM +0100, Martin Baker wrote:
> I use openSUSE and run FriCAS from there. I have found openSUSE to be stable
> over the years and so I'm keen to continue to use it.
> In October they are releasing Leap 16.0, Their website says it is "Expected
> to be Wayland-only (some Xorg remnants remain for now)"
> I don't know what this means but I assume it will continue to allow programs
> that require X.11 to use it or have some sort of X.11 emulator?
I do not know what the above means. I use LXDE as my desktop and
IIUC like most Linux desktops it is X11 only.
> So I am hoping that this won't affect how I use FriCAS but these low level
> issues do have a nasty way of throwing up unexpected problems and its
> potentially more cross platform issues.
> I don't actually require x.11 in that I do not start HyperDoc from my
> startup script:
> ./fricas1 -noht
> and I do not use 2D or 3D plotting functions.
> So it would be good if a startup script could be distributed with FriCAS
> that does not require X.11 at all and just uses the interface to the
> Terminal Console.
Startup script works fine on machine without X11, you just get an error
message that HyperDoc can not start. And with '-nox' option there is
no error message.
> I understand that Waldek is combining HyperDoc and fricas io into a separate
> program.
No. My work is on code included in FRICASsys. That should lead
to replacing most of code in 'br-*.boot' files by Spad code.
I would like to merge the new code with API generating code.
New code supports interactive use via current HyperDoc window,
that is Spad code is able to use current HyperDoc protocol.
Ideally new code should be able to generate HTML (api2.spad
can do part of work, but needs to be merged and expanded).
> In your last message you said "I think that search similar to
> constructor and operation search in HyperDoc could be provided by
> appropriate table of data and relativly simple Javascript code". This raises
> my hope that FriCAS could be made completely independent of these low-level
> and cross-platform issues. Is this correct?
That is slightly different thing. Currently API code written
by Ralf generates .rst files from which Sphinx generate
content of API site. This process provides a search box,
but IIUC this search basically works as "full text" search
on content of API site. I would prefer more targeted search
and think that relativly simple Javascript code could provide
such search. But this concerns API site, where interaction
is only due to Javascript (which limits what can be done).
For local use I would prefer to have a Web server inside
FRICASsys and dynamicaly generate HTML pages with content
corresponding to current HyperDoc.
Note: there are many ways to provide Web server functionality.
Currently JFriCAS uses Hunchentoot, but is is likely that
much simpler things would be enough.
--
Waldek Hebisch
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to fricas-devel+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/fricas-devel/aHkHXOszicJk-EVK%40fricas.org.
