Hi,
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.
Bye
--
Damien Cassou
http://damiencassou.seasidehosting.st
Updated to use onActivate: instead - changes in Pier-Wysiwyg 90.
Thanks,
John
On Jun 16, 2014, at 02:57 AM, Diego Lont <diego.lont(a)delware.nl> wrote:
> Hi Johan,
>
> I did not know that. So this means, we need a different fix for the problem in the Pier site. I see Johan has reverted the change for JQuery, I now did this for the configuration.
>
> John,
>
> Can you make a fix in the Pier add-on? If you give me your username on smalltalkhub I will add you to the pier team.
>
> Regards,
> Diego
>
> On 16 Jun 2014, at 09:40, Johan Brichau <johan(a)inceptive.be > wrote:
>
> > Hi John, Diego,
> >
> > Seaside 3.1.1 comes with jQuery UI 1.9
> > JQuery-UI 1.9+ does _not_ support the onSelect: event. [1]
> >
> > This method was therefore intentionally removed and may not be added again.
> >
> > best regards
> > Johan
> >
> > [1] http://api.jqueryui.com/tabs/
> >
> >
> > On 16 Jun 2014, at 09:15, Diego Lont <diego.lont(a)delware.nl > wrote:
> >
> > > Hi John,
> > >
> > > Thanks for spotting this and providing a fix.
> > >
> > > I could not find your user, so I committed your fix myself. I also updated the configuration of Seaside, such that version 3.1.2 of Seaside3 now contains this fix. As this is the development version and Pier depends on the stable (released) version, it will take a bit before this fix is actually included in the build you mention.
> > >
> > > Cheers,
> > > Diego
> > >
> > > On 15 Jun 2014, at 21:40, John Borden <jborden23(a)mac.com > wrote:
> > >
> > > > The latest image from https://ci.inria.fr/pharo-contribution/job/Pier3Addons/PHARO=30,VERSION=rel… starts fine, but when editing a page it fails with the error:
> > > >
> > > > Contents:
> > > > MessageNotUnderstood: JQTabs > >onSelect:
> > > >
> > > > Your request could not be completed. An exception occurred.
> > > >
> > > > Attached is a fix, would anyone have access to add write permissions for me to http://smalltalkhub.com/mc/Seaside/Seaside31/main/ ?
> > > >
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > John
> > > >
> > > > <JQuery-UI-JohnCBorden.90.mcz >_______________________________________________
> > > > Magritte, Pier and Related Tools ...
> > > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki
> > >
> > > _______________________________________________
> > > seaside-dev mailing list
> > > seaside-dev(a)lists.squeakfoundation.org
> > > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
> >
> > _______________________________________________
> > seaside-dev mailing list
> > seaside-dev(a)lists.squeakfoundation.org
> > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
>
> _______________________________________________
> Magritte, Pier and Related Tools ...
> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
Hi all,
I started a tutorial on QCMagritte. I used the seaside tutorial by James Foster (http://seaside.gemtalksystems.com/tutorial.html) as an example, as I believe it should be that easy to use QCMagritte.
I would appreciate it, if someone wants to give it a try. It would consider it a pro if you do not know (QC)Magritte, as I intend to start with the basics. I am now completed chapter 4: a simple todo application.
Cheers,
Diego
On 05 Jun 2014, at 15:16, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote:
> I normally find/feel QCMagritte has a lot of things I could use, but
> with scarce documentation it is really difficult to me to know where
> to start with.
>
> Would you provide a simple example of how to replace #call:/show: with
> announcements?
>
> Regards!
>
> Esteban A. Maringolo
>
>
> 2014-06-04 12:51 GMT-03:00 Stephan Eggermont <stephan(a)stack.nl>:
>> We have very few call:'s left in our apps. Most navigation is done with announcements.
>> We use a session subclass that has an announcer and delegate to that.
>>
>> You can find sample code in both Deltawerken (DESession & DEPageChoice) and QCMagritte
>> (QCSession & QCPageChoice).
>>
>> You can find a pre-made image (for Pharo 2 and 3) at http://ci.inria.fr/pharo-contribution/QCMagritte
>>
>> Stephan_______________________________________________
>> 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
Hi Johan,
I did not know that. So this means, we need a different fix for the problem in the Pier site. I see Johan has reverted the change for JQuery, I now did this for the configuration.
John,
Can you make a fix in the Pier add-on? If you give me your username on smalltalkhub I will add you to the pier team.
Regards,
Diego
On 16 Jun 2014, at 09:40, Johan Brichau <johan(a)inceptive.be> wrote:
> Hi John, Diego,
>
> Seaside 3.1.1 comes with jQuery UI 1.9
> JQuery-UI 1.9+ does _not_ support the onSelect: event. [1]
>
> This method was therefore intentionally removed and may not be added again.
>
> best regards
> Johan
>
> [1] http://api.jqueryui.com/tabs/
>
>
> On 16 Jun 2014, at 09:15, Diego Lont <diego.lont(a)delware.nl> wrote:
>
>> Hi John,
>>
>> Thanks for spotting this and providing a fix.
>>
>> I could not find your user, so I committed your fix myself. I also updated the configuration of Seaside, such that version 3.1.2 of Seaside3 now contains this fix. As this is the development version and Pier depends on the stable (released) version, it will take a bit before this fix is actually included in the build you mention.
>>
>> Cheers,
>> Diego
>>
>> On 15 Jun 2014, at 21:40, John Borden <jborden23(a)mac.com> wrote:
>>
>>> The latest image from https://ci.inria.fr/pharo-contribution/job/Pier3Addons/PHARO=30,VERSION=rel… starts fine, but when editing a page it fails with the error:
>>>
>>> Contents:
>>> MessageNotUnderstood: JQTabs>>onSelect:
>>>
>>> Your request could not be completed. An exception occurred.
>>>
>>> Attached is a fix, would anyone have access to add write permissions for me to http://smalltalkhub.com/mc/Seaside/Seaside31/main/ ?
>>>
>>>
>>>
>>> Thanks,
>>>
>>> John
>>>
>>> <JQuery-UI-JohnCBorden.90.mcz>_______________________________________________
>>> Magritte, Pier and Related Tools ...
>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>> _______________________________________________
>> seaside-dev mailing list
>> seaside-dev(a)lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
> _______________________________________________
> seaside-dev mailing list
> seaside-dev(a)lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
Hi all,
./compile.sh can be passed a parameter to compile only a specific file
rather than the whole book. Now I consider this probably only occurs
during development with a human executing the script (rather than some
CI process which will be processing the whole book) and I'm finding it
useful to automatically fire off a PDF Viewer on the generated file, as
per the line below tagged "ADDED".
if [[ $# -eq 1 ]]; then
dir=$(dirname "$1") # e.g., Zinc
pier_file=$(basename "$1") # e.g., Zinc.pier
pillar_one "$1"
produce_pdf "${dir}" "${pier_file}"
open "${dir}"/"${pier_file}".pdf # <----ADDED
else
pillar_all
compile_chapters
compile_latex_book
fi
Is this something others would find useful? or can you see issues with
it? Having this mod makes my working area dirty, and 'git clean' blows
it away - so I'd like to integrate something like it. Now the above
works for me on OSX, but for flexibility to deal with other platforms,
the "open" command could be replaced with an environment variable, and
do nothing if environment variable does not exist.
What do you think?
cheers -ben
PRMarkdownWriter >>visitAnnotatedParagraph: says "Pier seems to lack
consistency here ...".
Indeed, for #visitAnnotatedParagraph: we currently have:
* PRPillarWriter outputs all annotations unchanged
* PRMarkdownWriter
* prepends the the annotationLabel to the annotationText
* has special handling for @@todo by calling #visitCommentedLine:
* indicates it does some kind of nesting in a custom way; but I
can't work out the semantics; and it interrupts nested list numbering
similar to what I reported for comments.
* PRVisitor
* throws away the annotationLabel by just calling #visitParagraph
* knows nothing about @@todo
* knows nothing about nesting
* PRHTMLWriter has no definition inheriting from PRVisitor
* PRLaTeXWriter has no definition inheriting from PRVisitor
* PRTextWriter has no definition inheriting from PRVisitor
To bring some consistency I propose to...
1. Prepend annotationLabel for all the xxWriters
2. Change PRMarkdownWriter to use the code I implemented for nested
comments. Have all xxWriters use this also.
3. Drop the @@todo from PRMarkdownWriter, since if you want ToDos to be
hidden like a comment, you should just use a comment, e.g." %todo ..."
. However this change would alter the semantics of existing users of
Pier. So what is the process for such changes? Announce here and wait
some period? For consideration, there are currently no tests for
annotated paragraphs, so this could be considered outside the existing
API ;) - and so I'll add tests, which will be simpler without @@todo.
cheers -ben