seaside May 2016

seaside@lists.squeakfoundation.org

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

Seaside 3.2.0 final
by Johan Brichau 16 Aug '17

16 Aug '17

Hi everyone, Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog <https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog> Check out the Github pages for more information: - https://github.com/SeasideSt/Seaside <https://github.com/SeasideSt/Seaside> - https://github.com/SeasideSt/Seaside/wiki <https://github.com/SeasideSt/Seaside/wiki> If you experience issues, do not hesitate to report an issue via Github. Special thanks goes to all those who have helped, tested or contributed in some other way!

14 26

Twitter Bootstrap and Accordion
by Torsten Bergmann 22 Jul '16

22 Jul '16

3 3

Initialisation of componentClass
by Iwan Vosloo 18 Jun '16

18 Jun '16

Hi there, We have an issue related to magritte-seaside. When you set the Component to be used on a MADescription, eg: descriptionThings ^ MAToManyRelationDescription new ... componentClass: MyFancyTableComponent; yourself .. then there is no way (that I am aware of) to initialize the created MyFancyTableComponent in a customised way. In the example above, for instance one may have a MyFancyTableComponent that divides its items into several pages (like an MAReport would do). The number of items displayed per page has to be hard-coded in MyFancyTableComponent. It would be nice to have a way to initialize a newly created instance, something like: descriptionThings ^ MAToManyRelationDescription new ... componentClass: MyFancyTableComponent; initializeComponent: [ :newlyCreatedComponent| newlyCreatedComponent itemsPerPage: 40 ]; yourself There are, of course, several ways one could do this. I am not necessarily suggesting the above example as the way to do it... I am just illustrating the point. If you do not have such a mechanism, the only thing you can do is subclass MyFancyTableComponent with the express motivation - to be able to set a new instance up a certain way. We have a log of code that does this sort of subclassing. It makes things go really messy eventually. We'd like to get rid of all those subclasses and rather let the user of a component 'configure' it appropriately. Building something like what I am proposing means changes to magritte-seaside code though. So, if we do it we'd prefer to contribute upstream. Has anyone else come across this issue? Any ideas? Worthwhile to others too? Regards - Iwan -- Reahl, the Python only web framework: http://www.reahl.org

4 5

ConfigurationOfMaterialDesignLite - Pharo5 not yet working
by Sabine Manaa 25 May '16

25 May '16

Hi Mervan, Kevin, Olivier, I was just trying to load my code in Pharo5 and get an error when loading MDL with the following spec: project: 'materialdesignlite' with: [ spec className: #ConfigurationOfMaterialDesignLite; version: #development; repository: 'http://smalltalkhub.com/mc/KevinLanvin/MaterialDesignLite/main' It seems that MDLColor is not yet loaded. Could you please look for that? Regards Sabine Stack UndefinedObject(Object)>>doesNotUnderstand: #indigo MDLComponentsDemoApplication>>initialize MDLComponentsDemoApplication class(GRObject class)>>new MDLComponentsDemoApplication class(MDLApplication class)>>newApplicationNamed: MDLComponentsDemoApplication class>>initialize MCMethodDefinition>>postloadOver: [ :each | each postloadOver: (self obsoletionFor: each) ] in MCPackageLoader>>basicLoadDefinitions in Block: [ :each | each postloadOver: (self obsoletionFor: ...etc... [ :each | | newLabel | "Special handling for first and last element" (count = 0 or: [ count + 1 = size or: [ (Time millisecondsSince: lastUpdate) >= msecs ] ]) ifTrue: [ bar current: count. oldLabel = (newLabel := (labelBlock cull: each) ifNil: [ oldLabel ]) ifFalse: [ bar label: newLabel. oldLabel := newLabel ]. lastUpdate := Time millisecondClockValue ]. aBlock value: each. count := count + 1 ] in [ :bar | labelBlock := aStringOrBlock isString ifTrue: [ bar label: aStringOrBlock. [ :dummyItem | aStringOrBlock ] ] ifFalse: [ aStringOrBlock ]. self do: [ :each | | newLabel | "Special handling for first and last element" (count = 0 or: [ count + 1 = size or: [ (Time millisecondsSince: lastUpdate) >= msecs ] ]) ifTrue: [ bar current: count. oldLabel = (newLabel := (labelBlock cull: each) ifNil: [ oldLabel ]) ifFalse: [ bar label: newLabel. oldLabel := newLabel ]. lastUpdate := Time millisecondClockValue ]. aBlock value: each. count := count + 1 ] ] in OrderedCollection(Collection)>>do:displayingProgress:every: in Block: [ :each | ... OrderedCollection>>do: [ :bar | labelBlock := aStringOrBlock isString ifTrue: [ bar label: aStringOrBlock. [ :dummyItem | aStringOrBlock ] ] ifFalse: [ aStringOrBlock ]. self do: [ :each | | newLabel | "Special handling for first and last element" (count = 0 or: [ count + 1 = size or: [ (Time millisecondsSince: lastUpdate) >= msecs ] ]) ifTrue: [ bar current: count. oldLabel = (newLabel := (labelBlock cull: each) ifNil: [ oldLabel ]) ifFalse: [ bar label: newLabel. oldLabel := newLabel ]. lastUpdate := Time millisecondClockValue ]. aBlock value: each. count := count + 1 ] ] in OrderedCollection(Collection)>>do:displayingProgress:every: in Block: [ :bar | ... BlockClosure>>cull: [ ^ block cull: self ] in [ self prepareForRunning. CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in Block: [ ^ block cull: self ] [ p psValueAt: index put: anObject. aBlock value ] in CurrentJob(DynamicVariable)>>value:during: in Block: [ p psValueAt: index put: anObject.... BlockClosure>>ensure: CurrentJob(DynamicVariable)>>value:during: CurrentJob class(DynamicVariable class)>>value:during: [ self prepareForRunning. CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in Block: [ self prepareForRunning.... BlockClosure>>ensure: Job>>run MorphicUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: OrderedCollection(Collection)>>do:displayingProgress:every: OrderedCollection(Collection)>>do:displayingProgress: MCPackageLoader>>basicLoadDefinitions [ self basicLoadDefinitions ] in [ self handleLoadErrorsDuring: [ self basicLoadDefinitions ] ] in MCPackageLoader>>basicLoad in Block: [ self basicLoadDefinitions ] BlockClosure>>on:do: [ aBlock on: InMidstOfFileinNotification do: [ :notification | notification resume: true ] ] in MCPackageLoader>>handleLoadErrorsDuring: in Block: [ aBlock... BlockClosure>>on:do: MCPackageLoader>>handleLoadErrorsDuring: [ self handleLoadErrorsDuring: [ self basicLoadDefinitions ] ] in MCPackageLoader>>basicLoad in Block: [ self handleLoadErrorsDuring: [ self basicLoadDef...etc... -- View this message in context: http://forum.world.st/ConfigurationOfMaterialDesignLite-Pharo5-not-yet-work… Sent from the Seaside General mailing list archive at Nabble.com.

2 2

Re: [Seaside] Seaside 3.2.0 final
by Johan Brichau 15 May '16

15 May '16

Hi Sanjay, This was indeed a problem with the ConfigurationOfSeaside3. I fixed it and uploaded a new version of the configuration. When you use that one to load Seaside in your image, the jQuery examples should be loaded. Thanks for spotting this! cheers Johan > On 15 May 2016, at 08:16, Sanjay Minni <sm(a)planage.com> wrote: > > Hi Johan, > > the links to examples on JQuery, JQueryUI on Seaside 3.2 welcome page (bottom right panel) are not working. I tried creating the related dispatcher entries but somehow could not make it work. > > You may like to look into this > > regards > Sanjay > > --- > Sanjay Minni > +91-9900-902902 > > On Thu, May 5, 2016 at 7:51 PM, Johan Brichau <johan(a)inceptive.be <mailto:johan@inceptive.be>> wrote: > Hi everyone, > > Seaside 3.2.0 is now final: > https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog <https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog> > > Check out the Github pages for more information: > - https://github.com/SeasideSt/Seaside <https://github.com/SeasideSt/Seaside> > - https://github.com/SeasideSt/Seaside/wiki <https://github.com/SeasideSt/Seaside/wiki> > > If you experience issues, do not hesitate to report an issue via Github. > > Special thanks goes to all those who have helped, tested or contributed in some other way! > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org <mailto:seaside@lists.squeakfoundation.org> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside <http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside> > >

1 0

Re: Infinite Scrolling
by Paul DeBruicker 11 May '16

11 May '16

Hi Sabine, Oh you're right that is an integral part. Sorry I left it out earlier. It looks like this: renderMoreItems: someResults from: aRequest at: anId on: html | itemsToRender | itemsToRender := self checkMoreResultsComplete: someResults. itemsToRender isNil ifTrue: [ html script: (((html jQuery id: anId) registeredInterval) delay: 2 seconds; func: (html jQuery ajax script: [ :s | s << ((s jQuery class: 'results:visible:last') replaceWith: [ :h | self renderMoreItems: someResults from: aRequest at: anId on: h ]) ])). (html div) class: 'results'; with: [ html heading level2 with: [ html render: 'waiting for results .... '. html image resourceUrl: '/img/icon-loader.gif' ] ] ] ifFalse: [ html script: (html jQuery id: anId) registeredInterval. itemsToRender := itemsToRender copy select: [ :each | self filterItem: each ]. itemsToRender isEmpty ifTrue: [ self renderNoMoreItemsError: html ] ifFalse: [ self renderItems: itemsToRender on: html self renderEndlessScroll: html with: aRequest with: anId ] ] The someResults object is a future from http://www.squeaksource.com/Futures.html. The #registeredInterval script is just a throwaway script that creates creates a js setInterval and stores it in the DOM to poll whether the future has results or not. Sending it with no arguments clears the interval. If I were writing it again I'd just use setTimeout to do the polling. But thats all orthogonal to your question. Hope this helps Paul Sabine Manaa wrote > Hi Paul, > > thanks for sharing. I try to use it. > > I think there is a typo in > > method > ^'endessScroll' > ==> 'endlessScroll' > > Could you please send me a piece of code what your >>> self renderMoreItems: moreItems from: aRequest at: id on: h > does? > > Regards > Sabine -- View this message in context: http://forum.world.st/Infinite-Scrolling-tp4821669p4894337.html Sent from the Seaside General mailing list archive at Nabble.com.

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 May 2016