Hi!
We’ve just added a new post that contains nice screenshots and (short) explanation about galaxies.
https://www.facebook.com/ObjectProfile/posts/628687443884523?stream_ref=10
Faviola is doing a truly fantastic work.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi everyone,
sorry if I missed that, but is it a known issue that code completion popup is displaced (does not appear near the cursor)? Because for me it’s very frustrating and I’d try to fix it if someone can suggest me where to start looking?
Uko
Hi!
To welcome the effort of Francisco Hafon A. and Ronie Salgado, we have posted some new picture of Roassal3d.
https://www.facebook.com/ObjectProfile/posts/629794963773771
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Thanks Kilon for your nice words.
Currently, AstroCloud is a bit slow. For example, loading this image takes much more than it should. For now, speed is not our priority. AstroCloud has to be fast and we will make it fast. Probably relying on external library is the way to go.
Just to give a bit more context about why we are doing AstroCloud. ALMA is the largest observatory on Earth, making it the largest astronomical project in existence (http://www.almaobservatory.org). This is what humanity has best to detect life outside Earth.
ALMA is made of 66 high-precision antenas making it possible to see deep in the universe. Unfortunately, there is no good software to process these immensely complex pictures. Some tool suite naturally exist, but they were not made for ALMA, making these existing tools largely suboptimal to process complex picture of ALMA.
Faviola’s dream (and mine) is to produce a tool ready to be consumed by astronomers to process ALMA pictures. Faviola and I are currently seeking for additional resources on making this happen.
Regarding your help about documenting Roassal. It is very welcome! In one of my previous post, I said that 2014 will be the year of documenting Roassal. A book is on its way. We will need people to review it. So thanks!
Kind regards,
Alexandre
On May 6, 2014, at 2:40 PM, kilon alios <kilon.alios(a)gmail.com> wrote:
> Well then my hat off to you sir
>
> I am asking because rendering graphics is certainly an expensive (CPU and RAM) process. Rendering graphics is certainly something that interests me.
>
> Of course I dont expect Pharo to compete with C , but then thats why we have Nativeboost. But I would love to see Roassal evolve to a full blown graphics engine. Certainly motivates me more to learn Roassal as deeply as I can. I remember when you first said I should use Roassal for my vector editor , I was quite sceptical. But seeing all these new apps pop up from real scientists made me think twice and now I have put my vector editor on hold to learn more about Pharo and Roassal and of course Moose.
>
> Would love to help you document it further. Though for now I am learning it in a very slow pace. Congrats to you and all people involved with the libraries and of course to the people making the apps. You certainly changed my mind and I would love to see more apps that show the potential of these libraries.
>
> I am also wondering if you are so ambitious whether porting C libraries like imagmagick would make sense for Roassal.
>
>
>
> http://www.imagemagick.org/
>
> Or possibly other C graphics libraries.
>
>
> On Tue, May 6, 2014 at 9:18 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
> The picture is rendered in Roassal, but raw data is obtained from a file.
> AstroCloud, an application made on top of Roassal, does some sophisticated color mapping and transformation.
>
> Alexandre
>
>
> On May 6, 2014, at 12:40 PM, kilon alios <kilon.alios(a)gmail.com> wrote:
>
> > beautiful, I am a huge fan of astronomy and sci fi. Is the image of the galaxy rendered with Roassal or is it just an image file that Roassal is displaying ?
> >
> >
> > On Tue, May 6, 2014 at 6:56 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
> > Hi!
> >
> > We’ve just added a new post that contains nice screenshots and (short) explanation about galaxies.
> >
> > <1836600_628685437218057_2402452585680727709_o.png>
> >
> > https://www.facebook.com/ObjectProfile/posts/628687443884523?stream_ref=10
> >
> > Faviola is doing a truly fantastic work.
> >
> > Cheers,
> > Alexandre
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-GlamorousToolkit
New issue 1038 by kurs....(a)gmail.com: Debugger Shortcuts Problems
http://code.google.com/p/moose-technology/issues/detail?id=1038
While using shortcuts in debugger, e.g. alt+t for step over, once upon a
time the focus is moved from the stack window to the code window and alt+t
starts modifying the text. One has to click back to the stack window...
How to reproduce the problem:
Just use debugger with alt+t for some time.
Additional information:
Ubuntu x64
--
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
New issue 1051 by info.lan...(a)gmail.com: MessageNotUnderstood:
GLMTextMorphForEditView>>textMorph
http://code.google.com/p/moose-technology/issues/detail?id=1051
I've been trying to execute a script in the new workspace.
This script needed a temporary variable so I clicked on : Declare new ...
And the error occurred
MessageNotUnderstood: GLMTextMorphForEditView>>textMorph
--
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-Glamour
New issue 1032 by chisvasi...(a)gmail.com:
GLMPresentation>>dynamicActionsOnSelection does not work for text
presentations
http://code.google.com/p/moose-technology/issues/detail?id=1032
Text presentations have the selection in the port 'selectedText'.
GLMPresentation>>dynamicActionsOnSelection only computes the actions if
the 'selection' port is populated. Thus, it does not work for text
presentations.
--
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
New issue 1062 by v.blonde...(a)gmail.com: The GT-Debugger doesn't declare
variables created while debugging
http://code.google.com/p/moose-technology/issues/detail?id=1062
Describe the problem: what do you get? what do you expect?
When debugging, if you define a new variable in a debugged method, the
variable is not declared when you save.
How to reproduce the problem: step by step if necessary
For example, debug :
{ 1 .2 } asOrderedCollection
Go into.
In the method asOrderedCollection, write:
temp := self as: OrderedCollection.
^ temp
After saving, the temp variable is not declared and the method is compiled
without the declaration.
Additional information: platform, context which may impact the problem
Latest Moose 5.0 - W7
Please fill in the labels with the following information:
* Type-Defect
* Component-GTDebugger
--
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
New issue 1063 by v.blonde...(a)gmail.com: Save a modified unstacked block
raise DNU: DebugContext>>codeTextMorph
http://code.google.com/p/moose-technology/issues/detail?id=1063
Describe the problem: what do you get? what do you expect?
When you modfiy a block that is not on the stack (like [ self halt ]) and
you browse it, you get:
DNU: DebugContext>>codeTextMorph
How to reproduce the problem: step by step if necessary
create a method in a class Class:
sendBlock
^ [ self halt ]
And call :
Class new sendBlock value.
It will open the debugger.
Now modify the block content (remove the halt for example)
Save, click on browse in the notification window.
You should get the error.
Additional information: platform, context which may impact the problem
W7 - Moose 5.0
Please fill in the labels with the following information:
* Type-Defect
* Component-GTDebugger
--
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