smallwiki

smallwiki@list.inf.unibe.ch

2312 discussions

Re: [Seaside] Modal dialogs that appear with their "background"

by Diego Lont

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

10 years, 6 months

Re: [Seaside-dev] Re: Pier 3 image editor fails with MNU: JQTabs>>onSelect:

by Diego Lont

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

10 years, 6 months

Pier 3 image editor fails with MNU: JQTabs>>onSelect:

by John Borden

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

10 years, 6 months

Re: First pass analysis Re: Build failed in Jenkins: Pillar » 40,development,vm #558

by Stephan Eggermont

Uhm, Pharo 4 identifies itself as Pharo 4, not Pharo 3.x. All configurations need updates Stephan

10 years, 6 months

First pass analysis Re: Build failed in Jenkins: Pillar » 40,development,vm #558

by Ben Coman

The error is... MessageNotUnderstood: ByteString>>beginsWithSubCollection: This is a *Grease-Pharo30-Core extension to SequenceableCollection Build#557 console log has... Loaded -> ConfigurationOfGrease-JohanBrichau.263 Project: Grease stable [1.1.9] Loaded -> Grease-Core-JohanBrichau.86 --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ --- cache Loaded -> Grease-Pharo30-Core-pmm.15 --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ --- cache Build#558 console load only has... Loaded -> ConfigurationOfGrease-JohanBrichau.264 Project: Grease stable [1.1.9] Loaded -> Grease-Core-JohanBrichau.86 --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ --- cache ConfigurationOfGrease-JohanBrichau.263 has development: spec spec for: #'common' version: '1.1.9' ConfigurationOfGrease-JohanBrichau.264 has development: spec spec for: #'common' version: '1.1.10' #version1109: and #version1110: are the same, except only the former has... blessing: #'release'; package: 'Grease-Slime' with: 'Grease-Slime-topa.26'; while the latter has... blessing: #'development'; package: 'Grease-Slime' with: 'Grease-Slime-JohanBrichau.27'; So from my limited Metacello experience I can't see why Grease-Pharo30-Core was not loaded. cheers -ben ci-pharo-contribution(a)inria.fr wrote: > See <https://ci.inria.fr/pharo-contribution/job/Pillar/PHARO=40,VERSION=developm…> > > ------------------------------------------ > Started by upstream project "Pillar" build number 558 > originally caused by: > Started by timer > Building remotely on pharo-contribution-linux64-3.ci.inria.fr in workspace <https://ci.inria.fr/pharo-contribution/job/Pillar/PHARO=40,VERSION=developm…> > > Deleting project workspace... Deleting old artifacts from #556 > [vm] $ /bin/sh -xe /tmp/hudson8671814050563950483.sh > + set -xv > > # jenkins puts all the params after a / in the job name as well :( > export JOB_NAME=`dirname $JOB_NAME` > + dirname Pillar/PHARO=40,VERSION=development,VM=vm > + export JOB_NAME=Pillar > > wget --quiet -O - get.pharo.org/$PHARO+$VM | bash > + bash > + wget --quiet -O - get.pharo.org/40+vm > Downloading the latest 40 Image: > http://files.pharo.org/image/40/latest.zip > Pharo.image > Downloading the latest pharoVM: > http://files.pharo.org/vm/pharo/linux/stable.zip > pharo-vm/pharo > Downloading PharoV10.sources: > http://files.pharo.org/sources//PharoV10.sources.zip > Downloading PharoV20.sources: > http://files.pharo.org/sources//PharoV20.sources.zip > Downloading PharoV30.sources: > http://files.pharo.org/sources//PharoV30.sources.zip > Creating starter scripts pharo and pharo-ui > > ./pharo Pharo.image save $JOB_NAME --delete-old > + ./pharo Pharo.image save Pillar --delete-old > ./pharo $JOB_NAME.image --version > version.txt > + ./pharo Pillar.image --version > > REPO=http://smalltalkhub.com/mc/Pier/$JOB_NAME/main > + REPO=http://smalltalkhub.com/mc/Pier/Pillar/main > ./pharo $JOB_NAME.image config $REPO ConfigurationOf$JOB_NAME --install=$VERSION --group='ALL' > + ./pharo Pillar.image config http://smalltalkhub.com/mc/Pier/Pillar/main ConfigurationOfPillar --install=development --group=ALL > 'Installing ConfigurationOfPillar development' > > Loading 0.12-baseline of ConfigurationOfPillar... > Fetched -> ConfigurationOfGrease-JohanBrichau.264 --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/ --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/ > Loaded -> ConfigurationOfGrease-JohanBrichau.264 --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/ --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/ > Fetched -> ConfigurationOfSton-SvenVanCaekenberghe.10 --- http://smalltalkhub.com/mc/SvenVanCaekenberghe/STON/main/ --- http://smalltalkhub.com/mc/SvenVanCaekenberghe/STON/main/ > Loaded -> ConfigurationOfSton-SvenVanCaekenberghe.10 --- http://smalltalkhub.com/mc/SvenVanCaekenberghe/STON/main/ --- http://smalltalkhub.com/mc/SvenVanCaekenberghe/STON/main/ > Fetched -> ConfigurationOfMustache-NorbertHartl.33 --- http://smalltalkhub.com/mc/NorbertHartl/Mustache/main/ --- http://smalltalkhub.com/mc/NorbertHartl/Mustache/main/ > Loaded -> ConfigurationOfMustache-NorbertHartl.33 --- http://smalltalkhub.com/mc/NorbertHartl/Mustache/main/ --- http://smalltalkhub.com/mc/NorbertHartl/Mustache/main/ > Project: Grease stable [1.1.9] > Fetched -> Grease-Core-JohanBrichau.86 --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ > Project: Mustache stable [0.60] > Fetched -> Mustache-Core-NorbertHartl.23 --- http://smalltalkhub.com/mc/NorbertHartl/Mustache/main/ --- http://smalltalkhub.com/mc/NorbertHartl/Mustache/main/ > Project: STON stable [0.9] > Fetched -> STON-Core-SvenVanCaekenberghe.49 --- http://ss3.gemstone.com/ss/STON --- http://ss3.gemstone.com/ss/STON > Fetched -> Pillar-Model-DamienCassou.83 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-ExporterCore-DamienCassou.84 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-ExporterMarkdown-BenComan.59 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-ExporterLaTeX-BenComan.54 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-ExporterHTML-DamienCassou.46 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-ExporterPillar-DamienCassou.9 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-ExporterText-DamienCassou.5 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-Tests-Model-DamienCassou.97 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-Tests-ExporterCore-DamienCassou.56 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-Tests-ExporterMarkdown-BenComan.18 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-Tests-ExporterLaTeX-BenComan.83 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-Tests-ExporterHTML-BenComan.33 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-Tests-ExporterPillar-BenComan.6 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-Tests-ExporterText-DamienCassou.8 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-PharoInspector-DamienCassou.1 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-Cli-BenjaminVanRyseghem.7 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Fetched -> Pillar-GitBook-DamienCassou.1 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- http://smalltalkhub.com/mc/Pier/Pillar/main/ > Loaded -> Grease-Core-JohanBrichau.86 --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ --- cache > Loaded -> Mustache-Core-NorbertHartl.23 --- http://smalltalkhub.com/mc/NorbertHartl/Mustache/main/ --- cache > Loaded -> STON-Core-SvenVanCaekenberghe.49 --- http://ss3.gemstone.com/ss/STON --- cache > PRScript>>hasCaption(caption is shadowed) > Loaded -> Pillar-Model-DamienCassou.83 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-ExporterCore-DamienCassou.84 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > PRMarkdownCanvas>>htmlTag (PRHTMLTag is Undeclared) > > Loaded -> Pillar-ExporterMarkdown-BenComan.59 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-ExporterLaTeX-BenComan.54 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-ExporterHTML-DamienCassou.46 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-ExporterPillar-DamienCassou.9 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-ExporterText-DamienCassou.5 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-Tests-Model-DamienCassou.97 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-Tests-ExporterCore-DamienCassou.56 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-Tests-ExporterMarkdown-BenComan.18 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-Tests-ExporterLaTeX-BenComan.83 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-Tests-ExporterHTML-BenComan.33 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-Tests-ExporterPillar-BenComan.6 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-Tests-ExporterText-DamienCassou.8 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-PharoInspector-DamienCassou.1 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-Cli-BenjaminVanRyseghem.7 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > Loaded -> Pillar-GitBook-DamienCassou.1 --- http://smalltalkhub.com/mc/Pier/Pillar/main/ --- cache > ...finished 0.12-baseline./pharo $JOB_NAME.image test --junit-xml-output "$JOB_NAME.*" > + ./pharo Pillar.image test --junit-xml-output Pillar.* > 'Running tests in 17 Packages' > > > > echo ===================================================== > + echo ===================================================== > ===================================================== > echo = Try to compile EnterprisePharo > + echo = Try to compile EnterprisePharo > = Try to compile EnterprisePharo > git clone --depth 1 https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english.git enterprise_pharo > + git clone --depth 1 https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english.git enterprise_pharo > Cloning into 'enterprise_pharo'... > cd enterprise_pharo > + cd enterprise_pharo > ./download.sh > + ./download.sh > --2014-06-09 00:43:32-- https://ci.inria.fr/pharo-contribution/job/Pillar/PHARO=30,VERSION=stable,V… > Resolving ci.inria.fr (ci.inria.fr)... 193.51.193.223 > Connecting to ci.inria.fr (ci.inria.fr)|193.51.193.223|:443... connected. > HTTP request sent, awaiting response... 200 OK > Length: 10573570 (10M) [application/zip] > Saving to: `image5518x.zip' > > > 0% [ ] 0 --.-K/s > 44% [================> ] 4,678,072 22.3M/s > 91% [==================================> ] 9,714,320 23.2M/s > 100%[======================================>] 10,573,570 23.2M/s in 0.4s > > 2014-06-09 00:43:32 (23.2 MB/s) - `image5518x.zip' saved [10573570/10573570] > > Pharo.image > Pharo.changes > pillar > --2014-06-09 00:43:33-- http://get.pharo.org/vm > Resolving get.pharo.org (get.pharo.org)... 128.93.162.72 > Connecting to get.pharo.org (get.pharo.org)|128.93.162.72|:80... connected. > HTTP request sent, awaiting response... 200 OK > Length: 5311 (5.2K) [text/html] > Saving to: `STDOUT' > > 0K ..... 100% 652M=0s > > 2014-06-09 00:43:33 (652 MB/s) - written to stdout [5311/5311] > > Downloading the latest pharoVM: > http://files.pharo.org/vm/pharo/linux/stable.zip > pharo-vm/pharo > Downloading PharoV10.sources: > http://files.pharo.org/sources//PharoV10.sources.zip > Downloading PharoV20.sources: > http://files.pharo.org/sources//PharoV20.sources.zip > Downloading PharoV30.sources: > http://files.pharo.org/sources//PharoV30.sources.zip > Creating starter scripts pharo and pharo-ui > Preparing Pillar image > StartupPreferencesLoader > 'ok' > cp ../Pillar.image Pharo.image > + cp ../Pillar.image Pharo.image > cp ../Pillar.changes Pharo.changes > + cp ../Pillar.changes Pharo.changes > ./pharo Pharo.image eval --save "StartupPreferencesLoader allowStartupScript: false." > + ./pharo Pharo.image eval --save StartupPreferencesLoader allowStartupScript: false. > StartupPreferencesLoader > ./pharo Pharo.image eval --save "Deprecation raiseWarning: false; showWarning: false." > + ./pharo Pharo.image eval --save Deprecation raiseWarning: false; showWarning: false. > Deprecation > ./compile.sh > + ./compile.sh > Generating files for all chapters > [31mMessageNotUnderstood: ByteString>>beginsWithSubCollection: > [0mByteString(Object)>>doesNotUnderstand: #beginsWithSubCollection: > [ :markup | > (aLine beginsWithSubCollection: markup) > ifTrue: [ ^ aBlock value: (self class lineMatcher at: markup) ] ] in PRMatcherManager>>withItemParserForLine:do: in Block: [ :markup | ... > Array(SequenceableCollection)>>do: > PRMatcherManager>>withItemParserForLine:do: > PRDocumentParser>>parseLine: > PRDocumentParser>>parse > PRDocumentParser class>>parseStream: > PRDocumentParser class>>parse: > [ :input | > | input2 | > "The following are here because of case #12259: 'FileSystem memory reads/writes using a binary stream by default'." > input2 := input. > (aFile fileSystem store isKindOf: MemoryStore) > ifTrue: [ input2 := input2 contents asString readStream ]. > PRDocumentParser parse: input2 ] in PRExportConfiguration>>parseFile: in Block: [ :input | ... > [ aBlock value: stream ] in FileReference(AbstractFileReference)>>readStreamDo: in Block: [ aBlock value: stream ] > BlockClosure>>ensure: > FileReference(AbstractFileReference)>>readStreamDo: > PRExportConfiguration>>parseFile: > PRExportConfiguration>>parseAllInputFiles > PRExportConfiguration>>exportAllInOneOutputFile > PRExportConfiguration>>export > PRExportConfiguration>>export: > [ subconfName ifNil: [ configuration export ] ifNotNil: [ configuration export: subconfName ] ] in PRExportCommandLineHandler>>export in Block: [ subconfName ifNil: [ configuration export ] ifNo...etc... > BlockClosure>>on:do: > PRExportCommandLineHandler>>export > PRExportCommandLineHandler>>activate > PRExportCommandLineHandler class(CommandLineHandler class)>>activateWith: > [ aCommandLinehandler activateWith: commandLine ] in PRCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in Block: [ aCommandLinehandler activateWith: commandLine ] > BlockClosure>>on:do: > PRCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: > PRCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand > PRCommandLineHandler(BasicCommandLineHandler)>>handleArgument: > [ self handleArgument: (self arguments ifEmpty: [ '' ] ifNotEmpty: [ :arguments | arguments first ]) ] in PRCommandLineHandler(BasicCommandLineHandler)>>activate in Block: [ self handleArgument: (self arguments ifEmpty: [ ...etc... > BlockClosure>>on:do: > PRCommandLineHandler(BasicCommandLineHandler)>>activate > [0mBuild step 'Execute shell' marked build as failure > Archiving artifacts > Recording test results > >

10 years, 6 months

Pillar compile.sh

by Ben Coman

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

10 years, 6 months

[ANN] Generating beautiful html books from Pillar

by Damien Cassou

Nicolas Petton and I are proud to announce the possibility to create really nice HTML books from Pillar (I must thank https://github.com/GitbookIO/gitbook as well). The first book to get this nice layout is the Pillar documentation: http://damiencassou.gitbooks.io/pillar/introduction.pier.html -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

10 years, 6 months

PIllar >> #visitAnnotatedParagraph:

by Ben Coman

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

10 years, 6 months

[Pharo-users] [smallwiki] Pillar annotations for Latex

by Ben Coman

> Hi Ben, > > On Thu, May 22, 2014 at 6:09 PM, Ben Coman<btc(a)openinworld.com> wrote: > > Now is there any important function missing, or is there a better way to do > > this? > > thank you for your contribution. > > I would try to generate this instead: > > \begin{note} > foo bar baz > \end{note} > > This environment is meant for this. To output the \begin and \end parts, use > > canvas environment > > (look at the senders of #environment in the PRLaTeXWriter class for examples) > > To output the text, you can just write > > super visitAnnotatedParagraph: aParagraph > > > > I also want add an annotation type, which I'll describe in a following post. > > > I should we should think a bit how these should be handled. In the > meantime, you can just hack around :-). And please add unit tests. > > -- > Damien Cassou So I determined that the following works well... PRLaTeXWriter>>visitAnnotatedParagraph: anAnnotatedParagraph "Pier seams to lack consistency here ..." 'todo' = anAnnotatedParagraph annotation asLowercase ifTrue: [ ^ self visitCommentedLine: anAnnotatedParagraph ]. canvas environment name: 'note' ; with: [ super visitAnnotatedParagraph: anAnnotatedParagraph ]. to process Pillar markup... @@note Pay attention to the class definition for your new ""==BlankCellTest=="". It must be a subclass of the class ""==TestCase=="". This is easy to overlook. If you did it wrong already, no problem, just go back and correct it now and then save the code again. Within a class, methods are organised into "protocols" that are shown in the third browser pane from the left of Figure *testCellStateShouldBeOffEmpty*. We will group our "tests" inside a protocol of the same name. to produce this nice looking PDF showing the note indented with dividing lines... Now that was real easy to do!! Thanks for making Pillar accessible. I can't imagine making a similar change as easy in a Markdown processor in some other language. --------------- Next, in common.tex [1] I found... { \newcommand{\dothisicon}{\raisebox{-.5ex}{\includegraphics[height=1.2em]{pharo}}} \newcommand{\dothis}[1]{% \medskip \noindent\dothisicon \ifx#1\empty\else\quad\emph{#1}\fi \par\smallskip\nopagebreak} } and discovered I could do this in the Pillar markup... Before defining a class we should define a package to contain our classes. When we save a package all the classes will be saved together. It is a good practice to group together classes that work together. {{{latex: \dothis{Right-click on the background and open a System Browser.} \dothis{In the package list of the System Browser, choose "add package" to add a new package. Use the name "LaserG }}} to produce in the PDF two Pharo icons on separate lines... But that is awkward and verbose to do each time, and I though it would be nice for Pillar to handle this as an annotation like this... Before defining a class we should define a package to contain our classes. When we save a package all the classes will be saved together. It is a good practice to group together classes that work together. @@dothis Right-click on the background and open a System Browser. @@dothis In the package list of the System Browser, choose "add package" to add a new package. Use the name "LaserGame-Model". so I found I could do that by added the following hack to PRLaTeXWriter>>visitAnnotatedParagraph: ... 'dothis' = anAnnotatedParagraph annotation asLowercase ifTrue: [ ^ self writeRawDuring: [ stream newLine. stream << '\dothis{' . stream << anAnnotatedParagraph text trimBoth . stream << '} ' . ]. ]. However changing this to be less of a hack like this... 'dothis' = anAnnotatedParagraph annotation asLowercase ifTrue: [ ^ canvas command name: 'dothis' ; parameter: [ super visitAnnotatedParagraph: anAnnotatedParagraph ] ]. doesn't quite work, since the first Pharo icon runs onto the previous line... That can be fixed as follows.... PRLaTeXCommand>>name: aString stream newLine. "<---THIS LINE ADDED" stream << $\ << aString but I don't know if that is the right thing to do. Maybe there are times when you want commands to run on from a line. What would be the right thing? Also, is it reasonable to add this new annotation type? i.e. might it be integrated soon ? :) :) . This would really help with the Laser Game tutorial. [1] https://github.com/bencoman/PharoLaserGameTutorial/blob/master/common.tex cheers -ben P.S. This is my first post to the mail list using PostBox on OSX. Let me know if you notice any issues with it being not plain text and if you have any advice ensure plain text posts in PostBox.

10 years, 6 months

ChainAccessor

by Diego Lont

Hi all, I regularly run into the trouble that using a chain accessor gives the error message: MessageNotUnderstood: receiver of “…” is nil. I now spot it faster what I have done wrong here: I use a chain accessor on a un initialised value. I have 3 typical scenario’s where I use a chain accessor: 1. I have a variable that is a collection of some values, that I initialise always, and I want to access its properties. 2. I want to display some extra info, or maybe even allow editing some details of a required “base” value. 3. I want to display some extra info on a “base” value that might be initialised. I propose that on reading, it returns a nil value, when the previous value is nil already. The write method I want to leave as is. Going back to my scenario’s: 1. In this case I guess returning an error would be proper, but on the other hand: I will get this hard error too when I try to write to this variable. So I will still find out I did something wrong (forgot initialisation) when I test properly. 2. In this case, the first time reading generates an error, as the user has not made a choice yet. Returning nil there would be the appropriate behaviour. 3. In this case, returning nil would be the appropriate behaviour, as it only displays information. My question to you all would be: Do you agree that the default behaviour should be to return nil, instead of generate an error? As this would be easier in use? Alternatives: > Modify the description, adding a property that indicates if an error in reading should be blocking or should be interpreted as “nil”. > Create an accessor for each occurrences I have, thus avoiding using a chain accessor (i.e. by using a builder that replaces these accessors). Cheers, Diego

10 years, 6 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

smallwiki