Lazarus
Programming => Networking and Web Programming => Topic started by: JimD on March 12, 2019, 06:12:41 pm
-
I'd like to share some simple Indy10 docs & demos with the community:
https://github.com/jasc2v8/LazUnits/tree/master/Indy10
Hopefully this will help others get started with Indy10
Docs
- Indy10 install for Lazarus (non-visual components)
- Convert Indy10 Delphi (visual VCL) to Lazarus (non-visual)
Demos
- HTTP_WebServer_Simple
- HTTPS_WebServer_Simple
Environment
- Win10 Home, Lazarus v1.8.4 with Free Pascal v3.0.4
- Indy10.6.2.5494
- Openssl-1.0.2l-i386-win32
- Can easily be converted to support cross-platform
Thanks to Remy's help from this post: http://forum.lazarus-ide.org/index.php/topic,44554.0.html
-
You don't need to remove the visual components from the .dfm file at all. Just use the .dfm to .lfm converter tool in the Lazarus,. There is a Lazarus Indy package that install corresponding components into the Lazarus IDE. You probably need to get it from Indy SVN trunk snapshot.
-
Yes, understood, thank you.
It's just my personal preference is not to use the Indy10 VCL components, that's all.
-
Indy doesn't have any visual components. And all of the components it does have are not tied to VCL specifically, they can also be used in FMX, and FreePascal, too. In code, or at design-time.
-
Aha! the light comes on... :)
As you can tell, I have zero experience with Delphi, and still learning FPC/Lazarus.
I always thought if you dropped a component on a form it was a visual component.
I now understand the relationship between in code, design-time, run-time, and visual.
The best way to learn is jump in and make mistakes.
Thank you for keeping me on track!
-
I always thought if you dropped a component on a form it was a visual component.
Nope. Visual components are actually visual in your app's UI at runtime. Non-visual components are visible only inside the Form Designer at design-time, not at runtime.
-
Ah! Yes, I meant non-visual components! :-[