seaside February 2016

seaside@lists.squeakfoundation.org

9 participants
11 discussions

isolate
by recursive68＠gmail.com 26 Nov '19

26 Nov '19

Hi, Given it looks like the isolate method is never going to added back to the current or future versions of Seaside as it's been an open bug issue for the last 5 years, how in general would go about replicating it's behaviour ? I think it's a shame as I think this sort of functionality made Seaside standout from the crowd as a web framework. Thanks

4 5

Twitter Bootstrap and Accordion
by Torsten Bergmann 22 Jul '16

22 Jul '16

3 3

Re: [Seaside] ZINC - Kom dilemma Fwd: WADebugErrorHandler problem
by Robert Kuszinger 27 Mar '16

27 Mar '16

Sven, thanks for the tip. Actually the UTF problem won't appear with Zinc but I also need to do large file uploads. Zinc resets connection somewhere between 10-19 MB File size. Is there a built-in limitation? Anyway, an idea on how to break through this limit may also help. I need to upload 150-300 MB files regulary with this service. KomHttp did it out-of-the-box. thanks Robert 2016-01-18 12:45 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Robert, > > If you are using Pharo, it seems more logical that you would use > ZnZincServerAdaptor. > > But of course, it might not necessarily have to do with the adaptor. > > HTH, > > Sven >

10 32

Re: Cannot load Seaside anymore in a just-migrated GemStone [WAS] Re: [Glass] Zinc 2.4.3 on Gemstone
by Mariano Martinez Peck 24 Mar '16

24 Mar '16

On Thu, Oct 15, 2015 at 4:25 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi guys, > > I have a weird scenario I cannot solve. I am trying to load my app code > (together with all it's dependencies) in a just migrated stone (from > GemStone 3.1.0.4 to GemStone 3.2.9). I performed all the steps of the > migration. Yet, I have an error, pasted below. However, if I run the same > code to load my app in a fresh 3.2.9 extent, that works perfectly. It only > fails in my migrated (from 3.1.0.4) stone. > > The problem is in > > WAWalkbackErrorHandler class >> initialize > WAAdmin applicationExceptionHandlingDefaults at: #exceptionHandler put: > self > > It fails because the > > WAConfiguration >> attributeAt: aSymbol > ^ self attributeAt: aSymbol ifAbsent: [ WAAttributeNotFound signalWithKey: > aSymbol ] > > gives a key not found. > > I did a search in the mailing list and found related threads: > > http://forum.world.st/Glass-Zinc-2-4-3-on-Gemstone-td4759789.html#a4759875 > https://github.com/seasidest/seaside/issues/643 > > But none show a solution. > > And yes, it is obvious it will fail because: > > WAAdmin applicationExceptionHandlingDefaults allAttributes -> > anIdentityDictionary( ) > > Also, as you can see, the result of WAAdmin > applicationExceptionHandlingDefaults has no parent or anything: > > Inspect aWASharedConfiguration/ > -------------------- > . -> aWASharedConfiguration > (class)@ -> WASharedConfiguration > (oop)@ -> 1169561601 > (committed)@ -> true > cachedSearchContexts@ -> anIdentityDictionary( > #'exceptionHandler'->aWAAttributeSearchContext) > expressions@ -> aDictionary( ) > name@ -> 'Application Exception Handling Defaults' > parents@ -> anOrderedCollection( ) > > > I even tried the re-initialization of Seaside as provided by Bruno the > other day: > > WAAdmin unregister: 'reps'. > WAAdmin unregister: 'advisors'. > WAAdmin unregister: 'clients'. > > WAGemStoneProductionErrorHandler initialize. > WAWalkbackErrorHandler initialize. > WARemoteDebuggingWalkbackErrorHandler initialize. > > [ > WADispatcher default. > WASystemConfiguration allSubclasses > do: [ :each | each instance buildDescription ] ] > ensure: [ System commitTransaction ] . > > > Still, same error. > > > Any clues? Is there way I can re-initialize all Seaside? > > > This is the stack: > > aTDDebugger > -------------------- > 1. WAAttributeNotFound(AbstractException)>>_signalWith: @6 line 25 > 2. WAAttributeNotFound(AbstractException)>>signal @2 line 47 > 3. WAAttributeNotFound class>>signalWithKey: @4 line 4 > 4. [] in ExecBlock0(WAConfiguration)>>attributeAt: @2 line 2 > 5. IdentityDictionary>>at:ifAbsent: @5 line 8 > 6. WASharedConfiguration(WAConfiguration)>>attributeAt:ifAbsent: @3 line 2 > 7. WASharedConfiguration(WAConfiguration)>>attributeAt: @2 line 2 > 8. WASharedConfiguration(WAUserConfiguration)>>at:put: @2 line 7 > 9. WAWalkbackErrorHandler class>>initialize @3 line 2 > 10. MCMethodDefinition>>postload @11 line 6 > 11. MCMethodDefinition(MCDefinition)>>postloadOver: @2 line 2 > 12. [] in MCPackageLoader>>basicLoad @3 line 48 > 13. OrderedCollection(Collection)>>do: @5 line 10 > 14. OrderedCollection(Collection)>>do:displayingProgress: @2 line 3 > 15. [] in MCPackageLoader>>basicLoad @15 line 48 > 16. MCPackageLoader(ExecBlock)>>on:do: @3 line 42 > 17. [] in MCPackageLoader>>basicLoad @2 line 49 > 18. MCPackageLoader(ExecBlock)>>ensure: @2 line 12 > 19. MCPackageLoader>>basicLoad @11 line 51 > 20. [] in MCPackageLoader>>loadWithNameLike: @2 line 4 > 21. [] in ExecBlock0(MCPackageLoader)>>useChangeSetNamed:during: @2 line 9 > 22. ExecBlock0(ExecBlock)>>ensure: @2 line 12 > 23. MCPackageLoader>>useChangeSetNamed:during: @9 line 9 > 24. MCPackageLoader>>useNewChangeSetNamedLike:during: @3 line 2 > 25. MCPackageLoader>>loadWithNameLike: @6 line 4 > 26. MCVersionLoader>>load @9 line 6 > 27. MetacelloGoferLoad(GoferLoad)>>execute @6 line 3 > 28. [] in > MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer: > @5 line 17 > 29. [] in > MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer: > @14 line 21 > 30. MetacelloGemStonePlatform(MetacelloPlatform)>>do:displaying: @2 line 3 > 31. > MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer: > @7 line 5 > 32. > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadPackageDirective:gofer: > @4 line 4 > 33. MetacelloPackageLoadDirective>>loadUsing:gofer: @2 line 3 > 34. [] in > ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > @2 line 3 > 35. OrderedCollection(Collection)>>do: @5 line 10 > 36. > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > @3 line 3 > 37. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4 > 38. [] in > ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > @2 line 3 > 39. OrderedCollection(Collection)>>do: @5 line 10 > 40. > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > @3 line 3 > 41. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4 > 42. [] in > ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > @2 line 3 > 43. OrderedCollection(Collection)>>do: @5 line 10 > 44. > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > @3 line 3 > 45. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4 > 46. [] in > ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > @2 line 3 > 47. OrderedCollection(Collection)>>do: @5 line 10 > 48. > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > @3 line 3 > 49. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4 > 50. [] in > ExecBlock1(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > @2 line 3 > 51. OrderedCollection(Collection)>>do: @5 line 10 > 52. > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > @3 line 3 > 53. MetacelloLinearLoadDirective>>loadUsing:gofer: @6 line 4 > 54. > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadWithPolicy: > @7 line 7 > 55. MetacelloLoaderPolicy>>load @6 line 4 > 56. MetacelloFetchingMCSpecLoader>>doLoad @4 line 3 > 57. [] in ExecBlock0(MetacelloMCVersion)>>doLoadRequiredFromArray: @2 line > 12 > 58. MetacelloGemStonePlatform(MetacelloPlatform)>>do:displaying: @2 line 3 > 59. [] in MetacelloMCVersion>>doLoadRequiredFromArray: @7 line 12 > 60. MetacelloMCVersion(ExecBlock)>>ensure: @2 line 12 > 61. MetacelloMCVersion>>doLoadRequiredFromArray: @22 line 16 > 62. Array(Collection)>>loadRequiredForMetacelloMCVersion: @2 line 3 > 63. MetacelloMCVersion>>load: @2 line 3 > 64. [] in MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade: > @10 line 16 > 65. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42 > 66. [] in MetacelloScriptEngine>>handleNotificationsForAction: @6 line 6 > 67. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42 > 68. [] in MetacelloScriptEngine>>handleNotificationsForAction: @4 line 14 > 69. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42 > 70. [] in MetacelloScriptEngine>>handleNotificationsForAction: @2 line 20 > 71. MetacelloScriptEngine(ExecBlock)>>on:do: @3 line 42 > 72. MetacelloScriptEngine>>handleNotificationsForAction: @2 line 24 > 73. [] in MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade: > @2 line 5 > 74. MetacelloScriptEngine(ExecBlock)>>ensure: @2 line 12 > 75. MetacelloProjectRegistration class>>copyRegistryRestoreOnErrorWhile: > @8 line 14 > 76. MetacelloScriptEngine>>load:onProjectDownGrade:onProjectUpgrade: @2 > line 3 > 77. MetacelloScriptEngine>>load: @2 line 3 > 78. [] in MetacelloScriptApiExecutor(MetacelloScriptExecutor)>>execute: > @11 line 15 > 79. [] in MetacelloScriptApiExecutor>>executeString:do: @5 line 6 > 80. Array(Collection)>>do: @5 line 10 > 81. MetacelloScriptApiExecutor>>executeString:do: @6 line 4 > 82. String>>execute:against: @2 line 2 > 83. MetacelloScriptApiExecutor(MetacelloScriptExecutor)>>execute: @6 line 9 > 84. Metacello>>execute:args: @8 line 5 > 85. Metacello>>load: @2 line 2 > 86. [] in Executed Code > 87. ExecBlock0(ExecBlock)>>ensure: @2 line 12 > 88. Executed Code > 89. String(CharacterCollection)>>evaluateIn:symbolList:literalVars: @4 > line 13 > 90. > TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>evaluateString: > @5 line 3 > 91. > TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>doItMenuAction:selectedText: > @2 line 2 > 92. > TDWorkspaceClientElementBuilder(TDWindowBuilder)>>handleMenuActions:listElement:actionArg: > @12 line 10 > 93. [] in > TDWorkspaceClientElementBuilder(TDClientSourceElementBuilder)>>menuActionBlock > @6 line 8 > 94. > TDWorkspaceClientElementBuilder(ExecBlock)>>value:value:value:value:value: > @2 line 11 > 95. GsNMethod class>>_gsReturnToC @1 line 1 > > > Thanks in advance for any help. > > On Thu, Oct 15, 2015 at 1:40 PM, Gerhard Obermann <obi068(a)gmail.com> > wrote: > >> Hi, >> >> Not really, i only found the following in my notes. >> >> HTH >> Gerhard >> >> >> >> - >> >> Load Seaside 3.1.x but don’t initialize Seaside Classes >> >> >> | performInitialization | >> >> performInitialization := #(). >> >> [ >> >> GsDeployer deploy: [ Metacello new >> >> baseline: 'Seaside3'; >> >> repository: 'github://glassdb/Seaside31:gemstone3.1/repository'; >> >> load: 'CI']. >> >> ] on: MCPerformPostloadNotification do: [:ex | >> >> (performInitialization includes: ex postloadClass >> theNonMetaClass name) >> >> ifTrue: [ >> >> "perform initialization" >> >> ex resume: true ] >> >> ifFalse: [ >> >> GsFile gciLogServer: ' Skip ', ex postloadClass name >> asString, ' initialization.'. >> >> ex resume: false ] ] >> >> >> On Thu, Oct 15, 2015 at 5:47 PM, Mariano Martinez Peck < >> marianopeck(a)gmail.com> wrote: >> >>> Hi Gerhard, >>> >>> I am getting the exact same issue. Do you remember what you did to fix >>> it? >>> >>> Thanks, >>> >>> On Wed, May 21, 2014 at 10:39 AM, Gerhard Obermann <obi068(a)gmail.com> >>> wrote: >>> >>>> Hi Dale! >>>> >>>> I think as soon as I can load the stuff in my upgraded 3.2. DB, i can >>>> test and contribute to zink and/or Glass / Seaside 3.1. >>>> If it wont work until tomorrow i have to stay on 3.1.0.5 for the next >>>> few months at least. >>>> >>>> At the moment i am trying to load Seaside 3.1.1 with >>>> PS: To be able to load this i have loaded the Baseline packages BaselineOfGLASS1, >>>> BaselineOfSeaside3 , BaselineOfZinc manually from my forked GIT clone. >>>> >>>> GsDeployer deploy: [ >>>> Metacello new >>>> configuration: 'Grease'; >>>> repository: ' >>>> http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; >>>> get. >>>> >>>> "Load Seaside31" >>>> GsDeployer deploy: [ >>>> Metacello new >>>> baseline: 'Seaside3'; >>>> repository: 'github://glassdb/Seaside31:gemstone3.1/repository'; >>>> load: 'CI']. >>>> >>>> >>>> Not sure if i need to load Metacello new >>>> baseline: 'GLASS1'; >>>> repository: 'github://glassdb/glass:master/repository'; >>>> load. >>>> after the upgrade. >>>> >>>> What is the difference between >>>> (ConfigurationOfGLASS project version: '1.0-beta.9.1') load >>>> and >>>> Metacello new >>>> baseline: 'GLASS1'; >>>> repository: 'github://glassdb/glass:master/repository'; >>>> load. >>>> >>>> *The load of the Seaside package failed with the init of * >>>> *WAWalkbackErrorHandler => initialize* >>>> * WAAdmin applicationExceptionHandlingDefaults at: #exceptionHandler >>>> put: self* >>>> >>>> [1] WAAttributeNotFound (AbstractException) >> _signalWith: >>>> inCextensionArg: nil >>>> res: nil >>>> .t1: a WAAttributeNotFound occurred (error 2710) >>>> receiver: a WAAttributeNotFound occurred (error 2710) >>>> [2] WAAttributeNotFound (AbstractException) >> signal >>>> receiver: a WAAttributeNotFound occurred (error 2710) >>>> [3] WAAttributeNotFound class >> signalWithKey: >>>> aSymbol: #'exceptionHandler' >>>> receiver: WAAttributeNotFound >>>> [4] [] in ExecBlock0 (WAConfiguration) >> attributeAt: >>>> aSymbol: #'exceptionHandler' >>>> receiver: nil >>>> [5] IdentityDictionary >> at:ifAbsent: >>>> aKey: #'exceptionHandler' >>>> aBlock: anExecBlock0 >>>> anAssoc: nil >>>> .t1: anExecBlock0 >>>> receiver: anIdentityDictionary( ) >>>> [6] WASharedConfiguration (WAConfiguration) >> attributeAt:ifAbsent: >>>> aSymbol: #'exceptionHandler' >>>> aBlock: anExecBlock0 >>>> receiver: aWASharedConfiguration >>>> [7] WASharedConfiguration (WAConfiguration) >> attributeAt: >>>> aSymbol: #'exceptionHandler' >>>> aSymbol: #'exceptionHandler' >>>> receiver: aWASharedConfiguration >>>> [8] WASharedConfiguration (WAUserConfiguration) >> at:put: >>>> aSymbol: #'exceptionHandler' >>>> anObject: WAWalkbackErrorHandler >>>> receiver: aWASharedConfiguration >>>> [9] WAWalkbackErrorHandler class >> initialize >>>> receiver: WAWalkbackErrorHandler >>>> [10] MCMethodDefinition >> postload >>>> receiver: aMCMethodDefinition(WAWalkbackErrorHandler class>>initialize) >>>> >>>> >>>> Transcript: >>>> Fetched -> FastCGIPool-dkh.2 --- http://seaside.gemstone.com/ss/fastcgi >>>> --- http://seaside.gemstone.com/ss/fastcgiredirecting to >>>> http://seaside.gemtalksystems.com/ss/fastcgi/FastCGI-dkh.33.mcz >>>> >>>> Fetched -> FastCGI-dkh.33 --- http://seaside.gemstone.com/ss/fastcgi >>>> --- http://seaside.gemstone.com/ss/fastcgi >>>> Fetched -> Seaside-Adaptors-FastCGI-dkh.26 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- >>>> github://glassdb/Seaside31:gemstone3.1/repository >>>> Loaded -> Grease-Core-JohanBrichau.86 --- >>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache >>>> Loaded -> Grease-GemStone-Core-JohanBrichau.52 --- >>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache >>>> Evaluated -> Grease-GemStone-Core >> initializeTransactionMutex1051 >>>> Loaded -> Seaside-Core.gemstone-JohanBrichau.815 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-GemStone300-Core-DaleHenrichs.4 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-GemStone-Core-JohanBrichau.66 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-GemStone-Basic-Development-JohanBrichau.29 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Grease-Tests-Core-JohanBrichau.95 --- >>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache >>>> Loaded -> Grease-Tests-GemStone-Core-dkh.14 --- >>>> http://www.smalltalkhub.com/mc/Seaside/Grease11/main --- cache >>>> Loaded -> Seaside-Component-pmm.101 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-Canvas-pmm.127 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-Email-pmm.25 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-GemStone-Email-JohanBrichau.14 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-InternetExplorer-pmm.7 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-Session.gemstone-JohanBrichau.169 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-GemStone-Session-DaleHenrichs.3 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-RenderLoop-pmm.96 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-Tools-Core.gemstone-dkh.23 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-Flow-pmm.24 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-Examples-pmm.24 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-Widgets-StephanEggermont.35 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-GemStone-Tools-Production-JohanBrichau.15 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-Tools-Web-pmm.119 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> Loaded -> Seaside-GemStone-Tools-Web-DaleHenrichs.4 --- >>>> github://glassdb/Seaside31:gemstone3.1/repository --- cache >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Wed, May 21, 2014 at 3:06 PM, Dale Henrichs < >>>> dale.henrichs(a)gemtalksystems.com> wrote: >>>> >>>>> Marching Orders! Very good ... >>>>> >>>>> Johan, Gerhard, et. al., I want to follow your lead and fill in where >>>>> the work is needed ... >>>>> >>>>> Do you guys think that getting Seaside/Zinc/etc. ported to GemStone3.2 >>>>> takes precedence over getting Zinc running on GemStone3.1? >>>>> >>>>> I can take a crack at solving Gerhard's Seaside3.1 loading error, but >>>>> Zinc has been on the brink for so long, maybe I should hit it hard and get >>>>> the tests passing in GemStone 3.1 (encoding issues are right up my alley:)? >>>>> >>>>> If there are other outstanding problems that folks are looking at they >>>>> can be added into the mix... >>>>> >>>>> Dale >>>>> >>>>> >>>>> On Tue, May 20, 2014 at 10:42 PM, Johan Brichau <johan(a)yesplan.be> >>>>> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> I have been tampering off and on over the last few months to make >>>>>> Zinc 2.4.3 work in Gemstone. >>>>>> >>>>>> I made a pull request [1] with my changes, though not all tests are >>>>>> passing and since most of the changes had to do with encoding, byte arrays >>>>>> vs strings, multibyte strings, etc... I really need someone to take a look >>>>>> at them. Also, the pace is quite slow by myself ;-) >>>>>> >>>>>> This email is just to make sure that the pull request does not go >>>>>> unnoticed for someone wanting to take up work on the port. >>>>>> >>>>>> cheers! >>>>>> Johan >>>>>> >>>>>> [1] https://github.com/glassdb/zinc/pull/48 >>>>>> _______________________________________________ >>>>>> Glass mailing list >>>>>> Glass(a)lists.gemtalksystems.com >>>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Glass mailing list >>>>> Glass(a)lists.gemtalksystems.com >>>>> http://lists.gemtalksystems.com/mailman/listinfo/glass >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Glass mailing list >>>> Glass(a)lists.gemtalksystems.com >>>> http://lists.gemtalksystems.com/mailman/listinfo/glass >>>> >>>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

3 4

How to escape single quotes in generated JSON?
by Mariano Martinez Peck 01 Mar '16

01 Mar '16

Hi guys, I am trying to serialize a dictionary form Smalltalk with either NeoJSON or with Seaside's #asJson. Imagine something like this: | infoDict stream | stream := String new writeStream. infoDict := Dictionary new. * infoDict at: 'exception' put: 'a ''escape this'' aa'.* Note that the string of 'exception' may contain single quotes inside. Then, at some point I do: *self requestContext responseGenerator response nextPutAll: (infoDict asJson).* Problem is the string arrives without any escaping so....when I try to do this at client side from that string: jQuery.parseJSON(variableContainingThatString); I get an error as single quotes inside the double quotes do not seem allowed. I tried a lot of combinations of *"JSON.stringify*" or things like: variableContainingThatString*.replace(/[\\"'']/g, ''\\$&'').replace(/\u0000/g, ''\\0''); * but none work... So..I wonder...can I simply escape this from server side at the time I serialize to JSON? Any special way of doing this or I hack on the resulting string? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

4 4

[ANN] SeasideDynamicVariablesDebugger [WAS] Re: [ANN]: WADynamicVariablesErrorHandler (let me know if I should integrate this)
by Mariano Martinez Peck 29 Feb '16

29 Feb '16

Dear all, This is a quick email to let you know that I pushed the code into it's ow repository with all the needed documentation: https://github.com/marianopeck/SeasideDynamicVariablesDebugger Cheers, On Mon, Dec 7, 2015 at 3:36 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > Dear all, > > For those that have used Seaside, and you try to debug with the Debugger, > you know that upon request processing seaside uses Exceptions mechanism to > always have access to the current request, error handler, etc. The way that > this is done is via subclasses of WADynamicVariable: > > WACurrentRequestContext use: self during: aBlock > > In that case, "self" is the request instance and "aBlock" the closure that > takes care of the request processing. So, inside that closure, everywhere > you do "WACurrentRequestContext value" you get the correct request instance. > > Once inside the debugger, things get complicated. While you can restart, > proceed, etc (because the process you are debugging is inside the scope of > the dynamic variables), you cannot evaluate any piece of code that at the > end use the session or request because you get a WARequestContextNotFound > kind of error. The reason is obvious: The evaluation, do-it, print-it, etc > etc you on a piece of text or via the debugger inspector, creates another > closure/context which is not in the scope of the dynamic variables. > > For a client, we also have custom subclasses of WADynamicVariable, for > example UserContextInformation. And that means that almost every time in > the debugger I really need access to that object. > > To solve that issue, I create a project which is actually a proof of > concept: Check package SeasidePharoDebugging from > http://smalltalkhub.com/#!/~marianopeck/MarianoPublic > It does work for me, and if you think this could be useful for Seaside > itself, I can commit it there. > > The idea is very simple. I have a WADynamicVariablesErrorHandler subclass > of WADebugErrorHandler. We reimplements there #handleException: in order to > simply iterate all values of all dynamic variables (all WADynamicVaraible > subclasses) and store those into a dictionary in a class variable of > WADynamicVariablesErrorHandler. > > Then, I simply override (this is the part that must be cleared if we > integrate this in Seaside) WADynamicVarible >> #defaultAction to be > something like this: > > WADynamicVarible >> #defaultAction > ^ (WADynamicVariablesErrorHandler storedDynamicVariable: self class) > ifNil: [ self class defaultValue ] > > That way... when we handle an exception, we save out all values into a > class side. And then, in the debugger, whenever we evaluate, inspect, print > etc anything that would do a #value over a WADynamicVariable subclass, it > ends up calling #defaultAction (because there will be no handler in the > stack) and there, we first check if the have the value for that dynamic > variable. If we do, we answer that, if not, the defaultValue :) > > There are tests too. There is WACurrentRequestDebuggingTest which you can > try from /tests/seasidepharodebugging > > For the user, there is almost nothing to do. All WADynamicVariable > subclasses are managed automatically. All you need is to register the > exception handler: > > app filter configuration at: #exceptionHandler put: > WADynamicVariablesErrorHandler. > > The only drawback here is that this doesn't work with multiple debuggers > as the last debugger will override the class variable values and hence the > OLD already opened debuggers will be getting a wrong (the latest) value for > the dynamic variables. > > What do you think? I think that while it might not be the best solution > and it has limits, it is every is extremely simple and does the job. > Maybe you see problems I am not seeing? > > Let me know if do you want this integrated or not. In the meanwhile, I am > loading it from my repo for my apps and keeping the override (I would like > to get rid of it!!!). > > Best, > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

1 0

Reef Examples
by recursive68＠gmail.com 19 Feb '16

19 Feb '16

Hi, I'm trying to use REEF but can only find a few limited examples which aren't helping really. Does anyone know for example how I would update a RETextField value when a REButton is clicked ? I found this example someone answered to the query I had but it doesn't work: REForm subclass: #MyForm instanceVariableNames: 'textFieldContents' classVariableNames: '' poolDictionaries: '' category: 'ReefSample1-View'. textFieldContents ^textFieldContents textFieldContents: aString textFieldContents := aString initializeContents self add: (RETextField new on: #textFieldContents of: self). self add: (REButton new label: 'Try me!'; callback: [ self triggerThenDo: [ self inform: self textFieldContents ]]). All it does is generate a dialog box when the button is clicked. I don't know if the inform: method has changed since that was written but either way it doesn't update the textfield value when the button is clicked. Thanks

1 0

Re: [Seaside-dev] Re: Loading 3.2 in Pharo 4:
by Johan Brichau 15 Feb '16

15 Feb '16

Hi, 3.2 is a ‘release candidate’. The thing you hit is one of the reasons it’s still a release candidate. The Seaside-Security package does not work on Windows. I don’t know how you got the first error with WAServerManager though. When I load it the same way you do and start an adaptor, it works as intended. Do you have a bit more stack trace to know where that got sent? For the second error (WAError: no secure key generator availble because seeding failed), do not install ‘Seaside-Security’. If you already did, you can ‘uninstall’ : WASecureKeyGenerator uninstall I think we will just remove it from the OneClick build. Unless Philippe has another idea to fix this? cheers Johan > On 14 Feb 2016, at 17:44, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > I don't know, is Seaside 3.2 even out ? Or is it just development ? > > https://ci.inria.fr/pharo-contribution/job/Seaside/ > >> On 14 Feb 2016, at 16:37, phil(a)highoctane.be wrote: >> >> As I saw the default was an instance of WAServerManager, I removed the contents / contents: and returned default. >> >> This got me the control panel back, I was able to add an adapter. >> >> When I asked for loading the default page, I got >> WAError: no secure key generator availble because seeding failed >> >> Your request could not be completed. An exception occurred. >> >> What's the proper way to load 3.2? Is 3.2 even supported in 4.0? Should I stick to 3.1.x ? >> >> TIA >> >> Phil >> >> >> On Sun, Feb 14, 2016 at 4:31 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >> I tried to load the 3.2: >> >> (ConfigurationOfSeaside3 project version: #'release3.2') load: #('OneClick'). >> >> ... and when accessing the control panel, got an error: >> >> MNU: WAServerManager contents >> >> Version 3.1 loads nicely and control panel works. Just have to add an adapter and start it. >> >> Any idea of what is going south here? >> >> TIA >> Phil >> >> >> >> >> _______________________________________________ >> seaside-dev mailing list >> seaside-dev(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > _______________________________________________ > seaside-dev mailing list > seaside-dev(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

1 0

WAAnchor question
by David 11 Feb '16

11 Feb '16

I am trying to figure out how to make an anchor, with a callback, but with its url pointing to a page element id, so user do not have to scroll back again, for example #content I've tried several things, but can't get this to work. For the example: renderContentOn: html html div id: 'content'; with: [ "Code here" html anchor callback: [ 'example' explore ]; with: 'Clickable'. ] That will render the link in a standard format: /?_s=XXXXX&_k=YYYY&number but I'd need it to render the url with the hash also: Like: /?_s=XXXXX&_k=YYYY&number#content Is there any method I missed out for doing that? P.S. It works when no callback is specified if I say url: '#content', but I need both, the callback, and the page element id anchor. Thanks for your attention P.S.2. I am not subscribed to the list, please CC me in the answers

2 2

Bootstrap datepicker
by Thomas Heniart 07 Feb '16

07 Feb '16

Hi all, For my needs, I wanted a bootstrap datepicker but I didn't found project with. So for a moment I was using the JQDatepicker which works well but is not really nice, so I made one and I just want to share it if someone else wants to use it For the moment this is in development and you won't have all options but I'm still working to improve it and already added all locales library for most of languages To load it you just have to load the configuration of this project: Bootstrap-AddOns <http://smalltalkhub.com/mc/ThomasHeniart/Bootstrap-AddOns/main> and then load development version If you have any question or comment or critics about the code, tell me I really want to improve it ;) Cheers, Thomas

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside February 2016