At 09:07 27/02/2010, Lukas Renggli wrote:
>For now I left the package Pier-Security, Pier-Blog, Pier-Book in the
>main repository. These are very big packages and somehow belong to the
>core, I thought. But, I am open for discussion.
Pier-Security and Pier-Blog are major components that I plan to
integrate in all my distributions. So, for me, certainly part of the
main repository.
Pier-Book is, somehow more specific, although also a major component.
Regards,
Reza
At 10:25 27/02/2010, Lukas Renggli wrote:
>Load the latest Seaside-Pharo-Tools-Web and the latest RBF server. I
>fixed various minor problems, but it basically worked already before.
Thank you so mush Lukas for having considered so professionally my request!
After the above upgrade, I just had once *VNC Free Edition for
Windows* from RealVNC rendering correctly my image display via
"localhost:0". But no interaction was possible, and my image was again frozen.
Now, I'm moving my image to my experimental Linux / Debian / Apache
2.2 / Firewall server, and will give you feedback asap.
Regards,
Reza
Hi,
I'm getting trouble to connect to a remote image using RealVNC. I get
a "Connection time out" error message.
The configuration is:
- PharoCore1.0rc1 (Latest update: #10505)
+ Seaside 3
+ Pier 2
+ RFB-lr.13 from
<http://source.lukas-renggli.ch/unsorted/>http://source.lukas-renggli.ch/unsorted/,
I successfully launch RFBServer thanks to Seaside VNC Controller, and
Pier continues serving in spite of that connection failure.
However, I tried to connect to a local image using "localhost:0", but
I get "Unknown rect encoding". If I ask RealVNC to retry connecting,
my image freezes. Its the same after upgrading to *RFB-DamienCassou.28*.
I'd greatly appreciate any feedback on this issue.
Thank you in advance,
Regards,
Reza
At 23:28 26/02/2010, Lukas Renggli wrote:
>@Reza: ...
>Could you please recommit the package without spaces?
Just done; also added some more comments.
Regards,
Reza
I've slightly reorganized the repositories for Pier and Magritte 2, as
it was discussed in the thread with the subject "PRTagCloudWidget and
PRVerbatim".
The codebase of Pier and Magritte for Seaside 3.0 is located at:
Magritte 2: http://source.lukas-renggli.ch/magritte2
Pier 2: http://source.lukas-renggli.ch/pier2
Both repositories are readable by public, to write you have to be
added to the developers though. Just drop a mail to the list if you
want to commit something and we will add you.
Pier 2 Addons: http://source.lukas-renggli.ch/pier2addons
Furthermore I created a public repository for the numerous Pier
plugins that already exist and that (hopefully) will continue to grow.
Read and write on that repository does not require any registration.
Feel free to post your extensions there.
@Reza: I tried to move your commit that wraps widgets into commands to
the plugin folder, but there seems to be problems because the package
name contains spaces. Monticello wouldn't even load that package.
Could you please recommit the package without spaces?
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
Hello,
When I switch my pier 2 website to use session cookies I get nice restful
URL's. Only there is a question mark behind the URL even if there are no
query parameters.
I tracked this down to the WUrl>>purgeSeasideFields method. The question
marks disappears when I change the method to:
purgeSeasideFields
self queryFields keys do: [ :each |
(self isSeasideField: each)
ifTrue: [
self queryFields removeKey: each ifAbsent: [ ].
self queryFields isEmpty
ifTrue: [ self queryFields: nil ] ] ]
It is also possible to change the WAUrl>>encodeOn: method to check for an
empty queryFields collection.
Jan.
Hi,
I've been experimenting with the code in PRContentsWidget all day and I've
noticed that an #onAnswer callback was added for all components regardless
of whether the command was a view command or not. I experimented with only
adding the #onAnswer callback for non-view commands and all appears to
continue to function, plus a WAAnswerHandler decorator is only added when (I
presume) it's required.
Is there a reason for calling #onAnswer on view components? Do view
components sometimes #answer:?
If not I attach an mcz with my changes.
Cheers
Nick
Hi,
When I edit a structure (or perform any command), the command renders itself
in the position defined by the PRContentsWidget. Unfortunately on the site
I'm building the content is often surround by other widgets and it's not
always visually appealing to render the command 'in-place'.
I've experimented with a couple of different approaches when the command is
"aContext command isView not":
1) replacing the application's root component with a decorated component
generated from the command as:
self session presenter show: commandComponent
2) my second attempt modified the nearest ancestor with a local environment
to a more suitable "plain" environment.
Unfortunately both attempts have limitations. In the first all the
environment is lost and I've realised that in the second, environment
changes are visible to all users...
Rethinking my approach another alternative would be to goto another page for
the command and return on command completion.
Has anyone else solved a similar problem? All thoughts gratefully received
Thanks
Nick
At 13:36 26/02/2010, Lukas Renggli wrote:
>I suggest we create a new public repository called 'pieraddons2' where
>we can collect all the different plugins and extensions, and that we
>make the main repository read-only.
Good idea!
>If anybody
>else would like to commit directly to the Magritte and Pier
>repositories, please ask in the list.
I'm using Pier as a core component in a major project. I may
consequently have some patches to propose here and there. However, at
least at this point, I don't feel that it will need to commit
directly to the main repository. The integration, when found useful,
could be done by one of the main developers, after having discussed
the proposition through the list.
Regards,
Reza
Hi,
I'm using a PRTagCloudWidget and I've noticed that I'm seeing "div" appear
as popular tag - which comes from the verbatim sections of my page's
environment. I'd have thought that ideally verbatim sections shouldn't be
included in tag cloud tokenisation???
Assuming I haven't missed some simple mechanism for extracting a pages
contents without the verbatim section, I've been pondering how I'd
implement it. I can see that by creating a visitor, say
PRTagCloudTextWriter, and leaving the implementation
of PRTagCloudTextWriter>>visitVerbatim: blank the resulting text will be
free of any PRVerbatim objects. However I'm unsure how to wire it all
together. Currently PRTagCloudWidget reads a page contents via PRCase
class>>descriptionDocument which uses the PRCase>>document accessor, which
give wiki text output. My initial implementation thoughts would be:
1) add a new accessor to PRCase say cloudText (as a PRTagCloudWidget
extension)
2) PRCase>>cloudText would use PRTagCloudTextWriter to extract plain text
without PRVerbatim content
3) PRTagCloudWidget, then needs a mechanism for tagging PRCase>>cloudText as
the accessor it should use, in preference to PRCase
class>>descriptionDocument. How about introducing PRCase
class>>cloudTextdescriptionDocument (as a PRTagCloudWidget extension),
which
PRTagCloudWidget would find and realise that it should be used in preference
to PRCase class>>descriptionDocument??
Or perhaps I've missed something really simple???
Nick
