In cases where there is an MASelectorAccessor, I'd like to make the default
label = `the accessor capitalized unCamelCased`. It seems the overwhelmingly
common use case is `... #accessor: #dateCreated; #label: 'Date Created'`.
The current behavior is
MADescription>>#label
^ self propertyAt: #label ifAbsent: [ self class defaultLabel ]
Is anyone using (or can state a plausible use case for) this
subclass-customizable class-side #defaultLabel?
If no one is relying on the existing behavior, I'll make the change...
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Default-labels-tp4827879.html
Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.
Hi,
is there any photo gallery available for Pier? I mean a widget where I
could upload pictures and they are rendered in a nice way. I started
one 4 years ago but I abandoned it.
Bye
--
Damien Cassou
http://damiencassou.seasidehosting.st
Quoting from http://sdmeta.gforge.inria.fr/Teaching/Lille/0910-MetaModelisation/07-08-Co… section 4.1:
The Adaptive- Model has two instance variables, the first being used to refer to the descriptions of the instance and the other one to keep a list of the actual values of the model. Transforming the class of the adaptive model into a Trait [18] allows us turn any existing class into an adaptive model and to combine the descriptions defined in the class with the ones provided by the instance.
I cannot find this trait. Does it exist in magritte? I see MAAdaptiveModel, but I am indeed trying to add adaptivity to a class, and am struggling with it
oops. I tried squeak 5.1, not 5.0
> On 09 Sep 2016, at 08:18, Tapple Gao <tapplek(a)gmail.com> wrote:
>
> For the record, here’s the installation incantations that didn’t work, in the order I tried them:
>
> === In Squeak 5.0, attempt 1 ===
>
> Metacello new
> configuration: 'Seaside3';
> repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
> version: #stable;
> load: 'OneClick’.
>
> Metacello new
> configuration: 'Pier3';
> repository: 'http://www.smalltalkhub.com/mc/Pier/Pier3/main';
> version: #stable;
> load.
>
>
> === In Squeak 5.0, attempt 2 ===
>
> Metacello new
> configuration: 'Seaside3';
> repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
> version: #stable;
> load: 'OneClick’.
>
> Metacello new
> configuration: 'Pillar';
> repository: 'http://www.smalltalkhub.com/mc/Pier/Pillar/main';
> version: #stable;
> load.
>
>
> === In Squeak 5.0, attempt 3 ===
>
> Metacello new
> configuration: 'Seaside3';
> repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
> version: #stable;
> load: 'OneClick’.
>
> Metacello new
> configuration: 'Magritte3';
> repository: 'http://www.smalltalkhub.com/mc/Magritte/Magritte3/main';
> version: #stable;
> load.
>
>
> === Pharo 5, attempt 1 ===
>
> install seaside3, then pier 3, from catalog
>
>
> === Pharo 5, attempt 2 ===
>
> install seaside3, then pillar, from catalog
>
>
> === Pharo 5, attempt 3 ===
>
> Metacello new
> configuration: 'Seaside3';
> repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
> version: #stable;
> load: 'OneClick'.
>
> Metacello new
> configuration: 'Magritte3';
> repository: 'http://www.smalltalkhub.com/mc/Magritte/Magritte3/main';
> version: #stable;
> load.
>
> Metacello new
> configuration: 'Pier3';
> repository: 'http://www.smalltalkhub.com/mc/Pier/Pier3/main';
> version: #stable;
> load.
>
>
> === Pharo 4, attempt 1 ===
>
> Metacello new
> configuration: 'Seaside3';
> repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
> version: #'release3.1';
> load: 'OneClick'.
>
> Metacello new
> configuration: 'Magritte3';
> repository: 'http://www.smalltalkhub.com/mc/Magritte/Magritte3/main';
> version: #'release3.5';
> load.
>
> The final one failed in the most interesting way; it broke seaside by installing a mix of seaside for pharo 4 and seaside for pharo 5
>
>> On 09 Sep 2016, at 08:02, Tapple Gao <tapplek(a)gmail.com> wrote:
>>
>> Thank you. I uploaded my changes to http://www.smalltalkhub.com/#!/~tapple . However, I realized they are for an older version of pier, from before the Pillar split, so they’ll probably be a pain to merge. I’m using this pier one-click image from lukas: http://www.piercms.com/download (pharo 1.3). I’ve never been able to install a working pier using metacello on any image for the past year. I tried again yesterday, and, after another 5 failed attempts on 3 different images, finally found a working incantation:
>>
>> "Instructions: Take fresh pharo 4.0 image, run the following, and pier works. Thanks to https://www.list.inf.unibe.ch/pipermail/smallwiki/2015-December/008025.html"
>>
>> Metacello new
>> configuration: 'Seaside3';
>> repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
>> version: #'release3.1';
>> load: 'OneClick'.
>>
>> Metacello new
>> configuration: 'Pier3';
>> repository: 'http://www.smalltalkhub.com/mc/Pier/Pier3/main';
>> version: #'release3.0';
>> load.
>>
>> It will take me some time to merge my changes, migrate my website, and properly test everything in a newer pier. I’ll let you know when I have.
>>
>>> On 08 Sep 2016, at 13:38, Damien Pollet <damien.pollet(a)gmail.com> wrote:
>>>
>>> Hi !
>>>
>>> Monticello is a distributed version control system, so you could have your own repository on smalltalkhub to commit your modifications. In fact, given how MC (doesn't) handles branches, it's probably the recommended way of doing if you want experimental/development code to be clearly separate from the official branch.
>>>
>>> In terms of getting your changes merged in the official release, I'd suggest discussing them on one of the Pharo lists, or on the Slack channel. Some of the owners of the Magritte and Pier repos on sthub and recent developers are active there and should be able to help and even review your code or add you to the contributors.
>>>
>>>
>>> On 8 September 2016 at 12:15, Tapple Gao <tapplek(a)gmail.com> wrote:
>>> Hello all. It’s been a long time since I contributed to a smalltalk project, but I’d like to start again.
>>>
>>> I’m developing a complex website based on Pier and Magritte: https://fiberhood.nl
>>>
>>> Even though I’ve barely started, I’ve already found several things to fix in Pier and Magritte, and would like to submit my fixes back upstream. How should I do that? I assume I don’t have commit access to http://www.smalltalkhub.com/#!/~Magritte and http://www.smalltalkhub.com/#!/~Pier , although I don’t really know how to tell. I’m used to squeaksource, where it plainly says Global: Read or Global: Read and Write
>>>
>>> My username on smalltalkhub is tapple: http://www.smalltalkhub.com/#!/~tapple
>>> _______________________________________________
>>> Magritte, Pier and Related Tools ...
>>> https://www.list.inf.unibe.ch/listinfo/smallwiki
>>>
>>>
>>>
>>> --
>>> Damien Pollet
>>> type less, do more [ | ] http://people.untyped.org/damien.pollet
>>> _______________________________________________
>>> Magritte, Pier and Related Tools ...
>>> https://www.list.inf.unibe.ch/listinfo/smallwiki
>>
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.list.inf.unibe.ch/listinfo/smallwiki
>
Hello all. It’s been a long time since I contributed to a smalltalk project, but I’d like to start again.
I’m developing a complex website based on Pier and Magritte: https://fiberhood.nl
Even though I’ve barely started, I’ve already found several things to fix in Pier and Magritte, and would like to submit my fixes back upstream. How should I do that? I assume I don’t have commit access to http://www.smalltalkhub.com/#!/~Magritte and http://www.smalltalkhub.com/#!/~Pier , although I don’t really know how to tell. I’m used to squeaksource, where it plainly says Global: Read or Global: Read and Write
My username on smalltalkhub is tapple: http://www.smalltalkhub.com/#!/~tapple
