Hello,
I’ve just posted some pictures of the execution of Roassal and Glamour.
More pictures on:
https://www.facebook.com/ObjectProfile/posts/753449881408278
Roassal:
Glamour:
Merry Christmas!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Giorgio,
Thanks for the kind words.
Cheers,
Doru
On Wed, Dec 24, 2014 at 1:20 AM, giorgio ferraris <
giorgio.ferraris(a)gmail.com> wrote:
> Hi, Guys,
>
> I'm not (yet) working on Pharo (still VW and some VisualSmalltalk in the
> few time left free from my main job), but I follow what you do (not just
> you but all the community) and I have to admit you (all) work really hard.
> Bergel is doing a fantastic job, and your Moose is very nice, etc.
> But, I really liked the presentation of the GT stuff, I can understand the
> energy you put behind your work.
>
> Great work. I'm happy you are on the ST community and working on the
> language (ST) i like the most. Thanks!
> (Oh, I know you don't like to have Pharo called Smalltalk, but I don't
> like religion's wars, so that is yet smalltalk, for me).
>
> BTW: Happy Holidays to all.
>
> Giorgio
>
> On Wed, Dec 24, 2014 at 12:09 AM, Tudor Girba <tudor(a)tudorgirba.com>
> wrote:
>
>> We are happy to announce Moose 5.0:
>> *http://moosetechnology.org/#install*
>>
>>
>> Description
>> ---
>>
>> This is by far the most extensive Moose release to date. Just take a look
>> at these two trailers.
>> - Spotter: https://vimeo.com/113832673
>> - Inspector: https://vimeo.com/103463364
>>
>> The key highlights are:
>> - It is based on Pharo 3.0.
>> - Roassal2 is a complete reimplementation of the core visual engine of
>> Moose.
>> - Roassal2 replaced Roassal, EyeSee and Graph-ET, and it features many
>> new things including smooth animations, new composeable builders and
>> several new layouts.
>> - All built-in Moose visualizations use Roassal2.
>> - Glamour has been extended with a Pager browser and with Rubric as the
>> main text editor.
>> - GTSpotter is a new tool that makes it possible to find objects fast.
>> - GTInspector saw major usability improvements based on the Pager
>> browser, and it now comes with many object specific extensions.
>> - GTPlayground provides a new way to handle scripts and when combined
>> with GTInspector, it can replace the dedicated easels and editors.
>> - Moose Finder has been extended with the ability of handling in place
>> visualizations.
>> - GTDebugger has been strengthen and was made more robust.
>> - PetitParser has been extended with the notion of context which enables
>> elegant island parsing.
>>
>> A list of issues addressed in this release can be found at:
>>
>> http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%…
>>
>>
>> Installation
>> ---
>>
>> The Moose Suite 5.0 comes for each platform as a separate bundle:
>> - *Moose Suite 5.0 for Mac>http://moosetechnology.org/res/download/
>> moose_suite_5_0-mac.zip
>> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_5_0-mac.zip>
>> *
>> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-mac.zip*>
>> - *Moose Suite 5.0 for Windows>http://moosetechnology.org/res/download/
>> moose_suite_5_0-win.zip
>> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_5_0-win.zip>
>> *
>> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-win.zip*>
>> - *Moose Suite 5.0 for Linux>http://moosetechnology.org/res/download/
>> moose_suite_5_0-linux.zip
>> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_5_0-linux.zip>
>> *
>> <https://dl.dropboxusercontent.com/u/18323746/Moose/moose_suite_4_8-linux.zi…>
>>
>> The Moose Suite 5.0 can also be loaded in a Pharo 3.0 image either from
>> the Configuration Browser, or by executing the following script:
>>
>> ==Gofer new
>> == smalltalkhubUser: 'Moose' project: 'Moose';
>> == configuration;
>> == loadStable
>>
>>
>> Happy holidays!
>> The Moose team
>>
>
>
--
www.tudorgirba.com
"Every thing has its own flow"
Apparently when I move the moose from the finder elements (classes) to the model item I get
a DNU point:from:
MoprhTreeListManager>>clicked: event inTheCheckboxOf: aTargetMorph
| position |
position := aTargetMorph point: event position from: client.
^ self isCheckList and: [ (aTargetMorph checkClickableZone translateBy: 2 @ 0) containsPoint: position ]
Stef
Hi,
As you know, Pharo Days will take place at the end of January. It is a
great place to learn and exchange ideas about Pharo (and indirectly Moose).
If you plan to attend, please register as soon as possible:
http://pharodays2015.pharo.org
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
- a powerful modeling platform
- a nice tower of expressive piles of cool stuff.
E.g., If my visualizations works with small numbers, then it will work large Java or tweet models. And this is impressive.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
We downloaded the last Moose image, installed PetitJava and PetitDelphi.
We parsed Java code and inspected the result. While navigating this
result we got a strange behavior of the GTInspector (these are the only
actions we have done). Please find attached a screenshot of the window
(font problems seem to be back + no scrollbar but the first line is
partially hidden).
Regards,
--
Jean-Christophe Bach
Hi!
Can I modify the method source code by simply inspecting it?
Consider the following method
C>>foo
^ ‘hello’
If I do: (C>>#foo) inspect
when I have an inspector on the compiled method. I can see the source code. But I cannot modify it :-(
How to support a recompilation of the method?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Status: New
Owner: ----
CC: chisvasi...(a)gmail.com
Labels: Type-Defect Priority-Critical Component-Glamour Milestone-5.0
New issue 1101 by tu...(a)tudorgirba.com: Pager does not properly replace the
panes
https://code.google.com/p/moose-technology/issues/detail?id=1101
This is a critical bug.
1. In a Playground go on "(1 to: 100)"
2. In the second pane select "4"
3. In the third pane select "self" (you should have 4 panes now)
4. Go back to the second pane and select "2"
==> You will still see "4" on the third pane
The problem only occurs when there are more panes to the right.
Furthermore, the Glamour model is correct: the entity of the third pane is
indeed 2, but something is wrong in the rendering.
--
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 everyone,
I changed the RTMenuBuilder in Roassal2, especially it's behavior, default
colors and added more features as the definition of the highlight color.
I also changed a bit the architecture but could still be a lot improved.
We can also add a lot of different features to really specify the look of
the menu using the builder so let me know if you have any ideas, comments.
You can have a look with the example 06:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| v b |
v := RTView new.
b := RTMenuBuilder new view: v.
b menu: 'add' submenu: '10' callback: [
| es |
es := (RTLabel new color: [ :tt| Color random ]) elementsOn: (1 to:
10).
es do: [ :e | e translateTo: ((500 atRandom @ 500 atRandom) - (250
@ 250)) ].
v addAll: es.
v canvas signalUpdate ].
b menu: 'add' submenu: '20' callback: [
| es |
es := (RTLabel new color: [ :tt| Color random ]) elementsOn: (1 to:
20).
es do: [ :e | e translateTo: ((500 atRandom @ 500 atRandom) - (250
@ 250)) ].
v addAll: es.
v canvas signalUpdate ].
b menu: 'remove' submenu: 'odd' background: (Color blue alpha:0.3)
callback: [ (v elements select: [ :e | e model odd ]) do: #remove. v canvas
signalUpdate ].
b menu: 'remove' submenu: 'even' background: Color red callback: [ (v
elements select: [ :e | e model even ]) do: #remove. v canvas signalUpdate
].
b menu: 'shuffle' highlight: Color lightBlue callback: [
| tra |
tra := RTSmoothLayoutTranslator new.
tra nbCycles: 0.5.
(v elements do: [ :e | tra translate: e to: ((500 atRandom @ 500
atRandom) - (250 @ 250)) ]) ].
v open
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
sincerely yours,
Pierre Chanson
Mea Culpa, I fixed one error, introduced another one :(
I hot-fixed the other one as well. But the implementation of PPJavaParser
is broken. It cannot hanlde foo().bar() properly, causing the DNU while
calling #object: on PJ<xy>Node.
Cheers,
Jan
>
> ---------- Forwarded message ----------
> From: Tudor Girba <tudor(a)tudorgirba.com>
> Date: Wed, Dec 17, 2014 at 4:54 PM
> Subject: petitjava tests failing
> To: moose-dev <moose-dev(a)iam.unibe.ch>
>
> Hi,
>
> The PetitJava tests are failing:
> https://ci.inria.fr/moose/job/moose-5.0/3594/testReport/
>
> @Jan: I saw you committed the last. Could you check?
>
> Cheers,
> Doru
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
Hi!
Yesterday with Damien P., we had a great discussion about modeling color palettes. Damien showed me an implementation he did about cubehelix. This is a fantastic way to model colors, while preserving the intensity. More info about it on: https://www.mrao.cam.ac.uk/~dag/CUBEHELIX/
Here is a code example:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| v helix shape elements slider |
v := RTView new.
helix := RTCubeHelix new.
helix rotations: 2.
helix gamma: 2.
shape := (RTBox new height: 300; width: 1; color: [ :model | helix level: model ]).
elements := shape elementsOn: (0.0 to: 1.0 by: 0.002).
v addAll: elements.
RTHorizontalLineLayout new gapSize: 0; on: elements.
"Set the gamma value"
slider := RTSlider new.
slider view: v.
slider labelled.
slider callback: [ :aValue | helix gamma: 5 * aValue. elements updateShape ].
slider moveBelow.
slider build.
"Set the rotation value"
slider := RTSlider new.
slider view: v.
slider labelled.
slider callback: [ :aValue | helix rotations: 5 * aValue. elements updateShape ].
slider moveBelow.
slider build.
v
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
And the accompanying screenshot
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
Consider the following script:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
v := RTView new.
label := RTLabel elementOn: 'TypeSomething'.
v add: label.
v when: TRKeyDown do: [ :evt |
label trachelShape text: label trachelShape text, evt keyValue asCharacter asString.
v signalUpdate.
].
v
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
If I open the view, then typing write text in the roassal view. In GTInpector, this does not work, because the left pane keeps the key focus. I have the impression the left pane should release the keyboard focus when the mouse on the right pane. No?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
==== Preliminary Call for Papers ====
VISSOFT 2015:
3rd IEEE Working Conference on Software Visualization
September 27 - September 28, 2015, Bremen, Germany
http://vissoft.info
Software visualization is a broad research area encompassing concepts, methods, tools, and techniques that assist in a range of software engineering and software development activities. Covered aspects include the development and evaluation of approaches for visually analyzing software and software systems, including their structure, execution behavior, and evolution.
The VISSOFT IEEE Working Conference on Software Visualization continues the history of the ACM SOFTVIS Symposium on Software Visualization and the IEEE VISSOFT International Workshop on Visualizing Software for Understanding and Analysis. The conference focuses on visualization techniques that target aspects of software maintenance and evolution, program comprehension, reverse engineering, and reengineering, i.e., how visualization helps professionals to understand, analyze, test and evolve software. We aim to gather tool developers, experts, users, and researchers from software engineering, information visualization, computer graphics, and human-computer interaction to discuss theoretical foundations, algorithms, techniques, tools, and applications related to software visualization. We seek technical papers, empirical studies, applications, or case studies and provide a platform for presenting novel research ideas and tools.
Topics of interest include, but are not limited to:
* Innovative visualization and visual analytics techniques for software engineering data, such as,
- source code
- static and dynamic dependencies
- software evolution and repositories
- software documentation
- web services
- protocol, log, and performance data
- parallel techniques
- database schemes
- software security and privacy issues
- workflow and business processes
* Visualization to support program comprehension, software testing, and debugging
* Interaction techniques and algorithms for software visualization
* Visualization-based techniques in computer science and software engineering education
* Integration of software visualization tools and development environments
* Empirical evaluation of software visualization
* Industrial experience on using software visualization
Papers are solicited that present original, unpublished research results and will be rigorously reviewed by an international program committee. In addition to technical papers, VISSOFT features a New Ideas or Emerging Results (NIER) track and a Tool track related to the same list of topics suggested above. All accepted submissions will appear in the conference proceedings and the IEEE Digital Library.
-== Technical papers ==-
These contributions describe in-depth mature research results in the above-mentioned areas of interest. The submission of a video (up to 5 minutes in length) to accompany the paper is highly encouraged to show interaction possibilities. Authors who wish to submit such video should provide a URL to the video. Technical papers have to be maximum 10 pages long (including bibliography and annexes).
Abstract submission date: April 27, 2015
Full paper submission date: May 4, 2015
Author response period: June 8 - 12, 2015
Notification: June 18, 2015
Artifacts:
Traditionally, technical research papers are published without including any artifacts (such as tools, data, models, videos, etc.), even though the artifacts may serve as crucial and detailed evidence for the quality of the results that the associated paper offers. Following the effort initiated at ESEC/FSE’11, authors of accepted technical papers at VISSOFT 2015 can have their artifacts evaluated by the program committee. Positively evaluated artifacts will be reflected in the paper publication and presentation. More information about the artifacts may be found on http://www.artifact-eval.org.
Artifact submission for accepted papers: June 24, 2015
Artifact notification: July 31, 2015
Awards:
VISSOFT 2015 will award distinguished technical papers. Monetary awards will be sponsored by ObjectProfile.com
Special issue:
We plan to invite a selection of the technical papers accepted at VISSOFT 2015 to submit an extended version to a journal.
-== NIER papers ==-
The NIER contributions (New Ideas and Emerging Results) describe work-in-progress and preliminary exciting results. Authors should include open questions and even provocative hypotheses to get early feedback on their research ideas or even support through new research collaborations. NIER papers have to be maximum 5 pages long (including bibliography and annexes).
Paper submission date: June 15, 2015
Notification: July 31, 2015
-== Tool papers ==-
Tool contributions describe the design or actual utilization of software visualization tools, with a focus on relevant tool construction aspects or the use of the tool for gaining new insights. Authors should be prepared to demonstrate their tool at the conference. The submission may also contain a link to a screencast (video). Tools papers have to be maximum 5 pages long (including bibliography and annexes).
Paper submission date: June 15, 2015
Notification: July 31, 2015
General Chair:
Jürgen Döllner, Hasso-Plattner-Institut, Germany -- http://www.hpi.uni-potsdam.de/doellner/
Program Co-Chairs:
Fabian Beck, University of Stuttgart, Germany -- http://research.fbeck.com
Alexandre Bergel, University of Chile, Chile -- http://bergel.eu
Please visit http://vissoft.info for updates.
Best regards,
Fabian Beck and Alexandre Bergel
Program Co-Chairs
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
And there might be a similar (but earlier) problem with Coral (Since August 18).
I assume that has to do with
Name: PetitParser-JanKurs.234
Author: JanKurs
Time: 19 August 2014, 1:42:13.758355 pm
UUID: 2ce06ac7-8b97-40c0-aae0-4b06778e6cfc
Ancestors: PetitParser-DiegoLont.233
Merging the cool context extensions. Still work in progress. Some external parsers might get impacted in the meantime (together with Doru)
https://ci.inria.fr/pharo-contribution/job/Coral/
Stephan
Hi!
Today Andrei and I pair-programmed on a stack bar plot builder.
Here is an example:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
b := RTStackBarPlot new.
b interaction popupText.
b colorPalette colors: { Color blue . Color lightBlue }.
b add: #(37 33 0 0 0) title: 'DN1'.
b add: #(24 26 17 3 0) title: 'DN2'.
b add: #(25 29 15 1 0) title: 'DN3'.
b add: #(30 33 6 1 0) title: 'DN4'.
b addLegend: #('strongly agree' 'agree' 'neutral' 'disagree' 'strongly disagree').
b barWidth: 260 height: 20.
b addLabelToBars: [ :assoc | (assoc key / b totalSum * 100) asInteger asString, '%' ] if: [:assoc | assoc key > 5 ] color: Color white.
b build.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Result is the following:
Cheers,
Andrei & Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Name: ConfigurationOfFame-StephanEggermont.29
Author: StephanEggermont
Time: 12 December 2014, 1:44:19.682481 pm
UUID: a59ec3f1-2e02-4e1e-a35b-2b195f3f8f1c
Ancestors: ConfigurationOfFame-StephanEggermont.28
wrong version fix in place
Name: ConfigurationOfSmallDude-StephanEggermont.30
Author: StephanEggermont
Time: 12 December 2014, 1:52:50.120165 pm
UUID: a71f5053-b9c9-4024-8457-631db8e8cdf4
Ancestors: ConfigurationOfSmallDude-TudorGirba.29
Version for Moose 5.0
Name: ConfigurationOfPetitSQLParser-StephanEggermont.24
Author: StephanEggermont
Time: 12 December 2014, 1:59:02.954291 pm
UUID: 5150f87c-ee94-43cc-886d-d1933b341ab3
Ancestors: ConfigurationOfPetitSQLParser-StephanEggermont.23
Use the new version in #stable
Name: ConfigurationOfPetitSQLParser-StephanEggermont.25
Author: StephanEggermont
Time: 12 December 2014, 2:07:43.151571 pm
UUID: d631128c-fd0e-4ea6-a4b4-3f6d1ff7c784
Ancestors: ConfigurationOfPetitSQLParser-StephanEggermont.24
typo
I've added a first version of the release5.0 version, only containing
stable versions of the depending configurations. Loading that gives
an emergency debugger.
Gofer new
smalltalkhubUser: 'Moose' project: 'Moose';
configuration;
load.
((Smalltalk at: #ConfigurationOfMoose) project version: #'release5.0') load
Hi!
We have worked very hard on a Roassal exporter for the Web.
Milton has produced the class RTHTML5Exporter, which may be simply invoked as: RTHTML5Exporter new export: aRoassalView.
Check this out:
https://dl.dropboxusercontent.com/u/31543901/RoassalHTML/index.html
Try moving the mouse above the circle or dots in the curve.
The html file you see from your web browser is the result of do-iting the following expression:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| c b c2 |
c := RTComposer new.
"======"
b := RTGraphBuilder new.
b view: c view.
b edges
connectFrom: #superclass;
useInLayout.
b edges
if: [ :fromClass :toClass | toClass name beginsWith: 'TR' ];
connectTo: #dependentClasses;
color: (Color blue alpha: 0.3).
b nodes
if: [ :cls | cls name beginsWith: 'RT' ];
color: Color blue.
b nodes
color: Color red.
b layout cluster.
b global
normalizeSize: #numberOfMethods min: 5 max: 40 using: #sqrt;
alphaColor: 0.4.
b addAll: TRShape withAllSubclasses, RTShape withAllSubclasses.
b build.
c group.
"======"
c2 := RTCharterBuilder new.
c2 view: c view.
c2 interaction popup.
c2 extent: 300 @ 200.
c2 points: (RTShape withAllSubclasses sortedAs: #numberOfMethods).
c2 connectDotColor: Color blue.
c2 points: (TRShape withAllSubclasses sortedAs: #numberOfMethods).
c2 stackX.
c2 allY: #numberOfMethods.
c2 connectDotColor: Color red.
c2 axisX.
c2 axisY.
c2 build.
c group.
"======"
c layout: RTVerticalLineLayout new.
c propagateHighlightToAll.
"======"
legend := RTLegendBuilder new.
legend view: c view.
legend addText: 'This is a demonsration of a combination of builders'.
legend addText: 'The above visualization shows the dependencies between Roassal and Trachel shapes.'.
legend addText: 'Curves indicate the distribution of the number of methods'.
legend build.
"======"
RTHTML5Exporter new export: c view.
c view
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Name: ConfigurationOfPetitParser-StephanEggermont.57
Author: StephanEggermont
Time: 12 December 2014, 11:29:41.588663 am
UUID: 9cf8b80c-3e08-49ee-a014-4c6e815afaa3
Ancestors: ConfigurationOfPetitParser-usmanbhatti.56
Stable version for Moose 5
Name: ConfigurationOfPetitSQLParser-StephanEggermont.23
Author: StephanEggermont
Time: 12 December 2014, 11:35:05.659061 am
UUID: 981097a0-66e7-4933-91cb-bfca289c2862
Ancestors: ConfigurationOfPetitSQLParser-TudorGirba.22
New stable version for Moose 5
Hello,
I have been using GTInspector a lot lately and I think it is a great tool. Even though, sometimes I have to go back to the old inspector. Sometimes an inspector tab raise an error and instead of having a single unusable tab, or a inspector with less tabs I get no inspector at all.
Have anyone had this problem before?
In case you need help with this issue, how can I contribute?
Cheers,
Alejandro
Dear All,
Rosario, a really smart student from University of Chile, is working on a history-aware debugger (sometimes called Omniscient debugging).
Although this is still an early version of Rosario’s prototype and we are still unsure what we actually want (as you may guess, it all depends on the usage scenarios we want to cover), Rosario decided to do a small video, just to spark what has to be sparked :-D
http://vimeo.com/114094830 <http://vimeo.com/114094830>
Thanks Andrei for offering his help on this! It is good to have you among us!
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I would like to know why the basic icons in Moose comes from the Pharo2.0 version:
[cid:image001.png@01D0146A.C06A1150]
And not from Pharo3.0: ?
[cid:image002.png@01D0146B.15F1AAC0]
Cheers,
Vincent
________________________________
Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.