Re[2]: The max=0 issue is a bug ...
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 29313
interpreted = N
texte = >This is justifiably a bug if it only occurs in the Mac version; I just tested >the Linux Version and it also works fine.That's what I figured ... :) >I always use [ShowNext max=1], so >that I only have one link, since I find it looks amaturish to have a long list >of next groupings. I think most people will page through a select set, rather >than jumping around.I do whatever the client asks me to do ... :)By the way, when you say I find it looks amaturish to have a long list of next groupings it makes me think you have never have seen a professional use of shownext with multiple links. Here is a site I developed using multiple shownext links that looks far from amateurish to me:http://www.especiallyforyou.comJust remember, if you visit this site you'll have to register to get into the catalog, because this is a wholesale site and company registration is required for access to the online catalog. But registration is immediate, and as long as cookies are enabled in your browser you'll be able to get into the catalog instantly after registration -- to see how a series of shownext links can look very professional indeed ... :) >As for variable naming, most languages take the easy english language variable >names for themselves and require the _user_ to stay out of _their_ way. This is >hardly unique to WebCat ...Yes, but some software firms have done it the other way around from the beginning, and it makes their software a dream to use compared to webdna! Take a look at MGI for example, every MGI language tag begins with mgi which make it virtually conflict-free for the user, since he can use any variable name or db field name he wishes, as long as it does not begin with mgi ... :)Having a rule like Don't begin your variable or db field names with 'mgi'... is a lot easier to remember than to have to recall a list of common everyday words that the webdna software engineers decided to grab for their own specific uses ...Of course I agree that it would alleviate the problem somewhat if we could just look in the docs for a list of reserved names. It would ba a hassle compared to a rule like the one above, but at least it might help a little bit. But it's been YEARS and we still don't even have an alphabetical list of all the tags in the webdna language to refer to in the docs, much less a list of 'reserved names' ...:( >What you are asking is unreasonable, pure and simple.I'm not asking SM to change things, they made their bed and they can sleep in it. All I'm saying is that if PCS had had the foresight to recognize that users will always prefer to use common names for their variables, then they *may* have done things differently from the beginning.MGI did it better from the beginning, and their way has increased user flexibility and decreased the things the user has to 'worry about' in order to program MGI properly -- not to mention decreasing the frustration level new users experience in their debugging efforts which are basically non-existent when it comes to tag naming conflicts. The result is that MGI will continue to benefit from their insightful decision forever, whereas SM will continue to be hounded by users reporting problems which are nothing more than naming conflicts.But there's an even more bizarre issue in the webdna language when it comes to naming conflicts. I mean, it's bad enough for SM to grab [date] and use it as a global tag without giving it a pcs or sms prefix to set it apart from a common database field or variable named [date] -- but to use date as as an orderfile field name when they already know it is being used as a global tag?================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Associated Messages, from the most recent to the oldest:
>This is justifiably a bug if it only occurs in the Mac version; I just tested >the Linux Version and it also works fine.That's what I figured ... :) >I always use [ShowNext max=1], so >that I only have one link, since I find it looks amaturish to have a long list >of next groupings. I think most people will page through a select set, rather >than jumping around.I do whatever the client asks me to do ... :)By the way, when you say I find it looks amaturish to have a long list of next groupings it makes me think you have never have seen a professional use of shownext with multiple links. Here is a site I developed using multiple shownext links that looks far from amateurish to me:http://www.especiallyforyou.comJust remember, if you visit this site you'll have to register to get into the catalog, because this is a wholesale site and company registration is required for access to the online catalog. But registration is immediate, and as long as cookies are enabled in your browser you'll be able to get into the catalog instantly after registration -- to see how a series of shownext links can look very professional indeed ... :) >As for variable naming, most languages take the easy english language variable >names for themselves and require the _user_ to stay out of _their_ way. This is >hardly unique to WebCat ...Yes, but some software firms have done it the other way around from the beginning, and it makes their software a dream to use compared to webdna! Take a look at MGI for example, every MGI language tag begins with mgi which make it virtually conflict-free for the user, since he can use any variable name or db field name he wishes, as long as it does not begin with mgi ... :)Having a rule like Don't begin your variable or db field names with 'mgi'... is a lot easier to remember than to have to recall a list of common everyday words that the webdna software engineers decided to grab for their own specific uses ...Of course I agree that it would alleviate the problem somewhat if we could just look in the docs for a list of reserved names. It would ba a hassle compared to a rule like the one above, but at least it might help a little bit. But it's been YEARS and we still don't even have an alphabetical list of all the tags in the webdna language to refer to in the docs, much less a list of 'reserved names' ...:( >What you are asking is unreasonable, pure and simple.I'm not asking SM to change things, they made their bed and they can sleep in it. All I'm saying is that if PCS had had the foresight to recognize that users will always prefer to use common names for their variables, then they *may* have done things differently from the beginning.MGI did it better from the beginning, and their way has increased user flexibility and decreased the things the user has to 'worry about' in order to program MGI properly -- not to mention decreasing the frustration level new users experience in their debugging efforts which are basically non-existent when it comes to tag naming conflicts. The result is that MGI will continue to benefit from their insightful decision forever, whereas SM will continue to be hounded by users reporting problems which are nothing more than naming conflicts.But there's an even more bizarre issue in the webdna language when it comes to naming conflicts. I mean, it's bad enough for SM to grab [date] and use it as a global tag without giving it a pcs or sms prefix to set it apart from a common database field or variable named [date] -- but to use date as as an orderfile field name when they already know it is being used as a global tag?================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
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...
Related Readings:
categories (1997)
WebCat2 - [include] tags (1997)
New public beta available (1997)
New WebDNA Solutions ... (1997)
OFF-TOPIC: Check www.godaddy.com for me ... (2003)
Webcat 2.0.1 date math bug -> Crash! (1997)
date sorting and 'template (1997)
Attn: Bug in GeneralStore example b15 (1997)
creator code (1997)
Bugs still *not* fixed as promised ... (2000)
I'm tired of all this! (2000)
Summing fields (1997)
Shell context. (2002)
RE: Can a database get stomped by simultaneous access? (1997)
db protection on NT (1997)
Great product and great job ! (1997)
Re:ListFields and [name] (1997)
WebCat2b13 Command Reference Doc error (1997)
More on the email templates (1997)
Displaying xx number of characters (1997)