Hi,
Happy New Year!
I would suggest having also a look at Pier Widgets.
Cheers,
Reza
On January 2, 2013 at 5:13 PM "dtrussardi(a)tiscali.it"
<dtrussardi(a)tiscali.it> wrote:
> Ciao,
>
> Happy New Year to all.
>
> Thank Yanni for your answer ( sorry for my delay ).
>
> > On 24/12/12 4:48 AM, dtrussardi(a)tiscali.it wrote:
> >>> I have a pier site with a menu to manage some pages.
> >>> Some of this pages are configured to manage components.
> >>>
> >>> For test i add some Counter seaside application instances.
> >>>
> >>> Now when display a specific page with some counter it work fine:
> >>>
> >>> i can change any specific counter instance in the page.
> >>>
> >>> My problem is when i change the menu for display another page.
> >>>
> >>> In this case when redisplay a page with the counters all instance
are reset to 0.
> >>>
> >>> Now my question is:
> >>>
> >>> what do i do for redisplay the counter at the last update ?
> >>>
> >>> I need to configure something ?
> >
> > IIUC, a Seaside component is created and initialized for each
Seaside session. I believe there is a way to set some initial values
using link parameters, but the details are not at my fingertips.
> >
>
> I found one example relative to this question creating a blog based on
PRBlogKernelDistribution.
>
> > Can you say a bit more about how you are using the pier page to
manage components. Ideally, an example of the wiki markup, and maybe a
code snippet that configures the Pier component to create the WACounter
(or, the steps done in Pier, if you're not doing this part in code).
>
> It in the blog page, it rendering some counter example based on the
following code:
>
>
-------------------------------------------------------------------------------------------------------------------
> blogPostEmbeddingComponents
> ^ (PBPost named: 'embedding-components')
> title: 'Embedding components';
> tags: #('components' 'embedding' 'Seaside');
> publication: TimeStamp now;
> contents:
> 'Embedding Seaside components is straightforward. Simply add a
component to a node within the site''s tree structure, then add a
reference to that component within a blog post. For example if you add a
component as a child of this post, you can then then embed the component
using the syntax. \+mychild\+. Here is an embedded ajaxified counter:
>
> +ajaxcounter+
>
> ...and the standard counter:
>
> +counter+
>
> Test Seaside''s state management by clicking on the \+\+ and \-\-
links. Pier blogs are ideal for demoing and describing your Seaside
components. In fact you can use Pier as the basis for application
development by embedding components in pages, especially if you are
building a content-rich site.';
> addChild: ((PRComponent named: 'ajaxcounter')
> componentClass: JQCounterFunctionalTest;
> yourself);
> addChild: ((PRComponent named: 'counter')
> componentClass: WACounter;
> yourself);
> yourself.
>
-----------------------------------------------------------------------------------------------------------------------------------
>
>
>
> You can display the blog page and do some operations + - on one counter,
>
> After if you click on any menu item ( Home or Blog itself )
>
> you lose the state of the counter instances.
>
> But i need to remember the state of the counters instance ( or any
other my root components ) so that when redisplay the page i display the
>
> right last update value.
>
>
> I hope that the example is understandable.
>
> I remain available for any further information.
>
> Thanks for any considerations,
>
>
> Dario Trussardi
>
>
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Hi,
Indeed. I added
<Location />
Order deny,allow
Allow from all
</Location>
and now it works.
I used an old Apache 2 before (not that the 2.2.14 is too new either), and this seems to have not been necessary before.
Cheers,
Doru
On 17 Dec 2012, at 08:15, Dmitry Dorofeev <dima-sender-3c337a(a)yasp.com> wrote:
> You need
>
> Allow from all
>
> Inside the <Location />
>
> -Dmitry
>
> On 17.12.2012, at 0:47, Tudor Girba <tudor(a)tudorgirba.com> wrote:
>
>> Hi,
>>
>> I have the following problem with an apache 2.2.14 (running on Ubuntu 10) + a pier image:
>>
>> - I have my little pier image running on port 8004
>>
>> - if I "curl localhost:8004/pier", I get a proper page back
>>
>> - I then have a configuration like:
>> <VirtualHost *:80>
>> ProxyPreserveHost On
>> ServerName humane-assessment.com
>>
>> DocumentRoot /srv/humane-assessment.com/web
>> <Directory /srv/humane-assessment.com/web>
>> Order deny,allow
>> Allow from all
>> </Directory>
>>
>> RewriteEngine On
>> RewriteCond /srv/humane-assessment.com/web/%{REQUEST_FILENAME} !-f
>> RewriteRule ^/(.*)$ http://localhost:8004/pier/$1 [proxy,last]
>> </VirtualHost>
>>
>> - I enabled extra: proxy.load, proxy.conf, proxy_http.load, rewrite.load
>>
>> - accessing files stored in /srv/humane-assessment.com/web works just fine (for example, http://humane-assessment.com/favicon.ico)
>>
>> - however, when I go to http://humane-assessment.com/, I get "403 Forbidden"
>>
>>
>> Does anyone have an idea why that is?
>>
>>
>> Cheers,
>> Doru
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "The coherence of a trip is given by the clearness of the goal."
>>
>>
>>
>>
>> _______________________________________________
>> 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
--
www.tudorgirba.com
"Next time you see your life passing by, say 'hi' and get to know her."
Hi,
I have the following problem with an apache 2.2.14 (running on Ubuntu 10) + a pier image:
- I have my little pier image running on port 8004
- if I "curl localhost:8004/pier", I get a proper page back
- I then have a configuration like:
<VirtualHost *:80>
ProxyPreserveHost On
ServerName humane-assessment.com
DocumentRoot /srv/humane-assessment.com/web
<Directory /srv/humane-assessment.com/web>
Order deny,allow
Allow from all
</Directory>
RewriteEngine On
RewriteCond /srv/humane-assessment.com/web/%{REQUEST_FILENAME} !-f
RewriteRule ^/(.*)$ http://localhost:8004/pier/$1 [proxy,last]
</VirtualHost>
- I enabled extra: proxy.load, proxy.conf, proxy_http.load, rewrite.load
- accessing files stored in /srv/humane-assessment.com/web works just fine (for example, http://humane-assessment.com/favicon.ico)
- however, when I go to http://humane-assessment.com/, I get "403 Forbidden"
Does anyone have an idea why that is?
Cheers,
Doru
--
www.tudorgirba.com
"The coherence of a trip is given by the clearness of the goal."
Call for Workshops
==================
In 2013, the European Conference on Object-Oriented Programming (ECOOP),
European Conference on Modelling Foundations and Applications (ECMFA)
and the European Conference on Software Architecture (ECSA) will be
collocated in Montpellier, France.
The 3 conferences will host an exciting array of workshops that
address a variety of topics in object-oriented technology,
Model-Driven Engineering and software architecture.
A workshop is a forum for exchanging ideas and theories that are still
in an evolutionary stage. Typically, a workshop will either address a
focused topic in depth or explore connections between one of the three
conferences' domains and other areas of interest.
ECOOP 2013, ECMFA 2013 and ECSA 2013 thus invite proposals for
workshops lasting half a day, one day or two days.
The workshops will be held Monday and Tuesday 1-2 July 2013.
Proposals
=========
A workshop proposal must be submitted as one PDF file.
It must include the following information, in this order:
* Name of the workshop (first page)
* Table of contents for the proposal (with page numbers)
* Duration of the workshop (half-day, full day, 2 days)
* Abstract: 150-200 words describing the workshop, suitable for the
conferences Web site
* Keywords and addressed domains.
* References to previous editions of the workshop (if any), including
name of host conference and number of participants to the workshop
each year
* Summary of the workshop format: e.g., refereed papers, and/or short
papers, and/or invited talks, and/or problem solving, and/or
brainstorming sessions. How will papers or other submissions be
reviewed?
* Description of how the workshop papers and results will be published
or otherwise disseminated (see the "Dissemination of Workshop Results"
section below)
* Preliminary Call For Workshop Papers describing the workshop's
focus, its main topics and its deadlines
* A (draft) list of the workshop PC members
* A list of the workshop organizers
* For each organizer of the workshop:
- name,
- affiliation
- contact information
- a brief biography (up to 200 words), focusing on the organizer's
expertise in the field and (if applicable) experience as a workshop
organizer
* Primary contact: identify one organizer as the primary contact
* Any special requirements that the workshop may have
Workshop Schedule Constraints
=============================
Each workshop will have to pay attention to the following timing constraints :
* the program must be made public before the early registration
deadline of the conferences; we thus expect you to make it available
around mid-may;
* the workshop must be able to consider submissions of papers rejected
by the conferences, and have these enter its reviewing process; we
thus expect you to make your submission deadline around mid-april;
* the workshop must send its Call For Papers at least one month before
submission deadline; we thus expect you to send your CFP around
mid-march;
Proposal Submission and Review
==============================
Workshop proposals should be submitted by email to the workshop chairs,
at ws-chairs-ec-montpellier-2013(a)inria.fr
Proposals will be reviewed by the workshop chairs.
Proposals will be selected based on their relevance to the conferences
aims, beneficiaries, and timely advances in their respective topics.
In particular, proposals will be evaluated according to the following
criteria:
- The potential to advance the state of research and practice
- The organizers' commitment to stimulate discussion at the workshop
- The organizers’ commitment to arrange for sensible digital and
permanent post-meeting proceedings
- The organizers' experience and ability to lead a successful workshop
- Timeliness and expected interest in the workshop topics
- The balance and synergy between the proposed workshops.
- The continuity of previous years workshops
*Workshop proposal deadline: January 10th*
*Workshop proposal notification: January 16th*
Workshop proposals may still be submitted after January 10th, till
February 15th, and will be evaluated with the same criteria. But in
addition these "late" proposals may only be accepted if their themes
do not interfere with those of already accepted workshops. We thus
strongly advise you to submit your workshop proposal as soon as
possible, and *before* January 10th.
Dissemination of Workshop Results
=================================
A proposal should clearly state how the results of the workshop, that
is the papers and other outcomes, will be made available to
participants and others, both before and after the workshop event. ACM
DL publications are encouraged.
Contact
=======
For additional information about this Call for Workshops, please
contact the workshop chairs at ws-chairs-ec-montpellier-2013(a)inria.fr.
An up-to-date version of this call for workshops may be found at:
http://info-web.lirmm.fr/ec-montpellier-2013/index.php/satelliteevents?id=1…
Workshop Chairs
===============
Olivier Zendra, INRIA Nancy - France
Reda Bendraou, Université Pierre et Marie Curie - France
Damien Cassou, Université Lille 1 - France
Stéphane Ducasse, INRIA Lille - France
Hi,
I am working on a pier page, and I have a couple of images in it that seem to be slow to load, although they are served through apache.
It is true that the images are slightly large (~230K), but still I think they appear too slow.
The example is here:
http://www.humane-assessment.com/
Anyone has any idea of why this would happen?
Cheers,
Doru
--
www.tudorgirba.com
"Live like you mean it."
All my tests passed, and I thought I was done porting - it's never that
easy.
So, the problem I have is with PRComponent. In my case, the magritte
description of componentClass is dependent on one of the
prototypeInstance's values. Things worked before there was a prototype
instance, just using the componentClass. Now, there is a problem in:
initializeVisualComponentSettings: aComponent link: anInternalLink
At this point in the initialization, there is a nil value, in the place
which is used to dynamically determine what the rest of the magritte
description should be.
I think the fix is to ensure that when I have a nil value, the
corresponding magritte description generated should be appropriate for
the situation - i.e. it should not include the attribute descriptions
that are causing the problem in the above initialization.
Hi,
I am trying to set up a Pier3 webpage with Pier Admin inside, but I
have problems with the Apache2 configuration.
Does anyone have a sample of such a configuration?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi,
I now encounter the following issue: I can edit and change the CSS
file associated with a structure, and if I inspect the contents of the
PRFile instance, the text is indeed changed. However, the page still
renders according to the old stylesheet. The problem appears even if I
empty the browser cache.
Does anyone know where the problem might come from?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
