Subject:*
<
Name/Email:*
<
Message Icon:*
<
Select*
<
Message:*
<



Click the Preview to see the content in action.
Options:*
<
Confirmation Code*
<
9 - 2 = ?  
Input the result from the expression
Maximum attempts you can try: 10
*
<
     
getInfo('icons16'); $pathIcon32 = XOOPS_URL . '/' . $xoopsModule->getInfo('icons32'); $pathModuleAdmin = XOOPS_ROOT_PATH . '/' . $xoopsModule->getInfo('dirmoduleadmin');[/code] The here defined $pathIcon16 and $pathIcon32 would be then used throughout the whole module. And in the same way we'll define $pathIcon16 and $pathIcon32 in blocks, i.e. [code]$pathIcon16 = XOOPS_URL . '/' . $xoopsModule->getInfo('icons16'); $pathIcon32 = XOOPS_URL . '/' . $xoopsModule->getInfo('icons32');[/code] Last week I was working on the "Latest News Block" module and I wanted to use the icons defined in the module the way as I was using them so far, however I couldn't use the variable that way - XOOPS doesn't see a link in a block as an "absolute module link", i.e. that that regardless where the block is, on the front page, or in the module view, the link should stay the same because it is owned by the module. Instead, XOOPS takes the links as relative to the root, so therefore I needed to adjust my thinking and change the scheme :-) It's not an issue - with this approach we'll have the same consistent way applied in modules and in blocks, just instead of being "module-centric" as it was thus far, the links will be now "root-centric". Of course, in XOOPS 2.6.0 this will become no issue, because we'll have a direct link to the "media" repository, and XOOPS will find its way there automatically. [/quote]" />

Re: How to write an standard module for xoops (div table, pagination , sort, order)
by bumciach on 2013/10/28 10:48:41

Quote:

irmtfan wrote:

Huum why not use this in xoops_version.php ?
le="color: #000000"><?php $modversion['dirmoduleadmin'] = XOOPS_ROOT_PATH . '/' . 'Frameworks/moduleclasses'; $modversion['icons16'] = XOOPS_URL . '/' . 'Frameworks/moduleclasses/icons/16'; $modversion['icons32'] = XOOPS_URL . '/' . 'Frameworks/moduleclasses/icons/32';



+1


And about my experience with Objects. For me the best topic was
https://xoops.org/modules/newbb/viewtopic.php?viewmode=flat&type=&topic_id=68782&forum=28
Trabis explanation was excellent and helped me a lot in understanding how the xoopsobject works. Thus after that I had more easy in analise rest of classes like:
https://xoops.org/modules/newbb/viewtopic.php?viewmode=flat&type=&topic_id=69368&forum=4
And also analysis of Catzwolf work helped in understanding how to use objects into xoops module - his modules code was very simple (too very simplified so sometimes multiplicate sql query though). But those codes are very old so should consider other examples.
Re: How to write an standard module for xoops (div table, pagination , sort, order)
by chco2 on 2013/10/27 9:09:45

If you could make a simple example (or some simple examples) related to XOOPS, I think I have a really nice guide lying around that explains the concept of classes, so I'll see if I can whip it into something we can use here.
Re: How to write an standard module for xoops (div table, pagination , sort, order)
by redheadedrod on 2013/10/27 8:03:50

I will see what I can do. It is hard to take a subject that takes a series of books to explain and make it into a short tutorial but I can at least setup a primer to allow people to understand why Objects are good to use.

Re: How to write an standard module for xoops (div table, pagination , sort, order)
by Mamba on 2013/10/27 1:12:08

Quote:
Perhaps some examples would help out.

Could you write a short tutorial on this?

That would be very helpful!
Re: How to write an standard module for xoops (div table, pagination , sort, order)
by redheadedrod on 2013/10/25 12:09:32

I understand chco2 I am in programming classes now and it is obvious to me how much easier things are to update with classes than procedural coding.

Perhaps some examples would help out. But yes object orientated is much nicer when it is used but there is a learning curve on them. (One of my instructors told me that a standard procedural programmer can take up to 5 years to get the full understanding of object and how they work.)

I have been using them for about 3-4 years now and I am almost there. But they are much easier to maintain. We only use classes/objects in my Java class.

Who's Online

258 user(s) are online (164 user(s) are browsing Support Forums)


Members: 0


Guests: 258


more...

Donat-O-Meter

Stats
Goal: $15.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $15.00
Make donations with PayPal!

Latest GitHub Commits