Moose-dev April 2015

moose-dev@list.inf.unibe.ch

41 participants
85 discussions

Loading PetitParser breaks Pharo4 latest build

by Johan Fabry

Hi all, I don’t know if this is a know issue so I am reporting it: doing a ConfigurationOfPetitParser loadDevelopment in the latest Pharo 4 (40571) breaks some things. There is a DNU on opening the playground: AnObsoleteGLMLiveStringBrick(Object)>>doesNotUnderstand: #textLogic: It’s called from GTPlayground>>codeIn: where a ref to GLMLiveStringBrick is made. ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

9 years, 8 months

Showcase of initial support for word clouds and data scrapping (and the usual newbie questions)

by Offray Vladimir Luna Cárdenas

Hi all, On [1] you can see a small video showing the support for word clouds and data scrapping from Twitter for some public profiles (including mine). As you can see the visualization is embedded on grafoscopio trees/documents that provide context for the scripts and combine them with other documentation. You can create your own visualization by running the code at [2] and changing the profile name. [1] https://archive.org/details/gfcp-wordclouds-initial.mp4 [2] http://ws.stfx.eu/DVG4C8VFON1L So here are my usual questions: a) The code that puts an image in a name cloud accepts only png images and when the avatar has jpeg images I got an error. There is any way to make the RTNameCloud to work with jpg or to convert it to png. I was looking at Sven's documentation[3], but I can't make it work in my context (jpeg is taken from the web and converted to png without using the file system). [3] https://medium.com/concerning-pharo/elegant-pharo-code-bb590f0856d0 b) There is any way to go beyond 19 tweets. In recent conversations with Paul[4] he taught me how to extract tweets properly from a page using ZnClient, but it gets the last 19. There is any way to make ZnClient to go beyond that initial request and get, lets say 100 or more tweets? [4] http://forum.world.st/Data-scrapping-in-pharo-Extracting-tweets-contents-td… Thanks as always for keeping Pharo/Moose and their communities awesome! Cheers, Offray

9 years, 8 months

documentation on moose chef?

by Alexandre Bergel

Hi! Where can I find such a documentation? themoosebook is particular shy on chef :-( Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 8 months

Configuration of PetitParser

by Jan Kurš

Hi all, I updated the baseline in ConfigurationOfPetitParser and added some information about loading PetitParser on SmalltalkHub ( http://smalltalkhub.com/#!/~Moose/PetitParser/) I hope this covers all your needs. There is possibility to load only minimal core, as well as all the petit parser stuff without gui and with gui. Cheers, Jan How to Load Petit Parser -------------------------------- First, load configuration: Gofer new smalltalkhubUser: 'Moose' project: 'PetitParser'; configurationOf: #PetitParser; load. #### Load Everything ConfigurationOfPetitParser loadDevelopment. #### Load Everything Without GUI In case you don't want to load the GT: ConfigurationOfPetitParser loadPetitParser. #### Load GUI In case you want to use PetitParserBrowser and other support in GT: ConfigurationOfPetitParser loadPetitParserIDE. #### Load Core (ConfigurationOfPetitParser project version: #development) load: 'Core'.

9 years, 8 months

agilevisualization layout chapter

by Peter Uhnák

Hi, Is anybody working on layout chapter? This (summer) semester I'll be writing my bachelor thesis on model layouting and I am using Roassal, so since I need to get familiar with Roassal layouting abilities I could as well write something about it. :) Peter

9 years, 8 months

Roassal RTSetEdgeAlpha not applied on line heads

by Peter Uhnák

Hi, RTSetEdgeAlpha doesn't work properly when applied on ArrowedLine. The line itself is correctly changed, but the arrow head remains in original color. ~~~~~~~~~~~~~~~~~~~~~~~~~~ |v es| v := RTView new. es := RTEllipse new color: Color blue; elementsOn: #(1 2). v addAll: es. v add: (RTArrowedLine new color: Color purple; edgeFrom: es first to: es second). RTHorizontalLineLayout new gapSize: 30; on: es. es @ RTSetEdgeAlpha. ^ v ~~~~~~~~~~~~~~~~~~~~~~~~~~ p.s.: should I be posting bugreports in some Moose/Roassal bugtracker, or mailing list is fine? Thanks, Peter

9 years, 8 months

Changes in 5.1 for embeded playgrounds

by Offray Vladimir Luna Cárdenas

Hi, Because Pharo 4 is getting closer and I can see already improvements on shortcuts (Ctrl and Alt are switched finally and we have consistent behaviour between apps in Linux), I'm moving to moose 5.1 as my base platform for the development of grafoscopio. So far, so good, but I would like some of the behaviours on 5.0 back on 5.1, like the way to embed playgrounds with named nodes. So here is the screenshot of grafoscopio with a code type node open inside an interactive document running on Moose 5.0: http://mutabit.com/deltas/repos.fossil/offray-uvikuo/doc/tip/static/blog/ou… And here is the same interactive document open on Moose 5.1: http://mutabit.com/deltas/repos.fossil/offray-uvikuo/doc/tip/static/blog/ou… As you can see, in the first screenshot, the playground takes the same name of the node that is storing its contents, while the second one has just "Untitled" as title. My code for embedding playgrounds is ======================================== GrafoscopioBrowser>>bodyForCodeIn: constructor for: aNode "Shows the body of a node as an interactive playground. If node is not tagged it will return itself, so it can be rendered properly for other messages" | innerBrowser | aNode tags = 'código' ifFalse: [^self]. innerBrowser := GTPlayground new. constructor custom: innerBrowser. ======================================== How the code needs to be changed so I can get named playgrounds as was happening with 5.0. Cheers and keep the good work. Offray

9 years, 8 months

Issue 1103 in moose-technology: The list resulting of the Inspection of a MooseGroup should be in alphanumerical order

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1103 by v.blonde...(a)gmail.com: The list resulting of the Inspection of a MooseGroup should be in alphanumerical order https://code.google.com/p/moose-technology/issues/detail?id=1103 Describe the problem: what do you get? what do you expect? When you inspect with the moose panel (or an inspector) a model, the list of the group items are randomly sorted. I expect to have a alphanumerical sort on this list to quickly get an element of the list. How to reproduce the problem: step by step if necessary Do: LANPackageTestResource current model allClasses inspect. And go to the third tab (containing the list) Additional information: platform, context which may impact the problem Moose 5.0 Please fill in the labels with the following information: * Type-Enhancement * Component-GT -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

9 years, 8 months

Issue 1105 in moose-technology: Moose Importing Abstract Classes - Packages Reorganisation

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1105 by v.blonde...(a)gmail.com: Moose Importing Abstract Classes - Packages Reorganisation https://code.google.com/p/moose-technology/issues/detail?id=1105 The organisation of the Moose importers is a bit messy. The classe MooseAbstractImporter should be used by MooseImportingTask and be a subclass of MooseTask. MooseImportingTask is only used for smalltalk so it should be in Moose-SmalltalkImporter. And MooseOperator is not only for Smalltalk so it should be in the Moose-Core package. This following my mail from last year: http://www.iam.unibe.ch/pipermail/moose-dev/2014-April/019420.html and the discussion from 2011 from Usman and Stef: http://forum.world.st/Proposal-to-enhance-the-MooseTask-inheritance-and-Moo… Please fill in the labels with the following information: * Type-Engineering * Component-Moose -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

9 years, 8 months

Issue 1116 in moose-technology: fix bad dependencies in moose-core

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1116 by christop...(a)inria.fr: fix bad dependencies in moose-core https://code.google.com/p/moose-technology/issues/detail?id=1116 Moose-Core has dependencies to Moose-Algos-Graph and Moose-SmalltalkImporter that should not be there. action: move MooseIcons>>importIcon and MooseGroup>>cyclesToAll as extension methods of Moose-SmalltalkImporter and Moose-Algos-Graph. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

9 years, 8 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev April 2015