Re: [Lazarus] Why we chose Object Pascal instead
waldo kitty ha scritto: > Hans-Peter Diettrich wrote: >> Graeme Geldenhuys schrieb: >> >>> I can't agree more... We have had this exact same issue in our company >>> (before I arrived). They hired cheap (inexperienced) developers that >>> caused havoc in the code. They make the GUI seem fine for a while, but >>> underneath the design (if there actually was a design) is totally >>> rubbish and unable to cope with new requirements. Hence the reason I >>> was commissioned to do a total rewrite. >> That's why neither Cobol nor VB will ever die: they make secure >> long-term jobs > > that's also why "real coders" do not comment their source code ;) > We had a guy who'd found an even more clever way. He did comment the code, but his comments reported what the code didn't do, instead of what the code was doing. Sort of an embedded and disguised TODO list, which could easily lead to believe that a feature was implemented, when actually it wasn't! -- Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] OT [Re: Why we chose Object Pascal instead]
Martin Friebe ha scritto: > Giuliano Colla wrote: >> Felipe Monteiro de Carvalho ha scritto: >> >>> And here is the best comment about it: >>> >>> Capt. Kirk: >>> As a customer your choices are: >>> >>> 1. Hire an experienced competent developer who understands the library >>> functions, knows how to write properly structured code with >>> appropriate variable scope and data types, or >>> >>> 2. Hire someone who will produce what appears to be exactly the same output. >>> >>> As a customer who doesn't happen to be a developer himself, the above >>> two options translate as: >>> >>> 1. Hire an expensive expensive expensive who expensive the expensive >>> expensive, knows how to write expensive expensive code with expensive >>> expensive expensive and expensive expensive, or >>> >>> 2. Save a bunch of money and get exactly the same thing. >>> >>> >>> >> The funny thing is that whoever buys a car, a drill, a mobile phone, >> whatever, knows very well that what is visible doesn't tell what's >> inside, how reliable it is, and so on, and looks for expert advice. A >> lot of publishers make money printing magazines which provide a better >> insight on cars, cameras, phones etc. etc. >> Nonetheless, although everybody stumbles every day in the pitfalls of >> badly written software, it appears that very few apply to buying >> software the same kind of approach. :-( >> > Yeah, but where is the magazine: "The programmer's inside" ? Which > compares individual programmers, and gives tips, whom to use for which > purpose? > It's a classical egg-and-chicken problem. No magazine because of no interest or no interest because of no magazine? However, there's no "Programmer's inside" but also no "Program's inside". When you read reviews about Windows Vista, or IPhone or whatever, they only tell you what any user would see. Not even a minimal effort to guess what's inside, and how well it's done. They check if a car leaks water when it rains, they don't check if a sequence of perfectly legal keystrokes or mouse movements can freeze Microsoft Office (it does). Giuliano -- Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Why we chose Object Pascal instead
Felipe Monteiro de Carvalho ha scritto: > And here is the best comment about it: > > Capt. Kirk: > As a customer your choices are: > > 1. Hire an experienced competent developer who understands the library > functions, knows how to write properly structured code with > appropriate variable scope and data types, or > > 2. Hire someone who will produce what appears to be exactly the same output. > > As a customer who doesn't happen to be a developer himself, the above > two options translate as: > > 1. Hire an expensive expensive expensive who expensive the expensive > expensive, knows how to write expensive expensive code with expensive > expensive expensive and expensive expensive, or > > 2. Save a bunch of money and get exactly the same thing. > > The funny thing is that whoever buys a car, a drill, a mobile phone, whatever, knows very well that what is visible doesn't tell what's inside, how reliable it is, and so on, and looks for expert advice. A lot of publishers make money printing magazines which provide a better insight on cars, cameras, phones etc. etc. Nonetheless, although everybody stumbles every day in the pitfalls of badly written software, it appears that very few apply to buying software the same kind of approach. :-( Giuliano -- Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Italian users
Giuseppe Fava ha scritto: >hi everybody, >I'm thinking about to create an italian lazarus community and I'd like >to know how many Italians are reading this list and how many of these >are interested... > >Giuseppe > > > Here's one. Even if in the last months I've been too busy to partecipate actively. From the length of this thread, I'd gather that we're not too many ;-) Giuliano -- Giuliano Colla Still using C++ and Visual Studio? I'm using Object Pascal and Lazarus. ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] GTK2 is now the default widgetset
Graeme Geldenhuys ha scritto: > On Tue, Oct 7, 2008 at 4:46 PM, Mattias Gärtner > <[EMAIL PROTECTED]> wrote: >> The speed of gtk1 and 2 differ widely. On some platforms the gtk2 is even >> faster >> than gtk1. It depends on your window manager, video driver and the gtk2 >> version. >> AFAIR gtk 2.12 fixed some issues. > > Luckily my Ubuntu 7.10 has 2.12.xx. So I'll get an update now (at > home) and give it a spin in GTK2. Oh no! That means I have to recreate > the Raize font again. :-) I've been postponing this for ages, because > to a lot of effort. Before I manually drew all Raize characters in > FontForge so I could generate bitmap fonts for linux GTK1. Now I'll > have to try and make truetype fonts for GTK2. > Have you tried the misc-fixed font coming with most Linux distros? It's very similar to Raize, and it works just fine both with GTK1 and GTK2. -- Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Howto recode GUI
[EMAIL PROTECTED] ha scritto: > On Wed, Mar 19, 2008 at 11:40:13AM -0300, Felipe Monteiro de Carvalho wrote: >> You can convert from UTF-8 to Current locale and the opposite direct >> using AnsiToUTF8 and UTF8ToAnsi located LCLIntf. This doesn't allow an >> arbitrary locale, but only the current one. > I think, that you do not realize question. I know functions which > can convert strings from utf-8 to iso atd... But I do not know _how_ to > online convert lazarus gui strings (label captions, button captions, > ...). > It may be awkward, but for me it worked. You can't do it within Lazarus, but there's a number of editors which can do that for you. Just open the .lfm files in the editor, telling it the input encoding, then save it with the required output encoding. I used KEdit (from Kde). Kind regards, Giuliano -- Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] TEdit color and font color
In TEdit, with gtk widgetset at least, it is possible to change TEdit color, and font properties, but not both at the same time. With default font, background color can be changed at will, but if a font different from default is selected, or font style or font color is changed, the background color flips to default clWindow (=clWhite). This makes it impossible to change background color and have a good contrast at the same time. Is this a known issue, a widgeset limitation or a bug? Platform Linux, widgetset gtk1, recents svn trunk (rev 14232). Giuliamo -- Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Localization in toolkit like fpGUI
Graeme Geldenhuys ha scritto: > Hi, > > I know this is not directly related to Lazarus, but I thought with all > the experience collected and that Lazarus supports localization, I > might get some good ideas here... > > I want to localize the fpGUI toolkit. Standard dialogs, error > messages, etc... What is the best way to approach this. > > 1) GetText: This was my first thought, but that means every fpGUI > based application needs to ship with external .po files which I don't > like and don't want. fpGUI based applications must preferably be a > single executable at best. GetText works great for your own > applications, but not for the GUI framework I think. > Are you really sure that a single executable is a must? I found out, at least in my experience, that by an end user point of view, a self extracting zip (Windows), a tar.bz2 (*nix), or a .dmg (Mac) is pretty much the same, and allows to distribute a folder instead of a file. This makes it possible to keep large images as separate files, to add translation files without touching the source code, to provide a launch script, an icon in the taskbar or in the desktop, etc. It also permits to change the language at run-time, which sometimes is required. Just my 2 c Giuliano -- Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] [lazarus] Patch for processing WM_COPYDATA in Win32 / BugID 9210
Paul Ishenin ha scritto:
> Marc Weustink wrote:
>
>> Felipe Monteiro de Carvalho wrote:
>>
>>
>>> I think we should apply the WM_COPYDATA patch.
>>>
>>>
>> I don't agree on that.
>>
>> The messages received by the LCL are for VCL compatebility only. That
>> they happen to have the same values as the messages the win32 widgetset
>> uses is just a "coincidence"
>> Like we won't pass all events/signals/messages available for
>> carbon/gtk/qt, we won't pass all for win32.
>> For the simple reason that messages are not cross platform.
>>
>> I agree that we should think of a way that users can simply hook into
>> the main message/event/signal loop it they want to write an app specific
>> for one widgetset.
>> Adding all these messages/evets/signals to the LCL is not the way to do
>> this
>>
> Maybe Win32Widgetset.AllowMessage('WM_COPYDATA') ?
>
>
or
{$ifdef PASS_WM_COPYDATA}
..Patch
{$Endif}
Then those who really need it (because of zillions of source code lines
already written) will compile LCL with -dPASS_WM_COPYDATA.
The others will never notice.
Giuliano
___
Lazarus mailing list
Lazarus@lazarus.freepascal.org
http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Code Explorer problem with libc unit.
Marco van de Voort ha scritto: > On Sat, Feb 16, 2008 at 01:06:46PM +0100, Giuliano Colla wrote: >> Mattias Gaertner ha scritto: >>> On Thu, 14 Feb 2008 21:17:12 +0100 >>> Giuliano Colla <[EMAIL PROTECTED]> wrote: >>> >>>> When the libc unit ($FPCSOURCE/rtl/netwlibc/libc.pp) > > You are using Novell Netware/libc ? I think you mean packages/libc (formerly > packages/extra/libc > >>>> FPC 2.2.0, platform linux, widgetset irrelevant. >>> Fixed in 14151. Please test. >>> >> I had no doubts :-) , but I tested, and now it works as expected! >> >> Thanks a lot, it was a nuisance to comment/uncomment libc! > > Note that leaving that unit uncommented is the best anyway. It is deprecated > (former Kylix compability) and linux/x86 specific. IOW it will bring you > into problems when going to OS X/Solaris/x86_64-Linux/FreeBSD etc. Thanks, I'm aware of that, but we have a range of Linux specific applications, where cross-platform considerations do not apply, and libc services are handy. Giuliano -- Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Code Explorer problem with libc unit.
Mattias Gaertner ha scritto: > On Thu, 14 Feb 2008 21:17:12 +0100 > Giuliano Colla <[EMAIL PROTECTED]> wrote: > >> When the libc unit ($FPCSOURCE/rtl/netwlibc/libc.pp) is in the uses >> clause of a unit, it happens that code explorer gets confused, and >> whenever you click on "Find Declaration", if the target isn't in the >> current unit, it opens the libc unit, around a macNS finderInfo >> record, on the line: >> >> 0 : ( generic : array[0..31] of byte ); >> >> and reports an error: >> "An identifier was expected but generic has been found." >> Commenting out the libc brings back everything to normal. >> >> FPC 2.2.0, platform linux, widgetset irrelevant. > > Fixed in 14151. Please test. > I had made an entry in the bug tracker. Now I've added a note that the issue has been fixed. Maybe someone wants to set it to Resolved. Giuliano -- Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Code Explorer problem with libc unit.
Mattias Gaertner ha scritto: > On Thu, 14 Feb 2008 21:17:12 +0100 > Giuliano Colla <[EMAIL PROTECTED]> wrote: > >> When the libc unit ($FPCSOURCE/rtl/netwlibc/libc.pp) is in the uses >> clause of a unit, it happens that code explorer gets confused, and >> whenever you click on "Find Declaration", if the target isn't in the >> current unit, it opens the libc unit, around a macNS finderInfo >> record, on the line: >> >> 0 : ( generic : array[0..31] of byte ); >> >> and reports an error: >> "An identifier was expected but generic has been found." >> Commenting out the libc brings back everything to normal. >> >> FPC 2.2.0, platform linux, widgetset irrelevant. > > Fixed in 14151. Please test. > I had no doubts :-) , but I tested, and now it works as expected! Thanks a lot, it was a nuisance to comment/uncomment libc! Giuliano -- Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] List has been modified
zeljko ha scritto: > On Thursday 14 February 2008 20:58, Giuliano Colla wrote: >> mramirez ha scritto: >>> Testing new lazarus mail server ;-) >>> >>> cheers (with one shoot of tequila, don't recommend two, while coding) >>> mramirez >> When not coding, we might start some cultural exchange, to compare the >> virtues of tequila with grappa, sljivovica (zeljko, do you listen?), > > yes, but sljivovica is popular in Bosnia and northeast Croatia, not here , I guessed so, but it was more in character with tequila. > here is popular something like ouso (we call it anisetta you call it > grappa ) ;), wrong ;-) , we call anisetta "anisetta" (anise or aniseed flavored, similar to french absinthe and pastis, turkish raki, greek ouso, etc.), and grappa "grappa" (made with grape residue after winemaking, no flavors added). but I prefer red wine :)). me too (when it's good) :) Giuliano -- Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] Code Explorer problem with libc unit.
When the libc unit ($FPCSOURCE/rtl/netwlibc/libc.pp) is in the uses clause of a unit, it happens that code explorer gets confused, and whenever you click on "Find Declaration", if the target isn't in the current unit, it opens the libc unit, around a macNS finderInfo record, on the line: 0 : ( generic : array[0..31] of byte ); and reports an error: "An identifier was expected but generic has been found." Commenting out the libc brings back everything to normal. FPC 2.2.0, platform linux, widgetset irrelevant. Giuliano -- Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] List has been modified
mramirez ha scritto: > Testing new lazarus mail server ;-) > > cheers (with one shoot of tequila, don't recommend two, while coding) > mramirez > When not coding, we might start some cultural exchange, to compare the virtues of tequila with grappa, sljivovica (zeljko, do you listen?), cajuina (osvaldo are you there?) and more contributors, if available :-) Giuliano -- Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] test
Test from Bologna Italy. 59 m above sea level. Sunny but cold. Cheers (with a grappa*) Giuliano *schnaps -- Giuliano Colla Whenever people agree with me, I always feel I must be wrong (O. Wilde) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
