On Tue, May 28, 2013 at 7:13 AM, Bahman Movaqar wrote:
> I noticed that since there is no `import' statement in Pharo, class
> names can easily conflict. What is the common naming strategy that you
> people use to avoid that?
the first two letters are often an indication of the package. E.g.,
P
We should fix it.
Stef
On May 27, 2013, at 10:38 PM, Usman Bhatti wrote:
>
>
>
> On Mon, May 27, 2013 at 6:53 PM, stephane ducasse
> wrote:
> Usman there is a getText in the pharo repo on smalltalk but we have to check
> its state.
>
> It still has references to FileDirectory so I was th
Dear Pharoers,
Here are the results of evaluation and ranking of student proposals.
Those are 13 accepted projects with stipendiums from Google:
- A new trait implementation
by Sebastian Tleye, mentor Damien Cassou
http://gsoc2013.esug.org/projects/new-traits
- Animation Library based on
Great news ! Thanks for the effort, Janko.
On 28 May 2013, at 10:16, Janko Mivšek wrote:
> Dear Pharoers,
>
> Here are the results of evaluation and ranking of student proposals.
> Those are 13 accepted projects with stipendiums from Google:
>
> - A new trait implementation
> by Sebastian T
On 2013-05-28 12:07, Damien Cassou wrote:
> On Tue, May 28, 2013 at 7:13 AM, Bahman Movaqar wrote:
>> I noticed that since there is no `import' statement in Pharo, class
>> names can easily conflict. What is the common naming strategy that you
>> people use to avoid that?
>
>
> the first two le
On Tue, May 28, 2013 at 10:30 AM, Bahman Movaqar wrote:
> Thanks. I'll follow that convention.
>
> BTW I assume there is no central place to check if the two letter
> combination has already been taken or not, right?
nope. But you can ask the mailing list if you have a doubt. Don't
worry too mu
On 2013-05-28 13:07, Damien Cassou wrote:
> On Tue, May 28, 2013 at 10:30 AM, Bahman Movaqar wrote:
>> Thanks. I'll follow that convention.
>>
>> BTW I assume there is no central place to check if the two letter
>> combination has already been taken or not, right?
>
>
> nope. But you can ask th
Doru,
thanks for the answer.
I'm doing it in the way you suggest.
What I ment by know how to add to the result is the following: (Modifing a
bit the example you gave me)
a := 'AAA' asParser flatten ==> [:token | ResultSelfAdder new objectToAdd:
token; selector:#addA ].
b := 'BBB' asParser flatte
I am using a 3 letter prefix for my own projects. It works well too.
Lack of imports is not that bad. Cleaner code most of time.
Phil
Pharo Consortium Member
Le 28 mai 2013 12:52, "Bahman Movaqar" a écrit :
> On 2013-05-28 13:07, Damien Cassou wrote:
> > On Tue, May 28, 2013 at 10:30 AM, Bahman
Hi all,
I have a need to persist a really large and funny object structure in
Pharo (a huge Dictionary of Dictionaries) and I would like to be able to
query this data from a remote image.
Basically what I am looking for is some form of database that would
allow me to input elements in to thi
Hi,
I would more do it the other way around (from large to small):
niceObject := ParseResult new.
result do: [:eachResult | niceObject add: eachResult ]
Cheers,
Doru
On Tue, May 28, 2013 at 2:23 PM, Juan Ignacio Vaccarezza <
juanvaccare...@gmail.com> wrote:
> Doru,
> thanks for the answer.
This seems to be a perfect match for a Mongo DB via MongoTalk:
http://smalltalkhub.com/#!/~francois/MongoTalk
If you already have an object model, Esteban Lorenzano wrote a nice library
on top of it called Voyage that is probably useful for you. You can see
some details here:
http://smalltalkhub.c
Boris,
What is the class/type of the keys in your example? Are the keys simple objects
(String, Number, etc.) or complex (Person, Employee, Customer, Student,
Product, etc.).
With any remote database the challenge will be populating the result into your
local image. How deep/complex is the re
Boris zdravo,
Dne 28. 05. 2013 16:11, piše Boris Spasojević :
> I have a need to persist a really large and funny object structure in
> Pharo (a huge Dictionary of Dictionaries) and I would like to be able to
> query this data from a remote image.
>
> Basically what I am looking for is some for
If you need only queries around big static dictionary image persistence can
be sufficient.
Just load all data to image, save it and you will have in memory readonly
database (without transactions) .
2013/5/28 Boris Spasojević
> Hi all,
>
> I have a need to persist a really large and funny objec
Juan Ignacio Vaccarezza wrote:
Im pretty new at asking on mailists, and sometimes I
forget to add crucial information
Hi Juan,
I like to refer people to "How To Ask Questions The Smart Way" [1].
However it is friendlier here than the tone of the article so I wouldn't
worry too much abo
Nice article indeed!
thanks ben.
On Tue, May 28, 2013 at 1:46 PM, wrote:
> Juan Ignacio Vaccarezza wrote:
>
>> Im pretty new at asking on mailists, and sometimes I
>> forget to add crucial information
>>
>>
> Hi Juan,
>
> I like to refer people to "How To Ask Questions The Smart Way" [1].
>
Hi Doru,
I did it the other way to avoid the "if" inside the ParseResult>>add: .
Regards,
Juan
On Tue, May 28, 2013 at 11:55 AM, Tudor Girba wrote:
> Hi,
>
> I would more do it the other way around (from large to small):
>
> niceObject := ParseResult new.
> result do: [:eachResult | niceObject
I have a UI, let's call it ParentUI, which includes ChildUI - another
ComposableModel. In the default layout, ChildUI includes a toolbar.
When embedded in the ParentUI, I want the toolbars to be merged. It is easy
to include the ChildUI tools in the ParentUI bar by adding
ParentUI>>childTools, whi
| layout |
model := DynamicComposableModel new.
model instantiateModels: {#accessor. #TextInputFieldModel}.
layout := SpecLayout composed.
layout add: #accessor withSpec: TextInputFieldModel defaultSpec.
model openWithSpecLayout: layout.
leads to:
DNU SpecLayoutAddWithSpec(Object)>>doesNotUnderst
Sean P. DeNigris wrote
> leads to:
> DNU SpecLayoutAddWithSpec(Object)>>doesNotUnderstand: #subwidget:
That was in 2.0, in 30172, I get:
MessageNotUnderstood: DynamicComposableModel>>getText
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Spec-add-withSpec-Bug-tp46905
21 matches
Mail list logo