On Wed, Jun 1, 2016 at 2:31 PM, Christophe Demarey
<christophe.demarey(a)inria.fr> wrote:
Hi,
I do not think it is a good idea to silently download in headless mode.
You often deploy apps in production in headless mode. Why would you want to download the
sources?
I agreed with not download sources in headless mode. If you're going
headless, you're not an impressionable newcomer needing your hand held
to fix a problem.
I would rather see a default behavior not downloading
the sources and a settings to allow automatic sources download.
Lets not not do anything "automatic" and **hidden** from the user. If
an alert is being displayed (as is currently done), it may as well
have a button to download them. Give the user control.
This is a first-impression issue for newcomers. The default headful
behaviour should be to provide the user an alert, with a single button
press to fix the problem.
You could pop up a dialog in ui mode to enable the
feature the first time you see a missing sources file.
Do you mean a setting outside the Image in an INI file? Otherwise I
don't follow this logic. What happens after the dialog is popped up
and "automatic download" is enabled? The download starts? May as
well make it a "download" button, rather than an "automatic
download"
setting. It something that only needs to happen once.
cheers -ben
Christophe
> Le 31 mai 2016 à 20:33, Offray Vladimir Luna Cárdenas <offray.luna(a)mutabit.com>
a écrit :
>
> Is it possible to do the silent download only in headless mode? This would add to the
first impressions without reducing respossiveness.
>
> Cheers,
>
> Offray
>
> On 31/05/16 09:16, Sven Van Caekenberghe wrote:
>> In a 3.0 image it can be found under #downloadSources
>>
>> Yes it did it silently, the thing is, you do not always have a UI (headless
image). Many applications download extra files the first time they start up.
>>
>>> On 31 May 2016, at 16:09, Ben Coman <btc(a)openinworld.com> wrote:
>>>
>>> On Tue, May 31, 2016 at 9:52 PM, Sven Van Caekenberghe <sven(a)stfx.eu>
wrote:
>>>>> On 31 May 2016, at 15:19, Ben Coman <btc(a)openInWorld.com>
wrote:
>>>>>
>>>>> [cross-post to pharo-dev]
>>>>>
>>>>> On Tue, May 31, 2016 at 9:03 PM, Serge Stinckwich
>>>>> <serge.stinckwich(a)gmail.com> wrote:
>>>>>> No this is not buggy, I'm using this version on mac os x
also.
>>>>>> This is still is still a beta version of MOOSE 6.0, but the
stable
>>>>>> version should be release in a couple of days normally.
>>>>>>
>>>>>> You have to download the missing file (PharoV50.sources) from
here:
>>>>>>
http://files.pharo.org/sources/
>>>>> If this will remain a well defined location, I wonder if instead of
>>>>> *only* advising the file is missing, the user could be offered to
>>>>> download it to either image or vm location ? Could improve first
>>>>> impressions ?
>>>> Well, one day we had a very cool option whereby the missing source file
was downloaded automatically, but we had to disable it again because of unreliable
networking for some people. A pity.
>>> I can't remember seeing that behaviour myself, but I vaguely remember
>>> discussion. Can you remind me, did it If it automatically and silently
>>> downloaded the missing source file, thus delaying the UI from being
>>> responsive? That would be bad :). An common Microsoft anti-pattern
>>> IMO i.e. "Don't try to be too smart for your users" but
instead give
>>> them a sense of control. Bringing up a dialog for user choice in an
>>> immediately responsive UI might be acceptable.
>>>
>>> cheers -ben
>>>
>>>>> cheers -ben
>>>>>
>>>>>
>>>>>> and put in the same place as your image.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>>
>>>>>> On Tue, May 31, 2016 at 1:38 PM, tien dh
<tiendh11986(a)gmail.com> wrote:
>>>>>>> Hi,
>>>>>>> I've tried to used version 6.0 as you suggest, but it
seems to be buggy on
>>>>>>> Mac OS.
>>>>>>> In fact, I've downloaded Pharo Virtual machine and the
Image file and loaded
>>>>>>> the image into the virtual machine, but the software shown
the error
>>>>>>> message:
>>>>>>>
>>>>>>> "Pharo cannot locate the sources file named
>>>>>>> /Users/macbookpro/Downloads/PharoV50.sources.
>>>>>>>
>>>>>>> Please check that the file is named properly and is in the
>>>>>>> same directory as this image.
>>>>>>> Make sure the sources file is not an Alias."
>>>>>>>
>>>>>>> On Tue, May 31, 2016 at 2:34 PM, tien dh
<tiendh11986(a)gmail.com> wrote:
>>>>>>>> Xin chào Serge, I'm from Vietnam and It's nice to
see a greeting in
>>>>>>>> Vietnamese :)
>>>>>>>> Thanks for your quick reply.
>>>>>>>> I'm using version 5.1 on Mac OS. Yep, I've
imported a model, and I open
>>>>>>>> script windows via "All model classes" >
Browse > In Roassal Easel.
>>>>>>>> When I copy your new code to the script windows and click
the Play button,
>>>>>>>> it shows the an error:
>>>>>>>> MessageNotUnderstood:
GLMRoassal2Easel>>correctFrom:to:with:
>>>>>>>>
>>>>>>>> Am I wrong in using the tool? How can I test running of
Mondrian code?
>>>>>>>>
>>>>>>>> On Tue, May 31, 2016 at 1:31 PM, Serge Stinckwich
>>>>>>>> <serge.stinckwich(a)gmail.com> wrote:
>>>>>>>>> You should read :
http://agilevisualization.com/
>>>>>>>>>
>>>>>>>>> On Tue, May 31, 2016 at 12:29 PM, Serge Stinckwich
>>>>>>>>> <serge.stinckwich(a)gmail.com> wrote:
>>>>>>>>>> On Tue, May 31, 2016 at 12:04 PM, tien dh
<tiendh11986(a)gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>> Hello, I'm new to Mondiran and I'm
trying to run very simple piece of
>>>>>>>>>>> code:
>>>>>>>>>>
>>>>>>>>>> Xin chào Tien.
>>>>>>>>>> Where are you located ?
>>>>>>>>>>
>>>>>>>>>>> | view namespaces |
>>>>>>>>>>> namespaces := MooseModel root allModels first
allModelNamespaces.
>>>>>>>>>>> view := MOViewRenderer new.
>>>>>>>>>>> view shape rectangle
>>>>>>>>>>> width: #numberOfClasses;
>>>>>>>>>>> height: #numberOfMethods;
>>>>>>>>>>> linearFillColor: #numberOfLinesOfCode within:
namespaces.
>>>>>>>>>>> view nodes: namespaces.
>>>>>>>>>>> view edgesToAll: #providerNamespaces.
>>>>>>>>>>> view dominanceTreeLayout.
>>>>>>>>>>> view open.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I tried with Roassal Easel but it doesn't
compile. Where should I put
>>>>>>>>>>> the
>>>>>>>>>>> code and run?
>>>>>>>>>> Apparently you are running an old version of
Roassal.
>>>>>>>>>> Try to use the last version of MOOSE 6.0:
http://moosetechnology.org/
>>>>>>>>>>
>>>>>>>>>> Are you sure you have imported a model with the
MOOSE panel first ?
>>>>>>>>>>
>>>>>>>>>> The API change a little bit in MOOSE 6.0:
>>>>>>>>>>
>>>>>>>>>> | view namespaces |
>>>>>>>>>> namespaces := MooseModel root allModels first
allModelNamespaces.
>>>>>>>>>> view := RTMondrian new.
>>>>>>>>>> view shape rectangle
>>>>>>>>>> width: #numberOfClasses;
>>>>>>>>>> height: #numberOfMethods;
>>>>>>>>>> linearFillColor: #numberOfLinesOfCode within:
namespaces.
>>>>>>>>>> view nodes: namespaces.
>>>>>>>>>> view edges connectToAll: #providerNamespaces.
>>>>>>>>>> view layout dominanceTree.
>>>>>>>>>> view open.