Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Malcolm McLean <malcolm.arthur.mclean@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: Baby X is bor nagain
Date: Wed, 12 Jun 2024 10:51:12 +0100
Organization: A noiseless patient Spider
Lines: 49
Message-ID: <v4br2g$1jfqf$1@dont-email.me>
References: <v494f9$von8$1@dont-email.me>
 <v49seg$14cva$1@raubtier-asyl.eternal-september.org>
 <v49t6f$14i1o$1@dont-email.me>
 <v4bcbj$1gqlo$1@raubtier-asyl.eternal-september.org>
 <v4bh56$1hibd$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 12 Jun 2024 11:51:12 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="949b13f2b13f22ff92a4cfa4b2c0ba6d";
	logging-data="1687375"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+oVn6TMypRG1aGvFW6SRn42wTCccTiUCU="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:19ekaK/iPCAwh4dg3++YgCQdzpY=
Content-Language: en-GB
In-Reply-To: <v4bh56$1hibd$1@dont-email.me>
Bytes: 3609

On 12/06/2024 08:01, David Brown wrote:
> On 12/06/2024 07:40, Bonita Montero wrote:
>> Am 11.06.2024 um 18:15 schrieb Malcolm McLean:
>>
>>> These are Baby programs. But they use a cut down GUI. So they need to 
>>> get fonts and images into the program somehow. And so Baby X does 
>>> that by converting to 32 bit C arrays which can be compiled and 
>>> linked as normal. And for that, you need a tool. Writing a tiff file 
>>> decoder is not a trivial exercise.
>>
>> I converted my code into sth. that produces a C-string as an output.
>> Printing that is still very fast, i.e. the files produced are written
>> with about 2.6GiB/s. But the problem is still that all compilers don't
>> parse large files but quit with an out of memory error. So having a
>> .obj output along with a small header file would be the best.
>>
> 
> How big files are you talking about?  In an earlier thread (which I 
> thought had beaten this topic to death), "xxd -i" include files were 
> fine to at least a few tens of megabytes with gcc.  And it would be, 
> IMHO, absurd to have much bigger files than that embedded with your 
> executable in this manner.  I can understand wanting some icons and a 
> few resource files in a PC executable, but if you have a lot of files or 
> big files then a single massive executable often does not make much 
> sense as the binary file.
> 
> If you /do/ want such a file, it is typically for making a portable 
> package that can be run directly without installing.  But then you don't 
> mess around with inventing your own little pretend file systems, or 
> embedding the files manually, or using absurd ideas like XML text 
> strings.   You use standard, well-established solutions and tools such 
> as AppImage on Linux or self-extracting zip files on Windows.
> 
> 
You don't get what Baby X is all about.

These solutions will not work for the audience I am trying to target.
Baby X is clean, portable, and simple. As much as I can make it. And 
it's meant to be easy for people who are just beginning programmers to use.

But the main focus now is help and documentation. The improved ls 
command is now in the shell, and the next task is to improve the "help" 
command, at the same time as writing more docs. The two tasks naturally 
go together, and the website is beginning to gel.

-- 
Check out my hobby project.
http://malcolmmclean.github.io/babyxrc