- Pharo-users - lists.pharo.org

MorphTree behavior changed
by Hilaire Fernandes June 6, 2014

June 6, 2014

Hi, why when morph tree send updateList there is an announcement from the model? It was not the case before. Thanks Hilaire -- Dr. Geo http://drgeo.eu

3 4

Re: [Pharo-users] PIllar >> #visitAnnotatedParagraph:
by Ben Coman June 5, 2014

June 5, 2014

Damien Cassou wrote: > On Sun, Jun 1, 2014 at 6:10 PM, Ben Coman<btc(a)openinworld.com> wrote: >> Yes. I am doing something similar. btw, is it a strong convention that Tex commands and environments are all lowercase? That is, should I force the annotation label in "\begin{note}" to lowercase, or should I pass that through unchanged. > > > I think you should not change anything. Is it up to the writer to do > something not stupid. > >>> For Markdown, we should probably have the same solution as for HTML. >> I had a hunt around and it seems that Markdown doesn't support paragraph styles. And the workaround specified here... >> http://stackoverflow.com/questions/1058933/can-i-define-a-class-name-on-par… >> >> apparently does not work on github... >> https://github.com/github/markup > > in pillar we have both Markdown and GithubMarkdown as export options. > So we can have a solution dedicated to github if required. > > >> But Hey! Check this out... >> https://github.com/github/markup/blob/master/CONTRIBUTING.md >> >> Maybe we could add a Pillar-->HTML processor to Github? > > > There should not be any technical problem to do that. Do you want to > try? I can help if you have problems. > > >> "If your markup is in a language other than Ruby, drop a translator script in lib/github/commands which accepts input on STDIN and returns HTML on STDOUT..." >> https://github.com/github/markup/blob/master/lib/github/markups.rb >> >> >> So it seems that Text and Markdown cannot produce different formatted paragraphs. > > for text it is clear. For Markdown I'm still not sure if it is > possible or not. Maybe a<div class=<annotation>> would work. > > >> In those two cases, I still lean towards putting the annotation label in the output, but I'm happy enough to leave it out. > > > for text I think we should not change the current export. For > Markdown, I leave the decision to you. > > I've uploaded the updates to make annotations more consistent, and added the \dothis LaTeX command being used in the PharoLaserGame tutorial. source annotation test # item 1 @@note anno1 @@dothis anno2 ## item 11 @@note anno3 ## item 12 @@dothis anno4 ## item 13 --to=pillar annotation test # item 1 @@note anno1 @@dothis anno2 # ## item 11 @@note anno3 # ## item 12 @@dothis anno4 # ## item 13 Now this output is not the same and the source. Should I try to fix this the same as I did for comments. --to=html <div class="container"> annotation test <ol><li> item 1 </li></ol> anno1 anno2 <ol><li> <ol><li> item 11 </li></ol> </li></ol> anno3 <ol><li> <ol><li> item 12 </li></ol> </li></ol> anno4 <ol><li> <ol><li> item 13 </li></ol></li></ol> </div> --to=markdown annotation test 1. item 1 ^M ^M anno1^M ^M anno2^M ^M 1. 1. item 11 ^M ^M anno3^M ^M 1. 1. item 12 ^M ^M anno4^M ^M 1. 1. item 13 btw, what are all these non-break-spaces "^M ^M" for? --to=markdown \begin{document}^M^M annotation test \begin{enumerate} \item item 1 \end{enumerate} \begin{note} anno1 \end{note} \dothis{ anno2 }\begin{enumerate} \item \begin{enumerate} \item item 11 \end{enumerate} \end{enumerate} \begin{note} anno3 \end{note} \begin{enumerate} \item \begin{enumerate} \item item 12 \end{enumerate} \end{enumerate} \dothis{ anno4 }\begin{enumerate} \item \begin{enumerate} \item item 13 \end{enumerate} \end{enumerate} ^M^M\end{document}^M --to=text annotation test 1. item 1 anno1 anno2 1. 1. item 11 anno3 1. 1. item 12 anno4 1. 1. item 13 cheers -ben

2 1

Re: [Pharo-users] Saving Seaside components to Monticello
by phil＠highoctane.be June 4, 2014

June 4, 2014

Le 4 juin 2014 21:17, "spearson" <sam(a)xofz.com> a Ã©crit : > > Hello, > I created a Monticello repository on Smalltalkhub. When I commit my > package, my Object subclasses all get saved to the repository. However, > only my WAComponent subclass class definition gets saved (instance/class > variables). The renderContentOn: and updateRoot: methods are not getting > saved to the repository. Is this because they are overridden methods and > not new methods? > > How can I save my renderContentOn: and updateRoot: methods to the > repository? > > Strange. Never had this issue with Seaside. Phil > > -- > View this message in context: http://forum.world.st/Saving-Seaside-components-to-Monticello-tp4761679.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

2 1

Saving Seaside components to Monticello
by spearson June 4, 2014

June 4, 2014

Hello, I created a Monticello repository on Smalltalkhub. When I commit my package, my Object subclasses all get saved to the repository. However, only my WAComponent subclass class definition gets saved (instance/class variables). The renderContentOn: and updateRoot: methods are not getting saved to the repository. Is this because they are overridden methods and not new methods? How can I save my renderContentOn: and updateRoot: methods to the repository? -- View this message in context: http://forum.world.st/Saving-Seaside-components-to-Monticello-tp4761679.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

1 0

HTML5 Generation
by Larry Staton Jr. June 4, 2014

June 4, 2014

Iâm writing an implementation of Webmachine[1] in Pharo and Iâm at the point where I need to generate some resources. Webmachine does not care how you represent your resources, so Iâm looking for a way to represent my resources in text/html (or application/xml+xhtml). In Ruby, I use ROAR[2] with Webmachine to represent my resources[3]. I really like how Seaside lets you programmatically construct HTML, but Iâm not sure if I can just pull in the HTML generation and leave out the rest. Is this possible or do I have to recreate ROAR in Smalltalk (which isnât a bad idea!)? Thanks! /ls [1] http://smalltalkhub.com/#!/~statonjr/DLWebmachine [2] https://github.com/apotonick/roar [3] https://speakerdeck.com/statonjr/hypermedia-apis-with-webmachine-and-roar Larry Staton Jr. https://keybase.io/statonjr

6 5

Re: [Pharo-users] Form editor
by Stephan Eggermont June 4, 2014

June 4, 2014

Hi Phil, I mostly just use Gimp, but that is not a very efficient and effective solution. Most icons, especially those in flat styles, should be rendered/generated from a vector format instead of from a bitmap. They should be programmed, to be themable. Fontographer is actually a much better tool for the kind of icons found in bootstrap like styles Stephan

2 1

Form editor
by phil＠highoctane.be June 4, 2014

June 4, 2014

Hello, Is there any Form editor (bitmap form) that one could use in Pharo? Example of use would be to edit forms that are making up the icons. e.g. UIThemeWatery>>checkboxSelectedForm Exporting icons and importing them back is quite time consuming. How are you guys dealing with that? TIA Phil

1 0

Curl markup with Pillar
by Robert Shiplett June 3, 2014

June 3, 2014

re: Curl markup, as in web markup using declarative style in Curl PL from MIT, not cURL ( see www.curlap.com) My Japanese web pages are now generated using nunjucks + node.js but in the hope of using pharo 3 + Seaside on small virtual server, I thought I would see what it takes to add Curl markup to the Pilar repertoire. But the Pharo 3 RC image is giving a walkback over the configuration for Pillar, so I may not get to this this morning. mrkup, mrkdwn PS did any one see the role of an MIT OCaml / emacs guy in the Android visual app gen project from MIT ? PPS Curl Android/iOS app gen project is called "caede" as in "maple" (KAEDE)

4 7

Configuration browser and Fuel
by phil＠highoctane.be June 3, 2014

June 3, 2014

In Pharo 3.0 we do have Fuel in the image. Now, there is also Fuel in the ConfigurationBrowser. When one wants to work with Fuel, should one update the image with what is in the ConfigurationBrowser? TIA Phil

2 1

NeoJSON mapping of nil properties
by Esteban A. Maringolo June 2, 2014

June 2, 2014

Hi all... and Sven ;-) I'm mapping my objects with NeoJSONWriter, and I found it is not writing the properties whose values are null. NeoJSONPropertyMapping>>#writeObject: anObject on: jsonMapWriter | value | value := getter value: anObject. value ifNotNil: [ jsonMapWriter writeKey: propertyName value: value as: valueSchema ] It is a good default (saves space, and cpu cycles). But in my case the consumer of the JSON objects expect the objects to have all the attributes previously defined. Is there a way I can configure the mapper or the mapping to write null when the value is nil? Thank you! Esteban A. Maringolo

3 5