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
Hi
As part of fixing Issue 820 [1] I have to change some configurations.
I though that if I do
WAAdmin clearConfigurationCaches
all the configuration caches should be cleared. However that is not
what is happening. #preferenceAt: in WAApplication instances still
return the old value.
[1] https://code.google.com/p/seaside/issues/detail?id=820
Cheers
Philippe
Hello,
I am porting Seaside 3.1 to VisualWorks. I have come across something that I am not sure is the intended use of configuration options.
The default ‘trackingStrategy’ configuration is set in WAApplicationConfiguration and WARegistryConfiguration, in their respective #describeOn: methods. In both, the default is set as ‘WAQueryFieldHandlerTrackingStrategy new’, inserting an instance of it (rather than the class itself) in the #trackingStrategy configuration parameter. However, in WAApplicationConfiguration, the list of valid options (self trackingStrategyClasses) returns a list of classes (not instances).
This has two implications:
1) when I try to configure an application in VW (e.g., http://localhost:7777/tests/functional), I get an unhandled exception ‘WAQueryFieldHandlerTrackingStrategy doesNotUnderstand: #name’ in WAClassListAttribute >> #stringForValue: method. The argument in #stringForValue: suggests aClass should be passed in, but it’s an instance instead.
2) when I try to do the same in Pharo, I’ll see ‘a WAQueryFieldHandlerTrackingStrategy’ as the value next to the 'Tracking Strategy’ label, telling me it’s an instance that is set in the configuration. However, when I click the ‘Override’ button next to it, the value will be set to a class. In Pharo, you don’t see a problem because of the default Object >> #name implementation that returns ‘self printString’, and so the method #stringForValue: doesn’t complain even though it receives the wrong kind of object.
Remedy:
I got around the problem by changing both WAApplicationConfiguration and WARegistryConfiguration to use the class, rather than instance, and by changing the WARegistry >> #trackingStrategy method to:
^ (self configuration at: #trackingStrategy) new
This fixed my problem, but it might not be in line with the intentions of the designer. Seeing that most of the tracking strategy classes (i.e., subclasses of WAHandlerTrackingStrategy) do not use any instance variables, I see no problem with this change.
Jerry Kott
Smalltalk Development, Cincom Systems
PGP fingerprint: 07D0987E142BE7D39A3F99D71DAF1CF392A9236F
Now sent van my registered e-mail adress
_____________________________________________
From: Tanner, Brian
Sent: donderdag 16 oktober 2014 14:33
To: 'seaside-dev(a)lists.squeakfoundation.org'
Subject: Deferring file downloads until link is clicked
Dear mailing list,
I'm having problems downloading documents using Seaside with Cincom Smalltalk 7.9.1.
I see that a document is downloaded during rendering whilst I wish that to be deferred until the user clicks op the link (anchor). On the Seaside website (documentation, FAQ, How to: entry 14) there is an explanation of how to resolve this problem by using a callback on the anchor:
Is there a convenient way to make the document be created after the link is clicked?
Yes, this is a common problem. One solution is to create an anchor and redirect:
html anchor
callback: [
self session returnResponse: (WAResponse
document: anObject
mimeType: aMimeType
fileName: aString) ];
with: 'Export'.
This information however seems to be outdated. There is for example no Class method WAResponse>>document:mimeType:filename , there is however an instance method with this name. I understand that I need to access the response in the active Request Context, but how do I do that?
Regards,
Brian Tanner
Information Specialist
ES WW Application Services (APP)
brian.tanner(a)hp.com<mailto:brian.tanner@hp.com>
T +31 30 700 1306
M +31 6 11706314
PC +31 20 721 1814
Hewlett-Packard Nederland B.V.
Orteliuslaan 1000
3528 BD Utrecht
The Netherlands
[http://www8.hp.com/h10180/images/hp_blue_rgb_72ppi_22px.png]<http://www.hp.com/>
Please print thoughtfully
Call for Participation in the Smalltalk Devroom at FOSDEM 2015.
http://www.fosdem.org, please forward
" A devroom for the Pharo, Squeak, Amber, GST, Etoilé, Seaside,
Moose Smalltalk projects & Objective Smalltalk and Newspeak as
derived languages. Smalltalk environments offer a very high
development productivity, unmatched by their successors.
Come do some pair programming with us and experience yourself
the advantages of a real OO environment"
The meetup will take place Sunday, February 1, 2015,
room S.H.2214. This room has 100 seats,
a VGA video projector and wireless internet.
Presentations will be video recorded (CC BY).
Proposals on content and format are welcome.
HOW TO SUBMIT:
All submissions are made in the Pentabarf event planning tool at
https://penta.fosdem.org/submission/FOSDEM15
When submitting your talk in Pentabarf, make sure to select the
'Smalltalk devroom' as the 'Track'.
If you already have an account there, please reuse it.
QUESTIONS & VOLUNTEERS
Any questions, and video volunteers, please mail to
stephan[@]stack[dot]nl
with [FOSDEM] in the subject. I will send out updates on a regular
basis to the lists and anyone stating his interest.
PLANNED SCHEDULE:
Sessions of 30/60 minutes (-5 min setup), last session a two hour hands-on
introduction to smalltalk. First session or lunch session can
be show-us-your-project, lightning talks.
The desired time slot is meant to help you prevent conflicts with other dev
rooms in which you might have a talk or your travel arrangements.
There are alternative, non smalltalk-specific tracks available:
lightning talk and the main track
Please submit before December 1, 23:00 GMT+1.
Devroom related URLs:
http://www.pharo.orghttp://www.squeak.org/http://etoileos.com/http://www.seaside.st/http://smalltalk.gnu.org/http://www.moosetechnology.orghttp://amber-lang.nethttp://newspeaklanguage.org/http://http://objective.sthttp://www.esug.org
FOSDEM is the Free and Open source Software Developers' European
Meeting, a free and non-commercial two-day weekend event that offers
open source contributors a place to meet, share ideas and collaborate.