mORMot Open Source

Hello,

I have been thinking of two terms that should be used.

ThreadSafe - For code that works in multithreaded environment, don't crash and works as expected. (what it means )

ThreadSmart - That runs very fast and is (maybe) best solution

Basically some guidelines, as mentioned above are very very important. To help programmer to look for own code to make it better.

I just like to make challenge to someone(s) to start keeping up (a blog) document where would be up to date list of these. And I would like to have some kind of example codes sniplets.

Code Before and After from ThreadSafe to ThreadSmart Because this way it would be much more clear. We all have not very good English, me included, but we all speak Pascal. So it would be the universal language for all of us. This would help all very very much (And when I am talking of Someone I am not talking of that it necessarily should be  Arnaud Bouchez, he has done so much already)

-Tee-

OK,

Like all normal programs, Undo is very very important feature. And if there is some kind of support to save the changes at the serverside. Undo should be doable. (To work it would need some kind of table structure to save all the changes).

But multistage Undo would be a must feature in my point of view. Does not matter how it is done. But basically almost any kind of app would need an Undo, or at least would make it much better. I've been developing an application that did not have Undo, and it really made everything so bad (for User). Users had to really think very carefully what to do. And in many cases they did not have courage to do any changes even they needed to. Because there was no way back.

I think that any framework that sits between (G)UI and DB should have undo. Way or other...

-TP-

Hope that TTextWriter is not a Female then

(Sorry could not resist)

D2010 compiled it just fine...

-TP-

Could not compile, D6 don't open the project, dies in Access Violation (Something wrong in my installation). And D2007 gives internal error when trying to compile it So I can't compile and test it at all for now...

I try it at home, but if it would be possible to have compiled .exe, and some bat to run some standard "test suite", with various settings.

Maybe to modify the test program to write  Log on disk, to make posting into here easier...

-TP-

Oops,

I was more than less uninformative

I mean .exe compiled version of test/bechmark tool, so I could test them more easily (see the difference on my machine(s))

Sorry for that, I need to concentrate more

-Tee-

Maybe it would be worth to add multithreaded test into it

-TP-

Hello hello,

One question, if this is meant for small en medium blocks (most common) how it is going to scale with threads that use very large data blocks, think of handles large bitmaps?? Will it scale better than FastMM or is it the same?

-TP-

OK,

I forgot this totally,

Bug was between the screen and back of my head

Sorry about this, hope there would be native Stream "interface" in next release. So I would get rid of this "hack"

It is  very fast indeed, in memory compression especially Thanks for this!!!

-TP-

Hello hello,

Can I use this library to make Pdf, with high resolution image and transparent text and images on top of those images.

I need to have high resolution background images and have some text and transparent image on top of it...

Can I do this, and if, any tips?

.TP.

Whoooa...

I did jump a gun. Found and Error (or stumble upon one). Now you really wan't the Test code

There is some serious problem. That is why I did see lot of problems before.

-TP-

Hello,

I took the code from above for LZ-compression between streams and it works great, then I tried to make same code to work with LZO, and don't work. I just can't see what I am doing wrong here

  procedure LZODecompressStream(const Source, Dest: TStream);
  procedure LZOCompressStream(const Source, Dest: TStream);


procedure LZODecompressStream(const Source, Dest: TStream);
var
   Size: Integer;
   Buf, Tmp: Pointer;
   ComprSize: Integer;
begin
   Source.Read(ComprSize, SizeOf(ComprSize));
   GetMem(Tmp, ComprSize);
   try
     Source.Read(Tmp^, ComprSize);
     Size:= lzopas_decompressdestlen(Tmp);
     GetMem(Buf, Size);
     try
       Size:= lzopas_decompress(Tmp, ComprSize, Buf);
       if Size > 0 then
         Dest.WriteBuffer(Buf^, Size);
     finally
       FreeMem(Buf);
     end;
   finally
     FreeMem(Tmp);
   end;
end;


procedure LZOCompressStream(const Source, Dest: TStream);
var
   Size: Integer;
   Buf, Tmp: Pointer;
   ComprSize: Integer;
begin
   Size:= Source.Size;
   GetMem(Buf, Size);
   try
     Source.Seek(0, soFromBeginning);
     Source.Read(Buf^, Size);
     Size := lzopas_compressdestlen(Size);
     GetMem(Tmp, Size);
     try
       ComprSize := lzopas_compress(Buf, Source.Size, Tmp);
       Dest.Write(ComprSize, SizeOf(ComprSize));
       if Size > 0 then
         Dest.WriteBuffer(Tmp^, ComprSize);
     finally
       FreeMem(Tmp);
     end;
   finally
     FreeMem(Buf);
   end;
end;

Maybe more eyes can tell me how stupid I really am

btw. is there ompatible C# implementation of LZ or LZO?

-TP-