Re: [lazarus] Changing TObject
On Wed, Mar 21, 2007 at 07:15:41AM +0300, Al Boldi wrote: (reserved in the VMT by the virtual directive), it doesn't create room. This is also why you can't override non virtual methods. Thanks for this very clear and to the point answer. Would it be possible to implement virtual objects? Depends on what you mean by virtual objects. You know, an object that can be overridden like a virtual method But what is exactly overriden in the object? In the case of a method it is clear. The code of that specific method is overridable. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Changing TObject
Marco van de Voort wrote: On Wed, Mar 21, 2007 at 07:15:41AM +0300, Al Boldi wrote: (reserved in the VMT by the virtual directive), it doesn't create room. This is also why you can't override non virtual methods. Thanks for this very clear and to the point answer. Would it be possible to implement virtual objects? Depends on what you mean by virtual objects. You know, an object that can be overridden like a virtual method But what is exactly overriden in the object? In the case of a method it is clear. The code of that specific method is overridable. Override the whole object; consider this: TObject1 = class; This inherits the ancestor and changes the name, whereas something like: TObject = class ; override; Would inherit/override the ancestor while keeping the name. Is this possible to implement? Thanks! -- Al _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Changing TObject
On Wed, Mar 21, 2007 at 02:26:06PM +0300, Al Boldi wrote: But what is exactly overriden in the object? In the case of a method it is clear. The code of that specific method is overridable. Override the whole object; consider this: TObject1 = class; This inherits the ancestor and changes the name, whereas something like: TObject = class ; override; Would inherit/override the ancestor while keeping the name. Is this possible to implement? In general: No. All descendants would still be the old interface. This because that is the objecttype that is seen when the descendant is defined. (e.g. on RTL compilation). There is a Delphi feature called Class helper (which is one of the C# backports, and not the nicest one), but this doesn't solve this problem, since it doesn't help with already compiled code. (it only saves the substitution) _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
[lazarus] Managing Cross Platform Projects
Hi all, I was wondering what other did to manage cross platform projects? The problem that I have is writing the project in on OS (Windows for the current project) and then compiling over on linux. Everything compiles fine, but it's a pain to port a project over because of unit reference paths, etc that are different on each platform. I was curious as to what other do in this situation. My first thought is to save a version of the project to Linux, make sure everything compiles and then diff the units when I need to compile and update on the other platform. Any Suggestions? Thanks, -- Warm Regards, Lee _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Managing Cross Platform Projects
On 3/21/07, Lee Jenkins [EMAIL PROTECTED] wrote: I was wondering what other did to manage cross platform projects? I mostly use subversion to manage the source code. You will need a server for that, of course. It´s not hard to set up, I´ve already done it for internal non-open source projects. For gpl projects I use source forge´s svn =) I think that even with only 2 persons on a project, or even only 1 person working on different operating systems, subversion is a good solution. Further you can see all alterations later, it´s very convenient. but it's a pain to port a project over because of unit reference paths, etc that are different on each platform. Why are paths different on each platform? A project should normally work with paths relative to it´s project file directory, this way paths work everywhere. -- Felipe Monteiro de Carvalho _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
[lazarus] po files and utf8
Hi,
my *.po files are utf8 encoded. When I use GTK2 and Linux this is no problem.
Translation is done by:
TranslateUnitResourceStrings('myunit', myunit.%s.po', 'de', '');
I looked into lcl/translations.pas and it seems that every resourcestring is
converted by UTF8ToSystemCharSet();
But when I run my program under windows all lables that include äüü characters
are empty.
How can I translate it the right way?
Sebastian
_
To unsubscribe: mail [EMAIL PROTECTED] with
unsubscribe as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
[lazarus] Crossplatform Windows-Linux
I'm sorry to bring up something like this, but I really need help. I need to port an app from windows to linux. However, since all my development is under windows I would like to compile under windows and run it on a (or better the only) linux machine in the company. The linux machine is running Mandriva 2006 and does absolutely nothing at the moment other than serve a remote disk for backups. The app uses Synapse for networking and TDbf for it's data bank. I have never used Linux and have no idea about how it works. So here are my questions: 1) How do I (cross)compile a linux app from windows? (I will do a command line compile) 2) I keep reading here about clib that seems like something bad. How do I avoid using this? 3) Is Mandriva ok, or should I install something like Umbatu? regards, Andreas _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Managing Cross Platform Projects
Felipe Monteiro de Carvalho wrote: On 3/21/07, Lee Jenkins [EMAIL PROTECTED] wrote: I was wondering what other did to manage cross platform projects? I mostly use subversion to manage the source code. You will need a server for that, of course. It´s not hard to set up, I´ve already done it for internal non-open source projects. For gpl projects I use source forge´s svn =) I think that even with only 2 persons on a project, or even only 1 person working on different operating systems, subversion is a good solution. Further you can see all alterations later, it´s very convenient. Thank you. I'll take a look. but it's a pain to port a project over because of unit reference paths, etc that are different on each platform. Why are paths different on each platform? A project should normally work with paths relative to it´s project file directory, this way paths work everywhere. I use quite a few class objects from one project to another. I don't like to make copies of them just to place under a project so that it can find the unit. I guess I could place them all under lazarus components directory and use a macro...to specify the paths and let lazarus do the work... -- Warm Regards, Lee _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Managing Cross Platform Projects
On Wed, 21 Mar 2007 17:54:50 -0400 Lee Jenkins [EMAIL PROTECTED] wrote: Felipe Monteiro de Carvalho wrote: On 3/21/07, Lee Jenkins [EMAIL PROTECTED] wrote: I was wondering what other did to manage cross platform projects? I mostly use subversion to manage the source code. You will need a server for that, of course. It´s not hard to set up, I´ve already done it for internal non-open source projects. For gpl projects I use source forge´s svn =) I think that even with only 2 persons on a project, or even only 1 person working on different operating systems, subversion is a good solution. Further you can see all alterations later, it´s very convenient. Thank you. I'll take a look. but it's a pain to port a project over because of unit reference paths, etc that are different on each platform. Why are paths different on each platform? A project should normally work with paths relative to it´s project file directory, this way paths work everywhere. I use quite a few class objects from one project to another. I don't like to make copies of them just to place under a project so that it can find the unit. I guess I could place them all under lazarus components directory and use a macro...to specify the paths and let lazarus do the work... Put them into package. It's basically a folder with units. Mattias _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Managing Cross Platform Projects
Since the subject of SVN came up I couldn't resist to ask. Presently my method is to take a snapshot of the project directory to do backup. Easy and simple to do, and since I'm a one man show it is good enough for me. But of course there are problems if you need to look into changes in code, and transferring to another os also is not all that convenient. A while back I thought about setting up SVN because of the drawbacks, but since I am not familiar with it, the setting-up and running of it looked quite complicated. The other major concern that held me back was about how much disk space an SVN implementation consumes over time as it grows, and how big a backup of the SVN server data would be compared to my present method. What are your experiences? Regards, George Felipe Monteiro de Carvalho wrote: On 3/21/07, Lee Jenkins [EMAIL PROTECTED] wrote: I was wondering what other did to manage cross platform projects? I mostly use subversion to manage the source code. You will need a server for that, of course. It´s not hard to set up, I´ve already done it for internal non-open source projects. For gpl projects I use source forge´s svn =) I think that even with only 2 persons on a project, or even only 1 person working on different operating systems, subversion is a good solution. Further you can see all alterations later, it´s very convenient. but it's a pain to port a project over because of unit reference paths, etc that are different on each platform. Why are paths different on each platform? A project should normally work with paths relative to it´s project file directory, this way paths work everywhere. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Patch 4 sqlite3 componenteditor
Am Freitag, den 09.03.2007, 02:32 +0100 schrieb Mattias Gaertner: On Sat, 03 Mar 2007 14:29:11 +0100 tanila [EMAIL PROTECTED] wrote: Hello all, I found fixed a little Bug in sqlitecomponenteditor. The bug was fixed by Luiz. Thanks. Applied. Attachment includes the new version of $(LCLDIR)/components/sqlite/sqlitecomponenteditor.pas Maybe you meant: $(LazarusDIR)/components/sqlite/sqlitecomponenteditor.pas ? Shure... ;) Mattias _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Managing Cross Platform Projects
On 3/21/07, Lee Jenkins [EMAIL PROTECTED] wrote: I think that even with only 2 persons on a project, or even only 1 person working on different operating systems, subversion is a good solution. Further you can see all alterations later, it´s very convenient. Thank you. I'll take a look. Felipe hit the nail on the head. SubVersion is you friend in such a case, and well worth learning. I use quite a few class objects from one project to another. I don't like to make copies of them just to place under a project so that it can find the unit. I guess I could place them all under lazarus components directory and use a macro...to specify the paths and let lazarus do the work... No, rather used Lazarus Packages. That is what they were designed for. Place all you common code in a Package, then for each project that needs to use those files, you specify that package as a requirement in the Project - 'Project Inspector' dialog. -- Graeme Geldenhuys There's no place like S34° 03.168' E018° 49.342' _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
