Re: [fpc-pascal] Re: [Lazarus] Should TObject or TComponent have a Comment property?
On Tue, 16 Jul 2013 22:56:33 +0100 "vfclists ." wrote: >[...] > I have 2 main concerns here, a comment for the component itself which is > not particularly important and a comment for the component when I add it to > a form or data module. When I create a method I can add a comment to the > method. If I create a component in code, I can label that section of code, > but if I drag and drop a component from the palette onto the form what > option do I have? Descriptive variable and component names have a habit of > getting too long. You can comment the variable. For example: Edit1: TEdit; // Now, that's a great Name > It is hardly for the end users sake unless the enduser is > a programmer. I just need something to help when working in the IDE, eg > hovering over a component and seeing the comment in addition to what is > current displayed. Do you mean hovering over the component in the designer? At the moment the hint shows only the caption and some common values. It could be extended to show the help for the variable. Feel free to create a feature request. Mattias ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Sockets?
You can use the sockets library for that. Examples of sockets programming are available in the internet, mainly in C, but you can see how it works with that. On Wednesday 17 July 2013 17:09:58 you wrote: > I have prayed to Google many, many times, but I still cannot find an > answer (or, at least, an answer that compiles). I want to set up a > dirt-simple network client/server pair. So simple that all I do is hurl > bytes into a bucket, and they get transferred to the other side. Does > anyone know of something like that? > ___ > fpc-pascal maillist - fpc-pascal@lists.freepascal.org > http://lists.freepascal.org/mailman/listinfo/fpc-pascal ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Sockets?
On 13-07-17 11:14 AM, Michael Schnell wrote: Synapse makes handling of sockets rather easy. Thanks. I'll check that one out. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Sockets?
Good things to read: http://wiki.freepascal.org/Networking http://wiki.freepascal.org/lNet http://wiki.freepascal.org/Synapse none of those contain an example like you ask, however. But it should be easy to implement with either synapse or lnet. synapse might even be easier. -- Felipe Monteiro de Carvalho ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Sockets?
Synapse makes handling of sockets rather easy. -Michael ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Sockets?
On 07/17/2013 10:16 AM, Timothy Groves wrote: On 13-07-17 11:14 AM, Michael Schnell wrote: Synapse makes handling of sockets rather easy. Thanks. I'll check that one out. Here is an easy way to try Free Pascal, fpGUI, and Synapse: http://www.ctrlterm.com/ ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Sockets?
I have prayed to Google many, many times, but I still cannot find an answer (or, at least, an answer that compiles). I want to set up a dirt-simple network client/server pair. So simple that all I do is hurl bytes into a bucket, and they get transferred to the other side. Does anyone know of something like that? ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Sockets?
On 13-07-17 11:16 AM, Rainer Stratmann wrote: You can use the sockets library for that. Examples of sockets programming are available in the internet, mainly in C, but you can see how it works with that. I found one that didn't compile. I managed to clean it up, somewhat poorly, enough for it to run, but I haven't been able to understand it yet. Maybe with a bit more time... ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: Sockets?
pascalgeek.blogspot.com/2012/06/encryption-decryption-and-asynchronous.html -- View this message in context: http://free-pascal-general.1045716.n5.nabble.com/Sockets-tp5715840p5715847.html Sent from the Free Pascal - General mailing list archive at Nabble.com. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Re: [Lazarus] Should TObject or TComponent have a Comment property?
On 17/07/13 00:56, vfclists . wrote: I completely disagree. It is the code that is the primary expression of intent not the comments. This is mainly accomplished through sensible identifier naming. I perfectly agree, a well formed name is worth a thousand words, in this context. Comments exist to compensate for a developer's inability to express intent through the code and IMHO should be reserved for this sole purpose. In most cases you should be able to look at a function signature and know exactly what that function's intent is. Likewise you should be able to tell the intent of a class by its name and the names of its public/published members. This is, at least, what I strive for in my own code. Bob Martin's "Clean Code" dedicates the entire 4th chapter to the discussion of comments and make some very compelling arguments for limiting their use. That's true, in principle; thou' you shall look at the comments also like: you cannot express the meaning and whole role of a function by its name (unless you want to couple wikipedia, of course), especially where you made some tricks that _today_ they look obvious because you're in the thing, but _tomorrow_ they might not. I still endlessly thank myself for having put some of these comments somewhere in my code, some of 15 years ago... they helped me make the migration from DOS to Linux a little less hurting ;-) Of course, we're talking about good and wise use of comments, which is, IMHO, still an art. Just my 2c on this, Al. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Re: [Lazarus] Should TObject or TComponent have a Comment property?
On 17/07/13 00:56, vfclists . wrote: It is hardly for the end users sake unless the enduser is a programmer. we're talking about programming languages here, so that... whoever else shall an end user of a development tool/library be?!?!?!? X_X ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Re: [Lazarus] Should TObject or TComponent have a Comment property?
On Wed, Jul 17, 2013 at 3:53 AM, Mattias Gaertner wrote: > Do you mean hovering over the component in the designer? > At the moment the hint shows only the caption and some common values. > It could be extended to show the help for the variable. Feel free to > create a feature request. > > I think he's referring to hovering over the component icon on the component pallet. Right now the tool tip shows the class name and the unit it is defined in. I think he wants it extended to include a description of the component's purpose. So hovering over the TButton icon would display: TButton (StdCtrls) A push button control. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
