Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[Kasper Osterbye]

stepharo wrote
> I was just thinking about an experiment to map our world into a kind of 
> file system and use it to navigate
> because in your link you want to refer to the class/method
> and in fact it could be package/class/method package/resource or 
> package/class/resources (that we may have one day)

He he - yes, I have had all kinds of thoughts in that direction. But at the
moment it is most likely not where I will look. 

If anything - I would rather take a look on how one can use pillar-markup
inside method comments, and try to see if one can find a way to make the
interaction work. It should somehow be possible to hack into the syntax
highlighter to do this, but I am not sure. 

Right now, I will try to consolidate what I did. But Damien suggested I just
hold back until the Tx work is further progressed.




--
View this message in context: 
http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp4819726p4819827.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[stepharo]

I was just thinking about an experiment to map our world into a kind of 
file system and use it to navigate

because in your link you want to refer to the class/method
and in fact it could be package/class/method package/resource or 
package/class/resources (that we may have one day)



but this was just an idea

Le 15/4/15 21:42, Kasper Osterbye a écrit :

stepharo wrote

an idea: what about a version of FileSystem that can be used to navigate
classes?

I assume there is some tooling you would like to re-use?

If that is the case, I would think it would be more useful to look into what
might be the right common abstraction between filesystem and class/method
hierarchy - but it is hard to say without knowing the problem you were
thinking of (and was it related to the text-renderer in some way I did not
see?)

-- Kasper



--
View this message in context: 
http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp4819726p4819771.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

[Pharo-dev] two things I would like to know how to do in Spotter

[stepharo]

How can I find a directly package and not a class?

How can I scope search?

When I try to read the help via spotter I get an inspector?

After I found the help browser and the global shortcut.
may be it would be good that help found via spotter open it
and that there is a menu inside the wheel to get it.

Stef

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[Kasper Osterbye]

In short, no, it is not live, you switch between the two modes.

I’ll look at the link you sendt me later.

Best,

Kasper

On 16 apr., 2015, at 07:56 , Tudor Girba-2 [via Smalltalk] 
mailto:ml-node+s1294792n4819813...@n4.nabble.com>>
 wrote:

Is the highlighting happening live?

Could you please look at what already exists in the inspector integration. 
There you already have syntax highlighting as you type. I think it would be 
more useful to consolidate the live highlighting around Rubric than to invest 
in TextMorph:
http://www.humane-assessment.com/blog/writing-pillar-books-with-the-gtinspector

This road would be even better if we would get a better parser (in my view 
based on PetitParser) for Pillar.

Cheers,
Doru



On Wed, Apr 15, 2015 at 9:42 PM, Kasper Osterbye <[hidden 
email]> wrote:
stepharo wrote
> an idea: what about a version of FileSystem that can be used to navigate
> classes?

I assume there is some tooling you would like to re-use?

If that is the case, I would think it would be more useful to look into what
might be the right common abstraction between filesystem and class/method
hierarchy - but it is hard to say without knowing the problem you were
thinking of (and was it related to the text-renderer in some way I did not
see?)

-- Kasper



--
View this message in context: 
http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp4819726p4819771.html
Sent from the Pharo Smalltalk Developers mailing list archive at 
Nabble.com.




--
www.tudorgirba.com

"Every thing has its own flow"



If you reply to this email, your message will be added to the discussion below:
http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp4819726p4819813.html
To unsubscribe from Class comments rendered in Nautilus (through Pillar), click 
here.
NAML





--
View this message in context: 
http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp4819726p4819815.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[Tudor Girba]

Is the highlighting happening live?

Could you please look at what already exists in the inspector integration.
There you already have syntax highlighting as you type. I think it would be
more useful to consolidate the live highlighting around Rubric than to
invest in TextMorph:
http://www.humane-assessment.com/blog/writing-pillar-books-with-the-gtinspector

This road would be even better if we would get a better parser (in my view
based on PetitParser) for Pillar.

Cheers,
Doru



On Wed, Apr 15, 2015 at 9:42 PM, Kasper Osterbye  wrote:

> stepharo wrote
> > an idea: what about a version of FileSystem that can be used to navigate
> > classes?
>
> I assume there is some tooling you would like to re-use?
>
> If that is the case, I would think it would be more useful to look into
> what
> might be the right common abstraction between filesystem and class/method
> hierarchy - but it is hard to say without knowing the problem you were
> thinking of (and was it related to the text-renderer in some way I did not
> see?)
>
> -- Kasper
>
>
>
> --
> View this message in context:
> http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp4819726p4819771.html
> Sent from the Pharo Smalltalk Developers mailing list archive at
> Nabble.com.
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] PetitMarkdown

[Christophe Demarey]

Le 14 avr. 2015 à 22:51, p...@highoctane.be a écrit :

> I hate the figures not going where I want due to the LaTeX generation in 
> Pillar.

There should be options to place it where you want. Maybe a pillar expert could 
answer?

> As for class comments, markdown would make more sense to use when putting 
> files under source control on git and then stored in github because filetree 
> generates README.md files for such comments.
> 
> It makes for a nice reading there. In that respect, Pillar class comments 
> will be more of a nuisance than a help.

I don't agree. We can use pillar inside the image AND we can also generate a 
README.md file from pillar doc when useful.

> For generating web documentation, it is easier to provide markdown so that 
> any web framework will be able to conver (e;g; Showdown.js and 2 lines of 
> code).

We already have a pillar to MD converter.

We will have to deal with MD time to time but you do not necessarily have to 
adopt it. You just need to have a good way to interact with it.

smime.p7s
Description: S/MIME cryptographic signature

Re: [Pharo-dev] How to find versions of core packages?

[Dmitri Zagidulin]

Got it, thanks!

On Wed, Apr 15, 2015 at 3:23 PM, stepharo  wrote:

> In fact this is Sunit 3.0 or Sunit3.2
> I do not think that we will have the energy to get Sunit 40. The delta is
> not worth the pain.
>
> Stef
>
> Le 15/4/15 18:24, Dmitri Zagidulin a écrit :
>
>  How does one go about finding the version numbers of core libraries like
>> SUnit that are included in a particular Pharo distribution?
>>
>> (What prompted me to try and find out is that at the start of the SUnit
>> chapter in UPBE, it says "In the future, Pharo may include version of
>> SUnit4.0." And I was curious whether Pharo 4.0 includes that newer version
>> of SUnit, etc. But I'm also curious whether there's a general procedure or
>> convention for finding versions of external libraries that are also pulled
>> into Pharo core.)
>>
>
>
>

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[Kasper Osterbye]

stepharo wrote
> an idea: what about a version of FileSystem that can be used to navigate 
> classes?

I assume there is some tooling you would like to re-use?

If that is the case, I would think it would be more useful to look into what
might be the right common abstraction between filesystem and class/method
hierarchy - but it is hard to say without knowing the problem you were
thinking of (and was it related to the text-renderer in some way I did not
see?)

-- Kasper



--
View this message in context: 
http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp4819726p4819771.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[stepharo]

Kasper

an idea: what about a version of FileSystem that can be used to navigate 
classes?

Thanks for the renderer and yes these classes suck
Stef

Le 15/4/15 18:27, KasperOsterbye a écrit :

Thanks Damien for putting this on the mailing list.

A few words about the state of that Pillar-TextRenderer.

The TextRenderer accepts at least the commands shown by the screenshot noted
by Damien. In addition I would like to point to a special link type I added:
*LinkText>pharo://Classname[/methodname]* which will render a link which
when clicked will open a new Nautilus browser on said class and method.
(I think that link syntax migh actually be useful in both the HTML and Latex
Pillar exporters as well, perhaps just extracting the source and inserting
it inline in the produced document. - but perhaps that is already done using
some other feature I overlooked).

I am rather overwhelmed by the PluggableTextView and other TextMorphs, so
please understand that the supplied functionality is most likely not the
right way to do this, but it seems to work.

And Kilon, you are more than welcome to contact me and introduce me to this
project of yours. As new to the morphic system I can tell you that
documentation is really needed here.

-- Kasper



--
View this message in context: 
http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp4819726p4819735.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] How to find versions of core packages?

[Peter Uhnák]

There are many packages in Pharo (e.g. Spec) that don't have any explicit
version outside of the commit number - because it's integrated nobody is
bothered with release management (this is not a good thing but it is less
work). My guess is that SUnit is in the same state.

On Wed, Apr 15, 2015 at 9:09 PM, Dmitri Zagidulin 
wrote:

> That was my first thought, too. But I couldn't find ConfigurationOfSUnit
> (by any spelling) anywhere. (Not in the base image, not in the
> configuration browser). And I couldn't find it in the main Pharo repo.
>
> There's this: http://smalltalkhub.com/#!/~SUnit/SUnit but the description
> for it says 'This project is hosting the old squeaksource SUnit project.'
> so I wasn't sure if that's the repo that is used for Pharo core.
>
> On Wed, Apr 15, 2015 at 2:46 PM, kilon alios 
> wrote:
>
>> You could take a look at the available configuration, there are usually
>> version methods in the instance side  like for example
>>
>> version10: spec
>> 
>>
>> On Wed, Apr 15, 2015 at 7:24 PM, Dmitri Zagidulin 
>> wrote:
>>
>>> How does one go about finding the version numbers of core libraries like
>>> SUnit that are included in a particular Pharo distribution?
>>>
>>> (What prompted me to try and find out is that at the start of the SUnit
>>> chapter in UPBE, it says "In the future, Pharo may include version of
>>> SUnit4.0." And I was curious whether Pharo 4.0 includes that newer version
>>> of SUnit, etc. But I'm also curious whether there's a general procedure or
>>> convention for finding versions of external libraries that are also pulled
>>> into Pharo core.)
>>>
>>
>>
>

Re: [Pharo-dev] How to find versions of core packages?

[stepharo]

In fact this is Sunit 3.0 or Sunit3.2
I do not think that we will have the energy to get Sunit 40. The delta 
is not worth the pain.


Stef

Le 15/4/15 18:24, Dmitri Zagidulin a écrit :
How does one go about finding the version numbers of core libraries 
like SUnit that are included in a particular Pharo distribution?


(What prompted me to try and find out is that at the start of the 
SUnit chapter in UPBE, it says "In the future, Pharo may include 
version of SUnit4.0." And I was curious whether Pharo 4.0 includes 
that newer version of SUnit, etc. But I'm also curious whether there's 
a general procedure or convention for finding versions of external 
libraries that are also pulled into Pharo core.)

Re: [Pharo-dev] How to find versions of core packages?

[Dmitri Zagidulin]

That was my first thought, too. But I couldn't find ConfigurationOfSUnit
(by any spelling) anywhere. (Not in the base image, not in the
configuration browser). And I couldn't find it in the main Pharo repo.

There's this: http://smalltalkhub.com/#!/~SUnit/SUnit but the description
for it says 'This project is hosting the old squeaksource SUnit project.'
so I wasn't sure if that's the repo that is used for Pharo core.

On Wed, Apr 15, 2015 at 2:46 PM, kilon alios  wrote:

> You could take a look at the available configuration, there are usually
> version methods in the instance side  like for example
>
> version10: spec
> 
>
> On Wed, Apr 15, 2015 at 7:24 PM, Dmitri Zagidulin 
> wrote:
>
>> How does one go about finding the version numbers of core libraries like
>> SUnit that are included in a particular Pharo distribution?
>>
>> (What prompted me to try and find out is that at the start of the SUnit
>> chapter in UPBE, it says "In the future, Pharo may include version of
>> SUnit4.0." And I was curious whether Pharo 4.0 includes that newer version
>> of SUnit, etc. But I'm also curious whether there's a general procedure or
>> convention for finding versions of external libraries that are also pulled
>> into Pharo core.)
>>
>
>

Re: [Pharo-dev] How to find versions of core packages?

[Peter Uhnák]

I don't think it's that easy because you don't know what is loaded...
so the "laborious" way would be to check monticello browser to see what
commit number of a particular package is loaded, and then go through all
configuration methods and see if anything matches.
Maybe there is easier way but I haven't seen any.

Peter

On Wed, Apr 15, 2015 at 8:46 PM, kilon alios  wrote:

> You could take a look at the available configuration, there are usually
> version methods in the instance side  like for example
>
> version10: spec
> 
>
> On Wed, Apr 15, 2015 at 7:24 PM, Dmitri Zagidulin 
> wrote:
>
>> How does one go about finding the version numbers of core libraries like
>> SUnit that are included in a particular Pharo distribution?
>>
>> (What prompted me to try and find out is that at the start of the SUnit
>> chapter in UPBE, it says "In the future, Pharo may include version of
>> SUnit4.0." And I was curious whether Pharo 4.0 includes that newer version
>> of SUnit, etc. But I'm also curious whether there's a general procedure or
>> convention for finding versions of external libraries that are also pulled
>> into Pharo core.)
>>
>
>

Re: [Pharo-dev] How to find versions of core packages?

[kilon alios]

You could take a look at the available configuration, there are usually
version methods in the instance side  like for example

version10: spec


On Wed, Apr 15, 2015 at 7:24 PM, Dmitri Zagidulin 
wrote:

> How does one go about finding the version numbers of core libraries like
> SUnit that are included in a particular Pharo distribution?
>
> (What prompted me to try and find out is that at the start of the SUnit
> chapter in UPBE, it says "In the future, Pharo may include version of
> SUnit4.0." And I was curious whether Pharo 4.0 includes that newer version
> of SUnit, etc. But I'm also curious whether there's a general procedure or
> convention for finding versions of external libraries that are also pulled
> into Pharo core.)
>

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[kilon alios]

ok, but where and which repo ? Smalltalkhub ? GitHub ? Is part of Pillar ?
How I install these packages ?

On Wed, Apr 15, 2015 at 9:15 PM, Kasper Osterbye  wrote:

> kilon.alios wrote
> > So if you can provide me a link to your code, even if your code is far
> > from
> > final it will at least give me a good idea how things work. Suffice to
> see
> > I am very fresh with Morphic myself but I love to learn it, document it
> > and
> > improve it.
>
> The packages are named Pillar-TextRenderer (to be loaded first) and
> Pillar-NautilusProofOfConcept (goes second). The proof of concept overrides
> one method in the nautilus browser, so to go back you need to revert that
> change (versions is your friend here).
>
> The key method in the Pillar-TextRenderer is: PRDecoratedTextWriter
> class>>on: aParsedPillarDoc
>
> -- Kasper
>
>
>
> --
> View this message in context:
> http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp4819726p4819759.html
> Sent from the Pharo Smalltalk Developers mailing list archive at
> Nabble.com.
>
>

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[Kasper Osterbye]

kilon.alios wrote
> So if you can provide me a link to your code, even if your code is far
> from
> final it will at least give me a good idea how things work. Suffice to see
> I am very fresh with Morphic myself but I love to learn it, document it
> and
> improve it.

The packages are named Pillar-TextRenderer (to be loaded first) and
Pillar-NautilusProofOfConcept (goes second). The proof of concept overrides
one method in the nautilus browser, so to go back you need to revert that
change (versions is your friend here).

The key method in the Pillar-TextRenderer is: PRDecoratedTextWriter
class>>on: aParsedPillarDoc

-- Kasper



--
View this message in context: 
http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp4819726p4819759.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] PharoV40 sources still broken?

[Marcus Denker]

609 is good.

> On 15 Apr 2015, at 18:52, Peter Uhnák  wrote:
> 
> So what is the last known "stable" version now? 40605? Or can I use the 
> latest?
> 
> Peter
> 
> On Wed, Apr 15, 2015 at 4:06 PM, Torsten Bergmann  > wrote:
> >This should fix it:
> > Smalltalk allClasses do: [ :each | each class organization comment: nil; 
> > commentStamp: nil ]
> 
> Yes - can confirm the error and can also confirm this statement fixes it.
> 
> Thx
> T.
> 
> 

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[Peter Uhnák]

You might also consider Rubric instead of raw Morphic.

Peter

On Wed, Apr 15, 2015 at 6:58 PM, Sean P. DeNigris 
wrote:

> Kasper Osterbye wrote
> > I am rather overwhelmed by the PluggableTextView and other TextMorphs
>
> Welcome to the club! The only members are brave souls who dare to fight
> with
> the current editor mess before Tx brings us (hopefully soon) a beautiful
> design.
>
>
>
> -
> Cheers,
> Sean
> --
> View this message in context:
> http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp4819726p4819744.html
> Sent from the Pharo Smalltalk Developers mailing list archive at
> Nabble.com.
>
>

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[Sean P. DeNigris]

Kasper Osterbye wrote
> I am rather overwhelmed by the PluggableTextView and other TextMorphs

Welcome to the club! The only members are brave souls who dare to fight with
the current editor mess before Tx brings us (hopefully soon) a beautiful
design.



-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp4819726p4819744.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] PharoV40 sources still broken?

[kilon alios]

I would not call it unstable, I downloaded the file as Esteban pointed
(thank you ) and it works fine for me.

On Wed, Apr 15, 2015 at 7:52 PM, Peter Uhnák  wrote:

> So what is the last known "stable" version now? 40605? Or can I use the
> latest?
>
> Peter
>
> On Wed, Apr 15, 2015 at 4:06 PM, Torsten Bergmann  wrote:
>
>> >This should fix it:
>> > Smalltalk allClasses do: [ :each | each class organization comment:
>> nil; commentStamp: nil ]
>>
>> Yes - can confirm the error and can also confirm this statement fixes it.
>>
>> Thx
>> T.
>>
>>
>

Re: [Pharo-dev] Ubuntu ppa - How is it made?

[Sean P. DeNigris]

Markus Fritsche-4 wrote
> the scripts I am using

Thanks! I will have a look...



-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/Ubuntu-ppa-How-is-it-made-tp4819663p4819741.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[kilon alios]

Just pop open the Configuration Browser and choose to install MorphicDoc. I
am now trying to understand how layout policies for morphs works which is
what I will be documenting next.

Your link feature is also very important for me because I am taking
advantage of the examples methods of Nautilus to provide an easy way for
people to run examples based on documentation , having a link makes my life
even easier.

Together with MorphicDoc its my desire to develop a secondary project I
have talked about in the past but did not have the confidence to pursue,
called "Prometheas". I was thinking 2 things for the near future a) Better
Pillar support for help tool (it already support very basic pillar)  ,
already your work makes my life a lot easier b) better integration with
GTSpotter for help tool.

So if you can provide me a link to your code, even if your code is far from
final it will at least give me a good idea how things work. Suffice to see
I am very fresh with Morphic myself but I love to learn it, document it and
improve it.

On Wed, Apr 15, 2015 at 7:27 PM, KasperOsterbye  wrote:

> Thanks Damien for putting this on the mailing list.
>
> A few words about the state of that Pillar-TextRenderer.
>
> The TextRenderer accepts at least the commands shown by the screenshot
> noted
> by Damien. In addition I would like to point to a special link type I
> added:
> *LinkText>pharo://Classname[/methodname]* which will render a link which
> when clicked will open a new Nautilus browser on said class and method.
> (I think that link syntax migh actually be useful in both the HTML and
> Latex
> Pillar exporters as well, perhaps just extracting the source and inserting
> it inline in the produced document. - but perhaps that is already done
> using
> some other feature I overlooked).
>
> I am rather overwhelmed by the PluggableTextView and other TextMorphs, so
> please understand that the supplied functionality is most likely not the
> right way to do this, but it seems to work.
>
> And Kilon, you are more than welcome to contact me and introduce me to this
> project of yours. As new to the morphic system I can tell you that
> documentation is really needed here.
>
> -- Kasper
>
>
>
> --
> View this message in context:
> http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp4819726p4819735.html
> Sent from the Pharo Smalltalk Developers mailing list archive at
> Nabble.com.
>
>

Re: [Pharo-dev] Ubuntu ppa - How is it made?

[Markus Fritsche]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello Sean,

Damien Cassou originally created the scripts I am using. There are a few
manual steps involved that can be IMO automated.

Look at
https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-vm-core-i386
https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-launcher
https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-vm

Best regards,
  Markus

On 15.04.2015 17:15, Sean P. DeNigris wrote:
> NorbertHartl wrote
>> Taking this it is just a matter of putting the right dependencies in the
>> package file.
>
> Is our process documented somewhere? Could it be automated e.g. by our CI?
>
>
>
> -
> Cheers,
> Sean
> --
> View this message in context:
http://forum.world.st/Ubuntu-ppa-How-is-it-made-tp4819663p4819712.html
> Sent from the Pharo Smalltalk Developers mailing list archive at
Nabble.com.
>

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQFcBAEBAgAGBQJVLpp3AAoJEDhtnsHwg7Ep+dUJ/jJHQkBvcSGA0TkfypuuCaDc
iQmFMkq1NfxTGejFr0jQPAZVeX5igIC5gX0Rfqf8v4iAPmynzClAX/bPmasI9Jwv
jWhjNfmGNK+/KDuvW2n5Hj1VSFweW65BUxmBAX4QpleSMuouV1v7q2Gugv1tD3tY
aYElIjElWtF+cZ89jD0JblFZpiZ5OZ+EIsv5MVnI1URDni22sQfEJBuL7XtjH9gN
pZNcUPEi2pzTaNXwHR+jQNjQtnyENausldgI29RlKRo1c2aC2bUnmRQpkpdVXNGw
jvAtb4QVK85fX50TgY8jx6tVi7mECNFvdd0fVbKBuyVsamp6zLZ077vmiapiN1ML
3VhGd9P+s2zpxqqDww6PObcY4dS7dzA32luz/Nrzmq8WTq/yMXXeHckoLYhF0ROz
OdYRGUwSCTvuTlXd6r2M
=L69q
-END PGP SIGNATURE-

Re: [Pharo-dev] PharoV40 sources still broken?

[Peter Uhnák]

So what is the last known "stable" version now? 40605? Or can I use the
latest?

Peter

On Wed, Apr 15, 2015 at 4:06 PM, Torsten Bergmann  wrote:

> >This should fix it:
> > Smalltalk allClasses do: [ :each | each class organization comment: nil;
> commentStamp: nil ]
>
> Yes - can confirm the error and can also confirm this statement fixes it.
>
> Thx
> T.
>
>

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[KasperOsterbye]

Thanks Damien for putting this on the mailing list.

A few words about the state of that Pillar-TextRenderer.

The TextRenderer accepts at least the commands shown by the screenshot noted
by Damien. In addition I would like to point to a special link type I added:
*LinkText>pharo://Classname[/methodname]* which will render a link which
when clicked will open a new Nautilus browser on said class and method.
(I think that link syntax migh actually be useful in both the HTML and Latex
Pillar exporters as well, perhaps just extracting the source and inserting
it inline in the produced document. - but perhaps that is already done using
some other feature I overlooked).

I am rather overwhelmed by the PluggableTextView and other TextMorphs, so
please understand that the supplied functionality is most likely not the
right way to do this, but it seems to work.

And Kilon, you are more than welcome to contact me and introduce me to this
project of yours. As new to the morphic system I can tell you that
documentation is really needed here.

-- Kasper



--
View this message in context: 
http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp4819726p4819735.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

[Pharo-dev] How to find versions of core packages?

[Dmitri Zagidulin]

How does one go about finding the version numbers of core libraries like
SUnit that are included in a particular Pharo distribution?

(What prompted me to try and find out is that at the start of the SUnit
chapter in UPBE, it says "In the future, Pharo may include version of
SUnit4.0." And I was curious whether Pharo 4.0 includes that newer version
of SUnit, etc. But I'm also curious whether there's a general procedure or
convention for finding versions of external libraries that are also pulled
into Pharo core.)

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[kilon alios]

You want it for class comment , I want it for the Help Browser tool for the
Morphic documentation project I am doing . This could not come at a better
time, cant wait to look at the code, Thank you very much :)

On Wed, Apr 15, 2015 at 6:52 PM, Damien Cassou 
wrote:

> Hi,
>
> Kasper Østerbye has just finished a proof-of-concept that renders Pillar
> text inside a class comment pane.
>
> From the view, the developer can press $ (dollar) to edit the document in
> Pillar.
>
>
>
> Best regards,
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Success is the ability to go from one failure to another without
> losing enthusiasm." --Winston Churchill
>
>

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[Thierry Goubier]

Cool!

This is the way to go.

Thierry

2015-04-15 17:52 GMT+02:00 Damien Cassou :

> Hi,
>
> Kasper Østerbye has just finished a proof-of-concept that renders Pillar
> text inside a class comment pane.
>
> From the view, the developer can press $ (dollar) to edit the document in
> Pillar.
>
>
>
> Best regards,
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Success is the ability to go from one failure to another without
> losing enthusiasm." --Winston Churchill
>
>

[Pharo-dev] Class comments rendered in Nautilus (through Pillar)

[Damien Cassou]

Hi,

Kasper Østerbye has just finished a proof-of-concept that renders Pillar
text inside a class comment pane.

>From the view, the developer can press $ (dollar) to edit the document in 
>Pillar.


Best regards,

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

Re: [Pharo-dev] Ubuntu ppa - How is it made?

[Sean P. DeNigris]

NorbertHartl wrote
> Taking this it is just a matter of putting the right dependencies in the
> package file.

Is our process documented somewhere? Could it be automated e.g. by our CI?



-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/Ubuntu-ppa-How-is-it-made-tp4819663p4819712.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/40609
  Home:   https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 816d3d: 40609

[GitHub]

  Branch: refs/heads/4.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 816d3d78f5d8c1c06e95d885f5f48316922492ba
  
https://github.com/pharo-project/pharo-core/commit/816d3d78f5d8c1c06e95d885f5f48316922492ba
  Author: Jenkins Build Server 
  Date:   2015-04-15 (Wed, 15 Apr 2015)

  Changed paths:
R ScriptLoader40.package/ScriptLoader.class/instance/pharo - 
scripts/script608.st
A ScriptLoader40.package/ScriptLoader.class/instance/pharo - 
scripts/script609.st
R ScriptLoader40.package/ScriptLoader.class/instance/pharo - 
updates/update40608.st
A ScriptLoader40.package/ScriptLoader.class/instance/pharo - 
updates/update40609.st
M 
ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
M 
Settings-System.package/SystemSystemSettings.class/class/settings/systemSettingOn_.st
R 
System-Support.package/SmalltalkImage.class/class/settings/shouldDownloadSourcesFile.st
R 
System-Support.package/SmalltalkImage.class/class/settings/shouldDownloadSourcesFile_.st
M System-Support.package/SmalltalkImage.class/definition.st
R 
System-Support.package/SmalltalkImage.class/instance/settings/shouldDownloadSourcesFile.st

  Log Message:
  ---
  40609
15341 remove download sources setting
https://pharo.fogbugz.com/f/cases/15341

15342 Metaclasses should not have a source pointer
https://pharo.fogbugz.com/f/cases/15342

http://files.pharo.org/image/40/40609.zip

Re: [Pharo-dev] PharoV40 sources still broken?

[Torsten Bergmann]

>This should fix it:
> Smalltalk allClasses do: [ :each | each class organization comment: nil; 
>commentStamp: nil ]

Yes - can confirm the error and can also confirm this statement fixes it.

Thx
T.

Re: [Pharo-dev] PharoV40 sources still broken?

[Marcus Denker]

This should fix it:

Smalltalk allClasses do: [ :each | each class organization comment: nil;
commentStamp: nil ]

On Wed, Apr 15, 2015 at 2:53 PM, Esteban Lorenzano 
wrote:

> thankfully, is an easy fix :)
>
> > On 15 Apr 2015, at 14:36, Nicolai Hess  wrote:
> >
> > pharo 4.0 608 with PharoV40 sources:
> >
> > - enter some text in a workspace
> > - select the text
> > - choose "Method source with it"
> >
> > ->
> > RemoteString(Object)>>error:
> > [
> > filePositionHi > theFile size
> > ifTrue: [ self error: 'RemoteString past end of file' ].
> > theFile position: filePositionHi.
> > theFile nextChunk ] in RemoteString>>string in Block: [ ...
> > BlockClosure>>ensure:
> > RemoteString>>string
> > ClassOrganization>>comment
> > ClassOrganization>>classComment
> > [ :each |
> > bar current: (count := count + 1).
> > each
> > selectorsDo: [ :sel |
> > ((each sourceCodeAt: sel) includesSubstring: aString
> caseSensitive: caseSensitive)
> > ifTrue: [ addMethod value: each value: sel ] ].
> > (each organization classComment asString includesSubstring: aString
> caseSensitive: caseSensitive)
> > ifTrue: [ addComment value: each ] ] in [ :bar |
> > | count |
> > count := 0.
> > self
> > allBehaviorsDo: [ :each |
> > bar current: (count := count + 1).
> > each
> > selectorsDo: [ :sel |
> > ((each sourceCodeAt: sel) includesSubstring: aString
> caseSensitive: caseSensitive)
> > ifTrue: [ addMethod value: each value: sel ] ].
> > (each organization classComment asString includesSubstring:
> aString caseSensitive: caseSensitive)
> > ifTrue: [ addComment value: each ] ] ] in
> SystemNavigation>>allMethodsWithSourceString:matchCase: in Block: [ :each |
> ...
> > [ :aClass |
> > aBlock
> > value: aClass;
> > value: aClass class ] in SystemNavigation>>allBehaviorsDo: in Block:
> [ :aClass | ...
> > [ :name | aBlock value: (self at: name) ] in
> SystemDictionary>>allClassesDo: in Block: [ :name | aBlock value: (self at:
> name) ]
> > OrderedCollection>>do:
> > SystemDictionary>>allClassesDo:
> > SystemNavigation>>allBehaviorsDo:
> > [ :bar |
> > | count |
> > count := 0.
> > self
> > allBehaviorsDo: [ :each |
> > bar current: (count := count + 1).
> > each
> > selectorsDo: [ :sel |
> > ((each sourceCodeAt: sel) includesSubstring: aString
> caseSensitive: caseSensitive)
> > ifTrue: [ addMethod value: each value: sel ] ].
> > (each organization classComment asString includesSubstring:
> aString caseSensitive: caseSensitive)
> > ifTrue: [ addComment value: each ] ] ] in
> SystemNavigation>>allMethodsWithSourceString:matchCase: in Block: [ :bar |
> ...
> > BlockClosure>>cull:
> > [ result := block cull: self ] in [
> > self prepareForRunning.
> > [ result := block cull: self ]
> > on: JobNotification
> > do: [ :notification | notification handle: self ] ] in Job>>run in
> Block: [ result := block cull: self ]
> > BlockClosure>>on:do:
> > [
> > self prepareForRunning.
> > [ result := block cull: self ]
> > on: JobNotification
> > do: [ :notification | notification handle: self ] ] in Job>>run in
> Block: [ ...
> > BlockClosure>>ensure:
> > Job>>run
> > MorphicUIManager(UIManager)>>displayProgress:from:to:during:
> > ByteString(String)>>displayProgressFrom:to:during:
> > SystemNavigation>>allMethodsWithSourceString:matchCase:
> > SystemNavigation>>browseMethodsWithSourceString:matchCase:
> > [ :aPresentation |
> > aPresentation selectLine.
> > self systemNavigation browseMethodsWithSourceString: aPresentation
> selectedText matchCase: false ] in
> GLMPharoPlaygroundPresentation(GLMRubricSmalltalkCodePresentation)>>browsingSelectionActions
> in Block: [ :aPresentation | ...
> > BlockClosure>>glamourValueWithArgs:
> > GLMGenericAction(GLMAction)>>actOn:
> > GLMGenericAction(GLMAction)>>morphicActOn:
> > [ :ann | ann action morphicActOn: aPresentation ] in
> GLMMorphicPharoPlaygroundRenderer(GLMMorphicWidgetRenderer)>>installActionsOnModel:fromPresentation:
> in Block: [ :ann | ann action morphicActOn: aPresentation ]
> > BlockClosure>>cull:
> > BlockClosure>>cull:cull:
> >
>
>
>
--
Marcus Denker  --  den...@acm.org
http://www.marcusdenker.de

[Pharo-dev] Pillar: Link to anchor in same document

[Sean P. DeNigris]

I'm updating the Pharo website and want to link to an anchor on the same
page.

And after reading
https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/PillarChap/Pillar.pillar.html
, I tried:
*Ubuntu ppa instructions>ubuntu*
but it linked to http://pharo.org/ubuntu instead of
http://pharo.org/gnu-linux-installation.STAGE#ubuntu

Then I tried:
*Ubuntu ppa instructions>@ubuntu* -> linked back to the same page, but no
anchor was appended
*Ubuntu ppa instructions>#ubuntu* -> worked, but rendered the link text as
"¿?Ubuntu ppa instructions"

How should I handle this? For the time being I'll leave the last version
which works at least...




-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/Pillar-Link-to-anchor-in-same-document-tp4819681.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] PharoV40 sources still broken?

[Esteban Lorenzano]

> On 15 Apr 2015, at 14:52, kilon alios  wrote:
> 
> You dont even need to do all that, just open a new image and immediately 
> complains that sources are missing. But for some strange reason I can browser 
> code , I thought no sources meant not being able to see the source code. 
> Restarting the image saved with the setting to download sources does nothing. 

download sources is probably removed. 
but you can download it by your self :)

wget files.pharo.org/get-files/40/sources.zip 


cheers, 
Esteban

> 
> On Wed, Apr 15, 2015 at 3:36 PM, Nicolai Hess  > wrote:
> pharo 4.0 608 with PharoV40 sources:
> 
> - enter some text in a workspace
> - select the text
> - choose "Method source with it"
> 
> ->  
> RemoteString(Object)>>error:
> [ 
> filePositionHi > theFile size
> ifTrue: [ self error: 'RemoteString past end of file' ].
> theFile position: filePositionHi.
> theFile nextChunk ] in RemoteString>>string in Block: [ ...
> BlockClosure>>ensure:
> RemoteString>>string
> ClassOrganization>>comment
> ClassOrganization>>classComment
> [ :each | 
> bar current: (count := count + 1).
> each
> selectorsDo: [ :sel | 
> ((each sourceCodeAt: sel) includesSubstring: aString caseSensitive: 
> caseSensitive)
> ifTrue: [ addMethod value: each value: sel ] ].
> (each organization classComment asString includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addComment value: each ] ] in [ :bar | 
> | count |
> count := 0.
> self
> allBehaviorsDo: [ :each | 
> bar current: (count := count + 1).
> each
> selectorsDo: [ :sel | 
> ((each sourceCodeAt: sel) includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addMethod value: each value: sel ] ].
> (each organization classComment asString includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addComment value: each ] ] ] in 
> SystemNavigation>>allMethodsWithSourceString:matchCase: in Block: [ :each | 
> ...
> [ :aClass | 
> aBlock
> value: aClass;
> value: aClass class ] in SystemNavigation>>allBehaviorsDo: in Block: [ 
> :aClass | ...
> [ :name | aBlock value: (self at: name) ] in SystemDictionary>>allClassesDo: 
> in Block: [ :name | aBlock value: (self at: name) ]
> OrderedCollection>>do:
> SystemDictionary>>allClassesDo:
> SystemNavigation>>allBehaviorsDo:
> [ :bar | 
> | count |
> count := 0.
> self
> allBehaviorsDo: [ :each | 
> bar current: (count := count + 1).
> each
> selectorsDo: [ :sel | 
> ((each sourceCodeAt: sel) includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addMethod value: each value: sel ] ].
> (each organization classComment asString includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addComment value: each ] ] ] in 
> SystemNavigation>>allMethodsWithSourceString:matchCase: in Block: [ :bar | ...
> BlockClosure>>cull:
> [ result := block cull: self ] in [ 
> self prepareForRunning.
> [ result := block cull: self ]
> on: JobNotification
> do: [ :notification | notification handle: self ] ] in Job>>run in Block: 
> [ result := block cull: self ]
> BlockClosure>>on:do:
> [ 
> self prepareForRunning.
> [ result := block cull: self ]
> on: JobNotification
> do: [ :notification | notification handle: self ] ] in Job>>run in Block: 
> [ ...
> BlockClosure>>ensure:
> Job>>run
> MorphicUIManager(UIManager)>>displayProgress:from:to:during:
> ByteString(String)>>displayProgressFrom:to:during:
> SystemNavigation>>allMethodsWithSourceString:matchCase:
> SystemNavigation>>browseMethodsWithSourceString:matchCase:
> [ :aPresentation | 
> aPresentation selectLine.
> self systemNavigation browseMethodsWithSourceString: aPresentation 
> selectedText matchCase: false ] in 
> GLMPharoPlaygroundPresentation(GLMRubricSmalltalkCodePresentation)>>browsingSelectionActions
>  in Block: [ :aPresentation | ...
> BlockClosure>>glamourValueWithArgs:
> GLMGenericAction(GLMAction)>>actOn:
> GLMGenericAction(GLMAction)>>morphicActOn:
> [ :ann | ann action morphicActOn: aPresentation ] in 
> GLMMorphicPharoPlaygroundRenderer(GLMMorphicWidgetRenderer)>>installActionsOnModel:fromPresentation:
>  in Block: [ :ann | ann action morphicActOn: aPresentation ]
> BlockClosure>>cull:
> BlockClosure>>cull:cull:
> 
> 

Re: [Pharo-dev] PharoV40 sources still broken?

[Esteban Lorenzano]

thankfully, is an easy fix :)

> On 15 Apr 2015, at 14:36, Nicolai Hess  wrote:
> 
> pharo 4.0 608 with PharoV40 sources:
> 
> - enter some text in a workspace
> - select the text
> - choose "Method source with it"
> 
> ->  
> RemoteString(Object)>>error:
> [ 
> filePositionHi > theFile size
> ifTrue: [ self error: 'RemoteString past end of file' ].
> theFile position: filePositionHi.
> theFile nextChunk ] in RemoteString>>string in Block: [ ...
> BlockClosure>>ensure:
> RemoteString>>string
> ClassOrganization>>comment
> ClassOrganization>>classComment
> [ :each | 
> bar current: (count := count + 1).
> each
> selectorsDo: [ :sel | 
> ((each sourceCodeAt: sel) includesSubstring: aString caseSensitive: 
> caseSensitive)
> ifTrue: [ addMethod value: each value: sel ] ].
> (each organization classComment asString includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addComment value: each ] ] in [ :bar | 
> | count |
> count := 0.
> self
> allBehaviorsDo: [ :each | 
> bar current: (count := count + 1).
> each
> selectorsDo: [ :sel | 
> ((each sourceCodeAt: sel) includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addMethod value: each value: sel ] ].
> (each organization classComment asString includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addComment value: each ] ] ] in 
> SystemNavigation>>allMethodsWithSourceString:matchCase: in Block: [ :each | 
> ...
> [ :aClass | 
> aBlock
> value: aClass;
> value: aClass class ] in SystemNavigation>>allBehaviorsDo: in Block: [ 
> :aClass | ...
> [ :name | aBlock value: (self at: name) ] in SystemDictionary>>allClassesDo: 
> in Block: [ :name | aBlock value: (self at: name) ]
> OrderedCollection>>do:
> SystemDictionary>>allClassesDo:
> SystemNavigation>>allBehaviorsDo:
> [ :bar | 
> | count |
> count := 0.
> self
> allBehaviorsDo: [ :each | 
> bar current: (count := count + 1).
> each
> selectorsDo: [ :sel | 
> ((each sourceCodeAt: sel) includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addMethod value: each value: sel ] ].
> (each organization classComment asString includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addComment value: each ] ] ] in 
> SystemNavigation>>allMethodsWithSourceString:matchCase: in Block: [ :bar | ...
> BlockClosure>>cull:
> [ result := block cull: self ] in [ 
> self prepareForRunning.
> [ result := block cull: self ]
> on: JobNotification
> do: [ :notification | notification handle: self ] ] in Job>>run in Block: 
> [ result := block cull: self ]
> BlockClosure>>on:do:
> [ 
> self prepareForRunning.
> [ result := block cull: self ]
> on: JobNotification
> do: [ :notification | notification handle: self ] ] in Job>>run in Block: 
> [ ...
> BlockClosure>>ensure:
> Job>>run
> MorphicUIManager(UIManager)>>displayProgress:from:to:during:
> ByteString(String)>>displayProgressFrom:to:during:
> SystemNavigation>>allMethodsWithSourceString:matchCase:
> SystemNavigation>>browseMethodsWithSourceString:matchCase:
> [ :aPresentation | 
> aPresentation selectLine.
> self systemNavigation browseMethodsWithSourceString: aPresentation 
> selectedText matchCase: false ] in 
> GLMPharoPlaygroundPresentation(GLMRubricSmalltalkCodePresentation)>>browsingSelectionActions
>  in Block: [ :aPresentation | ...
> BlockClosure>>glamourValueWithArgs:
> GLMGenericAction(GLMAction)>>actOn:
> GLMGenericAction(GLMAction)>>morphicActOn:
> [ :ann | ann action morphicActOn: aPresentation ] in 
> GLMMorphicPharoPlaygroundRenderer(GLMMorphicWidgetRenderer)>>installActionsOnModel:fromPresentation:
>  in Block: [ :ann | ann action morphicActOn: aPresentation ]
> BlockClosure>>cull:
> BlockClosure>>cull:cull:
> 

Re: [Pharo-dev] PharoV40 sources still broken?

[kilon alios]

You dont even need to do all that, just open a new image and immediately
complains that sources are missing. But for some strange reason I can
browser code , I thought no sources meant not being able to see the source
code. Restarting the image saved with the setting to download sources does
nothing.

On Wed, Apr 15, 2015 at 3:36 PM, Nicolai Hess  wrote:

> pharo 4.0 608 with PharoV40 sources:
>
> - enter some text in a workspace
> - select the text
> - choose "Method source with it"
>
> ->
> RemoteString(Object)>>error:
> [
> filePositionHi > theFile size
> ifTrue: [ self error: 'RemoteString past end of file' ].
> theFile position: filePositionHi.
> theFile nextChunk ] in RemoteString>>string in Block: [ ...
> BlockClosure>>ensure:
> RemoteString>>string
> ClassOrganization>>comment
> ClassOrganization>>classComment
> [ :each |
> bar current: (count := count + 1).
> each
> selectorsDo: [ :sel |
> ((each sourceCodeAt: sel) includesSubstring: aString
> caseSensitive: caseSensitive)
> ifTrue: [ addMethod value: each value: sel ] ].
> (each organization classComment asString includesSubstring: aString
> caseSensitive: caseSensitive)
> ifTrue: [ addComment value: each ] ] in [ :bar |
> | count |
> count := 0.
> self
> allBehaviorsDo: [ :each |
> bar current: (count := count + 1).
> each
> selectorsDo: [ :sel |
> ((each sourceCodeAt: sel) includesSubstring: aString
> caseSensitive: caseSensitive)
> ifTrue: [ addMethod value: each value: sel ] ].
> (each organization classComment asString includesSubstring:
> aString caseSensitive: caseSensitive)
> ifTrue: [ addComment value: each ] ] ] in
> SystemNavigation>>allMethodsWithSourceString:matchCase: in Block: [ :each |
> ...
> [ :aClass |
> aBlock
> value: aClass;
> value: aClass class ] in SystemNavigation>>allBehaviorsDo: in Block: [
> :aClass | ...
> [ :name | aBlock value: (self at: name) ] in
> SystemDictionary>>allClassesDo: in Block: [ :name | aBlock value: (self at:
> name) ]
> OrderedCollection>>do:
> SystemDictionary>>allClassesDo:
> SystemNavigation>>allBehaviorsDo:
> [ :bar |
> | count |
> count := 0.
> self
> allBehaviorsDo: [ :each |
> bar current: (count := count + 1).
> each
> selectorsDo: [ :sel |
> ((each sourceCodeAt: sel) includesSubstring: aString
> caseSensitive: caseSensitive)
> ifTrue: [ addMethod value: each value: sel ] ].
> (each organization classComment asString includesSubstring:
> aString caseSensitive: caseSensitive)
> ifTrue: [ addComment value: each ] ] ] in
> SystemNavigation>>allMethodsWithSourceString:matchCase: in Block: [ :bar |
> ...
> BlockClosure>>cull:
> [ result := block cull: self ] in [
> self prepareForRunning.
> [ result := block cull: self ]
> on: JobNotification
> do: [ :notification | notification handle: self ] ] in Job>>run in
> Block: [ result := block cull: self ]
> BlockClosure>>on:do:
> [
> self prepareForRunning.
> [ result := block cull: self ]
> on: JobNotification
> do: [ :notification | notification handle: self ] ] in Job>>run in
> Block: [ ...
> BlockClosure>>ensure:
> Job>>run
> MorphicUIManager(UIManager)>>displayProgress:from:to:during:
> ByteString(String)>>displayProgressFrom:to:during:
> SystemNavigation>>allMethodsWithSourceString:matchCase:
> SystemNavigation>>browseMethodsWithSourceString:matchCase:
> [ :aPresentation |
> aPresentation selectLine.
> self systemNavigation browseMethodsWithSourceString: aPresentation
> selectedText matchCase: false ] in
> GLMPharoPlaygroundPresentation(GLMRubricSmalltalkCodePresentation)>>browsingSelectionActions
> in Block: [ :aPresentation | ...
> BlockClosure>>glamourValueWithArgs:
> GLMGenericAction(GLMAction)>>actOn:
> GLMGenericAction(GLMAction)>>morphicActOn:
> [ :ann | ann action morphicActOn: aPresentation ] in
> GLMMorphicPharoPlaygroundRenderer(GLMMorphicWidgetRenderer)>>installActionsOnModel:fromPresentation:
> in Block: [ :ann | ann action morphicActOn: aPresentation ]
> BlockClosure>>cull:
> BlockClosure>>cull:cull:
>
>

Re: [Pharo-dev] PharoV40 sources still broken?

[Sven Van Caekenberghe]

> On 15 Apr 2015, at 14:45, Sven Van Caekenberghe  wrote:
> 
> Yes, I can confirm your issue.
> 
> But using World Menu > Tools > Finder to search in Source does work well.

Probably because the Finder does not search in class comments, only in method 
sources.

Maybe we need a unit test to check the validity of all class comments ?

>> On 15 Apr 2015, at 14:36, Nicolai Hess  wrote:
>> 
>> pharo 4.0 608 with PharoV40 sources:
>> 
>> - enter some text in a workspace
>> - select the text
>> - choose "Method source with it"
>> 
>> ->  
>> RemoteString(Object)>>error:
>> [ 
>> filePositionHi > theFile size
>>ifTrue: [ self error: 'RemoteString past end of file' ].
>> theFile position: filePositionHi.
>> theFile nextChunk ] in RemoteString>>string in Block: [ ...
>> BlockClosure>>ensure:
>> RemoteString>>string
>> ClassOrganization>>comment
>> ClassOrganization>>classComment
>> [ :each | 
>> bar current: (count := count + 1).
>> each
>>selectorsDo: [ :sel | 
>>((each sourceCodeAt: sel) includesSubstring: aString caseSensitive: 
>> caseSensitive)
>>ifTrue: [ addMethod value: each value: sel ] ].
>> (each organization classComment asString includesSubstring: aString 
>> caseSensitive: caseSensitive)
>>ifTrue: [ addComment value: each ] ] in [ :bar | 
>> | count |
>> count := 0.
>> self
>>allBehaviorsDo: [ :each | 
>>bar current: (count := count + 1).
>>each
>>selectorsDo: [ :sel | 
>>((each sourceCodeAt: sel) includesSubstring: aString 
>> caseSensitive: caseSensitive)
>>ifTrue: [ addMethod value: each value: sel ] ].
>>(each organization classComment asString includesSubstring: aString 
>> caseSensitive: caseSensitive)
>>ifTrue: [ addComment value: each ] ] ] in 
>> SystemNavigation>>allMethodsWithSourceString:matchCase: in Block: [ :each | 
>> ...
>> [ :aClass | 
>> aBlock
>>value: aClass;
>>value: aClass class ] in SystemNavigation>>allBehaviorsDo: in Block: [ 
>> :aClass | ...
>> [ :name | aBlock value: (self at: name) ] in SystemDictionary>>allClassesDo: 
>> in Block: [ :name | aBlock value: (self at: name) ]
>> OrderedCollection>>do:
>> SystemDictionary>>allClassesDo:
>> SystemNavigation>>allBehaviorsDo:
>> [ :bar | 
>> | count |
>> count := 0.
>> self
>>allBehaviorsDo: [ :each | 
>>bar current: (count := count + 1).
>>each
>>selectorsDo: [ :sel | 
>>((each sourceCodeAt: sel) includesSubstring: aString 
>> caseSensitive: caseSensitive)
>>ifTrue: [ addMethod value: each value: sel ] ].
>>(each organization classComment asString includesSubstring: aString 
>> caseSensitive: caseSensitive)
>>ifTrue: [ addComment value: each ] ] ] in 
>> SystemNavigation>>allMethodsWithSourceString:matchCase: in Block: [ :bar | 
>> ...
>> BlockClosure>>cull:
>> [ result := block cull: self ] in [ 
>> self prepareForRunning.
>> [ result := block cull: self ]
>>on: JobNotification
>>do: [ :notification | notification handle: self ] ] in Job>>run in Block: 
>> [ result := block cull: self ]
>> BlockClosure>>on:do:
>> [ 
>> self prepareForRunning.
>> [ result := block cull: self ]
>>on: JobNotification
>>do: [ :notification | notification handle: self ] ] in Job>>run in Block: 
>> [ ...
>> BlockClosure>>ensure:
>> Job>>run
>> MorphicUIManager(UIManager)>>displayProgress:from:to:during:
>> ByteString(String)>>displayProgressFrom:to:during:
>> SystemNavigation>>allMethodsWithSourceString:matchCase:
>> SystemNavigation>>browseMethodsWithSourceString:matchCase:
>> [ :aPresentation | 
>> aPresentation selectLine.
>> self systemNavigation browseMethodsWithSourceString: aPresentation 
>> selectedText matchCase: false ] in 
>> GLMPharoPlaygroundPresentation(GLMRubricSmalltalkCodePresentation)>>browsingSelectionActions
>>  in Block: [ :aPresentation | ...
>> BlockClosure>>glamourValueWithArgs:
>> GLMGenericAction(GLMAction)>>actOn:
>> GLMGenericAction(GLMAction)>>morphicActOn:
>> [ :ann | ann action morphicActOn: aPresentation ] in 
>> GLMMorphicPharoPlaygroundRenderer(GLMMorphicWidgetRenderer)>>installActionsOnModel:fromPresentation:
>>  in Block: [ :ann | ann action morphicActOn: aPresentation ]
>> BlockClosure>>cull:
>> BlockClosure>>cull:cull:
>> 
> 

Re: [Pharo-dev] PharoV40 sources still broken?

[Sven Van Caekenberghe]

Yes, I can confirm your issue.

But using World Menu > Tools > Finder to search in Source does work well.

> On 15 Apr 2015, at 14:36, Nicolai Hess  wrote:
> 
> pharo 4.0 608 with PharoV40 sources:
> 
> - enter some text in a workspace
> - select the text
> - choose "Method source with it"
> 
> ->  
> RemoteString(Object)>>error:
> [ 
> filePositionHi > theFile size
> ifTrue: [ self error: 'RemoteString past end of file' ].
> theFile position: filePositionHi.
> theFile nextChunk ] in RemoteString>>string in Block: [ ...
> BlockClosure>>ensure:
> RemoteString>>string
> ClassOrganization>>comment
> ClassOrganization>>classComment
> [ :each | 
> bar current: (count := count + 1).
> each
> selectorsDo: [ :sel | 
> ((each sourceCodeAt: sel) includesSubstring: aString caseSensitive: 
> caseSensitive)
> ifTrue: [ addMethod value: each value: sel ] ].
> (each organization classComment asString includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addComment value: each ] ] in [ :bar | 
> | count |
> count := 0.
> self
> allBehaviorsDo: [ :each | 
> bar current: (count := count + 1).
> each
> selectorsDo: [ :sel | 
> ((each sourceCodeAt: sel) includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addMethod value: each value: sel ] ].
> (each organization classComment asString includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addComment value: each ] ] ] in 
> SystemNavigation>>allMethodsWithSourceString:matchCase: in Block: [ :each | 
> ...
> [ :aClass | 
> aBlock
> value: aClass;
> value: aClass class ] in SystemNavigation>>allBehaviorsDo: in Block: [ 
> :aClass | ...
> [ :name | aBlock value: (self at: name) ] in SystemDictionary>>allClassesDo: 
> in Block: [ :name | aBlock value: (self at: name) ]
> OrderedCollection>>do:
> SystemDictionary>>allClassesDo:
> SystemNavigation>>allBehaviorsDo:
> [ :bar | 
> | count |
> count := 0.
> self
> allBehaviorsDo: [ :each | 
> bar current: (count := count + 1).
> each
> selectorsDo: [ :sel | 
> ((each sourceCodeAt: sel) includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addMethod value: each value: sel ] ].
> (each organization classComment asString includesSubstring: aString 
> caseSensitive: caseSensitive)
> ifTrue: [ addComment value: each ] ] ] in 
> SystemNavigation>>allMethodsWithSourceString:matchCase: in Block: [ :bar | ...
> BlockClosure>>cull:
> [ result := block cull: self ] in [ 
> self prepareForRunning.
> [ result := block cull: self ]
> on: JobNotification
> do: [ :notification | notification handle: self ] ] in Job>>run in Block: 
> [ result := block cull: self ]
> BlockClosure>>on:do:
> [ 
> self prepareForRunning.
> [ result := block cull: self ]
> on: JobNotification
> do: [ :notification | notification handle: self ] ] in Job>>run in Block: 
> [ ...
> BlockClosure>>ensure:
> Job>>run
> MorphicUIManager(UIManager)>>displayProgress:from:to:during:
> ByteString(String)>>displayProgressFrom:to:during:
> SystemNavigation>>allMethodsWithSourceString:matchCase:
> SystemNavigation>>browseMethodsWithSourceString:matchCase:
> [ :aPresentation | 
> aPresentation selectLine.
> self systemNavigation browseMethodsWithSourceString: aPresentation 
> selectedText matchCase: false ] in 
> GLMPharoPlaygroundPresentation(GLMRubricSmalltalkCodePresentation)>>browsingSelectionActions
>  in Block: [ :aPresentation | ...
> BlockClosure>>glamourValueWithArgs:
> GLMGenericAction(GLMAction)>>actOn:
> GLMGenericAction(GLMAction)>>morphicActOn:
> [ :ann | ann action morphicActOn: aPresentation ] in 
> GLMMorphicPharoPlaygroundRenderer(GLMMorphicWidgetRenderer)>>installActionsOnModel:fromPresentation:
>  in Block: [ :ann | ann action morphicActOn: aPresentation ]
> BlockClosure>>cull:
> BlockClosure>>cull:cull:
> 

Re: [Pharo-dev] Can Monticello version message be a Text?

[Thierry Goubier]

2015-04-15 14:06 GMT+02:00 Yuriy Tymchuk :

> Can this be because my git name is different from monticello name?
>

No ;)

Is it still happening to you? I fixed a bug I could see with a case
submitted by Johan; it may not have fixed yours.

Thierry


>
> Uko
>
> > On 09 Apr 2015, at 23:40, Thierry Goubier 
> wrote:
> >
> > Le 09/04/2015 23:34, Yuriy Tymchuk a écrit :
> >> Sad. It happens to me quite a lot. So is this an issue in monticello?
> >
> > I don't know.
> >
> > Something is happening somewhere with the source code, and as a
> consequence Monticello test for finding the changes mark everything as
> changed.
> >
> > I'm pushing a solution for that symptom.
> >
> > https://pharo.fogbugz.com/default.asp?15321
> >
> > But I haven't found the reason. Something is switching the line endings
> on some of the MC definitions, and I don't know who or what is doing that
> (and not everytime).
> >
> > Thierry
> >
> >>
> >>
> >>
> >>> On 08 Apr 2015, at 22:13, Thierry Goubier 
> wrote:
> >>>
> >>> Uko,
> >>>
> >>> you seem to have the same bug Johan is describing.
> >>>
> >>> MC seems to loose the contents of a package working copy, and hence is
> unable to build a correct diff.
> >>>
> >>> I've seen it happen at times, but rarely enough so I didn't pay
> attention to it.
> >>>
> >>> Thierry
> >>>
> >>> Le 08/04/2015 09:44, Yuriy Tymchuk a écrit :
> 
> > On 07 Apr 2015, at 12:16, Thierry Goubier 
> wrote:
> >
> > Le 07/04/2015 11:01, Yuriy Tymchuk a écrit :
> >> Hi, thank you very much for investigating this.
> >
> > You're working on it too :)
> >
> >> These are the steps to reproduce:
> >>
> >> 1. Clone a git repo (e.g. https://github.com/Uko/VnaExporter.git)
> >> 2. Add it as gitfiletree repo to the pharo image.
> >> 3. Change something, commit part of the changes with Komitter.
> >> 4. Change something more.
> >> 5. Open Komitter, you should see a strange diff.
> >> 6. Select 1 or 2 methods & commit them.
> >> 7. Now you should have only 2 methods in your repo.
> >
> > I did, and I don't see anything suspicious. Browsing the repository
> at each step gave me the complete package as expected (minus the unsaved
> changes, of course).
> >
> > Can you show a screenshot at step 5?
> 
>  I've done a screen recording
> https://dl.dropboxusercontent.com/u/83145561/GitKomitter.mov
> 
>  Uko
> 
> >
> > Thierry
> >
> 
> 
> 
> >>>
> >>>
> >>
> >>
> >>
> >>
> >
> >
>
>
>

[Pharo-dev] PharoV40 sources still broken?

[Nicolai Hess]

pharo 4.0 608 with PharoV40 sources:

- enter some text in a workspace
- select the text
- choose "Method source with it"

->
RemoteString(Object)>>error:
[
filePositionHi > theFile size
ifTrue: [ self error: 'RemoteString past end of file' ].
theFile position: filePositionHi.
theFile nextChunk ] in RemoteString>>string in Block: [ ...
BlockClosure>>ensure:
RemoteString>>string
ClassOrganization>>comment
ClassOrganization>>classComment
[ :each |
bar current: (count := count + 1).
each
selectorsDo: [ :sel |
((each sourceCodeAt: sel) includesSubstring: aString caseSensitive:
caseSensitive)
ifTrue: [ addMethod value: each value: sel ] ].
(each organization classComment asString includesSubstring: aString
caseSensitive: caseSensitive)
ifTrue: [ addComment value: each ] ] in [ :bar |
| count |
count := 0.
self
allBehaviorsDo: [ :each |
bar current: (count := count + 1).
each
selectorsDo: [ :sel |
((each sourceCodeAt: sel) includesSubstring: aString
caseSensitive: caseSensitive)
ifTrue: [ addMethod value: each value: sel ] ].
(each organization classComment asString includesSubstring: aString
caseSensitive: caseSensitive)
ifTrue: [ addComment value: each ] ] ] in
SystemNavigation>>allMethodsWithSourceString:matchCase: in Block: [ :each |
...
[ :aClass |
aBlock
value: aClass;
value: aClass class ] in SystemNavigation>>allBehaviorsDo: in Block: [
:aClass | ...
[ :name | aBlock value: (self at: name) ] in
SystemDictionary>>allClassesDo: in Block: [ :name | aBlock value: (self at:
name) ]
OrderedCollection>>do:
SystemDictionary>>allClassesDo:
SystemNavigation>>allBehaviorsDo:
[ :bar |
| count |
count := 0.
self
allBehaviorsDo: [ :each |
bar current: (count := count + 1).
each
selectorsDo: [ :sel |
((each sourceCodeAt: sel) includesSubstring: aString
caseSensitive: caseSensitive)
ifTrue: [ addMethod value: each value: sel ] ].
(each organization classComment asString includesSubstring: aString
caseSensitive: caseSensitive)
ifTrue: [ addComment value: each ] ] ] in
SystemNavigation>>allMethodsWithSourceString:matchCase: in Block: [ :bar |
...
BlockClosure>>cull:
[ result := block cull: self ] in [
self prepareForRunning.
[ result := block cull: self ]
on: JobNotification
do: [ :notification | notification handle: self ] ] in Job>>run in
Block: [ result := block cull: self ]
BlockClosure>>on:do:
[
self prepareForRunning.
[ result := block cull: self ]
on: JobNotification
do: [ :notification | notification handle: self ] ] in Job>>run in
Block: [ ...
BlockClosure>>ensure:
Job>>run
MorphicUIManager(UIManager)>>displayProgress:from:to:during:
ByteString(String)>>displayProgressFrom:to:during:
SystemNavigation>>allMethodsWithSourceString:matchCase:
SystemNavigation>>browseMethodsWithSourceString:matchCase:
[ :aPresentation |
aPresentation selectLine.
self systemNavigation browseMethodsWithSourceString: aPresentation
selectedText matchCase: false ] in
GLMPharoPlaygroundPresentation(GLMRubricSmalltalkCodePresentation)>>browsingSelectionActions
in Block: [ :aPresentation | ...
BlockClosure>>glamourValueWithArgs:
GLMGenericAction(GLMAction)>>actOn:
GLMGenericAction(GLMAction)>>morphicActOn:
[ :ann | ann action morphicActOn: aPresentation ] in
GLMMorphicPharoPlaygroundRenderer(GLMMorphicWidgetRenderer)>>installActionsOnModel:fromPresentation:
in Block: [ :ann | ann action morphicActOn: aPresentation ]
BlockClosure>>cull:
BlockClosure>>cull:cull:

Re: [Pharo-dev] Icon in New list morph.

[Yuriy Tymchuk]

Thanks, I forgot about this already because at some point it started to work by 
itself. I guess the problem was in extent.

Uko



> On 10 Apr 2015, at 23:28, Nicolai Hess  wrote:
> 
> 
> 
> 2015-04-02 17:11 GMT+02:00 Yuriy Tymchuk  >:
> Hi,
> 
> can someone help me to figure out how the icon in a NewList is working? 
> Because when when you add an IconicButton, you have a border showing up on 
> hover and background becoming darker on click. Now when I create a standalone 
> IconicButton I don’t get this actions… Does anyone have any idea?
> 
> Uko
> 
> 
> This works for me and it shows the border on hover:
> ( IconicButton new 
> target: Workspace new;
> actionSelector: #open;
> labelGraphic: (Smalltalk ui icons iconNamed: 
> #workspaceIcon );
> color: Color transparent;
> extent: 20 @ 20;
> helpText: 'Open Workspace';
> borderWidth: 0) openInHand
> 
> Make sure your button extent is bigger as the icon.
> 
> 

Re: [Pharo-dev] Can Monticello version message be a Text?

[Yuriy Tymchuk]

Can this be because my git name is different from monticello name?

Uko

> On 09 Apr 2015, at 23:40, Thierry Goubier  wrote:
> 
> Le 09/04/2015 23:34, Yuriy Tymchuk a écrit :
>> Sad. It happens to me quite a lot. So is this an issue in monticello?
> 
> I don't know.
> 
> Something is happening somewhere with the source code, and as a consequence 
> Monticello test for finding the changes mark everything as changed.
> 
> I'm pushing a solution for that symptom.
> 
> https://pharo.fogbugz.com/default.asp?15321
> 
> But I haven't found the reason. Something is switching the line endings on 
> some of the MC definitions, and I don't know who or what is doing that (and 
> not everytime).
> 
> Thierry
> 
>> 
>> 
>> 
>>> On 08 Apr 2015, at 22:13, Thierry Goubier  wrote:
>>> 
>>> Uko,
>>> 
>>> you seem to have the same bug Johan is describing.
>>> 
>>> MC seems to loose the contents of a package working copy, and hence is 
>>> unable to build a correct diff.
>>> 
>>> I've seen it happen at times, but rarely enough so I didn't pay attention 
>>> to it.
>>> 
>>> Thierry
>>> 
>>> Le 08/04/2015 09:44, Yuriy Tymchuk a écrit :
 
> On 07 Apr 2015, at 12:16, Thierry Goubier  
> wrote:
> 
> Le 07/04/2015 11:01, Yuriy Tymchuk a écrit :
>> Hi, thank you very much for investigating this.
> 
> You're working on it too :)
> 
>> These are the steps to reproduce:
>> 
>> 1. Clone a git repo (e.g. https://github.com/Uko/VnaExporter.git)
>> 2. Add it as gitfiletree repo to the pharo image.
>> 3. Change something, commit part of the changes with Komitter.
>> 4. Change something more.
>> 5. Open Komitter, you should see a strange diff.
>> 6. Select 1 or 2 methods & commit them.
>> 7. Now you should have only 2 methods in your repo.
> 
> I did, and I don't see anything suspicious. Browsing the repository at 
> each step gave me the complete package as expected (minus the unsaved 
> changes, of course).
> 
> Can you show a screenshot at step 5?
 
 I’ve done a screen recording 
 https://dl.dropboxusercontent.com/u/83145561/GitKomitter.mov
 
 Uko
 
> 
> Thierry
> 
 
 
 
>>> 
>>> 
>> 
>> 
>> 
>> 
> 
> 

Re: [Pharo-dev] Ubuntu ppa - How is it made?

[Norbert Hartl]

> Am 15.04.2015 um 13:28 schrieb Sean P. DeNigris :
> 
> Is it built from sources? How does it solve the 32-bit lib problem?

Yes it is built from sources. In the older distributions there were explicit 
32bit packages, e.g. the infamous ia32-libs. Later they introduced 
architectures in the mix, so you can add a  package:i386 to select the i386 
version of it. Taking this it is just a matter of putting the right 
dependencies in the package file.

Norbert

[Pharo-dev] Ubuntu ppa - How is it made?

[Sean P. DeNigris]

Is it built from sources? How does it solve the 32-bit lib problem?



-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/Ubuntu-ppa-How-is-it-made-tp4819663.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.