Issue 799 in moose-technology: Editing code in Glamour must be faster
by moose-technology@googlecode.com
Status: New
Owner: ----
CC: esteba...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7
New issue 799 by tudor.gi...(a)gmail.com: Editing code in Glamour must be
faster
http://code.google.com/p/moose-technology/issues/detail?id=799
Launch the following browser, and then try to type more code. It is dead
slow. Using the same fragment in the workspace is fast. This means that we
are probably using the PluggableTextMorph in a wrong way. The problem
appeared since Pharo 1.4.
GLMWrapper new
show: [:a | a text ];
openOn: 'GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.
GLMWatcherWindow uniqueInstance toggleOpen.'
11 years
Triggering events in Roassal
by Fabrizio Perin
Hi,
is there in roassal any event that triggers right after the layout is
applied?
What I'm trying to do is to center on an element after the layout is
applied (so after the element have a position in the visualization).
Thanks,
Fabrizio
11 years
MooseFinder and glamour
by Fabrizio Perin
Hi,
I was loading some old code and some of browsers I wrote do not open
correctly anymore. Apparently I cannot do something like this anymore:
browser transmit
to: #finder;
from: #functions port: #selection;
andShow: [ :a | a custom: (MooseFinder startOn: a) ].
This because MooseFinder do not understand anymore startOn:.
Any suggestions on how can I make this glamour example working again?
mooseFinderOnSelectedElement
"self new mooseFinderOnSelectedElement openOn: (1 to: 100)"
<glmBrowser: 'Open MooseFinder On Selected Element' input: '(1 to: 100)'>
| browser |
browser := GLMTabulator new.
browser
column: #functions;
column: #finder.
browser transmit
to: #functions;
andShow: [ :a |
a list
title: 'Functions';
display: [ :each | each ] ].
browser transmit
to: #finder;
from: #functions port: #selection;
andShow: [ :a | a custom: (MooseFinder startOn: a) ].
^browser
Thanks,
Fabrizio
11 years
Re: Roassal ROMondrianExamples on VW issue
by Stephan Eggermont
Hi Vanessa,
>I fix the little bug with the numberOfLinearOfCode, however, I do not
>understand the issue with the String crlf as I can see the popupText ok.
>Where this happens?
Great, it now works for me. I've probably loaded something in the wrong order.
Thanks for the fast response,
Stephan
11 years
Roassal ROMondrianExamples on VW issue
by Stephan Eggermont
Hi,
In a 7.8.1 image, the Roassal SystemComplexity example shows a few MNUs.
The popupText expects String crlf instead of String cr, and numberOfLinesOfCode
is not recognized, even though it is added to ClassDescription in *roassal-core
Cheers,
Stephan
11 years
strengthening moose hi-graphs
by Tudor Girba
Hi,
Right now, we have several pieces of code that involve hi-graphs:
- DSM
- Softwarenaut
- Carrack
On the other hand, we have the graph support from Moose-Algos.
It would be cool to look into the variation and consolidate them. Perhaps
this can also be a topic for the Moose Dojo.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
11 years
Call for Participation in the Smalltalk Devroom at FOSDEM 2013
by Stephan Eggermont
Call for Participation in the Smalltalk Devroom at FOSDEM 2013.
http://www.fosdem.org
" A devroom for the Pharo, Squeak, Amber, GST, Etoilé, Seaside,
Moose Smalltalk projects & Newspeak as derived language.
Smalltalk environments offer a very high development productivity,
unmatched by their successors. Come do some pair programming
with us and experience yourself the advantages of a real OO
environment"
The meetup will take place Sunday, February 3, 2013,
from 9AM until 5PM, building AW. This room has 72 seats,
a VGA video projector and wireless internet.
More information will be available later.
Proposals on content and format are welcome.
People interested in running a session should announce that
on the smalltalk-devroom mailing list, with the following
information:
- Their name
- The project they are associated with
- A short bio, to be put on the website along with their speaker name
- (optionally) a picture of themselves
- The title of their session (which will go on the website and in the booklet)
- A abstract describing the session in further detail.
- The desired length of the session.
- The desired time slot in which they want to hold the session.
Suggested values for the duration are 55min, 25min, 6m40 (Pecha Kucha).
The desired time slot is meant to help you prevent conflicts with other dev
rooms in which you might have a talk or your travel arrangements.
There are alternative, non smalltalk-specific tracks available:
lightning talk and the main track
The deadline for submissions is December 31, 23:00 GMT+1.
Discussion takes place on the
smalltalk-devroom(a)lists.fosdem.org
mailing list. Please subscribe if you are interested:
https://lists.fosdem.org/listinfo/smalltalk-devroom
The local VUB/ULB Smalltalkers have been asked to organize
a sprint/BSUG meeting/Camp Smalltalk on Saturday February 2.
Devroom related URLs:
http://www.pharo-project.org
http://www.squeak.org/
http://etoileos.com/
http://www.seaside.st/
http://smalltalk.gnu.org/
http://www.moosetechnology.org
http://amber-lang.net
http://newspeaklanguage.org/
http://www.esug.org
11 years, 1 month