envolution-devel

[Envolution-devel] Standards

[<Luc...@cs...>]

SGFsbG8gdG8gZXZlcnlib2R5LCBJJ20gTHVjYSBhbmQgSSdtIHdvcmtpbmcgdG8gYWRhcHQgZW52
b2x1dGlvbiBzbyB0byBtYWtlDQppdCBmdW5jdGlvbmluZyBhbHNvIG9uIE9yYWNsZSwgdG9nZXRo
ZXIgd2l0aCBhIGNvbGxlYWd1ZSBvZiBtaW5lLg0KV2UgYXJlIHJpZ2h0IG5vdyByZWxlYXNpbmcg
ZmlsZXMgd2l0aCB0aGUgY29ycmVjdGlvbnMuDQpUaGluayB0aGF0IHdlJ2xsIG5lZWQgYSBjb3Vw
bGUgb2YgZGF5cyB0byBoYXZlIHNvbWV0aGluZyB1c2FibGUgb24gT3JhY2xlDQphbmQgd2UnbGwg
Y29uY2x1ZGUgdGhlIGZpcnN0IHBoYXNlIHdpdGggdGhlIHVwbG9hZCBvZiB0aGUgU1FMIHNjcmlw
dHMgb24NCnRoZSByaWdodCBmb2xkZXIuDQpXZSdkIGxpa2UgdG8ga25vdyBpZiB0aGVyZSBhcmUg
c29tZSBzdGFuZGFyZHMgdG8gd3JpdGUgdGhlIGNvZGUgb3IgdG8gbWVrZQ0KdGhlIGNvbW1lbnRz
LCB3ZSBzYXcgdGhhdCB0aGVyZSBpcyBhIHZlcnkgbmljZSBkZWJ1ZyB3aW5kb3csIGJ1dCBpdCcg
bm90IHNvDQptdWNoIHVzZWQuICBBcmUgdGhlcmUgYW55IHBvbGljZXMgYWJvdXQgaXQ/DQpXZSBh
cmUgbWFudGFpbmluZyB0aGUgb2xkIGNvZGUgd2hlbiB3ZSBtYWtlIGNoYW5nZXMgc28gdG8gYWxs
b3cgZXZlcnlib2R5DQp0byB1bmRlcnN0YW5kIGltbWVkaWF0ZWx5IHdoZXJlIGFuZCB3aHkgd2Ug
bWFkZSBzdWNoIG1vZGlmaWVycy4NCldlIGFyZSBhbHNvIHByZXBhcmluZyBzb21lIGd1aWRlbGlu
ZXMgdG8gd3JpdGUgcG9ydGFibGUgY29kZSBmb3IgbXlzcWwgYW5kDQpPcmFjbGUgKG9ubHkgaW4g
aXRhbGlhbiBmb3IgdGhlIG1vbWVudCkgc28gdGhhdCBldmVyeSBuZXcgbW9kdWxlIHdlIHRvdWNo
DQpvciBkZWJ1ZyBjb3VsZCBiZSB3cml0dGVuIGZvbGxvd2luZyB0aGVzZSBndWlkZWxpbmVzLg0K
U3BlYWtpbmcgYWJvdXQgb3RoZXIgbW9kdWxlcyBsaWtlIGNvbnRlbnQgZXhwcmVzcyBvciBwb3N0
IGNhbGVuZGFyIGV0YyBhcmUNCnRoZXJlIGFueSBvZmZpY2lhbCBvciBmb3JtYWwgY29udGFjdHMg
d2l0aCB0aGUgb3duZXJzIG9mIHRoZSBwcm9qZWN0cyB0bw0Kc3VibWl0IHRoZSBjb2RlIGZyb20g
dGhlIGVudm8gY29tbXVuaXR5Pw0KV2FudCB0byBzYXkgdGhhdCB3ZSB0aGluayB0aGF0IHRoaXMg
aXMgYSByZWFsbHkgZ29vZCBwcm9qZWN0IGFuZCBhcmUgcHJvdWQNCnRvIGJlIGFibGUgdG8gY29u
dHJpYnV0ZS4NCkJ5DQpMdWNhDQo=

[Envolution-devel] Standards

[<Luc...@cs...>]

DQpXZSBhcmUgc3R1ZHlpbmcgaG93IHRvIGRldmVsb3AgYSBuZXcgbW9kdWxlIGZvciBvdXIgcHJv
amVjdCwgYW5kIGFyZSB0cnlpbmcNCnRvIHVuZGVyc3RhbmQgaG93IHRvIGNvZGUgaXQgY29ycmVj
dGx5Lg0KTG9va2luZyB0byB2YXJpb3VzIG1vZHVsZXMgZm9yIGluc3BpcmF0aW9uIGNhcnJpZWQg
YSBmZXcgcXVlc3Rpb25zIHNpbmNlDQptYW55IGRldmVsb3BlcnMgdXNlZCBkaWZmZXJlbnQgbWV0
aG9kcyBhbmQgQVBJIGNhbGxzIGZvciBzYW1lIHRoaW5ncy4NCldoZXRoZXIgdGhpcyBkZXBlbmRz
IG9uIHRoZSBldm9sdXRpb24gb2YgdGhlIGNvZGUgKGZyb20gcGhwLW51a2UgdG8gZW52bykNCm9y
IHRoZSBza2lsbCBvciBzdHlsZSBvZiB0aGUgcHJvZ3JhbW1lciwgd2UgaGF2ZSBkaWZmaWN1bHR5
IGluIGRldGVybWluaW5nDQp0aGUgY29ycmVjdCB3YXkgb2YgZG9pbmcgYW5kIHdoeS4NCg0KVGhl
c2UgYXJlIHRoZSBmaXJzdCBkb3VidHMgd2UgaGF2ZToNCjEpIFdoZW4gSSB3YW50IHNldCB0aGUg
JE1PRFVMRV9VUkwgY29uc3RhbnQsIGlzIG11Y2ggY29udmVuaWVudCB1c2UgdGhlIEFQSQ0KZnVu
Y3Rpb24gb3IgdXNlIHN0YXRpYyBjb2RlIGFzIHNlZW4gaW4gdmFyaW91cyBtb2R1bGVzPw0KMikg
SW4gdGhlIHBlcm1pc3Npb24ncyBpbnN0YW5jZSwgd2hhdCBpcyB0aGUgZGlmZmVyZW5jZSBiZXR3
ZWVuIDo6IGFuZCAuKiA/DQpBcmUgdGhleSBzeW5vbnltcz8gV2hlcmUgY2FuIHdlIGZpbmQgc29t
ZSBtb2RlIG9uIGRldmVsb3BpbmcgdGhlIHBlcm1pc3Npb24NCnBhcnQgb2YgYSBtb2R1bGUgYW5k
IHdoYXQgaXMgdGhlIG1lYW5pbmcgb2YgdGhlIGZpcnN0IHBhcmFtZXRlciBwYXNzZWQgdG8NCnRo
ZSBmdW5jdGlvbiBwblNlY0F1dGhBY3Rpb24/ICAgSXQncyBhbHdheXMgc2V0IGF0IDAgaXMgaXQg
dXNlZnVsIGluIHRoZQ0KbXVsdGlzaXRlIG9wdGlvbj8NCjMpIEluIGEgbW9kdWxlcywgaWYgd2Ug
Y2hvb3NlIHRvIHNlcGFyYXRlIHRoZSBidXNpbmVzcyBsb2dpYyBpbiBkaWZmZXJlbnQNCmZpbGVz
IChpbmRleC5waHAgKyBpbmRleGZ1bmN0aW9ucy5waHAgZm9yIGV4YW1wbGUpLCBpcyBpdCBhZHZp
c2FibGUgdG8gcHV0DQp0aGUgc2VjdXJpdHkgY2hlY2sgKGlmIChwblNlY0F1dGhBY3Rpb24uLi4p
KSBpbiBhbGwgdGhlIGZpbGVzIG9yIG9ubHkgaW4NCnRoZSBpbmRleC5waHA/DQo2KSBXaGVuIEkg
d2FudCBsb2FkIHRoZSBtb2R1bGUncyBuYW1lIGluIHRoZSBjb25zdGFudCAkTU9EVUxFX05BTUUg
aXMNCmJldHRlciB1c2U6ICRnbG9iYWxzWyduYW1lJ10sDQogICAkZ2xvYmFsc1snTW9kTmFtZSdd
IG9yIGJhc2VuYW1lKGRpcm5hbWUoX19GSUxFX18pKSA/DQoNCg0KVGhlcmUgYXJlIG1hbnkgb3Ro
ZXJzIHRoaW5ncyBsaWtlIHRoZXNlLiBDYW4gd2Ugc3BlYWsgYWJvdXQgaXQ/DQoNCkx1Y2EgYW5k
IE1hcmNvDQo=

Re: [Envolution-devel] Standards

[Arden W. <ar...@li...>]

On Tue, 2003-07-22 at 07:50, Luc...@cs... wrote:
> 
> We are studying how to develop a new module for our project, and are trying
> to understand how to code it correctly.
> Looking to various modules for inspiration carried a few questions since
> many developers used different methods and API calls for same things.
> Whether this depends on the evolution of the code (from php-nuke to envo)
> or the skill or style of the programmer, we have difficulty in determining
> the correct way of doing and why.
> 
> These are the first doubts we have:
> 1) When I want set the $MODULE_URL constant, is much convenient use the API
> function or use static code as seen in various modules?

The daily_archive module is done this way with pnGetModURL.  This
function is slow sometimes in updating from one site to the next.  See
www.sudbury.linuxguru.ca and test how the function behaves by then
visiting www.sherbrooke.linuxguru.ca and watching how the function
reports the URL.  It does not adjust to a new site name.  I have had to
alter some of the code to directly place people at the index.

> 2) In the permission's instance, what is the difference between :: and .* ?
> Are they synonyms? Where can we find some mode on developing the permission
> part of a module and what is the meaning of the first parameter passed to
> the function pnSecAuthAction?   It's always set at 0 is it useful in the
> multisite option?
> 3) In a modules, if we choose to separate the business logic in different
> files (index.php + indexfunctions.php for example), is it advisable to put
> the security check (if (pnSecAuthAction...)) in all the files or only in
> the index.php?
> 6) When I want load the module's name in the constant $MODULE_NAME is
> better use: $globals['name'],
>    $globals['ModName'] or basename(dirname(__FILE__)) ?
> 
> 
> There are many others things like these. Can we speak about it?
> 
> Luca and Marco

Re: [Envolution-devel] Standards

[romeo b. .:Envolution.info:. <ci...@en...>]

Please have a look also at the discussion about the recall to pontuke..=20
maybe it would be useful to wait until the situation will be clear, in=20
order to take a good decision in stadards...

Romeo Bandinelli


At 15.50 22/07/03 +0200, you wrote:

>We are studying how to develop a new module for our project, and are trying
>to understand how to code it correctly.
>Looking to various modules for inspiration carried a few questions since
>many developers used different methods and API calls for same things.
>Whether this depends on the evolution of the code (from php-nuke to envo)
>or the skill or style of the programmer, we have difficulty in determining
>the correct way of doing and why.
>
>These are the first doubts we have:
>1) When I want set the $MODULE_URL constant, is much convenient use the API
>function or use static code as seen in various modules?
>2) In the permission's instance, what is the difference between :: and .* ?
>Are they synonyms? Where can we find some mode on developing the permission
>part of a module and what is the meaning of the first parameter passed to
>the function pnSecAuthAction?   It's always set at 0 is it useful in the
>multisite option?
>3) In a modules, if we choose to separate the business logic in different
>files (index.php + indexfunctions.php for example), is it advisable to put
>the security check (if (pnSecAuthAction...)) in all the files or only in
>the index.php?
>6) When I want load the module's name in the constant $MODULE_NAME is
>better use: $globals['name'],
>    $globals['ModName'] or basename(dirname(__FILE__)) ?
>
>
>There are many others things like these. Can we speak about it?
>
>Luca and Marco
>=86+w=ADzf=A2=AD+,=A6=89=EC=A2=B7=9Do%LY=AA=DEZ+aT=CC=AD=EC=A8=B9=C6=A7=AE=
=E9=E6=BA[b=A6W=A8=A5=EA=DA=B6)=E0=B3+-zk(=9D=AB"=9E=20
>^=99=A7!=8Aw=AD!1=CEQ4D=E3=93=20
>=D1=8C=8B=E2=9E=EC=7FZ)=DD=A3?6=8B=DE=AD[=E2=AE=DB=9A=ADf=9C=86)=DE=B1=ABm=
=85=EB=99=EBb=99=E1ky=EBk=89=A9\=AD'$=85=EA=DE=86=DBi=FF=FC0=C2=F9=B0j=B7=9C=
=A2o=F0=97=FA}=EA=FF=DF=8E=7F=D0I=EF=A2[=AD=8A=89=DDz=F7=A5=99=A8=A5=8Ax%=8A=
=CBD=9E=FA%=BA=D8=A8=9D=D7=AFzYb=B2=DB,=A2=EA=DCy=FA+=81=E9=DE=B6m=A6=CF=FF=
=AD+-=B2=CA.=AD=C7=9F=A2=B8=9D=EB=7F=AD+-=B3=F9b=B2=D8=A7~=8F=DE=9E=FA%=BA=
=D8=A8=9D=D7=AFz=20
>

Re: [Envolution-devel] Standards

[Scott K. <sc...@ki...>]

On Tue, 2003-07-22 at 11:08, romeo bandinelli .:Envolution.info:. wrote:
> Please have a look also at the discussion about the recall to pontuke.. 
> maybe it would be useful to wait until the situation will be clear, in 
> order to take a good decision in stadards...
> 
> Romeo Bandinelli
> 
> 

Actually to be clear the articles and posts concerning this Romeo are
just that...discussions.

There are no current talks between PostNuke and Envolution so
development should not stop because we chose to bring the issue in the
public eye and discuss it.

Envolution has tried twice in recent months to at leats get Postnuke to
the table to discuss the possibilities. Both times Postnuke refused to
do so......so PLEASE ....keep development moving. Sitting on the fench
waiting for something which may never happen is not productive for
anyone.

Zoom