as i coded some gui for my entertainment, i sudently saw this error:
txt x y xl yl txt colors font
put x y xl yl bmp colors
box x y xl yl colors
when i started to add the fader and buttons functions, it appears to be a problem.
because theses functions will call a text, an image and a rectangle
and the "color" parameter have to be always after the coordinates, to keep a compatibility, and if an item cannot access it's onw structures like image or text, it can display a coloured rectangle, this is interresting in case of html parsing with access problems to the ressources.

it took me only 1 hour to modify everything in my poor testdemo code to work with this update.

but now, it is more friendly to create complex graphic objects.


but why do i create this librairy? does anyone use it's functions?
i create this librairy because it is my vision of intelligence.
something with a general structure like grammar, geometry, objects.
and something platform independant.
i need to create a set of addressing modes for fool. a feature that can use parameters as pointers, values, files, structures, etc etc.
the finality is to save memory and create a new instruction set.
the proof is:

i use a functions list.
each function have a pointer and this pointer have a fixed position inside the function list.
the flist is created during compile.

in order to use less memory, i want to create a sort of transparent initialisation layer.
something you don't have to do while coding your application.

the OS is a set of functions loaded at a reserved location in ram or cache.
for the moment, all my functions occupies less than 64k, largelly less than code cache on my PIII.

this OS have a function list located at the start of it's segment.
each pointer is a composed of:
function's id, function's far pointer.
functionlist dd size
dd fid1,ffp1,0
dd fid2,ffp2,0
when creating your application, you will create a list of imported functions as this:
flist:
f dd size
.func1 dd fid1,0
.func2 dd fid2,0

then, when the application is loaded, to keep transparency, the OS will copy
the pointers from it's list.

but as MS DOS don't do that, i include all the pointers and functions inside the application.
and i don't want to code on RM all my life.

new feature with fool, and evolution.

now, it have the support for mouse and keyboard can emulate mouse "transparentlly".

CTRL + M toogle the mouse beetwen key and normal mode.

normal mode uses int33h for the moment.

buttons call objets when pressed and / or released.

zone call objet [esi+zone.event] when mouse hotspot is inside zone [x,y,xl,yl]

the mouse is active by default in the comheader.inc file.

to use the mouse, just read the coordinates, deltas, and status in mouse structure.

Code:

mouse  dd f.int33,.x,.y,.dx,.dy,.color,.bmp,.status,.wheel,.item
    

added the function f.grab, in order to grab graphic items.

2Dmap.asm is a test, to create a very big game map. more than 1000000*1000000 is very possible.

testfpu.asm is an attempt to mix real32 and fool, in order to make some precise computations.

justlib.asm is the minimal code required to use the comheader under dos.

oscilloscope.asm is an application to display some ram in a signal form.
it is also the start of a "win98 like" gui definition.

view application is a sort of hexadecimal reader in devellopment.
it will be the same base as oscilloscope, and will be the base of file system viewer.


13/03/09
update and backup of fool.
it will be the official package on fasm board. for THE REAL OS CONTEST.
this backup is more for me because tests will be very dangerous theses next days.

about files: bad idea, don't do it
to use correctlly the system and ad applications, i will create the .app file type.
it will be a sort of MZ, but a little different.

the header will contain position and size of the local flist (updated at load time), and the offset of entry, generaly a gnode.
to execute these, i will create the anode, to execute applications into other segment.

then it will be possible to load external applications, with restricted access if coded exclusivelly in fool style.

as i am building a "real" interface, i need items to be handled by any user item.
theses "user items" are mouse, keyboard or any human device that will reflect the human action.

when i tell this, it is mainly to remember that computers don't need a system but we, we need one to use the power of this machine.

the keyboard can be avoided for many purposes because of need devices.
then, a human device will be used to drive the system.
the human device will integrate a set of functions.

two or more families of devices will be possible. like pointing, keyboard, microphone, etc...
theses families will have a common main structure.
one human peripheral detected will install itself as a system object.
the system will give the hability to applications to use transparentlly the devices.

and the main major change is to reorganise the execution process.

basically, the execution process is to dive into the fool tree using "main" item, and dive more and more with "gnode", "node", "xnode".

but now, a change occured, i decided to add a new item able to call items.
the buttons and screen zones.
(maybe later, the keyboard will too..)

it gives me some problems but nothing very sad, just a priority problem.

Maybe some screenshots may help, this topic .

hello all.
i have the honor and regress to anounce that edfed will take a very long rest.
then, i'll stop all my coding/electronics/researches activities to travel and live a little more.
i lost my job about the power supply 1 week before it's achievment.
a little fed up by this stuff.
i'll ride my bike over the french roads.
i hope i'll recover the passion for coding after that.

bye bye.

i post the very last state of my dear FOOL machine just for the eventuality of material loss of my PC.
hope it will be there when i'll be back.

Good luck edfed. Enjoy your travels.

Sorry to hear that edfed, go recharge your batteries and come back with some new great ideas

batteires charged.

now, bootwriter0.6 for dos available.

it needs a little fix to select drive and update the parameters accordingly to the drive selected.

after, the lib itself is still the dumb version, but it don't limit the functionality of bw06.

be carefull when using this utility. for the moment, it is limited on floppy drive 0, but when drive selection popup will work, it will be able to write to any bios drive. and on usb pen under win98.

Nice - Glad to see your making progress!

hi edfed,
i got really big idea for you, coz i knew u r the guy who is capable to produce the output

mind if i chip in some idea?

Boot writer:

boot writer is an application made all in fool and a little assembly, to run under any DOS compatible environment.

the gui is simple.



first, the title bar:
displays a button to exit, and the name of the application.


just under this bar, the first form.
this edit form is the path of the file to load in the DOS file system.

to load the file, you should click on the form.

! when you load the file, the button "write it!" in the left down corner will display a "pixel image" of the file content, it is a cool trick i find usefull because it lets you verify the content with just one single look.


the second form lets you choose a drive detected via BIOS int13h.
valid drives will show their geometry in the drive popup window.

ones you selected the destination drive, you should verify the first sector coordinate in CHS.

for BOOT sector, all field should be C=0 H=0 S=1
for the second sector, CHS=0 0 2
etc...

the down right corner shows the size of the file in real sectors, and in bytes.

a single boot sector is 200h bytes, and 1 sector.

when you click on write it button





here is the screen shot of bootwriter application with ramview application.


requirement:
bios int 13h (write sectors),
dos int 21h (open & read file),
dos int 33h (mouse driver),
fool library.

todo list for the next version (0.7):

keyboard useage of all this application, and dependances, possibility to edits every forms, by selecting them with some tab (or a surprise. ..)

possibility to select the sectors in LBA form (Hexa or decimal), with automatic CHS<->LBA update.

possibility to view and edit content of file in a choosen editor.
possibility to load file from sectors, file system, file editor.
possibility to store file to sectors, ram, file system, file editor.



caution, be carefull with bootwriter, you can lose your datas forever!
But be confiant, i added a confirmation button.
a big one that should be clicked to launch the process.

update/save.

if you want to play a little, there is a sort of "how long can you survive", but it needs a speed in Pixels/s for balls, with int8.inc, it is possible to have the same speed on any compute.




the basic desktop in 320*200.


the desktop during a zoom test.


it is a little better each time i update it.