Moose-dev May 2011

moose-dev@list.inf.unibe.ch

33 participants
186 discussions

Re: [Pharo-project] Re: Highlight problem with glamour

by Marcus Denker

On May 12, 2011, at 4:51 PM, Tudor Girba wrote: > Hi, > > On 12 May 2011, at 16:44, Marcus Denker wrote: > >> >> On May 12, 2011, at 4:42 PM, Tudor Girba wrote: >>> >>> I did not mean that someone should look into the posted code. I was in a hurry and I simply asked a direct question if anyone has any idea of why 4096 would be a limit for highlighting text in TextMorph. The question had nothing to do with Glamour, but I am sorry if the form of the mail made you waste your time. >>> >>> In any case, I will look into this in more details. >>> >> >> >> maybe this is relevant? We should release 1.2.2.... >> >> http://code.google.com/p/pharo/issues/detail?id=4157 > > Hmm. Sounds similar, but I am too ignorant. > > I could reproduce the problem outside of Glamour. The issue is indeed not with TextMorph, but with PluggableTextMorph: > > string := ''. > 1 to: 1000 do: [:i | string := string, 'abcde']. > text := ((string asText addAttribute: TextColor red), ('xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' asText)). > (PluggableTextMorph on: text text: #yourself accept: #value) openInWindow > works fine in 1.2.2a -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

13 years, 11 months

Re: [Pharo-project] Re: Highlight problem with glamour

by Marcus Denker

On May 12, 2011, at 4:10 PM, Tudor Girba wrote: > Thanks, Fabrizio. > > I noticed a similar problem with highlighting Java code, but I thought it was related to the grammar. > > I CC-ed the Pharo mailing list. > > Anyone knows why it would be a problem to highlight text with more than 4096 characters in a TextMorph? > Which version of Pharo are you using? > Cheers, > Doru > > > On 12 May 2011, at 16:03, Fabrizio Perin wrote: > >> It basically breaks after 4096 characters. >> >> >> On 12 May 2011, at 16:02, Fabrizio Perin wrote: >> >>> Hi, >>> i was playing with textlint and i noticed that the highlight is broken. Seems that the problem is related to the length of the text. If you try to execute the script below you notice that the highlight doesn't work. If you lower 1000 to 100 it works. It seems that the break point is 194. After that it dies. >>> >>> | browser | >>> browser := GLMTabulator new. >>> browser >>> column: #details. >>> >>> "if you need initial display" >>> browser transmit to: #details; andShow: [:a | >>> a text display: [:x | >>> | string | >>> string := ''.1 to: 1000 do: [:i | string := string, 'jjjjj j j j j j jjj j']. >>> (string asText addAttribute: TextColor red), ('jjjjj j j j j j jjj j' asText) ] ]. >>> >>> browser openOn: 5 >>> >>> Any idea? >>> >>> Cheers, >>> >>> Fabrizio >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "The coherence of a trip is given by the clearness of the goal." > > > > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

13 years, 11 months

Highlight problem with glamour

by Fabrizio Perin

Hi, i was playing with textlint and i noticed that the highlight is broken. Seems that the problem is related to the length of the text. If you try to execute the script below you notice that the highlight doesn't work. If you lower 1000 to 100 it works. It seems that the break point is 194. After that it dies. | browser | browser := GLMTabulator new. browser column: #details. "if you need initial display" browser transmit to: #details; andShow: [:a | a text display: [:x | | string | string := ''.1 to: 1000 do: [:i | string := string, 'jjjjj j j j j j jjj j']. (string asText addAttribute: TextColor red), ('jjjjj j j j j j jjj j' asText) ] ]. browser openOn: 5 Any idea? Cheers, Fabrizio

13 years, 11 months

Issue 608 in moose-technology: VerveineJ exports some anchors with endLine = -1

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-VerveineJ Milestone-4.4 New issue 608 by tudor.gi...(a)gmail.com: VerveineJ exports some anchors with endLine = -1 http://code.google.com/p/moose-technology/issues/detail?id=608 Parsing Silverpeas retrieves 515 model classes (out of 1858) with a FileAnchor that has a positive startLine, but an endLine that is -1. These classes can be checked by: - parse and load the MSE into Moose - select all model classes and then select based on: each sourceAnchor notNil and: [each sourceAnchor startLine > 0 and: [each sourceAnchor endLine = -1]] Even more interesting is that if you look in the methods of these classes, they have a correct endLine.

13 years, 11 months

DistributionMap and SmallLint rules

by Andre Hora

Hello, I just created some visualizations (Marcus's idea) using DistributionMap with SmallLint rules to check how distributed are the lint problems in a class. I enclosed some figures with the distribution for some packages of Moose. So, the small boxes represent methods. The red color is a method with more than 3 lint problems, the orange 2 problems, green 1 problem and white no problem. We can clearly see a lot of "lint problems" in Famix package. Of course, we have some false-positives mainly for Glamour and Mondrian as we can check in [1]. Btw, I also created a job in Hudson to generate a simple report with smallLint rules in Moose (and Pharo): Job: https://pharo-ic.lille.inria.fr/hudson/view/LintReport/job/LintReportMoose Report: https://pharo-ic.lille.inria.fr/hudson/view/LintReport/job/LintReportMoose/… regards, [1] Lukas Renggli, Stéphane Ducasse, Tudor Gîrba and Oscar Nierstrasz, “ Domain-Specific Program Checking,” Proceedings of the 48th International Conference on Objects, Models, Components and Patterns (TOOLS’10) -- Andre Hora

13 years, 11 months

Issue 628 in moose-technology: [Glamour] Useless mouseUp event in test

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium New issue 628 by damien.c...(a)gmail.com: [Glamour] Useless mouseUp event in test http://code.google.com/p/moose-technology/issues/detail?id=628 GLMTreeMorphicTest>>testChildrenBlock has a line which looks like: self send: self tree mouseUpOnItem: self treeRoots first. The test passes whether the line is present or not.

13 years, 11 months

Issue 627 in moose-technology: Glamour-Morphic unit tests are fragile to changes in the submorphs tree

by moose-technology＠googlecode.com

Status: New Owner: damien.c...(a)gmail.com CC: tudor.gi...(a)gmail.com Labels: Type-Engineering Priority-Low New issue 627 by damien.c...(a)gmail.com: Glamour-Morphic unit tests are fragile to changes in the submorphs tree http://code.google.com/p/moose-technology/issues/detail?id=627 Glamour-Morphic unit tests contain code like this: treeMorph := window submorphs last submorphs first submorphs first submorphs first submorphs first. self assert: treeMorph class = LazyMorphTreeMorph. Which is very fragile to any changes in the submorphs tree. I propose to replace each of these piece of code to something like: treeMorph := self find: LazyMorphTreeMorph in: window The method #find:in: could use something like Morph>>allMorphsDo: to find a corresponding morph in the submorphs tree. I guess this would made the code slower but haven't tested it.

13 years, 11 months

Namespace and Packages

by Usman Bhatti

I am creating a C# extractor for Moose. I am using Fame for java to access Famix objects and populate their information (similar to VerveineJ). While creating Famix.Class objects for C# classes, I need to set parent namespace to represent the namespace that the class belongs to. However, the Famix.Class only provides a single method to set the parent and that take a Famix.Package as a parameter. So, the following expression is an error for a Famix.Class object. class.setParentPackage(Namespace) Since, C# uses namespaces instead of Packages to organize classes, it would be good to set a Famix.Namespace to be the parent of a class. Does meta-model not provide a way that we can set Famix.Namespace as a parent of a class. I can see another method in the Famix.Class and that is SetContainer(ContainerEntity se). Can I use this method to set a Namespace to be the parent of a Class and keeping the parentPackage relationship empty? thanks. Usman

13 years, 11 months

Petit SQL Parser

by Fabrizio Perin

Hi all, i did implement an SQL parser using Petit Parser. I toke the grammar specification from SQLite http://www.sqlite.org/lang.html . The grammar implemented is not complete, for now i did implement "just" the create table statement, it means that you should be able to parse at least a script for create the database. The code is in squeaksource http://www.squeaksource.com/@09zbthA-fDDfyUNQ/_OIex3aA . To download it you can evaluate this: Gofer new squeaksource: 'PetitSQLParser'; package: 'ConfigurationOfPetitSQLParser'; load. (Smalltalk at: #ConfigurationOfPetitSQLParser) perform: #loadDefault in the repository there are several packages: the core contains the parser for the grammar. In the package parser there is a parser that instantiate some draft objects representing relational elements. In the next future i will start to implement also other statements. If you start to use it and you have some problem please let me know. Cheers, Fabrizio

13 years, 11 months

About V4.4 and versioning

by Johan Fabry

Hi all, I saw the tweet 'Preparing Moose suite 4.4'. Excellent news, I look forward to make a new version of AspectMaps to run on 4.4 :-) I have one request though: as I dont have that much time to spend on AspectMaps, I cannot keep it 100% up to date with the fast pace that Moose is evolving. So for me, reproducibility of a given version is key. So I downloaded the 4.3 moose suite (one-click) release. This is for me the version in which AspectMaps loads, since it is an official *release*. But this version *can* *not* be loaded using ConfigurationOfMoose. Hence AspectMaps cannot be loaded completely from source staring with a Pharo 1.2 image, which is a shame, really. (Of the different 4.3.x configurations a number of them break when loading, BTW.) So my request: it would be cool if for 4.4 there is a version in ConfigurationOfMoose that produces an image identical to what is first released as the 4.4 one-click. For an official release I think this is a reasonable request and an effort worthwhile to consider. If later on, for 'intermediate versions' such configurations are made, this would be a nice extra but I understand that we all have limited time ;-) -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

13 years, 11 months

← Newer
1
...
11
12
13
14
15
16
17
18
19
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev May 2011