By apache friends I assume you mean something like XAMMP which is a a simple (LOL) Apache, MySQL and PHP stack. Essentially a full web server you can play with or use to host a web service.
At the courselab end:
Publish for CD
Upload to a folder
At the web end:
Post login redirect to or include a page with hyperlinks to the start file(s) of the module(s) into the main PHP template file.
Open the module in a new window.
-----
The samples page here does exactly that.
Your question is more about how you use PHP and hyperlinks at the server end rather than courselab.
The pages to drive this will be PHP but the viewer will see only html, that is the content is usually dynamically generated at the server.
You might see html but the pages are made up of PHP instructions to include a certain other file(s) in the code the end user sees. Look at the source code for this page, it's all html BUT at the server end it isn't, it will all be PHP.
You need to go do some reading on using PHP with dynamic pages.
By apache friends I assume you mean something like XAMMP which is a a simple (LOL) Apache, MySQL and PHP stack. Essentially a full web server you can play with or use to host a web service.
At the courselab end:
Publish for CD
Upload to a folder
At the web end:
Post login redirect to or include a page with hyperlinks to the start file(s) of the module(s) into the main PHP template file.
Open the module in a new window.
-----
The samples page here does exactly that.
Your question is more about how you use PHP and hyperlinks at the server end rather than courselab.
The pages to drive this will be PHP but the viewer will see only html, that is the content is usually dynamically generated at the server.
You might see html but the pages are made up of PHP instructions to include a certain other file(s) in the code the end user sees. Look at the source code for this page, it's all html BUT at the server end it isn't, it will all be PHP.
You need to go do some reading on using PHP with dynamic pages.
