But there is one favor you could do to me: Send me as much as you can of you 'not classified' pascal sources (from time to time). I am sure it would help a lot to get my pascal knowledge transformed from ST Pascal plus to Lazarus/FPC. This would be very nice!
...

My route was through TP5, TPW then Delphi. My workplaces exclusively used Windows generations. I have plenty of Delphi source, but it doesn't import into Lazarus very cleanly so far.

I've just upgraded my RAM (to16GB) so my system has been offline for a bit. I'll see if I have any useful code for you when I get a better chance to play.

There doesn't seem to be a well-defined system Ubuntu/Puppy API, but Lazarus 'wraps' functions and datatypes up, so it doesn't really matter for simple programs.

I'll see if I have any useful code for you when I get a better chance to play.

I think even stuff like your "Hello World" Application would help to make me able to get One Step into Lazarus. The older Pascal System that i have had learned and used for many years does not include classes and stuff like that.

I'll see if I have any useful code for you when I get a better chance to play.

I think even stuff like your "Hello World" Application would help to make me able to get One Step into Lazarus. The older Pascal System that i have had learned and used for many years does not include classes and stuff like that.

So, every line of Pascal code surely would give some help to me.

Thanks in advance...

RSH

Dear RSH,
Lazarus is basically like Delphi. I have learned that Delphi books (before .NET Delphi versions) are good to learn Lazarus. Actually, much better than Lazarus wiki pages...

@RSH I'm working on converting an old Delphi 6 app that uses 2 general-purpose classes/objects I wrote some time ago which should work fine in Lazarus all versions. I'll upload it when it works correctly in Linux. It's currently being held up by a section of code that saves/loads a custom datafile to disk in a 'Windows' way. You might find the OOP code useful to pick apart.

Unfortunately, much of my older code uses a set of self-written custom objects (VCLs) which were very windows-specific, and hard to unpick from the projects. Other code is for Windows DLLS mostly written in 16-bit TPW for Win 3.1- not very useful for Linux!

As tatamata says, Lazarus IDE is exactly like Delphi (before V.8.0), but there are problems converting existing Delphi projects written for Windows into Linux Lazarus apps, as I am finding out!

There are loads of Delphi code snippets on the web that should plug into Lazarus just fine.

Delphi/Lazarus is a fantastic event-driven OOP language IMO. It's a natural step up from non-OOP and/or interpreted languages. The powerful and simple IDE is also great for the 'lazy programmer' to create a working app in minutes to test a concept or create a mock-up.

It is worth writing thoroughly debugged re-useable objects wherever you can in OOPascal/Lazarus as this unleashes it's true power to create complex but mainly bug-free code quickly. The objects take longer to write than regular code, but can be easily subclassed when necessary to extend them. I think there's a real 'beauty' in an OOP-written app, and they are easier to maintain.

'helloworld' is a one-line testing GUI 'mock-up' app - not very useful for study

I'm really enjoying the challenge though, and Linux/Lazarus has only crashed once so far. I'm very excited at the cross-platform and 32/64-bit capability, and in awe of the Lazarus/FreePascal programming team - what a great job they've done!

No worries about the crash. It was the Lazarus IDE bugging out for no apparent reason, but I'm used to saving code frequently during development.

One thing worth mentioning about the LAZY distribution:
The compiler objected to a CopyFile statement as illegal. I looked into the FPC Runtime Library and FPC Free Component guides to see if I could find an alternative routine, but nada.

A short search on the web revealed the FileUtil unit (containing CopyFile) which was not included in the guide at all, but included in the FPC distribution binaries.

The Guides has been the original documentation of Lazarus 0.9.30.1 and FPC 2.4.2. I did nothing remove, change or add.

minesadorada wrote:

The compiler objected to a CopyFile statement as illegal. I looked into the FPC Runtime Library and FPC Free Component guides to see if I could find an alternative routine, but nada.

Maybe this has to do with the fact that the LazY Puppy Lazarus SFS uses the rtl directory of the FPC 2.4.4 sources?

This one has been necessary to change because there has been a main bug in the original sfs. It has been impossible to add an event to the object manager. Only after removing rtl dir (2.4.2) and adding rtl dir (2.4.4) this bug was gone and Lazarus not only runs - it worked also.

This limitation is a lucid puppy based limitation. I did already several times use all ten sfs files (without pupsave) and there were no problems at all.

I have made some work on this. It seems to be impossible to change the number of loadable .sfs files. I did create some pup_roX (X is the number) directories in /initrd. As long as working with puppy everything works fine (i did use 11 .sfs files at a time), but the created pup_roX directories will not be saved at shutdown._________________LazY PuppyRSH's DNASARA B.

It's not impossible to add more sfs files and maintain persistence since it had been done with other puplets.

You have to create the directories on boot up by modifying the init file, located within the initrd.gz, to do it. At one time that was all you had to modify. I am not sure if you have to modify any other files now.

The HowTos for:
(a) modifying initrd.gz
(b) adding more sfs files in Puppy 4.x
are SOMEWHERE on this forum. As usual, tthe problem is finding them and with (b) are the instructions complete for today's pups?

After editing initrd.gz as shown LazY Puppy will be able to load 12 .sfs files without a complaining sfs-load.

You can use the Edit intrd.gz with GUI in the LazY Puppy menu to edit the initrd.gz. Please, do make a copy of your initrd.gz first.

The GUI is self explaining and easy to use (because it is written by myself)

I will add this feature to the LazY Puppy Update!

ICPUG wrote:

It's not impossible to add more sfs files and maintain persistence since it had been done with other puplets.

You have to create the directories on boot up by modifying the init file, located within the initrd.gz, to do it. At one time that was all you had to modify. I am not sure if you have to modify any other files now.

The HowTos for:
(a) modifying initrd.gz
(b) adding more sfs files in Puppy 4.x
are SOMEWHERE on this forum. As usual, tthe problem is finding them and with (b) are the instructions complete for today's pups?

I knew it must be possible in any way, because i had a test on slacko, which can load more than 6 .sfs files.

I just did think there must be an easier way to do this without editing the initrd.gz. But this didn't work

I coded a GUI application in Lazy Puppy which uses many features of FPC. I then opened the linux project in the Windows 7 64-bit version of Lazarus; told it to compile for Win64 and it did it without a hitch!

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum