<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> These are great requirements you are posting! I even think a dedicated hardware is needed. That's a big project indeed. I don't know much about founding hunting, I guess it is complicate and time consuming. In the other hand I am still astonished to see every day how poor is the impact of computer in teaching (in k12 and lower grades). In the other hand I am gratefull the use of computer in education is poor because regarding the existing option it will be a nighmare. Still most of the society use computer on a daily basis but the option for the education is poor. In my opinion, a perfect computer in education will be ubiquitous : it will look like a book when the learner needs a book, it will look like an exercises book when the learner need to exercises, it will look like a notebook when she needs to take handwritten note, it will look like a binder when she needs to access her lessons, etc. All contents would be dynamic of course. And of course it be lightweight, very and replace this horrible 10kg bag too many young learners needs to carry on. Hilaire <div class="moz-cite-prefix">Le 30/04/2021 à 22:43, Gerald Klix a écrit : </div> <blockquote type="cite" cite="mid:7c556880-ba21-ae18-22dd-6b6b1273d9ac@klix.ch"> That got me really thinking. I once had similar dreams. Haver has less far reaching goals, I just want some means to create and distribute portable applications with seamless support for orthogonal persistence. The most far reaching idea is to distribute packages and complete applications (images) by a peer to peer network, something like IPFS (<a class="moz-txt-link-freetext" href="https://en.wikipedia.org/wiki/InterPlanetary_File_System" moz-do-not-send="true">https://en.wikipedia.org/wiki/InterPlanetary_File_System</a>). If I think about the "requirements" of your idea: - Knowledge should be represented as Code - Inexperienced pupils should be able to manipulate Code/Knowledge therefore: - An even simpler editor A really simple editor, something like Scratch/Blocky, however without the huge gap between a text editor and the blocks editor. With your VectorGraphics package, this will be great fun. - Much easier recovery from mistakes. The current image, change-log, file-your-code-into-a-clean-image rigamarole is much to complicated. I don't know whether this can be solved with a database and transactions. Perhaps we need something like Python's virtual environments. Maybe a pack of Smalltalk images that are controlled from a master image; e.g. automate the aforementioned procedure. - Runaway recursions should also be caught, be before virtual memory is exhausted. - Debugging the code the runs in the UI-Process should be easy. Remote debugging a dependent image? A separate UI-Process that draws in a PasteUpMorph? - A suitable system for interactive development/teaching. - An easy interface to version control. GIT is a nightmare for newbies. (I still prefer mercurial and, believe me, the first Source Code Control System I used in my life was SCCS ...) I has to have the feeling of the undo function in MS Office. - A simpler module system than mine, for this use case explicit imports are probably best. *We need funding, this looks like a big project* Just my sundry thoughts. </blockquote> <pre class="moz-signature" cols="72">-- GNU Dr. Geo <a class="moz-txt-link-freetext" href="http://drgeo.eu">http://drgeo.eu</a> <a class="moz-txt-link-freetext" href="http://blog.drgeo.eu">http://blog.drgeo.eu</a></pre> </body> </html>