seaside October 2015

seaside@lists.squeakfoundation.org

22 participants
18 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

WAComponent to PDF
by Hilaire 05 Nov '15

05 Nov '15

Hello, I would like to render WAComponents as PDF documents. I took at look at Artefact, but it is an important work to render again the data as PDF with Artefact, not to mention I feel it is a duplicated work. Moreover, I have quite long documents spanning over several pages, some of my tables are complex with some columns spanning over 2 or 3 columns and I have about 50 different documents to turn as PDF file. Now I am think about rendering these components on dedicated pages, then using wkhtmltopdf. What I would do is get these components rendered at dedicated urls, then call wkhtmltopdf with these urls as arguments. Practically how will you do that? How to forge an URL for a page rendering the component with a dedicated decoration for PDF conversion (dedicated css, header, footer)? My initial though is REST. Is it the right direction? Or are there other options? Thanks for tips, enlightenment or thought on the matter. Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu

6 13

Re: WAComponent to PDF
by Torsten Bergmann 02 Nov '15

02 Nov '15

Otto Behrens wrote: >We took all our CSS out of Seaside and put it on disk. We use less and >what not to "compile" it and get the web server to produce it. Mainly >because 1. Seaside is too heavyweight to serve (dynamically created) >CSS up as well as the HTML and 2. The tools are a but scrappy to deal >with CSS properly (but would be nice if we had a Seaside-like library >that helps with CSS). Did you check: http://gcotelli.github.io/RenoirSt for Pharo? Bye T.

3 2

still struggling with the confusing scripting API's
by Chris Muller 31 Oct '15

31 Oct '15

I'm still trying to get my head around "what is the best way to write javascript in Seaside. I just spent an entire morning and still failed to write the simplest expression via an aggregation of Seaside's JSDecoration's. This is what I want to render: new MyJavascriptObject(document.getElementById("id1")) Using Seasides various brushes and canvas API, I could not even get the first two words right. I tried: html script with: (html javascript create access: 'MyJavascriptObject')) html script with: (html javascript create add: 'MyJavascriptObject')) html script with: (html javascript create alias: 'MyJavascriptObject')) html script with: (html javascript create assign: 'MyJavascriptObject')) None of those produce "new MyJavascriptObject", what am I missing? Its almost like there is a missing JSDecoration or capability missing from JSStatement..? After throwing up my hands with that, I decided to try "hard coding" the Javascript strings into my Seaside rendering methods: html script with: (html javascript script: [ : s | s add: 'new MyJavascriptObject(document.getElementById("', (aPufDomainComponent htmlId),'") ]) which produces: new MyJavascriptObject(document.getElementById(\"id1\") So that is pretty much what I want, but see that it is escaping the quote characters, which makes it hard to read in the browser. Are those necessary or is there some way to avoid that? I wanted to avoid having to put big chunks of hardcoded Javascript strings into my Smalltalk code. Any advice is appreciated. - Chris PS -- I think the inconsistency of the API is part of my struggle. JSObject script: can accept a Block, and WAHtmlCanvas>>#script: SAYS it takes "aBlock", but that HAS to be wrong, because WAScriptTag>>#with: ends up writing the Block's "greaseString" to the stream... thanks.

3 4

The SushiShop
by Damien Cassou 30 Oct '15

30 Oct '15

Hi, is the SushiShop Seaside example application still available anywhere? Is there a modern version somewhere? Thanks -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

3 3

Objects on demand for big collections
by Oswall Verny Arguedas C. 29 Oct '15

29 Oct '15

It will be possible to load objects on demand (for a list or html table) to avoid unnecessary objects and load ?.To page sending large lists of objects from the server to the client. I use Pharo 4 and Seaside 3.2 on linux ubuntu. ThanksOswall

3 2

Seaside, JWT and REST
by Sebastian Heidbrink 21 Oct '15

21 Oct '15

Hi! I have a working JWT (JsonWebToken) protected Zinc based REST server. I do also have a Seaside server as a user platform. Now I would like to integrate some results of the REST interfaces of the Zinc based server into my seaside frontend. How would I define an ajax call including a JWT token in Seaside that populates a table rendered by seaside on/after page load? Thank you for any ideas! Sebastian

2 3

Encoding on saving html file
by Dave 20 Oct '15

20 Oct '15

Hi folks, I've an encoding issue when saving an html page. The page has some strings with accented letters like: è or é and so on. I save the page retrieving the stream doing: html context document stream contents but every accented char is wrong encoded. Can you help me? Thanks Dave -- View this message in context: http://forum.world.st/Encoding-on-saving-html-file-tp4856116.html Sent from the Seaside General mailing list archive at Nabble.com.

3 10

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside October 2015