is there any photo gallery available for Pier? I mean a widget where I
could upload pictures and they are rendered in a nice way. I started
one 4 years ago but I abandoned it.
I am trying the book component in the latest Pier and I notice that the user comments component does not seem to appear anymore. Is there something I should do, or is this a bug?
"It's not what we do that matters most, it's how we do it."
I've been fiddling with Pharo 1.1.1 One-Click which didn't include Seaside
by default (at least not that I could see). I loaded seaside via the
squeaksource repository. Firstly it seemed like Magritte wasn't included in
the Seaside install. Is this so?
So I installed Magritte. Then when I tried to run the Magritte example in
the Seaside book I got MyContactAddress>>doesNotUnderstand #new
So I repeated the above steps with Pharo 1.2.1 One-Click. With the same
result except I got Address>>doesNotUnderstand: #asComponent.
I'm confused. Although this is my normal state I wonder if someone could
The Pier Sprint in Eindhoven, The Netherlands, starts in 5 days. On July 2
and 3 we will be working on enhancing the first-time user experience of
Pier. For that reason we have involved usability experts/interaction
designers to help us developers ;-).
We are very happy with the 10 attendees (developers and designers) we have
so far. This is your last chance to join us.
Registration and more Information:
Sprint User Stories: http://pier.andriese.net:8001/pier/blog
Pier Issues List: http://code.google.com/p/pier/issues/list
If for some reason you can't make it to Eindhoven, you're welcome to send
user stories to this list.
See you in Endhoven.
The ISAAC / Delta Lloyd Pier Sprint team
I've added social sharing widget support to blog entries. To use:
0) update to Pier-Blog-NickAger.147
1) Edit your blog
2) In "Social Sharing class" entry enter: PBSocialWidgetsAddThis
3) Save changes
4) Your blog entries should now contain the social widgets from
Implementation allows pluggable social widget renderers; replace
PBSocialWidgetsAddThis with a renderer for your desired the social widgets.
All feedback welcome,
On 10 June 2011 14:14, Esteban Lorenzano <estebanlm(a)gmail.com> wrote:
> Hi Lukas,
> Sorry I'm disturbing you.
Please direct such mails at the mailing list :-)
> I'm playing with magritte for morphic and I found something odd about the implementation: looks not finished. Maybe because until now, nobody I know is trying to use it in commercial proyects (I have a client for a desktop app :) )
> Right now, my main concern is about MATextMorph>>#buildMorphEditor implementation, it is using #selected accessors and for that (instead #string), so they show 'false' strings... also, they fail at validation time if I'm asking for a number, but I'm assuming there will be other problems.
Magritte-Morphic worked quite well in Squeak 3.9 and was used to
render a complete Morphic interface for Pier. Since then I haven't
spent much time with it though. Doru is using it in Moose and has
recently applied some fixes, so he might have better knowledge. Note
that Moose is using Pharo 1.3, so that might be a reason it doesn't
> I wonder if I can join the "magritte developers" group, and upload my fixes to make it work properly
I've added you.
> pd: btw, it looks like I will be giving a talk "magritte magic" at esug :)
Great, please go ahead :-)
Saturday morning I'm still looking for a group to join at StarupWeekend
Toronto. In the lunch lineup, right behind me, is someone from a small
group looking for a developer. So I'm in.
They already have a landing page on a server, but I need to build a
prototype that queries a URL for a JSON response, and display the
result. We'll have to figure out how to tie it together for a demo.
Since I've got a free hand, I used a Pier CMS, and loaded JSON from
SqueakSource. Then a wrote a PRWidget to get the JSON data, parse, and
display. Still some clean up, CSS, and deployment to do.
You can follow along at #swtoronto and somewhere on Facebook and Twitter
is the "GettingGives" stuff -- no links, sorry I'm not a Facebooker or
Twitterer (yet?), and I forgot to ask the business crew earlier.