Status: New
Owner: ----
CC: alexandr...(a)gmail.com
Labels: Type-Defect Priority-Critical Component-Roassal Milestone-4.9
New issue 987 by tu...(a)tudorgirba.com: Roassal does not display edges when
the source is not visible
http://code.google.com/p/moose-technology/issues/detail?id=987
Try this:
view nodes: { 1 . 2 }.
view edgeFromAssociation: 2->1.
view horizontalLineLayout horizontalGap: 1000.
I think it is easy to fix, but at the same time it is really annoying, so I
mark it as critical :)
--
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
Hi,
Andrei did a wonderful job and added both line selection and dynamic
variables to the Playground and Inspector.
So, now, the Playground replaces the default Workspace in the Moose image.
Enjoy,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Status: New
Owner: chisvasi...(a)gmail.com
Labels: Type-Enhancement Priority-Medium Component-Glamour
Component-GlamorousToolkit
New issue 1050 by tu...(a)tudorgirba.com: Playground should create dynamic
variables
http://code.google.com/p/moose-technology/issues/detail?id=1050
evaluating
a := 41.
a + 1
should work as in the default workspace
--
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
Updates:
Summary: GTInspector should select the current line when Cmd+o is pressed
Comment #1 on issue 1041 by tu...(a)tudorgirba.com: GTInspector should select
the current line when Cmd+o is pressed
http://code.google.com/p/moose-technology/issues/detail?id=1041
(No comment was entered for this change.)
--
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
Hi!
I am playing with unicode characters:
-=-=-=-=-=-=-=-=-=-=-=-=
Gofer new
url: 'http://smalltalkhub.com/mc/abergel/Sparkline/main';
addPackage: 'Sparkline';
load.
-=-=-=-=-=-=-=-=-=-=-=-=
#( 1 2 3 4) spark => '▁▃▅▇’
#(-5 10 0) spark => '▁█▃'
RxsNode withAllSubclasses spark: #numberOfMethods => '▂▃▂▃▁▁▅█▁▁▂▁’
I got the inspiration from https://github.com/holman/spark
By the way, I would love to have a short tutorial about unicode characters at esug.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
[Apologies for multiple copies]
>
> [CFP] Dyla'14, Workshop on Dynamic Languages and Applications, at
> PLDI, Edinburgh
>
> - What: 8th Workshop on Dynamic Languages and Applications.
> - Where: Co-located with PLDI'14, Edinburgh, UK
> - When: June 12th,
>
> Sponsored by ACM SIGPLAN
>
> Submission deadline: March 15th
>
> More info on the website: http://www.lifl.fr/dyla14/
>
> Dyla is a place where developers and researchers can discuss new
> advances in the design, implementation and application of
> dynamically-typed languages.
>
> The expected audience of this workshop includes practitioners and
> researchers sharing the same interest in dynamically-typed languages.
> Lua, Python, Ruby, JavaScript and others are gaining a significant
> popularity both in industry and academia. Nevertheless, each community
> has the tendency to only look at what it produces. Broadening the
> scope of each community is the goal of the workshop. To achieve this
> goal Dyla's program and organization committees are composed of
> leading persons from many such languages.
>
> Topics
> --
>
> - live programming
> - programming language extensions
> - programming environment extensions
> - domain-specific languages & tooling
> - executing environments
> - static & dynamic analyses
> - meta-object protocols
> - optional type-checking
> - reverse engineering
> - testing environments
>
> Organizing committee:
> --
>
> - Damien Cassou, University of Lille 1, FR
> - Carl Friedrich Bolz, King's College London, GB
> - Johan Andersson, Burtcorp in Gothenburg, SE
> - Roberto Ierusalimschy, Catholic Univ. in Rio de Janeiro, BR
> - Tom Van Cutsem, Vrije Universiteit Brussel, BE
>
> Program committee:
> --
>
> - Anne Etien, University Lille 1, France
> - David Schneider, Heinrich-Heine-Universität Düsseldorf, DE
> - Didier Verna, EPITA/LRDE, France
> - Edd Barrett, Department of Informatics, King's College London, GB
> - Joe Gibbs Politz, Brown University, USA
> - Peng Wu, IBM T.J. Watson Research Center, USA
> - Tim Felgentreff, Hasso-Plattner-Institut, DE
> - T. Stephen Strickland, University of Maryland, US
> - Yoshiki Ohshima, Viewpoints Research Institute, USA
> - Zachary P. Beane, Portland, USA
> - the 5 workshop organizers
>
> Abstract:
> --
>
> Java and C# have been a major influence in the adoption of
> object-oriented language characteristics: academic features like
> interfaces, garbage collection, and meta-programming became
> technologies generally accepted by the industry. However, with the
> adoption of these languages, their limitations became apparent, as
> testified by industry reactions: invokedynamic has been
> included in the latest Java virtual machine release; the dynamic
> language runtime (DLR) is gaining popularity; C# adopted
> dynamic as a valid static type.
>
> Researchers and practitioners struggle with static type systems,
> overly complex abstract grammars, simplistic concurrency mechanisms,
> limited reflection capabilities, and the absence of higher-order
> language constructs such as delegation, closures, and continuations.
> Dynamic languages such as Ruby, Python, JavaScript and Lua are a step
> forward in addressing these problems and are getting more and more
> popular. To make these languages mainstream, practitioners have to
> look back and pick mechanisms up in existing dynamic languages such as
> Lisp, Scheme, Smalltalk and Self.
>
> The goal of this workshop is to act as a forum where practitioners can
> discuss new advances in the design, implementation and application of
> dynamically-typed languages that, sometimes radically, diverge from
> the statically typed class-based mainstream. Another objective is to
> discuss new as well as older "forgotten" languages and features in
> this context.
>
>
> Format and Submission Information
> --
>
> The workshop will have a demo-oriented style. The idea is to allow
> participants to demonstrate new and interesting features and discuss
> what they feel is relevant for the dynamic-language community. To
> participate in the workshop, you can either
>
> - submit (before March 15th 2014) an article (ACM Tighter Alternate
> style) describing your presentation and/or tool. Your article, which
> must include from 2 to 15 pages, will be carefully reviewed by the
> program committee. If accepted, your article will be presented
> during the workshop and be published to the ACM Digital Library (at
> your option) and the workshop's web site. Please submit to
> http://www.easychair.org/conferences/?conf=dyla14.
>
> - or give a 10-minute lightning demo of your work. A dedicated session
> will be allocated for this, provided there is ample time available.
> In this case, send us the title of your demo.
>
> A session on pair programming is also planned. People will then get a
> chance to share their technologies by interacting with other
> participants.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1049 by alexandr...(a)gmail.com: topleft pane is oddly filled
http://code.google.com/p/moose-technology/issues/detail?id=1049
Describe the problem: what do you get? what do you expect?
How to reproduce the problem: step by step if necessary
- open a meta browser from the WorldMenu/Moose
- select a box in the roassal visualization, and the top left pane is not
properly filled. It seems like many items are at the same position
Additional information: platform, context which may impact the problem
- the last successful artifact, loaded today.
Please fill in the labels with the following information:
* Type-Defect, Type-Enhancement, Type-Engineering, Type-Review, Type-Other
* Component-XXX
--
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
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-EyeSee Milestone-5.0
New issue 1024 by tu...(a)tudorgirba.com: EyeSee Editor crashes by default
http://code.google.com/p/moose-technology/issues/detail?id=1024
Just open an EyeSee Editor and press Cmd+s. The diagram is not initialized.
--
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