seaside March 2013

seaside@lists.squeakfoundation.org

30 participants
33 discussions

using CSS for default Magritte-Editors
by Stefan Krecher 14 Mar '13

14 Mar '13

Hi, i have a main-component where i overwrite updateRoot to inject some css. On the main-page, i render a list of domain-objects, every domain-object gets an "edit"-link. By pressing edit, i construct a component (-> descriptions asComponentOn: aMitarbeiter). The component will be rendered via self call: component. To inject css in the resulting editor, i add a custom MAFormDecoration (with an overwritten updateRoot:). Now i have the editor for that domain-object. The domain-object has a one-to-many-relationship to another domain-object, it is modelled like this: descriptionHistorieArbeitsbereiche ^MAToManyRelationDescription new classes: (Array with: HistorieArbeitsbereiche); accessor: (MAPluggableAccessor read:[ :mitarbeiter | mitarbeiter historieArbeitsbereiche ] write: [:mitarbeiter :historieArbeitsbereiche | mitarbeiter historieArbeitsbereiche: historieArbeitsbereiche]); label: 'Arbeitsbereiche'; default: #(); priority: 500; beSorted; cssClass: #historieArbeitsbereiche; reference: (HistorieArbeitsbereiche descriptionArbeitsbereich); yourself The problem is, that i have no idea, how to inject css in the resulting editor (when i click on "edit" or "add"). Is there a way to inject an link to a css into the header of _every_ page that is rendered? If i use call: to render a component, the calling component gets replaced (including the <header> section). If a magritte-editor is redered via a OneToMany-Relationsip i don't seem to have access to the header-section of the resulting html (i only could use a custom renderer - here i could try to load css from the <body>-section of the page - but that seems do be no clean way. thx and regards, Stefan

2 1

Re: GSoC13: Distributed Issue Tracker
by Stephan Eggermont 12 Mar '13

12 Mar '13

Göran wrote: >Would you like me to dig out the Gjallar codebase and share it with you? >With some annotations? There should be lots to pick/learn from it. I have a Gjallar0.4 image here. Any changes since then? Stephan

2 1

GSoC13: Distributed Issue Tracker
by Stephan Eggermont 12 Mar '13

12 Mar '13

Distributed Issue Tracker Level: (intermediate, advanced) Possible mentor: Stephan Eggermont Possible second mentor: Diego Lont Description A native smalltalk distributed issue tracker. It should have basic issue tracking functionality including attaching files/pictures/code. It should have a native interface, a web interface and a scripting API. Primary development is in Pharo. Issue trackers have different kind of users. To make clear that different users have different needs, persona can be helpful. Isabelle is an information technology student looking for an interesting language and environment to learn. She wants to contribute to and learn from a smart community and needs interesting experiences on her cv. She has already learned the basics of a few mainstream languages and feels ready to try something more exotic. Smalltalk seems interesting as the origin of many inventions. Yann is the major developer of a web-based platform based on Pharo and Seaside. He needs to ensure the platform keeps working smoothly and is updated regularly with the latest changes. In production he uses the released versions. He fears the major clean-ups Pharo is making make it difficult for him to keep up. He is dependent on a few old unmaintained squeaksource packages. Janine just found an interesting old package on squeaksource. It was last changed in 2007. She has been using smalltalk for a few years, so knows what to expect when trying to load an unmaintained package. There are some missing classes that still exist in squeak. Tony is the developer of a package that is used with nearly all smalltalks. He mainly works with a commercial smalltalk and keeps just enough contact with the Pharo community to keep his package working. He has complained about some changes that made it necessary for him to change his package structure. He mainly updates the Pharo version on his way to and from the office in the train. Eve maintains a few of the crucial Pharo kernel packages. They are under heavy development and once in a while everything breaks, leading to a flood of issues. They mostly come from outsiders, as she talks daily with the Pharo core team. She has to close a lot of them as duplicates. She also has to review code that gets attached in one form or another to the issue. Daniel is a maintainer of the vm that forms the basis for the Pharo vm. The vm is used by many more projects. Lara is a release manager for a well known linux distribution. Pharo is just one of 30 languages that are included in the distribution. Before doing a release she scans the issue tracker for any show stoppers. She had to stop including environments because of security issues. Technical Details The recent decision by Google to deprecate and stop its API for the Google Issue Tracker used by a.o. the Pharo, Seaside, MOOSE and Metacello projects makes it necessary for those projects to select a different issue tracker. The timespan before this decision has to be made is too short for the development of a new issue tracker from scratch. Now most development in Smalltalk uses distributed version control systems, either Monticello or Git, the question arises why these projects still would want to use a centralized issue tracker. The long-standing problems in keeping squeaksource up-and-running are only one example of the problems of depending on centralized infrastructure. Other examples are the move of Lukas' repository and the number of times where the Pharo CI infrastructure was not available, especially on holidays and weekends. The currently used issue trackers cannot work disconnected. Integrating the issue tracker in the CI workflow of the projects is crucial. The goals of the persona should be translated into a storymap. Delivery should be iterative and incremental, driven by value to the community and technical risk. The student is expected to be active on the mailing list and discuss development there. This includes handling (source) contributions by others. There is a small prototype available. Benefits to the Student - getting to know the difficulties of issue tracking/the workflow of open source projects - experience with distributed systems - experience an agile open source environment Benefits to the Community - better integrated workflow - native issue tracker, accessible both in-image, web and automated - showcase for productive environment Questions Here are seven persona. Which ones are missing/should be fleshed out?

2 1

GSoC13: Google Summer of Code started, your ideas please!
by Janko Mivšek 09 Mar '13

09 Mar '13

Dear Smalltalkers, Time for your cool project ideas on this year Smalltalk GSoC! For now just express any idea you have here on the mailing list. Later we will together develop it to be in complete format together with two mentors needed. Deadline is end of Mart, so we have three weeks of time. To see how fully developed ideas look like please look at 2012 ones at: http://gsoc2012.esug.org/ideas. Note also that students yourselves can propose a GSoC project. So if you like to be a student on this year GSoC and have a nice idea, don't be shy and propose it here! The community will listen you and guide to the really nicely proposed project. Last year 6 student proposed projects were accepted and finished successfully! For the community, start looking around for students. Think about how to approach the universities near by you, do you know who to contact there, etc. We are namely preparing an application to this year Smalltalk Google Summer of Code under ESUG umbrella, as last year. If accepted, Google will pay few stipendiums to students on our Smalltalk projects. More on our special Smalltalk GSoC 2013 website: http://gsoc2013.esug.org I'm specially inviting mentors of all past GSoCs to rejoin the mentors mailing list, where we discuss all details about this year GSoC: http://groups.google.com/group/smalltalk-gsoc-mentors While students interested on GSoC please join a special Smalltalk GSoC mailing list for you: http://groups.google.com/group/smalltalk-gsoc-students Best regards Janko -- Janko Mivšek Smalltalk GSoC Admin Team http://gsoc2013.esug.org

1 0

build drop-down select list when clicked
by bobn＠rogers.com 07 Mar '13

07 Mar '13

Hello, Is there a way to build the 'select' list when the drop-down button is pressed? Our application uses drop-down lists for options that have a short list to pick from (longer lists use a lightbox list prompt). In most cases, the list of values is not needed, since the user is not going to change the selection. So, I'd prefer to defer getting the list to when the user asks for it (round trip time to get the list is less than 50ms). Getting the data is not expensive, but including it in the initial data retrieval for the full view is a coding hassle. I've tried various #onClick: code, like loading a new rendering of the select component with the list populated, but no luck. i.e. html select onClick: ("get the list and display it"); list: (Array with: initialSelection); "for initial display" selected: initialSelection; callback: [:value | ... ] Thanks for any help, Bob Nemec

2 6

KomHttpServer on SqueakMap
by H. Hirzel 07 Mar '13

07 Mar '13

Hello Chris Attached is a screenshot of the KomHttpServer entry for Squeak 4.4 on SqueakMap. The entry I loaded for running Squeak 4.4. and Seaside 3.0.3 is the one marked with (4.4) which seems to apply to the Squeak version. What do the parenthesis mean? The other version numbers seems to be the version numbers of the KomHttpServer. Could you please shed some light on this issue? Regards Hannes N.B. 897 out of 898 Seaside 3.0.3 tests work fine in Squeak 4.4

4 4

Re: [squeak-dev] [Seaside] New catalog entry for Seaside 3.0.3
by H. Hirzel 07 Mar '13

07 Mar '13

Hello On 3/1/13, Chris Muller <ma.chris.m(a)gmail.com> wrote: >> If a kind soul can get one working, I'll make sure it stays working >> with the magic of CI on build.squeak.org. Er, that means that I'm not >> sure whether Chris reported _working_ configurations. > > Hi, that Seaside configuration should "work". I did not run the tests > (don't know how) but I was able to start a server and build a > rudimentary page using one of the ajax frameworks that rendered and > accepted input.. > Thank you Tobias for coming up with a Seaside configuration which loads fine and Chris for the SqueakMap entry. I loaded Seaside from SqueakMap into a pristing Squeak4.4 image. One click on the Seaside entry. I did not load any prerequisites. Now my question: How do I start it? It used to be something of the following (Smalltalk at: #WAServerAdaptorBrowser) open. (Smalltalk at: #WAPharoServerAdaptorBrowser) open. (Smalltalk at: #WAServerAdaptor) open. However none works. A note in the SqueakMap entry would be appreciated. The note says: 'Seaside requires a web server; the most commonly used is KomHttpServer'. But there is no SqueakMap entry for that. Then later let's move on to a SqueakCI job for this. Regards Hannes

4 4

New catalog entry for Seaside 3.0.3
by Chris Muller 07 Mar '13

07 Mar '13

Hi Tobias, I made new Community-Supported catalog entries for: DynamicBindings ("4.4" and "head") KomHttpServer ("4.4") Grease ("1.1.0" and "head") Sport (already up-to-date, no action taken) Seaside ("3.0.3") These each consume with single-click (necessary pre-reqs are loaded automatically for each package). Installing the head versions always perform a merge, similar to updating trunk packages. I didn't know what version to make for DynamicBindings and KomHttpServer so I just made them the same as the Squeak version they're for. I didn't make head versions of KomHttpServer or Seaside because I wanted to ask your (and others') opinions about it. If Seaside Development Team is still putting out Squeak versions and using Metacello to keep that managed, our catalog entries should definitely reflect that. Otherwise, it's worth asking, what is the best way for us as a community to keep up a dependably working version of Seaside for Squeak? Do you know why the Metacello scripts keep failing for stuff that was once working? Best, Chris On Tue, Feb 26, 2013 at 7:29 AM, Tobias Pape <Das.Linux(a)gmx.de> wrote: > Hi again Seasiders > > > Anfang der weitergeleiteten Nachricht: > >> Von: Tobias Pape <Das.Linux(a)gmx.de> >> Betreff: [Seaside] Making seaside load in Squeak again. >> Datum: 26. Februar 2013 09:42:56 MEZ >> An: Seaside - general discussion <seaside(a)lists.squeakfoundation.org> >> Kopie: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> >> Antwort an: Seaside - general discussion <seaside(a)lists.squeakfoundation.org> >> >> Hey Seasiders >> >> I am trying to prepare a stable Seaside Image for Squeak 4.4 >> and just tried loading via the Metacello configuration >> (Like this: >> >> Installer ss >> project: 'MetacelloRepository'; >> install: 'ConfigurationOfSeaside30'. >> ((Smalltalk at: #ConfigurationOfSeaside30 project) version: #stable) load >> >> ) >> >> This fails, as there is a dependency on Zinc #stable in >> #squeakCommon. Also, I think it is worthwhile to add WebCilent >> to the Adaptors for, at least, Squeak, if not Pharo, too. >> >> I have seen that there is progress for that in the Seaside31 repository, >> especially for the 3.1 version of Seaside. > > In my effort to see what I can do I succeeded in > Running Seaside 3.1 atop Squeak 4.4 (I needed to bring an interim Grease 1.1.1 version for that) > > You load [1] > http://netshed.de/seaside/ConfigurationOfGrease-topa.191.mcz > http://netshed.de/seaside/ConfigurationOfSeaside30-topa.415.mcz > and then you can DoIt > > ((Smalltalk at: #ConfigurationOfSeaside30) project version: '3.1.0') load: #(Development OmniBrowser Swazoo WebClient Welcome). > (Smalltalk at: #WAServerAdaptorBrowser) open > > in a fresh Squeak4.4-12327. > (Then rightclick in the Seaside Control Panel and 'Add adaptor', a WebServer Adaptor, > which uses WebClient. Then go to localhost:8080 and be happy.) > > Now I will try to work on Seaside 3.0. > >>> > To any Seaside dev, please consider merging my versions :) > << > > Best > -Tobias > > [1] this is no MC repo, I just don't have access to the Seaside Repos and didn't want to pollute > any MetacelloRepository.

4 4

Re: [squeak-dev] [Seaside] New catalog entry for Seaside 3.0.3
by Dale Henrichs 07 Mar '13

07 Mar '13

Chris, I think that the officially correct script is the configuration .... Dale ----- Original Message ----- | From: "Chris Muller" <ma.chris.m(a)gmail.com> | To: "Dale Henrichs" <dhenrich(a)vmware.com> | Cc: "Seaside - general discussion" <seaside(a)lists.squeakfoundation.org>, "The general-purpose Squeak developers list" | <squeak-dev(a)lists.squeakfoundation.org> | Sent: Tuesday, March 5, 2013 7:24:56 PM | Subject: Re: [squeak-dev] [Seaside] New catalog entry for Seaside 3.0.3 | | > to get a working one-click script recorded there that can do it. | | Not only just working, but the officially-correct script |

1 0

ConfigurationOfSeaside for Pharo 2.0
by Torsten Bergmann 04 Mar '13

04 Mar '13

Hi @seaside-dev (CC-ing Pharo list and seaside users list): Pharo 2.0 is upon completion and it would be good to have a working Seaside running on it out of the box using a ConfigurationOfSeaside accessible through the configuration browser. (Aida is also already working this way). What I currently know from own simple tests and postings is that it is basically working on Pharo 2.0 using this load script: https://github.com/renggli/builder/blob/master/scripts/seaside31-pharo2.st and then "Zinc Server" Gofer new squeaksource: 'ZincHTTPComponents'; "package: 'Zinc-HTTP';" package: 'Zinc-Seaside'; load. "Start Zinc" " (ZnZincServerAdaptor port: 8080) codec: GRPharoUtf8Codec new; start. " There are some small issue left in #includesSubString: vs. #includesSubstring: (now in Pharo). I found it in - WAAbstractFileLibrary>>updateRoot:, - WAFormTag>>isInternetExplorer - WARenderContext>>absoluteUrlForResource: Also when one uploads files using config -> files the methods for the uploaded content get generated but not packaged with Monticello for whatever reason. Is there a plan/timeline for having a valid Seaside on top of Pharo available. Creating an updates ConfigurationOfSeaside was also discussed here on the seaside list ... but still not yet realized. We all know time is always an issue - but at least I want to start a dicussion if it is possible (maybe with the help from many using a virtual sprint). Also is there any plan in moving Seaside to SmalltalkHub as well? Since there is now infrastructure for CI ready on Pharo side it could be used for Seaside also. Any comments? If possible respond on "seaside-dev" list so it is discussed on one central place (http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev) Thanks T.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside March 2013