Ok for me
where are the files for 1.3: the first slices? (not tagged for-14)?
On Sep 3, 2011, at 10:28 AM, Alain Plantec wrote:
:))
I'm documenting shout using (an help for the help browser + adding
Shout-Examples with several examples).
Now, maybe 1.3 should be fixed without this help and
I think it is a good idea to have the number parser separate, after
all it might also make sense to use it separately.
+1.
Modularity and composibility is a strong apsect of PP so we should use them.
Especially since in the future we want to use petitSmalltalk for pharo (to be
checked
Alain
either we should change some textEditor into CodeEditor (and the inverse) or we
should make sure that by default texts are not shouted.
Because we have a lot of place (like workspace, some inspector panes
So what do you think?
Stef
All editors should be shout-able, but they should only be shouted if
their model implements #shoutAboutToStyle: or whatever specific
callback the system configured shouter is using.
If CodeEditor has support for shouting only, then OB is screwed again
because there the extra behavior of
*** Warning: Warning: This package depends on the following classes:
LessonView
ScriptManager
You must resolve these dependencies before you will be able to load
these definitions:
LessonViewshoutAboutToStyle:
ScriptManagershoutAboutToStyle:
Not sure if this is intentional,
Hi lukas
Does not look good to me. Looks like strnage dependencies.
Thanks for reporting.
Stef
*** Warning: Warning: This package depends on the following classes:
LessonView
ScriptManager
You must resolve these dependencies before you will be able to load
these definitions:
On Sep 4, 2011, at 10:48 AM, Lukas Renggli wrote:
All editors should be shout-able, but they should only be shouted if
their model implements #shoutAboutToStyle: or whatever specific
callback the system configured shouter is using.
Yes I saw that. I'm still waiting for alain description to
Hi,
Strange indeed. The thing is that in my image, these methods are not
extensions. So, I cannot see why they would not load.
In any case, Glamour was always loaded in the Dev image.
Cheers,
Doru
On 4 Sep 2011, at 10:58, Stéphane Ducasse wrote:
Hi lukas
Does not look good to me. Looks
Now may be the default should be inverted.
Not styled by default else we should really have a look at all the places
where we should not shout and fix them.
Because it looks strange to have a red text in inspector left pane especially
when shout tries to parse anOrderedCollection ()
Strange indeed. The thing is that in my image, these methods are not
extensions. So, I cannot see why they would not load.
In any case, Glamour was always loaded in the Dev image.
Ok, I do not use the official dev image, but then again it worked up
until a few days ago. Something must have
On Sep 4, 2011, at 11:11 AM, Lukas Renggli wrote:
Now may be the default should be inverted.
Not styled by default else we should really have a look at all the places
where we should not shout and fix them.
Because it looks strange to have a red text in inspector left pane
especially when
On 4 September 2011 12:18, Stéphane Ducasse stephane.duca...@inria.fr wrote:
On Sep 4, 2011, at 11:11 AM, Lukas Renggli wrote:
Now may be the default should be inverted.
Not styled by default else we should really have a look at all the places
where we should not shout and fix them.
On Sep 4, 2011, at 1:00 PM, Lukas Renggli wrote:
On 4 September 2011 12:18, Stéphane Ducasse stephane.duca...@inria.fr wrote:
On Sep 4, 2011, at 11:11 AM, Lukas Renggli wrote:
Now may be the default should be inverted.
Not styled by default else we should really have a look at all the
On Sep 4, 2011, at 1:53 PM, Stéphane Ducasse wrote:
On Sep 4, 2011, at 1:00 PM, Lukas Renggli wrote:
On 4 September 2011 12:18, Stéphane Ducasse stephane.duca...@inria.fr
wrote:
On Sep 4, 2011, at 11:11 AM, Lukas Renggli wrote:
Now may be the default should be inverted.
Not styled
On 4 September 2011 14:05, Benjamin
benjamin.vanryseghem.ph...@gmail.com wrote:
On Sep 4, 2011, at 1:53 PM, Stéphane Ducasse wrote:
On Sep 4, 2011, at 1:00 PM, Lukas Renggli wrote:
On 4 September 2011 12:18, Stéphane Ducasse stephane.duca...@inria.fr
wrote:
On Sep 4, 2011, at 11:11 AM,
On Sep 4, 2011, at 2:08 PM, Lukas Renggli wrote:
On 4 September 2011 14:05, Benjamin
benjamin.vanryseghem.ph...@gmail.com wrote:
On Sep 4, 2011, at 1:53 PM, Stéphane Ducasse wrote:
On Sep 4, 2011, at 1:00 PM, Lukas Renggli wrote:
On 4 September 2011 12:18, Stéphane Ducasse
The inspector is shouted because the not to shout was the default behavior
of Shout, but now,
okToStyle
self shoutEnabled
ifFalse: [^ false].
(model respondsTo: #shoutAboutToStyle:)
ifFalse: [^true].
^model shoutAboutToStyle: self
the bold part make the default behavior to shout.
So
No, #shoutEnabled returning true makes it enabled.
shoutEnabled return true if Shout classes are installed in the system.
This is a bug then.
#okToStyle should never be called when Shout is not installed.
#shoutEnabled returns true, if the model might request highlighting. I
suggested Alain
On Sep 4, 2011, at 2:34 PM, Lukas Renggli wrote:
No, #shoutEnabled returning true makes it enabled.
shoutEnabled return true if Shout classes are installed in the system.
This is a bug then.
#okToStyle should never be called when Shout is not installed.
#shoutEnabled returns true,
which shout the text if the model do not know #shoutAboutToStyle:
No. The interaction is different:
1. TextMorph changes its contents.
2. TextMorph notifies its styler withe the morph and its model that
there might be the need to style.
3. The styles does whatever it wants to do:
- The
On 03 Sep 2011, at 18:54, Hernán Morales Durand wrote:
2011/9/2 Stéphane Ducasse stephane.duca...@inria.fr:
On Sep 2, 2011, at 7:16 AM, Hernán Morales Durand wrote:
Two more:
ScriptLoader new installingInstaller
should not work and should not be used.
Nobody should use
On 02 Sep 2011, at 23:01, Lukas Renggli wrote:
It would be better if this were prevented. I will have a look to see if I
can keep track of these connections and worker processes in a weak data
structure so that they can be managed better.
Better no weak data structures. The listener
Yeah, the idea of the weak data structure was to have a fallback to the
current situation in case something went wrong when explicitely managing the
connections. The current implementation now uses a normal ordered collection.
It passes all tests.
Sounds great!
Note that this version of
Hi Sven,
There seems to be a new problem with Zinc when building Seaside. Not
sure what it is:
+ build.sh -i seaside3 -s seaside3-zinc -o seaside3-zinc
build.sh: Execution aborted (/usr/local/bin/cog)
THERE_BE_DRAGONS_HERE
PrimitiveFailed: primitive #signal in a Semaphore() failed
4
Hi all,
just coming back ...
yes
if not styled is the default then #okToStyle should
return false if #shoutAboutToStyle is not implemented by the model:
(model respondsTo: #shoutAboutToStyle:)
ifFalse: [^true].
should be:
(model respondsTo: #shoutAboutToStyle:)
Lukas,
On 04 Sep 2011, at 18:17, Lukas Renggli wrote:
There seems to be a new problem with Zinc when building Seaside. Not sure
what it is:
Strange indeed. I just downloaded the lastest base seaside3 image from
http://jenkins.lukas-renggli.ch and executed the
Towards better HTTP client usage
At the last Pharo Sprint in Lille (July 8th), Stéphane and I were at one point
trying to remove some old HTTPSocket usage (which indirectly uses Zn) and
replace it with direct and clean Zn usage. We hadn't much time left and didn't
get very far. But I realized
On 03.09.2011 13:57, Igor Stasenko wrote:
On 3 September 2011 12:57, Philippe Marschall kus...@gmx.net wrote:
On 02.09.2011 17:19, Igor Stasenko wrote:
On 2 September 2011 17:27, Philippe Marschall kus...@gmx.net wrote:
On 02.09.2011 15:39, Igor Stasenko wrote:
Looks like it tries to destroy
Strange indeed. I just downloaded the lastest base seaside3 image from
http://jenkins.lukas-renggli.ch and executed the
builder/scripts/seaside3-zinc.st code manually and the server started and
worked as expected.
The strange thing is that it happened in both builds, Seaside 3.0 and 3.1.
On 04/09/2011 11:13, Lukas Renggli wrote:
Strange indeed. The thing is that in my image, these methods are not
extensions. So, I cannot see why they would not load.
In any case, Glamour was always loaded in the Dev image.
Ok, I do not use the official dev image, but then again it worked up
On 04 Sep 2011, at 20:27, Lukas Renggli wrote:
Strange indeed. I just downloaded the lastest base seaside3 image from
http://jenkins.lukas-renggli.ch and executed the
builder/scripts/seaside3-zinc.st code manually and the server started and
worked as expected.
The strange thing is that
Just looking at the code, I can't think of an explanation (since it worked
before). The last diff is pretty small, all in one class.
Could it be VM related ? Can I download the exact same VM that you are using,
but that would be a linux one I guess ? Maybe I should set up a build process
Hi,
On 4 Sep 2011, at 20:59, Alain Plantec wrote:
On 04/09/2011 11:13, Lukas Renggli wrote:
Strange indeed. The thing is that in my image, these methods are not
extensions. So, I cannot see why they would not load.
In any case, Glamour was always loaded in the Dev image.
Ok, I do not
On Sep 4, 2011, at 8:20 PM, Alain Plantec wrote:
Hi all,
just coming back ...
yes
if not styled is the default then #okToStyle should
return false if #shoutAboutToStyle is not implemented by the model:
(model respondsTo: #shoutAboutToStyle:)
ifFalse: [^true].
Alain
it means that we should define shoutAboutToStyle: to certain places like
inspector pane.
Isn't?
:)
On Sep 4, 2011, at 8:20 PM, Alain Plantec wrote:
Hi all,
just coming back ...
yes
if not styled is the default then #okToStyle should
return false if #shoutAboutToStyle is not
On 04 Sep 2011, at 21:33, Lukas Renggli wrote:
Just looking at the code, I can't think of an explanation (since it worked
before). The last diff is pretty small, all in one class.
Could it be VM related ? Can I download the exact same VM that you are
using, but that would be a linux one
14119
-
- Issue 4760: Shout default to shout only if shoutAboutToStyle is defined.
Thanks Alain Plantec.
http://code.google.com/p/pharo/issues/detail?id=4760
- Issue 4756: More cleaning of ImageSegment. Thanks Mariano Martinez-Peck.
On 04/09/2011 22:26, Stéphane Ducasse wrote:
Alain
it means that we should define shoutAboutToStyle: to certain places like
inspector pane.
Isn't?
:)
arrggh, I've tried and it exhibits a problem. see the end of the answer.
yes, you can do it with a shoutAboutToStyle:
something like:
On 04/09/2011 21:56, Tudor Girba wrote:
Hi,
On 4 Sep 2011, at 20:59, Alain Plantec wrote:
On 04/09/2011 11:13, Lukas Renggli wrote:
Strange indeed. The thing is that in my image, these methods are not
extensions. So, I cannot see why they would not load.
In any case, Glamour was always
Hi,
To show how Moose can support the analysis of various data sets, I am looking
for a case study containing a complex data structure that does not represent a
software system, and a set of questions associated with it. Ideally, the data
should be freely available and it should contain a set
Hi Tudor,
I don't know if you want few data sets or many ones, but for each case
I found Selecting genes with dissimilar discrimination strength for
sample class prediction, report case studies in two real cancer
microarray datasets (CAR and LUNG) for gene expression profiling. The
Lymphoma case
Hi,
Thanks, but I am looking for data sets that contained graphs of entities with
properties, rather then numbers.
To give an idea, an example would be a set of persons that have multiple
properties, such as age or function, and have various kinds of relationships
with other persons. Ideally,
Hi Doru!
I like swimming. Swimovate is a watch that makes a geek swimmer happy: it
records set and provides numerous data. Data is structured as a tree, not
really a graph, even thought this is not impossible to find a graph structure.
I worked on analyzing swimming sets in moose. I haven't
2011/9/4 Tudor Girba tu...@tudorgirba.com:
Hi,
Thanks, but I am looking for data sets that contained graphs of entities with
properties, rather then numbers.
Oh, that was just the top of the iceberg, look at cellular interaction
networks like protein-protein interactions, relations between
I've used as an example of datamining a dataset about car accidents we got
from here http://www.nhtsa.gov/NASS .
Hope it helps :)
Guille
On Sun, Sep 4, 2011 at 11:58 PM, Hernán Morales Durand
hernan.mora...@gmail.com wrote:
2011/9/4 Tudor Girba tu...@tudorgirba.com:
Hi,
Thanks, but I am
Stanford has many large graph-like datasets to download: social
networks, web graphs, peer-to-peer networks, shopping networks, road
networks, wikipedia networks, etc.
http://snap.stanford.edu/data/
Lukas
On 5 September 2011 06:24, Guillermo Polito guillermopol...@gmail.com wrote:
I've
On Sep 4, 2011, at 11:54 PM, Alain Plantec wrote:
On 04/09/2011 22:26, Stéphane Ducasse wrote:
Alain
it means that we should define shoutAboutToStyle: to certain places like
inspector pane.
Isn't?
:)
arrggh, I've tried and it exhibits a problem. see the end of the answer.
yes, you
47 matches
Mail list logo
