J3.x talk:Creating a simple module/Developing a Basic Module - Revision history

Sovainfo: /* Last line of mod_helloworld.php */

2014-11-12T01:28:27Z

Last line of mod_helloworld.php

← Older revision		Revision as of 01:28, 12 November 2014
Line 1:		Line 1:
	== Last line of mod_helloworld.php ==		== Last line of mod_helloworld.php ==
	As a newbie within module developing I'd say, even if it's maybe nothing - the last paragraph in this section states "The one line that we haven’t explained so far is the first line.". But the last line haven't been explained either. Not to go into any deep explanations, just a sentence or two - so you know what it'll do to the module if you'd leave it out. [[User:Alekks\|Alekks]] ([[User talk:Alekks\|talk]]) 14:33, 11 November 2014 (CST)		As a newbie within module developing I'd say, even if it's maybe nothing - the last paragraph in this section states "The one line that we haven’t explained so far is the first line.". But the last line haven't been explained either. Not to go into any deep explanations, just a sentence or two - so you know what it'll do to the module if you'd leave it out. [[User:Alekks\|Alekks]] ([[User talk:Alekks\|talk]]) 14:33, 11 November 2014 (CST)
			:Absolutely agree. section 2 is very hard to read. The line you are referring to implements the 3rd bullit point. Suggest to change the bullit points into a,b,c and mention add a, add b, add c so the reader knows whereto the comments apply. add c would at least show the code and the text at the bullit point. What do you think? [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 19:28, 11 November 2014 (CST)

	== $params ==		== $params ==

Alekks at 20:33, 11 November 2014

2014-11-11T20:33:18Z

← Older revision		Revision as of 20:33, 11 November 2014
Line 1:		Line 1:
			== Last line of mod_helloworld.php ==
			As a newbie within module developing I'd say, even if it's maybe nothing - the last paragraph in this section states "The one line that we haven’t explained so far is the first line.". But the last line haven't been explained either. Not to go into any deep explanations, just a sentence or two - so you know what it'll do to the module if you'd leave it out. [[User:Alekks\|Alekks]] ([[User talk:Alekks\|talk]]) 14:33, 11 November 2014 (CST)

	== $params ==		== $params ==

Sovainfo: /* $params */

2014-05-08T00:34:45Z

$params

← Older revision		Revision as of 00:34, 8 May 2014
Line 8:		Line 8:

	:Because it's a "simple" module tutorial. When I first developed modules (which scarily wasn't that long ago) I didn't care where all this stuff came from - it was just amazing that it existed. Again for simple module development I'm not sure that matters - with the $app thing for example I'd rather get people redefining it. Firstly as I said I don't think people for a basic "here's how to create a module" tutorial we need to involve JModuleHelper and also because I really think you should define $app yourself for your things so it's as standalone as possible! The only thing arguably you should need is the $module object (as that contains params + module title instance) or if you only need the params then just $params.		:Because it's a "simple" module tutorial. When I first developed modules (which scarily wasn't that long ago) I didn't care where all this stuff came from - it was just amazing that it existed. Again for simple module development I'm not sure that matters - with the $app thing for example I'd rather get people redefining it. Firstly as I said I don't think people for a basic "here's how to create a module" tutorial we need to involve JModuleHelper and also because I really think you should define $app yourself for your things so it's as standalone as possible! The only thing arguably you should need is the $module object (as that contains params + module title instance) or if you only need the params then just $params.

			::Never mind. Hope that the J4 redesign will get rid of modules anyway![[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 19:34, 7 May 2014 (CDT)

	== Don't like "for page rendering" ==		== Don't like "for page rendering" ==

Wilsonge: /* Don't like "for page rendering" */

2014-05-07T12:11:34Z

Don't like "for page rendering"

← Older revision		Revision as of 12:11, 7 May 2014
Line 12:		Line 12:

	Don't like "for page rendering", would say: while rendering the page. It completely puts me off, thinking the module is the procedure to render a page, which is handled by JDocumentHtml. [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 04:05, 7 May 2014 (CDT)		Don't like "for page rendering", would say: while rendering the page. It completely puts me off, thinking the module is the procedure to render a page, which is handled by JDocumentHtml. [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 04:05, 7 May 2014 (CDT)

			:In retrospect I don't like it either :P changed

Wilsonge: /* $params */

2014-05-07T12:11:07Z

$params

← Older revision		Revision as of 12:11, 7 May 2014
Line 7:		Line 7:
	::Why would you want to avoid mentioning JModuleHelper::renderModule. The first thing that comes to mind is how should I know $params is available? Where to look for the other variables availabe. Or state them, would be nice to know $app is available!. [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 03:49, 7 May 2014 (CDT)		::Why would you want to avoid mentioning JModuleHelper::renderModule. The first thing that comes to mind is how should I know $params is available? Where to look for the other variables availabe. Or state them, would be nice to know $app is available!. [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 03:49, 7 May 2014 (CDT)

	:Because it's a "simple" module tutorial. When I first developed modules (which scarily wasn't that long ago) I didn't care where all this stuff came from - it was just amazing that it existed. Again for simple module development I'm not sure that matters - with the ~~<source lang="php">~~$app~~</source>~~ thing for example I'd rather get people redefining it. Firstly as I said I don't think people for a basic "here's how to create a module" tutorial we need to involve JModuleHelper and also because I really think you should define ~~<source lang="php">~~$app~~</source>~~ yourself! ~~If next week Joomla decides $app isn't needed in that function then you don't want to find yourself dependent on that.~~ The only thing arguably you ~~could want~~ is the $module object (as that contains params + module title instance).		:Because it's a "simple" module tutorial. When I first developed modules (which scarily wasn't that long ago) I didn't care where all this stuff came from - it was just amazing that it existed. Again for simple module development I'm not sure that matters - with the $app thing for example I'd rather get people redefining it. Firstly as I said I don't think people for a basic "here's how to create a module" tutorial we need to involve JModuleHelper and also because I really think you should define $app yourself for your things so it's as standalone as possible! The only thing arguably you should need is the $module object (as that contains params + module title instance) or if you only need the params then just $params.

	== Don't like "for page rendering" ==		== Don't like "for page rendering" ==

	Don't like "for page rendering", would say: while rendering the page. It completely puts me off, thinking the module is the procedure to render a page, which is handled by JDocumentHtml. [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 04:05, 7 May 2014 (CDT)		Don't like "for page rendering", would say: while rendering the page. It completely puts me off, thinking the module is the procedure to render a page, which is handled by JDocumentHtml. [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 04:05, 7 May 2014 (CDT)

Wilsonge: /* $params */

2014-05-07T12:10:11Z

$params

← Older revision		Revision as of 12:10, 7 May 2014
Line 6:		Line 6:

	::Why would you want to avoid mentioning JModuleHelper::renderModule. The first thing that comes to mind is how should I know $params is available? Where to look for the other variables availabe. Or state them, would be nice to know $app is available!. [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 03:49, 7 May 2014 (CDT)		::Why would you want to avoid mentioning JModuleHelper::renderModule. The first thing that comes to mind is how should I know $params is available? Where to look for the other variables availabe. Or state them, would be nice to know $app is available!. [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 03:49, 7 May 2014 (CDT)

			:Because it's a "simple" module tutorial. When I first developed modules (which scarily wasn't that long ago) I didn't care where all this stuff came from - it was just amazing that it existed. Again for simple module development I'm not sure that matters - with the <source lang="php">$app</source> thing for example I'd rather get people redefining it. Firstly as I said I don't think people for a basic "here's how to create a module" tutorial we need to involve JModuleHelper and also because I really think you should define <source lang="php">$app</source> yourself! If next week Joomla decides $app isn't needed in that function then you don't want to find yourself dependent on that. The only thing arguably you could want is the $module object (as that contains params + module title instance).

	== Don't like "for page rendering" ==		== Don't like "for page rendering" ==

	Don't like "for page rendering", would say: while rendering the page. It completely puts me off, thinking the module is the procedure to render a page, which is handled by JDocumentHtml. [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 04:05, 7 May 2014 (CDT)		Don't like "for page rendering", would say: while rendering the page. It completely puts me off, thinking the module is the procedure to render a page, which is handled by JDocumentHtml. [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 04:05, 7 May 2014 (CDT)

Sovainfo: /* Don't like "for page rendering" */ new section

2014-05-07T09:05:45Z

Don't like "for page rendering": new section

← Older revision		Revision as of 09:05, 7 May 2014
Line 6:		Line 6:

	::Why would you want to avoid mentioning JModuleHelper::renderModule. The first thing that comes to mind is how should I know $params is available? Where to look for the other variables availabe. Or state them, would be nice to know $app is available!. [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 03:49, 7 May 2014 (CDT)		::Why would you want to avoid mentioning JModuleHelper::renderModule. The first thing that comes to mind is how should I know $params is available? Where to look for the other variables availabe. Or state them, would be nice to know $app is available!. [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 03:49, 7 May 2014 (CDT)

			== Don't like "for page rendering" ==

			Don't like "for page rendering", would say: while rendering the page. It completely puts me off, thinking the module is the procedure to render a page, which is handled by JDocumentHtml. [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 04:05, 7 May 2014 (CDT)

Sovainfo: /* $params */

2014-05-07T08:49:38Z

$params

← Older revision		Revision as of 08:49, 7 May 2014
Line 4:		Line 4:

	:So there probably should be a sentence saying $params is generated by us automatically. As this is a "simple" module tutorial - I really want to avoid going into the fact this is automatically generated by the JModuleHelper. I'd rather just say the thing with the params is created magically for you to manipulate. --[[User:Wilsonge\|Wilsonge]] ([[User talk:Wilsonge\|talk]]) 18:43, 6 May 2014 (CDT)		:So there probably should be a sentence saying $params is generated by us automatically. As this is a "simple" module tutorial - I really want to avoid going into the fact this is automatically generated by the JModuleHelper. I'd rather just say the thing with the params is created magically for you to manipulate. --[[User:Wilsonge\|Wilsonge]] ([[User talk:Wilsonge\|talk]]) 18:43, 6 May 2014 (CDT)

			::Why would you want to avoid mentioning JModuleHelper::renderModule. The first thing that comes to mind is how should I know $params is available? Where to look for the other variables availabe. Or state them, would be nice to know $app is available!. [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 03:49, 7 May 2014 (CDT)

Wilsonge: /* $params */ Reply

2014-05-06T23:43:57Z

$params: Reply

← Older revision		Revision as of 23:43, 6 May 2014
Line 2:		Line 2:

	This document explains calling a helper class passing $params for future use. The problem is, it doesn't mention where that $params is coming from. And what other data is available? [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 08:41, 6 May 2014 (CDT)		This document explains calling a helper class passing $params for future use. The problem is, it doesn't mention where that $params is coming from. And what other data is available? [[User:Sovainfo\|Sovainfo]] ([[User talk:Sovainfo\|talk]]) 08:41, 6 May 2014 (CDT)

			:So there probably should be a sentence saying $params is generated by us automatically. As this is a "simple" module tutorial - I really want to avoid going into the fact this is automatically generated by the JModuleHelper. I'd rather just say the thing with the params is created magically for you to manipulate. --[[User:Wilsonge\|Wilsonge]] ([[User talk:Wilsonge\|talk]]) 18:43, 6 May 2014 (CDT)

Sovainfo: /* $params */ new section

2014-05-06T13:41:03Z

$params: new section

New page

== $params ==

This document explains calling a helper class passing $params for future use. The problem is, it doesn't mention where that $params is coming from. And what other data is available? [[User:Sovainfo|Sovainfo]] ([[User talk:Sovainfo|talk]]) 08:41, 6 May 2014 (CDT)