> * introduce functionality to tell Weblocks that it is the user's > actual intention to use the boxed files
Would this be a keyword arg for DEFWEBAPP? (and instance variable for WEBLOCKS-WEBAPP) Sounds OK to me. I'm just wondering if that's what you had in mind. > * catch the warning in the demo (would need introduction of a > specifical condition class first) I would not recommend silencing the warning within the demo. In general, when dealing with routine / expected conditions, I'd rather prevent the condition from occurring than handle it through the condition system. -Keith On May 14, 9:44 am, "Leslie P. Polzer" <[email protected]> wrote: > Keith M. Corbett wrote: > > > You're right, this is a useful warning. > > > Turns out it wasn't coming from my app. I load WEBLOCKS-CLSQL-DEMO > > with my app, and that's the source of the warning. Minor bug, worth > > fixing? > > What would you propose to fix this? I see several ways right now: > > * introduce functionality to tell Weblocks that it is the user's > actual intention to use the boxed files > > * catch the warning in the demo (would need introduction of a > specifical condition class first) > > * specify an explicit path in the demo > > Of course the second one is just a variation of the first one. > Personally I like it best. > > The third would just duplicate code on the other hand. > > Leslie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
