Re: Reserved words - Enhancement request

This WebDNA talk-list message is from

2000

It keeps the original formatting. numero = 28459
interpreted = N
texte = At 8:19 PM -1000 2000/03/02, Kenneth Grome wrote:> >I totally agree, but I think that it is too late now. There is a lot>>of code that would break if they renamed the tags.>>I disagree!>>Nothing will break sites developed for 3.x versions unless the user >upgrades, and there's no reason why anyone would HAVE TO upgrade to >a newer version. This is not a communist country and we are not >forced to upgrade -- we will *always* have a choice of whether to >upgrade or not.But if I want to write a web based database application and distribute it, do I tell my customers that it only works on one or the other. It is much better to say that this application works with 3.x versions of Typhoon Pro and above.>Saying it's too late is just an excuse, because it is NEVER too >late to fix problems. Any prudent software firm will fix every bug >or problematic feature it is aware of -- if it actually hopes to >make its software the best possible product in the long run ...It is true that they must fix it, but not at the expense of breaking everything else. When there are better solutions.>Any site that currently runs webcatalog 3.x will continue to work >fine while running version 3.x, so to ignore this fix at the expense >of everyone who might end up buying webcatalog in the future is a >decision based not on the future quality of the product, but on >other parameters such as whatever is 'easiest' or 'cheapest' thing >to do ...>>It takes real pride in your product to 'bite the bullet' and fix >things that should have been fixed a long time ago, especially when >the fixing might make more work for you and cost your company some >money in the short term. IT seems to me that the most successful >companies all over the world tend to fix things when their users >inform them of problems, especially when those same users care >enough to spend their time describing the problems and suggesting >potential solutions.>>What's more, I see no reason why a new version with this stuff fixed >cannot be run on the same server that already has an older version >of webcatalog running on it -- provided SM recognizes the need of >some users to continue using an old version concurrently with a new >version on the same box.>It would be fine if I could put for the 3.x tags and for things I have converted, but not if that would make my web server run slower or require a lot more memory. I would much rather have reserved word checking than a bloated WebDNA. Once I get the reserved word error message, I can fix it and continue working instead of spending a couple of hours trying to discover what I did wrong. While it would be nice if I were not restricted from using the field name URL, I can live with dbURL a lot easier than adding another 5 meg to my machine. I just want to quickly know when a collision has occurred.>>>There IS something we can do now AND something that SM could do to>>ease the pain.>>>>We as users should start coding all db field names with a 2 character>>prefix. dbPrice or myPrice would solve the problem.>>No this will not solve the problem. The shopping cart code built >into in webcatalog *requires* a price field in the database, and >it also references a price field in the cart file. These field >names are non-negotiable, and there will continue to be problems >whenever a [price] tag is used inside a founditems context which >appears inside or around an orderfile context -- unless work-arounds >are implemented.>I have never used the shopping cart stuff. There are enough people writing shopping carts. I bought Typhoon pro to build web-based Databases applications, so I will have to bow to your knowledge of the shopping cart features. It looks like there may be something broken there that I do not understand. Sorry.Although I have been a programmer for over 20 years now, I am still a newbie to WebCat so please forgive if I misunderstand. I have only been using it for about a month or two, but I have written several applications so far and mostly like it. There are some major warts though. It would be good to see SM moving to improve the product. -Chuck-__________________________________________________________________________Chuck Rice -------------------------------------------------------------Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server.To end your Mail problems go to .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:

Re: Reserved words - Enhancement request (Chuck Rice 2000)
Re: Reserved words - Enhancement request (Kenneth Grome 2000)
Re: Reserved words - Enhancement request (Aaron Lynch 2000)
Re: Reserved words - Enhancement request (Kenneth Grome 2000)
Reserved words - Enhancement request (Chuck Rice 2000)

At 8:19 PM -1000 2000/03/02, Kenneth Grome wrote:> >I totally agree, but I think that it is too late now. There is a lot>>of code that would break if they renamed the tags.>>I disagree!>>Nothing will break sites developed for 3.x versions unless the user >upgrades, and there's no reason why anyone would HAVE TO upgrade to >a newer version. This is not a communist country and we are not >forced to upgrade -- we will *always* have a choice of whether to >upgrade or not.But if I want to write a web based database application and distribute it, do I tell my customers that it only works on one or the other. It is much better to say that this application works with 3.x versions of Typhoon Pro and above.>Saying it's too late is just an excuse, because it is NEVER too >late to fix problems. Any prudent software firm will fix every bug >or problematic feature it is aware of -- if it actually hopes to >make its software the best possible product in the long run ...It is true that they must fix it, but not at the expense of breaking everything else. When there are better solutions.>Any site that currently runs webcatalog 3.x will continue to work >fine while running version 3.x, so to ignore this fix at the expense >of everyone who might end up buying webcatalog in the future is a >decision based not on the future quality of the product, but on >other parameters such as whatever is 'easiest' or 'cheapest' thing >to do ...>>It takes real pride in your product to 'bite the bullet' and fix >things that should have been fixed a long time ago, especially when >the fixing might make more work for you and cost your company some >money in the short term. IT seems to me that the most successful >companies all over the world tend to fix things when their users >inform them of problems, especially when those same users care >enough to spend their time describing the problems and suggesting >potential solutions.>>What's more, I see no reason why a new version with this stuff fixed >cannot be run on the same server that already has an older version >of webcatalog running on it -- provided SM recognizes the need of >some users to continue using an old version concurrently with a new >version on the same box.>It would be fine if I could put for the 3.x tags and for things I have converted, but not if that would make my web server run slower or require a lot more memory. I would much rather have reserved word checking than a bloated WebDNA. Once I get the reserved word error message, I can fix it and continue working instead of spending a couple of hours trying to discover what I did wrong. While it would be nice if I were not restricted from using the field name URL, I can live with dbURL a lot easier than adding another 5 meg to my machine. I just want to quickly know when a collision has occurred.>>>There IS something we can do now AND something that SM could do to>>ease the pain.>>>>We as users should start coding all db field names with a 2 character>>prefix. dbPrice or myPrice would solve the problem.>>No this will not solve the problem. The shopping cart code built >into in webcatalog *requires* a price field in the database, and >it also references a price field in the cart file. These field >names are non-negotiable, and there will continue to be problems >whenever a [price] tag is used inside a founditems context which >appears inside or around an orderfile context -- unless work-arounds >are implemented.>I have never used the shopping cart stuff. There are enough people writing shopping carts. I bought Typhoon pro to build web-based Databases applications, so I will have to bow to your knowledge of the shopping cart features. It looks like there may be something broken there that I do not understand. Sorry.Although I have been a programmer for over 20 years now, I am still a newbie to WebCat so please forgive if I misunderstand. I have only been using it for about a month or two, but I have written several applications so far and mostly like it. There are some major warts though. It would be good to see SM moving to improve the product. -Chuck-__________________________________________________________________________Chuck Rice -------------------------------------------------------------Brought to you by CommuniGate Pro - The Buzz Word Compliant Messaging Server.To end your Mail problems go to .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 Chuck Rice

DOWNLOAD WEBDNA NOW!

Re: Reserved words - Enhancement request

2000

Top Articles:

Related Readings: