seaside December 2015

seaside@lists.squeakfoundation.org

16 participants
17 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: 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

TableReport slow down
by Hilaire 02 Jan '16

02 Jan '16

Hello, I am experiencing a slow down rendering a large table report: The table report is more than 240 lines. Reading at the source html, it is about 900 bytes per lines, so a bit more than 200kB for the report. Not much for the rest of the page. The page renders in a bit more 5s, on a local loop. Profiling shows most of time is spent in WideString>>at:put: For me 200KB is not that big and this slow down does not look normal. Seaisde is 3.1.3.2 Smalltalk is Pharo3 CPU is double core intel 800Mhz-2000Mhz VM is 3.9-7 The profiling tree is as shown in the screenshot. Thanks Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu

5 16

make WAWalkbackErrorHandler
by Esteban Lorenzano 24 Dec '15

24 Dec '15

Hi, So, I’m in Togo teaching Pharo and Seaside to students, and part of the course is to make a small application (they have 3 days for doing it). The first blocking issue they have is that since default error handler is WAHtmlErrorHandler they are lost each time they made a simple mistake (WAHtmlErrorHandler eats rendering problems, for example… or just shows DNU without saying anything. And of course showing the students the configuration interfase is overkill :) Now, since the default registration includes the toolbar, meaning than by default we have a “development app” (A correct approach, IMO), I wonder if we couldn’t put WAWalkbackErrorHandler as default as well? (I remember previous versions of Seaside had it, but it had changed since then). cheers, Esteban

3 3

Setting Up Pharo and Seaside on the Digital Ocean ISP
by Bruce Prior 11 Dec '15

11 Dec '15

I am looking for a procedure that would load Pharo and Seaside into Digital Ocean. I have worked through Sven Van Caekenberghe's tutorial in setting up a simple website on Digital Ocean and that worked great. But I would like to run Seaside there, too. TIA, Bruce

3 3

oops
by Robert Withers 11 Dec '15

11 Dec '15

1 0

Hi everyone
by Robert Withers 11 Dec '15

11 Dec '15

So sorry for missing out on your progress. Best, Robert

1 0

Re: [Pharo-users] Datatables
by Mariano Martinez Peck 08 Dec '15

08 Dec '15

Hi guys, Pablo was asking about Datatables which is a JS plugin, not databases :) Pablo, In Smalltalk hub there are a couple of DataTables projects. It would be interesting to know which one is the "official". Second, please ask in Seaside mailing list. For my client, I forked the original DatatablesFileLibrary because I needed extra plugins. And then, I simple used JS. So the steps are simply add the file library into the libs of your app. Then render some html table. Finally, invoke some JS. Either from jQuery or from normal JS. Note that I can imagine that some of the Datatables found in Smalltalkhub should have examples. Check them out. Something like this (it's full of domain stuff and probably I am copy pasting with errors but will help you to get the idea): 1) Register lib to app: app addLibrary: DataTablesFileLibrary (or whatever class name is it) 2) Then render table and container (whatever you want, however you want...you simple need a container and a table). containerDiv := html div. containerDivId := containerDiv ensureId. containerDiv class: 'reportContainer'; with: [ html table id: self tableId; with: [ self renderTableOn: html. ]. *html script: (FaDataTablesHelper datatablesScriptFor: tableID tableHeightString: '"scrollY": (0.80 * $(window).height()),' containerDivId: containerDivId). * The magic here is that to the generated table you pass via #script: the Datatables JS. 3) Generate datatables JS: FaDataTablesHelper class >> datatablesScriptFor: tableID tableHeightString: aTableHeightString containerDivId: aContainerDivId ^ ' $(document).ready(function() { var getCellText = function (elem) { //get only the element text return elem.contents().filter(function() { return this.nodeValue; }).text(); }; // this is so that the table does not use all the height space and hence the horizontal scroll looks outside the empty space. // By default, we make the table a max height of a % of the windows. var oTable = $(''#', tableID asString ,''').DataTable( { ', aTableHeightString, ' "scrollX": "100%", "scrollCollapse": true, "paginate": false, "stateSave": false, "stateDuration": -1, "destroy": true, "filter": false, "ordering": false, "searching": false, "sort": false, "orderClasses": false, "autoWidth": false, "jQueryUI": false, // J: ColResize. // I: ColPin. It needs ColReorder. // R: ColReorder // "dom": ''C<"clear">Rt'', "dom": ''t'', // colVis: { // label: function (index, title, th) { // return $(''a[href]'', th).text() || getCellText($(th)); // } // }, // this is in case I want to use the paginate for the Scroller "iDisplayLength": -1 } ); // oTable.colResize.init({fixedLayout: true, dblClick: ''matchContent''}); // Previosuly it was the below line, but this is bad...because if the widths of the columns keep fixed // all along the session, we may wast a lot of space because columns were kepts with its original width... // and when filtering, sorting, etc..the width of the column changes to better adjust its width needs..." // Check if body width is higher than window width :) if ( $(''#', tableID asString ,''').width() > $("#', aContainerDivId,'").width() ) { // Add default fixedColumns // oTable.colPin.init({ // fixedColumns: { // leftColumns: 1, // rightColumns: 1, // heightMatch: ''auto'' // } // }); new $.fn.dataTable.FixedColumns( oTable, { leftColumns: 1, rightColumns: 1 } ); }; //table is bigger than container }); // document on load '. This point 3) depends completely on how you want to use Datatables. Read it's documentation in order to know what you need/want. Also..use the Developer Tools of the browser (console) since you may have missing plugins, or wrong JS code etc. That console will be your friend until you make it work. Cheers, On Sat, Dec 5, 2015 at 11:25 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > I have used this datatable package in Seaside in my app. > > MCSmalltalkhubRepository > owner: 'GastonDallOglio' > project: 'DataTables' > user: '' > password: '' > > For the examples, looking at the Datatables JS API was helpful. The > version was the older one. > > You can use it like this (there is some bootstrap mixed in) > > html tbsTable > beStriped; > beHover; > script: ((html jQuery new dataTable) bFilter: false; bPaginate: false; > bInfo: false); > class: 'table-responsive'; > with: [ > html tableHead with: [ > html tableHeading with: 'ID' seasideTranslated . > html tableHeading with: 'MAC' seasideTranslated . > html tableHeading with: 'IP' seasideTranslated . > html tableHeading with: 'Status' seasideTranslated > ]. > .... > > > > On Sat, Dec 5, 2015 at 9:09 AM, stepharo <stepharo(a)free.fr> wrote: > >> You can use >> - Voyage to access MongoDB read the entreprise Pharo book >> - Garage for relational databases. >> >> http://pharo.org/news/garage-database >> Stef >> >> >> Le 4/12/15 15:58, Pablo R. Digonzelli a écrit : >> >> Hi, I am interesting in using Datatables in a Seaside app. >> I know there is wrapper fot this in StHub. Is there is examples how to >> use it? >> >> >> TIA >> >> ------------------------------ >> *Ing. Pablo Digonzelli* >> Software Solutions >> IP-Solutiones SRL >> Metrotec SRL >> 25 de Mayo 521 >> San Miguel de Tucumán >> Email: pdigonzelli(a)softsargentina.com >> pdigonzelli(a)gmail.com >> Cel: 5493815982714 >> >> >> > -- Mariano http://marianopeck.wordpress.com

1 0

Split form
by J.F. Rick 08 Dec '15

08 Dec '15

Hi, I'm creating a web interface using seaside that's a bit complicated. One particular annoying part is that I have to use multiple forms: (1) Form 1 contains some fields (2) Form 2 is used for uploading images asynchronously (3) Form 3 contains more fields that really belong to Form 1. Because of layout and because forms can't be within other forms, I have to have both Form 1 and 3, though really they should be the same form that uses one submit button. Is there a good way to combine the forms in such a way that the callbacks for both forms are evaluated? I did notice that the _k are identical for both forms. Cheers, Jeff

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside December 2015