Hello,
I have a couple of questions with Pier. I have a Website developed with it
on a apache server and everything works fine, but sometimes the image (or
the VM) goes down so I have to run the script again. Is there any way to
automatically run it? I tried a cron with a script, but haven't worked so
well. The server haven't reboot in a while and still I had the problem, so
I think maybe that's not the reason.
Also, after some time, even if I run the pier.sh script and even if I see
squeak running, the website is down. For now the solution have been copy and
paste the folder and use this "new Pier". Did I made something for this to
happen?
Thanks,
Vanessa.
--
View this message in context: http://forum.world.st/Pier-image-running-issues-tp4534942p4534942.html
Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.
Hi,
I am experiencing some strange problem with one of my pages which is classified as "Malicious Sources". This problem only arrises behind a compagny firewall on my
Blog page. The page concerned is : http://stakepoint.com/news My other pages do not have this problem:
What can the origin of this ?
My image is an old Pier image, (its up for about 3 years now).
Bes tregards,
Maarten,
The error message is as follows.
=======================
English
Access Denied (content_filter_denied)
Your request was denied because of its content categorization: "Malicious Sources"
Français
Accès BLoqué (content_filter_denied)
Votre requête a été bloquée car le contenu de la page est dans une catégorie interdite : "Malicious Sources"
20th International Smalltalk Joint Conference - Call for Contributions
Gent, Belgium
August 27-31, 2012; Camp Smalltalk August 25-26
http://esug.org/Conferences/2012
This call includes:
1) Developers forum
2) Innovation Technology Award
3) International Workshop
4) Student Volunteer program
5) Free ESUG tickets program
----------------------------------------------------------------------
For the past 20 years, the European Smalltalk User Group (ESUG) has
organised the International Smalltalk Conference, a lively forum on
cutting edge software technologies that attract people from both
academia and industry for a whole week. The attendees are both
engineers using Smalltalk in business and students and teachers using
Smalltalk both for research and didactic purposes.
This year's edition of the largest European Smalltalk event will
include:
- The regular Smalltalk developers conference with
renowned invited speakers
- a Smalltalk camp that proved fruitful for interactions and
discussions (August 25-26)
- 9th edition of the Innovation Technology Awards where prizes
will be awarded to authors of best pieces of
Smalltalk-related projects
- IWST: an international workshop on Smalltalk and dynamic
languages
You can support the ESUG conference in many different ways:
- Sponsor the conference. New sponsoring packages are described
at http://www.esug.org/About/SupportESUG
- Submit a talk, a software or a paper to one of the events.
See below.
- Attend the conference. We'd like to beat the previous record
of attendance (170 people at
Amsterdam)!
- Students can get free registration and hosting if they enroll
into the the Student Volunteers program. See below.
1) Developers Forum: International Smalltalk Developers Conference
----------------------------------------------------------------------
This year we are looking for YOUR experience on using Smalltalk. In
addition, we are looking for tutorials. The list of topics includes,
but is not limited to the following:
- XP practices
- Development tools
- Experience reports
- Model driven development
- Web development
- Team management
- Meta-Modeling
- Security
- New libraries & frameworks
- Educational material
- Embedded systems and robotics
- SOA and Web services
- Interaction with other programming languages
Submissions due on 15 June 2012
Notification of acceptance on 25 June 2012
How to submit?
Pay attention: the places are limited so do not wait till the last
minute to apply. Prospective presenters should submit a request to
board(a)esug.org AND damien.cassou(a)gmail.com AND
stephane.ducasse(a)free.fr following the template below. Please use this
template since the emails will be automatically processed!
Subject: [ESUG 2012 Developers] + your name
First Name:
Last Name:
Email where you can always be reached:
Title:
Abstract: (max 1400 characters)
Bio: (max 1400 characters)
Any presentation not respecting this form will be discarded
automatically
2) Innovation Technology Award
----------------------------------------------------------------------
We are proud to announce the 9th Innovation Technology Awards. The top
3 teams with the most innovative software will receive, respectively,
500 Euros, 300 Euros and 200 Euros during an awards ceremony at the
conference. Developers of any Smalltalk-based software are welcome to
compete. This year we will request 3-5min videos.
More information at:
http://www.esug.org/Conferences/2012/Innovation-Technology-Awards
3) International Workshop - IWST 2012
----------------------------------------------------------------------
International Workshop on Smalltalk Technologies, August 28
The goals of the workshop is to create a forum around advances or
experience in Smalltalk and to trigger discussions and exchanges of
ideas. Participants are invited to submit research articles. We will
not enforce any length restriction. Nevertheless, we expect papers of
two kinds:
- Short position papers describing emerging ideas.
- Long research papers with deeper description of experiments and of
research results.
We welcome research papers on all aspects, theoretical as well as
practical, of Smalltalk related topics. All accepted papers will be
published in ACM DL, and the authors of the best papers will be
invited to submit an extended version to a journal special issue (to
be confirmed).
Submissions deadline: June 15, 2012
Notification of acceptance: July 15, 2012
More information at:
http://www.esug.org/Conferences/2012/International-Workshop---IWST-2012
4) Student Volunteer Program
----------------------------------------------------------------------
If you are a student wanting to attend ESUG, have you considered being
a student volunteer? Student volunteers help keep the conference
running smoothly; in return, they have free accommodations, while
still having most of the time to enjoy the conference.
More information at:
http://www.esug.org/Conferences/2012/StudentVolunteers
5) Free ESUG tickets program
----------------------------------------------------------------------
ESUG will offer 10 free entrance tickets. To get a free ticket you
should send a mail to board(a)esug.org
Subject: [ESUG 2012 Free entrance] + your name
And you should write a small motivation.
We hope to see you there and have fun together.
--
The ESUG board
Board mailing list: board(a)lists.esug.org
Hi,
Based on the new file library (see previous mail) I've started work on a
Twitter Bootstrap Magritte form renderer [1].
The repository includes the Twitter Bootstrap libraries, Twitter Bootstrap
Magritte form and component renderers and a configurable Magritte form
rendering example.
If you want to give it a spin, you'll need the latest Seaside and Magritte
3 code, as well as the code from the repository.
I've put the sample up on seasidehosting -
http://twitterbootstrap.seasidehosting.st/
Cheers
Nick
[1] http://ss3.gemstone.com/ss/TwitterBootstrap
Hi Yanni,
On 8 March 2012 16:51, Yanni Chiu <yanni(a)rogers.com> wrote:
> On 08/03/12 2:58 AM, Nick Ager wrote:
>
>> Have you had any luck viewing the output ePUB file with iBooks on iOS? I
>> tried with my iPhone but it wouldn't open. I also noticed that the
>> section link wasn't numbered - any thoughts?
>>
>
> I don't have iBooks, iOS, iPhone to try, but I'll try the dev simulator on
> MacOSX.
>
> I'm not sure what is meant by section link number. The EPUB standard
> appeared to be a maze of other standards and some now deprecated specs. So
> rather than decipher the spec, I unzipped a few example EPUB books, and
> gleaned a small subset to implement.
>
> Here's my plan:
>
> 1. Add my test Pier book as a TestCase
> 2. Add a way to include a .css stylesheet
> 3. Fix bugs reported on different platforms
This sounds great - look forward to hearing how you get along
Nick
Hi Yanni,
> You should be able navigate to the book in the sample distribution, then
> look for a view "Book EPUB" and download the .epub file. Then open in an
> EPUB reader. (Or, in Firefox you can open a new tab, instead of doing the
> download).
>
> The EPUB navigation pane works, but the internal Pier book links (in the
> table of contents, say) do not work. I'll look into it.
>
Great I've seen my first Pier ePUB book. I could view it in the Firefox
add-on.
Have you had any luck viewing the output ePUB file with iBooks on iOS? I
tried with my iPhone but it wouldn't open. I also noticed that the section
link wasn't numbered - any thoughts?
Cheers
Nick
Hi,
I've completed an initial port of Pier 3 (Pier using Magritte 3
descriptions) to Gemstone.
It can be loaded in Gemstone using:
Gofer it
> squeaksource: 'MetacelloRepository';
> package: 'ConfigurationOfPier3AddOns';
> load.
>
> MCPlatformSupport commitOnAlmostOutOfMemoryDuring: [
> ConfigurationOfPier3AddOns load ].
By default this configuration will load Pier-Admin and the Pier add-ons
necessary to make this work - (Pier-Admin is described in this screen-cast:
http://vimeo.com/32749535)
Let me know how you get on,
Nick
Hi,
I just wanted to let you know that the Glamour and Metanool (transformation engine between Fame and Magritte) are now using Magritte 3.
Consequently, in the latest Moose image you will find Magritte 3.
Cheers,
Doru
--
www.tudorgirba.com
Things happen when they happen,
not when you talk about them happening.
Hi,
Magritte 3 is now available for Gemstone - with tests green. The
configuration has been updated and I loaded Magritte 3 with:
Gofer it
squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfMagritte3';
load.
MCPlatformSupport commitOnAlmostOutOfMemoryDuring: [
ConfigurationOfMagritte3 project stableVersion load: #('Seaside Tests') ].
However the tests run extremely slowly - in the test suite I've measured
20x slowdown between Magritte 2 and Magritte 3 - making the tests a pain to
execute.
I've run a series of tests to characterise where the problem might be. The
tests are as follows:
-----
1) Test-suite benchmark:
| testSuite |
testSuite := (OBClassCategoryNode on: 'Magritte-Tests-Model-Description')
classes
inject: TestSuite new
into: [:suite :classNode |
(classNode theClass inheritsFrom: TestCase)
ifTrue: [suite addTests: classNode theClass suite tests].
suite].
Time millisecondsToRun: [ testSuite run ].
2) Description benchmark:
Magritte 2:
Time millisecondsToRun:
[100 timesRepeat: [ MABooleanDescription description ] ].
Magritte 3:
Time millisecondsToRun:
[100 timesRepeat: [ MABooleanDescription new magritteDescription ] ].
3) Micro-benchmark
Magritte 2:
Time millisecondsToRun:
[100 timesRepeat: [ MABooleanDescription class allSelectors select: [
:each | each isDescriptionSelector ] ] ].
Magritte 3:
Time millisecondsToRun:
[100 timesRepeat: [ Pragma allNamed: MAPragmaBuilder
magritteDescriptionPragma from: MABooleanDescription to: Object ] ].
* The micro-benchmark is illustrative of the difference between Magritte 2
and Magritte 3 - Magritte 2 uses a naming convention to retrieve
descriptions, whereas Magritte 3 uses Pragmas.
-----
Results:
Pharo Magritte 2: (1) 436 (2) 0 (3) 85
Pharo Magritte 3: (1) 743 (2) 58 (3) 12
Gemstone Magritte 2: (1) 988 (2) 30 (3) 2229
Gemstone Magritte 3: (1) 21663 (2) 1575 (3) 444
Cavet: Although Gemstone and Pharo are running on the same machine -
Gemstone is running virtualised in a VMWare Linux installation, so the
results are not directly comparable, although the 30x performance decrease
between Pharo and Gemstone surprised me.
First the good news:
For Magritte the pragma description look-up is more performant than the
named-based lookup (micro-benchmark (3)).
Now the bad news:
In Pharo Magritte 2 is faster then Magritte 3 when running a description
lookup based test-suite containing 1416 tests. My feeling is that in the
context of a real application performing a smaller number of lookups this
is probably not significant.
However in Gemstone the performance degradation is more noticeable and if
nothing else makes running the tests painful.
How to proceed:
Magritte 2's performance advantage is gained from caching the descriptions.
However I think the benefits of having dynamic (non-caching) descriptions
outweigh the disadvantages and I'd be reluctant to add a generic layer of
caching. In Pharo I don't think this is an issue. However in Gemstone I
feel that these numbers need some further investigation.
Any thoughts how to proceed?
Nick
Hi,
I'm pleased to announce a new version of Magritte - Magritte 3. The
rational for Magritte 3 is eloquently described by Lukas in his mail below.
The work on Magritte 3 was started by Esteban and completed by myself.
I've created a screen-cast which describes:
- the rational for Magritte 3
- the refactorings available to ease the transition from Magritte 1 or
2 to Magritte 3
- A walk-through of updating a sample from Magritte 2 to Magritte 3.
The screen-cast is on vimeo at:
http://vimeo.com/37032840
The sample used in screen-cast can be downloaded as:
Gofer it
> url: 'http://ss3.gemstone.com/ss/MagritteMagic';
> package: 'ConfigurationOfMagritteMagic';
> load.
>
> (Smalltalk at: #ConfigurationOfMagritteMagic) load.
The slides used in the screen-case can be viewed on slideshare at:
http://www.slideshare.net/nickager/magritte3
Enjoy
Nick
---------- Forwarded message ----------
From: Lukas Renggli <renggli(a)gmail.com>
Date: 17 November 2010 17:21
Subject: Re: Providing lookup environment for descriptions
To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
The way Magritte builds descriptions by default has become quite a
nuisance. I think that at some point Magritte should be improved
in that regard. I wrote a proposal this summer for how to proceed,
but of course I had to finish my writing and never actually
found the time to implement it:
--------------------
I propose to perform the following (non-backward compatible) changes
in the Magritte 2 code-base to resolve some major annoyances and
issues that keep on reoccurring:
- Move descriptions from class-side to instance-side. This resolves
various issues such as cache-invalidation, instance specific
descriptions, dynamic descriptions, context dependent descriptions,
etc. Furthermore the descriptions will be closer to the code they
describe and it will be possible to describe class- and instance-side
of an object, not just the instance-side.
- Rename the method #description as the default entry point into
Magritte to #magritteDescription. This avoids common problems where
the domain model already defines such a method.
- Instead of using a naming convention for description methods, use a
pragma called <magritteDescription> to annotate the methods. And to extend
and
change existing descriptions use <magritteDescription: aSelector>. Finally
all
Smalltalk implementation reached a consensus of pragmas that can be
safely used cross-platform.
All in all the "new" Magritte would look like in the following
example. Imagine a shop item with the accessor #place:
Item>>place
^ place
Item>>place: aString
place := aString
The meta-description is defined on the instance-side and annotated. It
can refer to itself for the possible places:
Item>>placeDescription
<magritteDescription>
^ MASingleOptionDescription new
options: self possiblePlaces;
label: 'Place of Item';
accessor: #place;
yourself
Class extensions can modify a description using:
Item>>placeDescriptionXmlStorage: aDescription
<magritteDescription: #placeDescription>
^ placeDescription xmlTag: 'xname'
Since these changes are not backward compatible I'll try to provide
automatic refactorings for most parts. Moving existing code to the new
codebase will certainly cause some problems, but in the long run I
believe this to be a much better approach than the current one. If
people have any feedback, concerns or other changes that would be
important in the same run I am happy to hear them.
