[Stormdos-develop] Re[4]: stormdos development
Status: Planning
Brought to you by:
exhu
From: Juras <yb...@tu...> - 2004-04-23 17:55:44
|
Hello Kohut, Friday, April 23, 2004, 2:29:30 PM, you wrote: KI> I have translated your ideas to HTML. See attachment. Send comments. Good job!!! Thanks! Especially the LOGO!!! As for the rest of design, I'll think it over and menu highlighting is a bit buggy in Mozilla... I think it's early to publish any sophisticated WWW site now, because nothing user-interesting is implemented yet. But the logo is very good, i'll try to experiment on it, if you don't mind. (all copyright I'll address to you, of course ;) And it's a good useable sketch now I see it clear. Do you experience any problems with the stormdos-develop mailing-list? I've commited some more changes to device engine through the CVS. Try to use anonymous CVS access and download the module sd32_fpc . Pay attention to modules.txt in doc subdir and kcontext.pas. Please, send any feedback on whether you've succeeded in downloading through CVS and whether you looked thorough kcontext.pas unit's interface part. And, I think it'll be more consistent to commit all changes to the CVS through me. Think over PE image-manipulation unit - no FILE I/O but manipulation via CALLBACK functions for FILE I/O i.e. const // file operation number PE_FO_OPEN=1; PE_FO_CLOSE=2; PE_FO_READ=3; ... type TFOREADPARAMS=record dest_ptr:pointer; bytes_to_read:DWORD; end; TFILEIOPROC=function(opcode:DWORD;params:pointer):INT; PPEIMAGE=^TPEIMAGE; TPEIMAGE=record imagep:pointer; fileproc:TFILEIOPROC; ... end; function initimage(fileproc:TFILEIOPROC;peimg:PPEIMAGE):INT; function loadheaders_and_sections_info(peimg:PPEIMAGE):INT; function map_at(peimg:PPEIMAGE;base_addr:DWORD):INT; // provides FIXING-UP, relocation etc. ... Be aware that NO CLASS/OBJECTS, no standard memory allocation/deallocation functions are available!!! -- Best regards, Juras mailto:yb...@tu... |