A simple example using just the Generic NetDun class, and some hand-code to
prime the various properties.
DIP Server
DIP stands for Dynamic IP Addressing. The NetAuto protocol is designed to automatically find and
connect to other (NetAuto) programs on the LAN which are running. This discovery is done via the
UDP broadcast system. If your network is a WAN than an alternate mechanism is needed
for the machines to find each other.
One approach is the DIP system - if all the programs are aware of a DIP server
address, then they can find each other through that address.
This example is the server side of the DIP protocol. This app requires
WinEvent.
RSS Client Jump Start
A simple program that uses the WebClient class to fetch an RSS file from
ClarionMag. The received RSS page is displayed in a 'raw' format as it is
received.
RSS Client with xFiles
Similar to the RSS jump Start, this program parses the incoming RSS information
(using xFiles) and displays it in a list box.
SOAP
The SOAP folder contains two example apps, one which uses
xFiles and one which uses normal Clarion commands to do the XML part. The
example makes use of the
Unit Converter at WebServiceX.net.
Web Client Jump Start
A really simple program that fetches a single page from a web site.
Web Client Polling Agent
A small window which loops through a list of web pages, fetching them one at a
time. You can adjust the pages looked for, as well as the time between checks.
Web Client Weather requires xFiles
The Weather app is designed to interact with the
Global Weather service at WebServiceX.net. It uses
xFiles to convert from Clarion structures to XML and back again. The example
was used as the basis for
Clarion Live webinar #48 which discussed the Webclient class at some length.
The weather application also contains a simple Drive procedure that let's you
manually fetch web pages, inspect the results, and so on.
Web Strain
Another simple application that fetches two pages from a web server as fast as
it can, and repeats in a loop.
1. Basic Browse and Form
This is the simplest example. It provides a server that
displays the contents of a single table, and allows you to Add, Change and
Delete entries.
This example has popup style forms.
2. Basic with Menu
A simple example with a Double-Drop style menu, and a couple of related browses
and forms. The browses in this example are File-Loaded, not Page loaded.
3. Basic with Login
A simple application with a browse and form, but which also has simple Login and
Logout functionality. This application uses the Chrome menu style. The default
login is demo, and the default password is demo. This example has page style
forms.
4. Frame with Menu
A small application that uses HTML Frames to layout the screen. The login and
password is demo / demo as with the other examples.
6. Basic SSL
Demonstrates a server running on an SSL connection. Note the requirement for the
SSL DLL's to be copied to the application folder. See
Building Secure (SSL) Web Sites
for more information on building SSL into your web applications.
7. Login before Frame
8. Mixed SSL
9. Always SSL
10. Basic Graph Requires Insight Graphing
11. Send email from a web browser
13. PDF Report requires C6EE
14. PDF Report requires PDF Tools
15. PDF Report requires wPDF control
16. CPCS Report
19. Select item
20. Multi DLL
21. Browse in Form
22. Relation update
23. Browse to another Form
24. Form to Form
25. Parent Child Browse
26. File Upload
27. Frame with Taskpanel
28. Buttons
29. Basic XML
30. Hyperlinks
31. Accounts
32. Error Page
33. Drop Filter
34. Calculator
35. Time Fields
36. Html Editor
37. Legacy basic
38. Legacy Report Requires C6EE
39. Messagebox
40. File Download
41. Legacy Graph requires Insight
42. Soap Server
43. Access Levels
45. wScript ActiveX
46. Timers
47. Pages
48. Tagging
49. Locators
50. Multirow
51. Secwin
53. Validation
54. Excel requires Office Inside
55. Services requires SelfService
56. Menus
57. Tabs
58. PHP
59. Multisite requires C6
61. Captcha
80. External
The External example is divided into 2 parts. The first part (web80) is a normal web server, which includes a form containing an EXTERNAL
form field. The second app is called PUTT.APP and is an example of an AGENT program. This program runs on the local machine and accesses
the local hardware.
Web80
Note: WebServer, Scripts tab, option to
include ExternalServer scripts on.
Note: WebServer, Security tab,
X-Frame-Options is blank.
Web80 is the "normal" web server
example in this application. The only interesting thing about this
example is the use of a field of type EXTERNAL on the form. Using this
external field data is fetched from the local agent program, and placed
in the barcode field on the form.
Buttons on the form (also of
type External) allow you to control where the barcode is directed to,
and whether it is reading data from the agent or not.
Putt
Note: WebHandler, Embed Code, CreateHeader
method;
p_HeaderDetails.AccessControlAllowOrigin = self.RequestOrigin
The PUTT example makes use of WINEVENT to access a COM Port on the machine. In this example the comm port is polled, and any
incoming data is moved into the glo:prox global variable. This value can then be fetched by a page using the GetData procedure.
This example app requires WinEvent and XFiles to compile, but it
should be straight-forward to replace these with other tools or code if
you wish. xFiles is used to save, and restore the global settings.
WinEvent is used to read incoming values from the Comm port.
A
typical use case for this app would be a Barcode reader, attached to a
USB or COM port of the client computer. An incoming barcode is stored in
glo:prox, and held there until it is fetched by an External field in
some other web page. In this example the External field is on a form in
the web80 app.
Legacy
LegEmail.App
A simple Send-Email example built using the Clarion (Legacy) template chain.
NetLeg.App
A simple version of the NetDemo app, based on the Clarion (Legacy) template
chain.
Linkpoint requires xFiles
LinkPoint is an interface provided by some banks so that credit cards can be
processed online. This example uses NetTalk and xFiles together to talk to
LinkPoint.
NetOptions
An example that shows many of the common uses for the
NetOptions function.
Proxy
The Debugging Proxy Tool is a useful tool for programmers who are using NetSimple objects to communicate with
other network enabled applications.
This tool helps you monitor and see the actual communication between your application and other network applications.
For example if you are talking directly to a Web server, Web client, Email server and so on, you can use the Proxy
Example to view the actual commands sent and received from your application.
Specific documentation for this example can be found
here.
