seaside-dev May 2017

seaside-dev@lists.squeakfoundation.org

10 participants
12 discussions

"Bootstrap" project for Seaside with separated Magritte support in a new project "BootstrapMagritte" on STHub
by Torsten Bergmann 16 Jul '18

16 Jul '18

Hi, The bundling with magritte polluted the repo and the Bootstrap project with stuff that was not really needed for "Seaside + Bootstrap" only. Also a "Bootstrap-Demo" package appeared that was more a demo for magritte than for Bootstrap. Since there already was an "Bootstrap-Examples" package this added more confusion (at least on my side). I now took action and cleaned up the Bootstrap project again to remove the magritte stuff. If one wants to to use Bootstrap with Seaside he does not necessarily have to go the Magritte path, so IMHO this was necessary. The magritte stuff for Bootstrap is now hosted as an own separate project on STHub which would also help to see to which part code additions really belong. As a result: ============ 1. The Bootstrap project now again only contains and loads the initial three packages: - Bootstrap-Core - Bootstrap-Tests-Core - Bootstrap-Examples assembled by the known ConfigurationOfBootstrap 2. The Magritte support on top of Bootstrap is now separated in an own project to avoid too much mixin. See "BootstrapMagritte" on SmalltalkHub. The new repo "http://smalltalkhub.com/#!/~TorstenBergmann/BootstrapMagritte" has the same commiters as the old one, so feel free to continue with your work. This project includes two packages: - Bootstrap-Magritte-Core (former Bootstrap-Magritte) - Bootstrap-Magritte-Examples (former Bootstrap-Demo) assembled by a new ConfigurationOfBootstrapMagritte for this particular project 3. The Bootstrap/ConfigurationOfBootstrap is now available as - a release version 0.4.0 for Seaside 3.0.9 - a release version 0.5.0 for Seaside 3.0.10 - a release version 0.6.0 for Seaside 3.1.0 (#stable) - a development version 0.7.0 for Seaside 3.1.0 for new stuff 4. The CI for Bootstrap is green for Pharo 2.0 and now also Pharo 3.0 5. The config browser is updated for Pharo 2.0 and Pharo 3.0 with the "Bootstrap" package So you can now also open a fresh Pharo 3.0 image, open World menu -> Configuration Browser to load "Bootstrap". Then run ZnZincServerAdaptor startOn: 8080 and start coding your web application with the latest Seaside 3.1.0. Next steps: Setting up a CI for the new project "BootstrapMagritte"/ConfigurationOfBootstrapMagritte Have fun! Bye Torsten

3 7

Grease and Seaside github primary codebase?
by Johan Brichau 05 Jun '17

05 Jun '17

Hi guys, We have been using the Smalltalkhub repository as the primary repository until now. The most recent version of Grease (1.3.0) is only on github at this time. However, I would prefer using the github repos as the main repositories because it supports branching a lot better than MC and it offers the ability for people to fork their own version and pull their changes back in a ‘controlled’ way (i.e. reviewed pull requests). The work on git for Pharo (Iceberg) is advancing very well. Although not entirely stable at this time, everybody can already use git repos for smalltalk by means of the filetree format in MC. We have also been using git repos for Smalltalk in the GemStone/S universe for years now. Once we start using git for development, we can still copy the packages back to an MC repository, although that’s something I would want to avoid as well. I would simply update the ConfigurationOf and have it refer to the github repos for the new versions on the latest platform versions. What do you all think? cheers Johan

4 5

Seaside dev on Slack
by Johan Brichau 31 May '17

31 May '17

Hi all, We set up a Slack channel. https://seaside-st.slack.com/ <https://seaside-st.slack.com/> Join us if you like cheers Johan

4 6

WATagBrush>>#tag should be class side?
by Esteban A. Maringolo 30 May '17

30 May '17

I'm playing with a small utility that walks the canvas and the hierarchy of WATagBrush, and one thing I find is that #tag method is implemented on the instance side, whilst the class side requires a new instance to obtain the HTML tag name. In most cases this isn't an issue since brushes are simple, but in the case of WABasicFormTag it tries to get the encoding from the request context and you fail to obtain the tag unless within a context. Since the returned value doesn't change based on conditions of the brush [1], shouldn't #tag be implemented class side and instances delegate to the class by default and implement only if necessary? As far as I could see the change would be idempotent, even third party subclasses of WATagBrush would continue to work if they don't implement #tag class-side. What do you think? Esteban A. Maringolo [1] The only case I found is the heading tag, that uses h1, h2, h3, etc.;and it would continue to work.

4 5

GRDynamicVariable implementations for VW and VASt
by Max Leske 27 May '17

27 May '17

Hey, I've whipped up implementations for GRDynamicVariable in VW and VASt (see links below). The implementations are based on the older version of the current Pharo implementation (i.e. they use the class as as key opposed to a singleton instance). I don't know how VW and VASt pick up changes. Do we e-mail them changesets or something? Cheers, Max VW: https://www.dropbox.com/s/09kw4piw7iexzeh/GRDynamicVariable_VW.st?dl=0 <https://www.dropbox.com/s/09kw4piw7iexzeh/GRDynamicVariable_VW.st?dl=0> VASt: https://www.dropbox.com/s/y5lmzchf2i0oyxc/GRDynamicVariable_VASt.st?dl=0 <https://www.dropbox.com/s/y5lmzchf2i0oyxc/GRDynamicVariable_VASt.st?dl=0>

5 8

GRSmallDictionary2 and GROrderedMultiMap2
by Johan Brichau 27 May '17

27 May '17

Hi Philippe, I noticed you worked on new versions of GRSmallDictionary and GROrderedMultiMap. For now, they are unused? cheers Johan

2 1

Global Seaside re-initialization
by Esteban A. Maringolo 26 May '17

26 May '17

Hi all, I loaded Seaside 3.2 on top of the previously loaded 3.1 in VW and now everytime I try to access an application I'm getting errors of the kind of the one in the following stack: Message not understood: #keyFromContext: Seaside.WAQueryFieldHandlerTrackingStrategy class(Object)>>doesNotUnderstand: Seaside.WAApplication(Seaside.WARegistry)>>handleFiltered: Seaside.WAApplication>>handleFiltered: Seaside.WAExceptionFilter(Seaside.WARequestFilter)>>handleFiltered: optimized [] in [] in Seaside.WAExceptionFilter>>handleFiltered: BlockClosure>>on:do: For some reason the configuration is returning the class of the tracking strategy instead of an instance. I could create a new image from scratch, but I'd like to know how to reset everything, since most initializations are automatically executed by class side #initialize method. Regards! Esteban A. Maringolo

3 3

Updated Seaside Control Panel for Pharo 6 / Seaside 3.2
by Sven Van Caekenberghe 25 May '17

25 May '17

Hi, I updated the Seaside Control Panel for Pharo 6 / Seaside 3.2. As far as I can see, it works fine now. I don't know the exact procedure to get this into Seaside proper, hence I include the MC package. It is obviously important to get this in before we release Pharo 6, but it is probably also a good idea that somebody else has a look at what I did. === Name: Seaside-Pharo-Tools-Spec-SvenVanCaekenberghe.20 Author: SvenVanCaekenberghe Time: 24 May 2017, 4:17:49.490067 pm UUID: b1168881-a70c-0d00-9de6-8d500cd45859 Ancestors: Seaside-Pharo-Tools-Spec-JohanBrichau.19 Updated the Seaside Control Panel for Pharo 6 / Seaside 3.2 using latest Spec conventions - Add a refresh button to the main toolbar to sync with changes done outside the UI (add a #refreshAdaptors action and use it for add/remove updating as well) - Inform the user when remove fails due to a still running adaptor - Use IconListModel instead of NewListModel - Fix selection maintenance on the list of adaptors - Fix the context menu on the list of adaptors - Use new recommended icon access method - Added help strings to the buttons in the main toolbar - Added a proper About text - Add a window icon - Remove unused state/action stuff from the toolbar implementation === Sven PS: The 'Spec UI Framework' book was helpful as was Nicolai's help on the ML - Thank you.

5 9

Grease tests for subStrings
by Johan Brichau 25 May '17

25 May '17

Hi, First step to release a new version of Seaside, is to release the development version of Grease. Working on that, I notice: With Pharo 6, the method #subStrings: was renamed to #substrings: However, there is a test in Grease-Tests-Core that verifies the behavior of #subStrings: If I change that test to use #substrings:, it means Grease expects all dialects to implement a #substrings: method. My idea is that: - either the dialect indeed implements that method - Grease-specific dialect packages implement it when necessary Philippe, I notice you already factored-out any sends of those methods in the dev version of Seaside. Does it make sense to keep the test in such a case? Opinions? Johan

3 2

Re: [Seaside-dev] Seaside dev on Slack
by Johan Brichau 25 May '17

25 May '17

Hi Reg, I think Slack only works by invitation. The intention is to use it only for communication on development. So, if you intend to develop on any of the seaside projects, please send us your email. For any other questions, I prefer we keep using the users mailinglist. I don’t want all Seaside users on the Slack channel. I hope you understand. best Johan > On 25 May 2017, at 16:31, Reg Krock <reg.krock(a)gmail.com> wrote: > > Hi Johann, > > How do I sign up to be able to join the slack seaside group? > > Thanks > > Reg > >> On 25 May2017, at 9:09 AM, Johan Brichau <johan(a)inceptive.be <mailto:johan@inceptive.be>> wrote: >> >> Hi all, >> >> We set up a Slack channel. >> >> https://seaside-st.slack.com/ <https://seaside-st.slack.com/> >> >> Join us if you like >> >> cheers >> Johan >> _______________________________________________ >> seaside-dev mailing list >> seaside-dev(a)lists.squeakfoundation.org <mailto:seaside-dev@lists.squeakfoundation.org> >> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev May 2017