Perhaps using "long" to represent the string could work
or using long* with the following hard coded manner to pass the string..
bytes := 'adsadsasdd' asByteArray.
ea := ( ExternalAddress allocate: bytes size) .
1 to: bytes size do: [ :e |
( ea byteAt: e put: ( bytes at: e )
Ah. ha... Very Good. For the whole time I've used Pharo the last 12
months I've had a misconception about Examples.
I thought they must have been Example coded somewhere like
GLMBasicExamples, the MOEaselExamples and these somehow flagged for
searching - and that I never got any results becau
I believe I have a solution of sorts, use a void* ptr for the argument type
and create a method to use to nul-teminate any smalltalk strings passed as
arguments. It seems to work ok, unless anyone can spot any problems with
such an approach.
Thanks
The below line in yellow fixes the issue - yupi!!
How do I submit this?
BallonMorph class >> string: str for: morph corner: cornerName
"Make up and return a balloon for morph. Find the quadrant that
clips the text the least, using cornerName as a tie-breaker. tk 9/12/97"
| tm vertices |
tm := sel
- Original Message -
| From: "Sean P. DeNigris"
| Dale Henrichs wrote
| >
| > If you don't want to experience the pain of developing on a new
| > platform,
| > then don't move to the new platform until the hubbub has died down
| > ...
| >
| I'm perfectly happy, but it seemed like nobod
Dale Henrichs wrote
>
> In my last post, I provided my vision of the future
>
That was very helpful. I can see the big picture much better now...
Dale Henrichs wrote
>
> If you don't want to experience the pain of developing on a new platform,
> then don't move to the new platform until the h
Bill,
I agree with the "no real argument" bit:)
Dae
- Original Message -
| From: "Wilhelm K Schwab"
| To: Pharo-project@lists.gforge.inria.fr
| Sent: Saturday, April 28, 2012 3:08:33 PM
| Subject: Re: [Pharo-project] What about making the configuration
browser more visible
No real argument, but it's not "my choice" - it's the only option. I had
parsers not work and *COMPLETE* meltdowns that would scare away any new user,
both until I followed the advice to shun the symbolic versions.
Yes, there are gaps to close.
From:
Sean,
In my last post, I provided my vision of the future ... for the present, the
answer is "what you see is what you get" ...
When a new version of Pharo comes on the scene, the challenge is to port the
existing configurations to the new version ... it does not happen magically and
it does
Sean,
What do I think? I think that's a loaded question:)
Honestly? I THINK that we've reached a cross roads for Monticello/Metacello. I
THINK of Metacello as a pontoon bridge that keeps goods and services flowing
while we build the real bridge.
The "relentless evolution" of Pharo puts pressur
Hi,
On Apr 27, 2012, at 8:11 PM, Schwab,Wilhelm K wrote:
> I know it's not a popular opinion, but overall, they don't work. It is so
> bad that any effort on my part to fix one here or there would simply be
> sticking a finger in a collapsing Hoover dam. "Yelling in general" is a
> mis-chara
Bill,
If you value the opinions of "your experts" over the good advice that you have
received on this thread so far then that is your choice.
I'd say that your "experts" have a gap to close... and you should expect them
to close it...
Dale
- Original Message -
| From: "Wilhelm K Schwab
20027
-
Issue 5731: Add trait test for a specific failing case
http://code.google.com/p/pharo/issues/detail?id=5731
Issue 5729: remove #profile from InflateStream
http://code.google.com/p/pharo/issues/detail?id=5729
--
Marcus Denker -- http://marcusdenker.de
Hi,
I'm trying to pass a smalltalk string to a FFI wrapper method I've written,
the C function uses a macro "type" for the argument, but as far as I can
see is basically a char* type. I've tried using char* as the argument type
and it fails values to pass the string argument.
If I change the argu
It seems very reasonable to have such a crucial infrastructure to have some
base support in the core image. But I have had experts tell me to *never* load
a symbolic version. There is a gap to close...
From: pharo-project-boun...@lists.gforge.inria.fr
If you use Pharo, you can also do that
<>
Note that you have to change 'Selector' with 'Example', and then you can type a
list of arguments separated by a dot and the expected result.
(If you want some inner details, it will do something like methodFor:
{_WHAT_YOU_HAVE_ENTER_})
Have fun,
Ben
This test reproduces the problem :)
testOriginWithRequiredMethod
| tr1 c1 |
tr1 := self createTraitNamed: #TTT1 uses: {}.
tr1 compile: 'foo ^ self explicitRequirement'.
self assert: (tr1 >> #foo) origin == tr1.
c1 := self createClassNamed: #CTT1 superclass: Object uses: tr1.
In the paper it says that
self assert: (C>>#c) origin = C.
when m*ethod c is defined locally in class C*, which overrides its defi-
nition from Trait2. Its origin is then such a class C.
And the definition does not stand any limitations on requirements... :/
I'll write some tests.
On Sat, Apr
I just discovered this new "bit of magic" from the Newbies list. My
first impression playing with it is that MethodFinder>>methodFor: should
be somehow more prominent in Tools>Finder and also in PharoByExample
book. Quite a unique feature and demonstration of Smalltalk power for
newcomers.
c
Hi Guillermo.
When you combine these triggers with ads (as in your example), I see an
analogy with the model of qt ui, see:
http://qt-project.org/doc/qt-4.8/signalsandslots.html
In effect:
"A signal is emitted when a particular event occurs." -> A Announcement is
send when a particular event (tri
What about the stepping behaviour? Is the plan to remove that as well?
I've got the hunch that stepping should only be restricted to special worlds.
Otherwise you get a lot of behaviour, and complexity, that you don't need in a
more traditional UI.
My 2 cents...
- Francisco
On 28 Apr 2012, a
On Sat, Apr 28, 2012 at 1:13 PM, Denis Kudriashov wrote:
> Hello.
>
>
> 2012/4/27 Guillermo Polito
>
>> onShow
>> onDelete
>> onKeyUp
>> onKeyPress
>> onKeyDown
>> onClick
>> onMouseDown
>> onMouseUp
>> onDoubleClick
>> onDragged
>> onDropped
>> onMove?
>> onResize?
>>
>>
Hello.
2012/4/27 Guillermo Polito
> onShow
> onDelete
> onKeyUp
> onKeyPress
> onKeyDown
> onClick
> onMouseDown
> onMouseUp
> onDoubleClick
> onDragged
> onDropped
> onMove?
> onResize?
>
> For all containers
> onChildAdded
> onChildRemoved
>
Maybe this is only way
Hello pharoers
I contacted the restaurant and book the places for 19h30-20h00.
The restaurant is the sylmar
2 Pce Sebastopol, 59000 Lille
03 20 57 14 39
http://www.yelp.fr/biz/the-sylmar-restaurant-lille
http://maps.googl
20026
-
Issue 5722: Be able to remove traits from class definition
http://code.google.com/p/pharo/issues/detail?id=5722
Issue 5715: Enhance the Slice Maker so that is gets the issue title
automatically
http://code.google.com/p/pharo/issues/detail?id=5715
We should check that what we described in
http://marcusdenker.de/publications/Duca09bTraitsAPI.pdf
Stef
On Apr 28, 2012, at 1:02 AM, Guillermo Polito wrote:
> For example, the trait TPureBehavior has the method #traitComposition, which
> is an explicit requirement, and I can do
> I hav
26 matches
Mail list logo
