On 22 Feb 2017, at 03:38, Donovan Brooke <dbrooke@euca.us> =wrote:Hello,
My .02=C2=A2 on this. =
I believe WSC was addressing the issue I brought up =about encapsulation in WebDNA on this change.
Encapsulation is a very important part of contemporary =programming and works hand-in-hand with variable scoping (Which I think =is what Tom is dealing with now).
Unfortunately, this was one of the last things SMSI was =working on before WSC purchased WebDNA=E2=80=A6 and this stuff was never =fully worked out nor documented well.
My =opinion is that people like Tom (who uses this stuff in a real world =situation) should work directly with WSC and the WSC programmer =specifically whom **understands** OOP programming (specifically =encapsulation and variable scoping) to refine WebDNA in this area.
The end result of this partnership should =be:
1.) Clear use of Variable Scoping (in Include, =Function, and Text / Math variables=E2=80=A6 as well as the ancillary =tags/contexts, such as [ListVariables..])
2.) Refinement =of the Include tag=E2=80=99s feature of =E2=80=9C&varname=3Dvalue=E2=80==9D... addressing encapsulation.
3.) Clear documentation =of all of this.
There is a real =opportunity here (in my opinion) to bring WebDNA to a new level of =sophistication / maturity. I do think WebDNA is not that far off from =getting there=E2=80=A6 it just needs some tweaks and some better =documentation and understanding.
Sincerely,
Donovan
On Feb 21, 2017, at 9:07 AM, Tom Duke <tom@revolutionaries.ie> wrote:Chris,
Hi - that behaviour that you describe is consistent and makes =sense.
But my problem is when I use =insecure text variables to set default values in an include file. = I would not expect an insecure text variable to overwrite an =incoming include variable.
Taking your =example but setting the text variable in the include file to insecure
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-test1.dn=a=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-
[include file=3Dtest2.inc&var1=3D8&var2=3D9&var3=3D=23]
<br>
main file : [var1] with =[var2] with [var3]
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94==E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94=E2=80=94=E2==80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-test2.in=c=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-
[text secure=3DF]var3=3D0634[/text]
included file : [var1] with [var2] with [var3]
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94==E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94=E2=80=94=E2==80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94=E2=80=94
I would think that in this case var3 should =not be overwritten. Perhaps I am misunderstanding the relationship =between text and include variables.
It =means that instead of using
[text =secure=3DF]var3=3D23[/text]
to set default =values in include files I will have to use
[showif =[url][var3[/url]=3D[url][raw][var3][/raw][/url]][text]var3=3D23[/text][/sh=owif]
- Tom
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
Digital Revolutionaries
1st Floor, =Castleriver House
14-15 Parliament Street
Temple Bar,Dublin 2
Ireland
----------------------------------------------
[t]: + 353 1 4403907
[e]: <mailto:tom@revolutionaries.ie>
[w]: =<http://www.revolutionaries.ie/>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
On 21 February 2017 at 08:35, <christophe.billiottet@webdna.us> wrote:
Hello Tom, there is a behavioral change: here the results of =loading test1.dna on 8.5.1 and 6.2
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-test1.dn=a=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-
[include file=3Dtest2.inc&var1=3D8&var2=3D9&var3=3D=23]
<br>
main file : [var1] with =[var2] with [var3]
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94==E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94=E2=80=94=E2==80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-test2.in=c=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-
[text]var3=3D0634[/text]
included =file : [var1] with [var2] with [var3]
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94==E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94=E2=80=94=E2==80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94=E2=80=94
on 8.5.1 we get
included file : 8 with 9 with 0634
main file : =[var1] with [var2] with 0634
on 6.2 we =get
included file : 8 with 9 with 23
main =file : [var1] with [var2] with 0634
However, in test1.dna, we load a file and simultaneously pass =three variable values, and the included file overwrites one of the =variables with another value. It seems consistant to me that the result =shows the overwriting variable, and not the overwritten one.
So, to me, 8.5.1 is consistant.
Any opinion about this?
- chrisOn Feb 20, 2017, at =17:37, Tom Duke <tom@revolutionaries.ie> wrote:
Hi all,
Ok I have just hit an =issue with variables using WebDNA 8.5.1 on CentOS 7.
Prior to the upgrade calling this include:
[include =file=3D/common/includes/smUtility-navlist-bootstrap.inc&smNAVCLASS=3Dp=rimary-nav]
and having this in the include =file:
[text secure=3DF]smNAVCLASS=3D[/text]
would result in the variable 'smNAVCLASS' =being set to 'primary-nav'.
After the =upgrade the variable 'smNAVCLASS' being set to '' - i.e. blank.
So the line "[text =secure=3DF]smNAVCLASS=3D[/text]" is overwriting the passed in include =variable.
Is this the intended behaviour? = If so then I have a lot of code to rewrite.
- Tom
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail =to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug= Reporting: support@webdna.us
--------------------------------------------------------- =This message is sent to you because you are subscribed to the mailing =list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: =support@webdna.us
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail =to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug= Reporting: support@webdna.us
On 22 Feb 2017, at 03:38, Donovan Brooke <dbrooke@euca.us> =wrote:Hello,
My .02=C2=A2 on this. =
I believe WSC was addressing the issue I brought up =about encapsulation in WebDNA on this change.
Encapsulation is a very important part of contemporary =programming and works hand-in-hand with variable scoping (Which I think =is what Tom is dealing with now).
Unfortunately, this was one of the last things SMSI was =working on before WSC purchased WebDNA=E2=80=A6 and this stuff was never =fully worked out nor documented well.
My =opinion is that people like Tom (who uses this stuff in a real world =situation) should work directly with WSC and the WSC programmer =specifically whom **understands** OOP programming (specifically =encapsulation and variable scoping) to refine WebDNA in this area.
The end result of this partnership should =be:
1.) Clear use of Variable Scoping (in Include, =Function, and Text / Math variables=E2=80=A6 as well as the ancillary =tags/contexts, such as [ListVariables..])
2.) Refinement =of the Include tag=E2=80=99s feature of =E2=80=9C&varname=3Dvalue=E2=80==9D... addressing encapsulation.
3.) Clear documentation =of all of this.
There is a real =opportunity here (in my opinion) to bring WebDNA to a new level of =sophistication / maturity. I do think WebDNA is not that far off from =getting there=E2=80=A6 it just needs some tweaks and some better =documentation and understanding.
Sincerely,
Donovan
On Feb 21, 2017, at 9:07 AM, Tom Duke <tom@revolutionaries.ie> wrote:Chris,
Hi - that behaviour that you describe is consistent and makes =sense.
But my problem is when I use =insecure text variables to set default values in an include file. = I would not expect an insecure text variable to overwrite an =incoming include variable.
Taking your =example but setting the text variable in the include file to insecure
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-test1.dn=a=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-
[include file=3Dtest2.inc&var1=3D8&var2=3D9&var3=3D=23]
<br>
main file : [var1] with =[var2] with [var3]
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94==E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94=E2=80=94=E2==80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-test2.in=c=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-
[text secure=3DF]var3=3D0634[/text]
included file : [var1] with [var2] with [var3]
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94==E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94=E2=80=94=E2==80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94=E2=80=94
I would think that in this case var3 should =not be overwritten. Perhaps I am misunderstanding the relationship =between text and include variables.
It =means that instead of using
[text =secure=3DF]var3=3D23[/text]
to set default =values in include files I will have to use
[showif =[url][var3[/url]=3D[url][raw][var3][/raw][/url]][text]var3=3D23[/text][/sh=owif]
- Tom
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
Digital Revolutionaries
1st Floor, =Castleriver House
14-15 Parliament Street
Temple Bar,Dublin 2
Ireland
----------------------------------------------
[t]: + 353 1 4403907
[e]: <mailto:tom@revolutionaries.ie>
[w]: =<http://www.revolutionaries.ie/>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
On 21 February 2017 at 08:35, <christophe.billiottet@webdna.us> wrote:
Hello Tom, there is a behavioral change: here the results of =loading test1.dna on 8.5.1 and 6.2
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-test1.dn=a=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-
[include file=3Dtest2.inc&var1=3D8&var2=3D9&var3=3D=23]
<br>
main file : [var1] with =[var2] with [var3]
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94==E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94=E2=80=94=E2==80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-test2.in=c=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-
[text]var3=3D0634[/text]
included =file : [var1] with [var2] with [var3]
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94==E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94=E2=80=94=E2==80=94=E2=80=94=E2=80=94-=E2=80=94=E2=80=94=E2=80=94
on 8.5.1 we get
included file : 8 with 9 with 0634
main file : =[var1] with [var2] with 0634
on 6.2 we =get
included file : 8 with 9 with 23
main =file : [var1] with [var2] with 0634
However, in test1.dna, we load a file and simultaneously pass =three variable values, and the included file overwrites one of the =variables with another value. It seems consistant to me that the result =shows the overwriting variable, and not the overwritten one.
So, to me, 8.5.1 is consistant.
Any opinion about this?
- chrisOn Feb 20, 2017, at =17:37, Tom Duke <tom@revolutionaries.ie> wrote:
Hi all,
Ok I have just hit an =issue with variables using WebDNA 8.5.1 on CentOS 7.
Prior to the upgrade calling this include:
[include =file=3D/common/includes/smUtility-navlist-bootstrap.inc&smNAVCLASS=3Dp=rimary-nav]
and having this in the include =file:
[text secure=3DF]smNAVCLASS=3D[/text]
would result in the variable 'smNAVCLASS' =being set to 'primary-nav'.
After the =upgrade the variable 'smNAVCLASS' being set to '' - i.e. blank.
So the line "[text =secure=3DF]smNAVCLASS=3D[/text]" is overwriting the passed in include =variable.
Is this the intended behaviour? = If so then I have a lot of code to rewrite.
- Tom
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail =to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug= Reporting: support@webdna.us
--------------------------------------------------------- =This message is sent to you because you are subscribed to the mailing =list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: =support@webdna.us
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail =to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug= Reporting: support@webdna.us
DOWNLOAD WEBDNA NOW!
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...