By the way, we can add a rule that checks if a package has a comment. Because
for example I had no idea that you can comment packages.
> On 24 May 2016, at 14:37, Cyril Ferlicot Delbecque
> wrote:
>
>
>
> On 24/05/2016 13:19, Christophe Demarey wrote:
>>
>>> Le 24
On 24/05/2016 13:19, Christophe Demarey wrote:
>
>> Le 24 mai 2016 à 10:08, Esteban Lorenzano a écrit :
>>
>> there is a space: same as class comment now.
>
>
> only for the class comment, not for other package metadata
>
Maybe the package comment can be at the place
> On 24 May 2016, at 10:09, Cyril Ferlicot Delbecque
> wrote:
>
>
>
> On 24/05/2016 07:44, Sven Van Caekenberghe wrote:
>>
>> The missing class comments are totally unacceptable, we should refuse these.
>>
>
> +1
>
> It is really frustrating to take free
> On 24 May 2016, at 04:00, Sean P. DeNigris wrote:
>
> Doing some exploring... BlueInk, Chroma, Flashback, Renraku - all packages
> with no class comments. How would a new user discover what these are?
How comes that Renraku has no class comments?
> On 24 May 2016, at 13:19, Christophe Demarey
> wrote:
>
>
>> Le 24 mai 2016 à 10:08, Esteban Lorenzano a écrit :
>>
>> there is a space: same as class comment now.
>
>
> only for the class comment, not for other package metadata
you
> Le 24 mai 2016 à 10:08, Esteban Lorenzano a écrit :
>
> there is a space: same as class comment now.
only for the class comment, not for other package metadata
there is a space: same as class comment now.
> On 24 May 2016, at 10:00, Christophe Demarey
> wrote:
>
> I already have support for package comments with cargo (including ui) using
> the package manifest. In fact, it is more. I have support for package
>
On 24/05/2016 07:44, Sven Van Caekenberghe wrote:
>
> The missing class comments are totally unacceptable, we should refuse these.
>
+1
It is really frustrating to take free time to improve the comments of
the current classes and to see that there is dozens of classes without
comment
On 24/05/2016 04:00, Sean P. DeNigris wrote:
> Doing some exploring... BlueInk, Chroma, Flashback, Renraku - all packages
> with no class comments. How would a new user discover what these are?
>
BlueInk is the new configurable formatter.
In Chroma there is only one classe with a class comment.
Le 24/5/16 à 08:21, Esteban Lorenzano a écrit :
On 24 May 2016, at 08:05, stepharo wrote:
When people use a configuration and add a description
hovering over the package show you the description and this helps for real.
yes, this is super cool… but I would like the
> On 24 May 2016, at 08:05, stepharo wrote:
>
> When people use a configuration and add a description
>
> hovering over the package show you the description and this helps for real.
yes, this is super cool… but I would like the possibility to toggle a “comment”
for packages
> On 24 May 2016, at 04:00, Sean P. DeNigris wrote:
>
> Also, not new to Pharo 5.0, but thinking as a new user... Nautilus presents
> the system as an overwhelming mess of top level packages. I guess this is
> because we're showing packages, which are a dependency/SCM
When people use a configuration and add a description
hovering over the package show you the description and this helps for real.
Stef
Le 24/5/16 à 04:00, Sean P. DeNigris a écrit :
Doing some exploring... BlueInk, Chroma, Flashback, Renraku - all packages
with no class comments. How would a
> On 24 May 2016, at 07:41, Sven Van Caekenberghe wrote:
>
>
>> On 24 May 2016, at 03:37, Sean P. DeNigris wrote:
>>
>> Sean P. DeNigris wrote
>>> Is there a more complete description than the announcement?
>>
>> I should've mentioned that I did see the
> On 24 May 2016, at 04:00, Sean P. DeNigris wrote:
>
> Doing some exploring... BlueInk, Chroma, Flashback, Renraku - all packages
> with no class comments.
The missing class comments are totally unacceptable, we should refuse these.
Apart from BlueInk (a code
> On 24 May 2016, at 03:37, Sean P. DeNigris wrote:
>
> Sean P. DeNigris wrote
>> Is there a more complete description than the announcement?
>
> I should've mentioned that I did see the link to the bugtracker, but I'm
> looking for some middle ground between the 5
Doing some exploring... BlueInk, Chroma, Flashback, Renraku - all packages
with no class comments. How would a new user discover what these are?
Also, not new to Pharo 5.0, but thinking as a new user... Nautilus presents
the system as an overwhelming mess of top level packages. I guess this is
Sean P. DeNigris wrote
> Is there a more complete description than the announcement?
I should've mentioned that I did see the link to the bugtracker, but I'm
looking for some middle ground between the 5 bullet points in the
announcement and the 2400+ issues tagged for Pharo 5.0
-
Cheers,
Is there a more complete description than the announcement? I've been
dutifully following the mailing lists, but don't feel like I have a real
handle on what the new features are and why they matter. Thanks!
-
Cheers,
Sean
--
View this message in context:
19 matches
Mail list logo