That is cool.
Doru
On Thu, Oct 30, 2014 at 11:37 PM, stepharo wrote:
> Ronie is working on unifying all the api and proposing one syntax
> mechanism for
> - nativeBoost back-end
> - FFI
> and may be Alien
>
> The FFI situation is not good and we know we should improve it.
>
>
> On
I see. But WATestError it is in the same package it is "Fileing", on line
3284 and is referenced many times before. I am sorry I have not enough
knowledge about the internals to do more debugging.
Seems to be a lack of coordination between FileOut and FileIn. Maybe
nothing to do...
Now a simpler
Ronie is working on unifying all the api and proposing one syntax
mechanism for
- nativeBoost back-end
- FFI
and may be Alien
The FFI situation is not good and we know we should improve it.
On 29/10/14 20:18, Thomas Bany wrote:
Oops, sorry, I was misslead by Steph reply.
Some of t
this one is in SmaCC. I'll see if I can switch to your solution.
I had a look at Nautilus add protocol for fun. 2303 entries for a
subclass of MorphTreeModel :( I reduce that to 11 entries in
AltBrowser add protocol for the same use case.
:(
Same feeling here but we will live with it for now.
It says that the class WATestError is not available.
Yes, I did. It is in the .st file
c. You get a bunch of errors in Transcript while filing in
No magic ball so we cannot guess.
Example of Transcript messages (in case it helps):
WADocumentHandlerResponseTest>>createAndVerifyB
2014-10-30 13:16 GMT+01:00 stepharo :
>
> On 30/10/14 06:57, José Comesaña wrote:
>
>> I've found this problem in Pharo 3 (seems to happen in Pharo 4 too):
>>
>> Do:
>>
>> 1. Fileout Seaside-Tests-Core
>> 2. Remove Seaside-Test-Core
>> 3. File in the file created in step 1
>>
>> You will find:
>>
Paul
I'm going over the plugin code and hierarchy and I will probably clean
it a bit and publish real class comments.
I'm checking the plugin to see the ones that are working and the one we
can remove or fix.
Writing what I'm learning in
https://github.com/SquareBracketAssociates/PharoForTheEn
On 30/10/14 06:57, José Comesaña wrote:
I've found this problem in Pharo 3 (seems to happen in Pharo 4 too):
Do:
1. Fileout Seaside-Tests-Core
2. Remove Seaside-Test-Core
3. File in the file created in step 1
You will find:
a. The structure of the package changes.
What do you mean by it cha
I've found this problem in Pharo 3 (seems to happen in Pharo 4 too):
Do:
1. Fileout Seaside-Tests-Core
2. Remove Seaside-Test-Core
3. File in the file created in step 1
You will find:
a. The structure of the package changes.
b. Comments for WaContextTest are lost
c. You get a bunch of errors in
How I do SO wish I could attend ( I even have old friends living in Lille !
)
And then a trip across to see and walk Rue Chifflet in Besancon and an
afternoon in Strasbourg ?
un
*rêve ...*
Robert Shiplett/Shifflet/Chifflet
On 29 October 2014 20:18, Sven Van Caekenberghe wrote:
> We are excite
Here is what I found.
I'm adding a doc into book garage (pharo for the entreprise)
How to create Nautilus-Plugins
Here we will give some brief explanations on how to create your own
plugin. By the way there are only two requirements
to create a Nautilus-Plugin:
• the class should inherit from
Hi Stef,
this one is in SmaCC. I'll see if I can switch to your solution.
I had a look at Nautilus add protocol for fun. 2303 entries for a subclass
of MorphTreeModel :( I reduce that to 11 entries in AltBrowser add protocol
for the same use case.
Thierry
12 matches
Mail list logo
