seaside September 2013

seaside@lists.squeakfoundation.org

29 participants
33 discussions

Re: [Seaside] including javascript and static files in a project.
by Joachim Tuchel 20 Sep '13

20 Sep '13

Sergio, You are asking about the workflow during development, not just how to deploy, right? I guess this is where filetree and cypress will be the tools that rock. Instead of pressing all non-st artefacts into a file library and using monticello/store/envy to keep them under version control, turning things around and using today's standard vcs sytems for both non-st and st code will be the bright new world. But cypress is, to my knowledge, just an idea and some prototypes... For now, you can either do one of A) keep all in st and use WaFileLibrary. This locks out all non-st users in the team B) use separate repositories for st and non-st artefacts. This makes the whole process more complex, but non-st members have access C) create a sophisticated mix of A) and B). This is complicated and error-prone. Most of the work is needed to synchronize yor file library with the outer-world contents... C) is how most projects I am aware of do it. Most have troubles with that approach. Joachim Diego Lont <diego.lont(a)delware.nl> schrieb: >Hi sergio, > >The default answer is, use a web server between your seaside image and the actual webpage, and have this web server serve the including static files, since this is much faster than pulling them through your image … and more flexible, that other people can easily check them in. > >Cheers, >Diego > >On Sep 19, 2013, at 8:37 PM, sergio_101 wrote: > >> >> hey, all! >> >> i have been away from seaside for awhile. too much day job programming to do any fun programming.. >> >> just wondered how people were including javascript and other static files in their projects. >> >> i really liked using monticello, but i never really got a handle on how to include all of the static files in the project so that other team members could use them and edit them (and check in their changes) without thinking about it at all.. >> >> does anyone have a clean and clever workflow? >> >> thanks! >> >> -- >> ---- >> peace, >> sergio >> photographer, journalist, visionary >> #BitMessage BM-2D8VWUJSS41RFKh1ec83preVabHrnniExa >> >> http://www.ThoseOptimizeGuys.com >> http://www.CodingForHire.com >> http://www.coffee-black.com >> http://www.painlessfrugality.com >> http://www.twitter.com/sergio_101 >> http://www.facebook.com/sergio101 >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > >_______________________________________________ >seaside mailing list >seaside(a)lists.squeakfoundation.org >http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

2 3

Re: Grease conflicts #packages with RPackage
by Mariano Martinez Peck 20 Sep '13

20 Sep '13

Anyone? On Wed, Aug 28, 2013 at 2:12 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi guys, > > I was trying to build a new image with latest Pharo 2.0 with all the > frameworks I use. While installing, I get a dnu in: > > packageFromOrganizer: anRPackageOrganizer > "This method returns the package this method belongs to. > It takes into account classes and traits. > If the method is in no package, returns nil by now" > self flag: 'TODO: use anRPackageOrganizer, or better delegate to > anRPackageOrganizer'. > ^self origin packages > detect: [ :each | > (each includesSelector: self selector ofClassName: self origin > theNonMetaClass originalName) > or: [ each includesSelector: self selector ofMetaclassName: self origin > theNonMetaClass originalName]] > ifNone: [ nil ] > > because "each" (which was GRPackage) dnu #includesSelector:ofClassName: > > Problem is that "self origin" answers GRPackage. And GRPackage DOES > implement a CLASS side method #packages that answers instances of > GRPackage.....not RPackage... > > So...which one do we prefix? GRPackage class #packages to #greasePackages? > > BTW, there are yet more class side implementations of #packages, which are > basically subclasses for the HelpSystem (CustomHelp). So we have for > example SUnitAPIDocumentation, RegexAPIDocumentation, ProfStefAPIHelp, HelpAPIDocumentation, AnnouncementsAPIDocumentation. > > Guess we should update the HelpSystem as well? > > Let me know and I open issues/submit fixes. > > Cheers, > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

2 4

including javascript and static files in a project.
by sergio_101 20 Sep '13

20 Sep '13

hey, all! i have been away from seaside for awhile. too much day job programming to do any fun programming.. just wondered how people were including javascript and other static files in their projects. i really liked using monticello, but i never really got a handle on how to include all of the static files in the project so that other team members could use them and edit them (and check in their changes) without thinking about it at all.. does anyone have a clean and clever workflow? thanks! -- ---- peace, sergio photographer, journalist, visionary #BitMessage BM-2D8VWUJSS41RFKh1ec83preVabHrnniExa http://www.ThoseOptimizeGuys.com http://www.CodingForHire.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

2 1

Authenticating requests of Seaside REST filters (Using Zinc?)
by Esteban A. Maringolo 16 Sep '13

16 Sep '13

I want to add authentication to a Seaside app I'm programming. Particularly to the REST API I implemented by means of a WARestfulFilter. I want to use HTTP authentication against my existing authentication subsystem. But I don't know where to "hook in" the authentication process. Options: 1) Should I have my own Zinc delegate for the API? Authenticating everything before it reaches the ZnSeasideServerAdaptorDelegate? 2) Should I have to use something different than WARestfulFilter and use instead a WARestfulHandler starting at a different URN path? (maybe with a different delegate at that path). E.g. have the "common" seaside delegate installed a myhost/ui/ and the "REST" http authenticated delegate installed at "myhost/api/"? Any suggestion is welcome. -- Regards! -- View this message in context: http://forum.world.st/Authenticating-requests-of-Seaside-REST-filters-Using… Sent from the Seaside General mailing list archive at Nabble.com.

3 5

[Seaside News] Smalltalkhub, ConfigurationOfSeaside3, Seaside3.1
by Johan Brichau 15 Sep '13

15 Sep '13

Hi Seasiders, The Seaside repository moved to Smalltalkhub, a new ConfigurationOfSeaside3 was created and Seaside 3.1 is in release candidate mode. Current stable release for all platforms is 3.0.8 (with a final bugfix release 3.0.9 coming up). Seaside 3.1 has all tests green on Pharo 1.4 and 2.0. We are working on Gemstone and Squeak Seaside and all Seaside team curated projects can be found here: http://www.smalltalkhub.com/#!/~Seaside We have grouped all Metacello configurations for these projects in a single repository: http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main Important: there now is a single configuration for both Seaside 3.0 and Seaside 3.1: ConfigurationOfSeaside3 To load current stable Seaside 3.0.8: Gofer new url: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; package: 'ConfigurationOfSeaside3'; load. ((Smalltalk at: #ConfigurationOfSeaside3) project version: #stable) load To load Seaside 3.1.0: ((Smalltalk at: #ConfigurationOfSeaside3) project version: '3.1.0') load Stay tuned for a follow-up email on Seaside3.1 For the Seaside team, Johan, Philippe, Dale, John

3 2

Spec server browser basic functionality working
by Philippe Marschall 13 Sep '13

13 Sep '13

Hi With the help of Benjamin we could get the basic functionality of the spec based server browser working. You have to load Seaside-Pharo-Tools-Spec from [1] (should work with Seaside 3.0) and then do WAPharoServerAdapterSpecBrowser open If you don't have any servers registered you can do so with: ZnZincServerAdaptor new Things that aren't working currently: * refreshing the server status when pressing buttons * status icons * adding servers * context menu (port, encoding) * world menu registration [1] http://smalltalkhub.com/mc/Seaside/Seaside31/main Cheers Philippe

2 2

Re: How was it received?
by Stephan Eggermont 12 Sep '13

12 Sep '13

Hi Friedrich, We had quite a number of people interested in QCMagritte. Several people asked us about it after the presentation. The demo was impressive even though we lost a ^ in creating the different builders. (fixed now). We'll create a short screencast just demo-ing the modified twitter bootstrap. Tobias Pape already looked at getting it to work with Squeak, and we created a CI job for it on PharoContributions. While doing that, we found some ConfigurationOf... issues that are now fixed. Cheers, Stephan

1 0

RE: Problem upgrading seaside from an existing image (Pharo #14438 and Seaside 3.0)
by Stephan Eggermont 12 Sep '13

12 Sep '13

Ok, I wasn't clear. I was looking at the packages downloaded to the package cache

4 7

Where can I get Pier?
by James Foster 10 Sep '13

10 Sep '13

http://www.piercms.com/download contains a couple links, each of which seems to have a very nice install of Seaside but Pier is absent! A month ago I got a nice Pier image from that link. Attempting to load ConfigurationOfPier3 gives this error: 'Could not resolve: ConfigurationOfZincHTTPComponents [ConfigurationOfZincHTTPComponents] in /Users/jfoster/cloud2/pier3/Pier.app/Contents/Resources/package-cache http://mc.sftx.eu/ZincHTTPComponents ERROR: ''GoferRepositoryError: Could not resolve the server named: mc.sftx.eu''' Attempting to load ConfigurationOfPier2 gives this error: 'MessageNotUnderstood: Form>>capitalized' Anyone got a decent Pier image in Pharo that they can share? James

2 1

grease configuration broken
by Tudor Girba 10 Sep '13

10 Sep '13

Hi Jochan, You just committed a broken bleedingEdge method in the ConfigurationOfGrease: bleedingEdge: spec <symbolicVersion: #'bleedingEdge'> spec for: #'common' version: #'1.1.3-baseline'. Because of this method, the whole configuration is not usable because Metacello has this annoying behavior of wanting all versions to be correct before being able to use one of them. Could you fix it? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

1 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 September 2013