[Oberon] Oberon Text and new systems; was Re (n): Question about Oakwood guidelines and design choices

[Joerg]

I fully agree, to render HTML5 you need a lot of code.

For completeness: The V5 text is prepared for an offeset (Texts.PieceDesc.voff). You can even set the offset (Edit.ChangeOffset) but TextFrames does not display that field. By adding an own MyTextFrames.Mod without changing Text.Mod you could enable offsets.

It’s like the color: it’s there (Texts.PieceDesc.col) By changing the display driver Display.Mod without changing Texts.Mod you can display colored text.

Here a screenshot of a colored FPGA implementation. Color depth is 4 (16 colors!) the rest is color mixing.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.jpg
Type: image/jpeg
Size: 58751 bytes
Desc: not available
URL: <http://lists.inf.ethz.ch/pipermail/oberon/attachments/20210608/bafc44c3/attachment-0001.jpg>
-------------- next part --------------


br
Jörg

> Am 08.06.2021 um 23:03 schrieb Michael Schierl <schierlm at gmx.de>:
> 
> 
> Hello Peter,
> 
> 
>> Am 08.06.2021 um 18:24 schrieb peter at easthope.ca:
>> 
>> Should a universal Oberon Text type be derived from V4, ETH Oberon or
>> V5?  Also acknowledge that HTML5 is far more ubiquitous than any
>> Oberon Text type.  Hypothetically an Oberon system can be built with
>> plain ASCII text and HTML5 and no Oberon Text. Discussion by the
>> knowledgeale and experienced people can help.
> 
> The most complex application on most "smaller" OSes today is the Web
> browser. And even when they are several megabytes large, they cannot
> adequately parse what "HTML5" has become today (even if you exclude
> JavaScript).
> 
> With the demise of the old edgehtml engine (and deprecation of old IE
> Trident and Opera Presto engine) there are effectively only two
> feature-complete rendering engines for HTML5 left (Gecko used by Mozilla
> Firefox, and Webkit/Chromium/Blink used by the others). And the size of
> their (uncompressed) sources is gigantic.
> 
> So, I would not try to provide any (badly compatible) HTML5 support to a
> system like Oberon which tries to be simple and tries to remove what can
> be removed.
> 
> By the way, V5 text does not have vertical offsets, so no
> subscripts/superscripts.
> 
> 
> Regards,
> 
> 
> Michael
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon