Latest OB, category autocompletion does always a lowercase

Hi. In the latest OB code, when I put "add category" to a method, and I start to type...it automatically finds several categories, but it always put lowercase to the name.
For example, I have Package called *MyApp  and I want to create a method category for that....when I type, the option showed is *myapp
Would be great if this is case sensitive.

Cheers

Mariano

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Protocols are lowercase by convention, that's why it suggests only
lowercase variants. You can still manually type something uppercase of
course.

Lukas

On Friday, October 22, 2010, Mariano Martinez Peck
<[hidden email]> wrote:
> Hi. In the latest OB code, when I put "add category" to a method, and I start to type...it automatically finds several categories, but it always put lowercase to the name.
> For example, I have Package called *MyApp  and I want to create a method category for that....when I type, the option showed is *myapp
> Would be great if this is case sensitive.
>
> Cheers
>
> Mariano
>

--
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Protocols are lowercase by convention, that's why it suggests only
lowercase variants. You can still manually type something uppercase of
course.

Lukas

On Friday, October 22, 2010, Mariano Martinez Peck
<[hidden email]> wrote:
> Hi. In the latest OB code, when I put "add category" to a method, and I start to type...it automatically finds several categories, but it always put lowercase to the name.
> For example, I have Package called *MyApp  and I want to create a method category for that....when I type, the option showed is *myapp
> Would be great if this is case sensitive.
>
> Cheers
>
> Mariano
>

--
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On Friday, October 22, 2010, Mariano Martinez Peck
<[hidden email]> wrote:
>
> On Fri, Oct 22, 2010 at 2:46 PM, Lukas Renggli <[hidden email]> wrote:
>
> Protocols are lowercase by convention,
> But is this still true for packages extensions??  I always keep case sensitive for *MyPackage (I think this is because before monticello have problems with this)

PackageInfo always matched category names case-sensitive and protocols
case-insensitive.

> Maybe just a little change that for those categories with * it doesn't apply the lowercase would be nice.

The way it currently works is intentional. It helps people to adhere
to the convention and reduces future inconsistencies.

Lukas



--
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Am 2010-10-22 um 14:48 schrieb Lukas Renggli:
> Protocols are lowercase by convention,[…]

Just wanted to add, that this depends on platform and
environment. For example, the GemStone protocols are
Initial Uppercase by default.
  Personally, I find extension protocols exactly matching
their packages more exact and clear, especially when I combine
them with actual "protocol names" as in:
*SqueakSource-Notification-Email-accessing

where “SqueakSource-Notification-Email” is the the package
and “accessing” the category I actually intend.

So Long,
        -Tobias
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project