Issue 799 in moose-technology: Editing code in Glamour must be faster

List overview All Threads
Download

newer

older

Issue 866 in moose-technology:...

#moosedojo on Twitter

moose-technology＠googlecode.com

27 May 2012 27 May '12

8:59 a.m.

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.'

Show replies by date

moose-technology＠googlecode.com

3 Jun 3 Jun

12:34 p.m.

New subject: Issue 799 in moose-technology: Editing code in Glamour must be faster

Updates: Status: Accepted Comment #1 on issue 799 by esteba...(a)gmail.com: Editing code in Glamour must be faster http://code.google.com/p/moose-technology/issues/detail?id=799 (No comment was entered for this change.)

moose-technology＠googlecode.com

4:05 p.m.

New subject: Issue 799 in moose-technology: Editing code in Glamour must be faster

Comment #2 on 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 Accepted! That is a step forward :)

moose-technology＠googlecode.com

24 Jul 24 Jul

5:12 p.m.

New subject: Issue 799 in moose-technology: Editing code in Glamour must be faster

Comment #3 on 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 Esteban: any news on this front?

moose-technology＠googlecode.com

5 Sep 5 Sep

3:38 p.m.

New subject: Issue 799 in moose-technology: Editing code in Glamour must be faster

Updates: Labels: -Priority-Medium Priority-High Comment #4 on issue 799 by tu...(a)tudorgirba.com: Editing code in Glamour must be faster http://code.google.com/p/moose-technology/issues/detail?id=799 This is an important bug, and I need help to fix it. Does anyone have time to look into it?

moose-technology＠googlecode.com

4:22 p.m.

New subject: Issue 799 in moose-technology: Editing code in Glamour must be faster

Comment #5 on issue 799 by esteba...(a)gmail.com: Editing code in Glamour must be faster http://code.google.com/p/moose-technology/issues/detail?id=799 yeah, sorry... I've been busy like hell :(

moose-technology＠googlecode.com

16 Oct 16 Oct

8:15 a.m.

New subject: Issue 799 in moose-technology: Editing code in Glamour must be faster

Comment #6 on issue 799 by tu...(a)tudorgirba.com: Editing code in Glamour must be faster http://code.google.com/p/moose-technology/issues/detail?id=799 The simple text editor seems to be ok now. The problem is in the SmalltalkCode GLMWrapper new show: [:a | a smalltalkCode ]; 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. 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. '

moose-technology＠googlecode.com

15 Nov 15 Nov

9:48 a.m.

New subject: Issue 799 in moose-technology: Editing code in Glamour must be faster

Comment #7 on issue 799 by step...(a)stack.nl: Editing code in Glamour must be faster http://code.google.com/p/moose-technology/issues/detail?id=799 Observations - only code, not text. Text stays fast. - only editing at the end. At the beginning stays fast. - source code examples in GLMBasicExamples are mostly short enough, so the speed drop off seems to be very sudden - speed loss doesn't seem to be exponential or high O, adding much more text just makes it a bit slower - adding dots at the end of the text stays fast - changing GLMSmalltalkCodelModel isCodeCompletionAllowed from true to false eliminates the lag, but making the text twice as long again reintroduces it - difference between workspace and browser is: workspace remains responsive, shows directly the text you're typing, highlighting then happens a second later

moose-technology＠googlecode.com

16 Nov 16 Nov

10:27 a.m.

New subject: Issue 799 in moose-technology: Editing code in Glamour must be faster

Updates: Status: Fixed Comment #8 on issue 799 by chisvasi...(a)gmail.com: Editing code in Glamour must be faster http://code.google.com/p/moose-technology/issues/detail?id=799 The problem was that PluggableTextMorph was created with autoAccept: true. This means that GLMMorphicModel>>accept:notifying: is called on each key stroke which completely replaces the text, recompiles it and redoes the highlighting twice.

moose-technology＠googlecode.com

11:13 a.m.

New subject: Issue 799 in moose-technology: Editing code in Glamour must be faster

Updates: Cc: tudor.gi...(a)gmail.com Comment #9 on issue 799 by esteba...(a)gmail.com: Editing code in Glamour must be faster http://code.google.com/p/moose-technology/issues/detail?id=799 wow... it was a stupid error (the harder errors to get... )... and I spent like 3 days (during 3 months, he, trying to understand the style process and why that was happening :)

moose-technology＠googlecode.com

11:23 a.m.

New subject: Issue 799 in moose-technology: Editing code in Glamour must be faster

Comment #10 on issue 799 by tu...(a)tudorgirba.com: Editing code in Glamour must be faster http://code.google.com/p/moose-technology/issues/detail?id=799 Well, the reason why we had this code in there was so that we can get a hook for getting announced when the text changes inside the morph. We need this information so that we can set the text port in the presentation. So, we fixed the syntax highlighting, but now the text setting is broken.

4180

days inactive

4353

days old

moose-dev@list.inf.unibe.ch

Manage subscription

10 comments

1 participants

tags (0)

participants (1)

moose-technology＠googlecode.com