Okey so I looked deeper into the interpreter and found that the receiver of
the next call is the returned value of the previous. I'm pretty sure it
explains the infinite loop I was encountering.
It also made it problematic to register the morph to the anouncement of the
adapter, since #addDependen
here is a "hackish" solution:
collection1 := #(1 2 3 4 5) asOrderedCollection.
collection2 := #($a $b $c $d $e) asOrderedCollection.
list1 := ListModel new.
list1 items: collection1.
list1 dragEnabled: true.
list1 dropEnabled: true.
list1
Goubier Thierry wrote
> Another approach, that I would use, is to put more complex objects
> inside the lists. Thoses objects would know how to get added / removed
> from their respective collections, and then I would propagate collection
> changes to the ListModel instances.
That sounded promi
Hum, I was pondering the problem at home and started from scratch. I don't
have the issue anymore ...
2014-04-03 18:40 GMT+02:00 Thomas Bany :
> Hey,
>
> I have a quick question. I'm trying to build an adapter (called
> MorphicSwitchAdapter) and a model for SimpleSwitchMorp. I based my layout
>
Hi,
It is gone. And for me it is a very annoying.
Now if you want the system to prevent looking I am afraid you have to
modify some system class method as there is no more hook to do it
properly (see the mailing list archive for discussion about that a few
weeks ago). Then I don't know the conseq
Hey,
I have a quick question. I'm trying to build an adapter (called
MorphicSwitchAdapter) and a model for SimpleSwitchMorp. I based my layout
on the ones in existing adapter (namely MorphicButtonAdapter).
And I get stuck in an infinite loop during the interpretation of the layout
of the adapter.
Damien Cassou wrote:
On Thu, Apr 3, 2014 at 1:28 PM, Norbert Hartl wrote:
Is there a rather complex example available that uses spec. I mean a sort of a complex UI that solves some real use cases from where I can steal ideas and patterns how things are done. I'm just a UI noop an
On Thu, Apr 3, 2014 at 1:28 PM, Norbert Hartl wrote:
> Is there a rather complex example available that uses spec. I mean a sort of
> a complex UI that solves some real use cases from where I can steal ideas and
> patterns how things are done. I'm just a UI noop and like to have all the
> guid
If I remember well, we used this way to get some data about image required
by PDF format.
Maybe there is a smarter way to do this, I will have a look with Olivier
about this.
2014-04-03 10:32 GMT+02:00 Stephan Eggermont :
> Reg Krock took a look at how difficult it would be to port Artefact to
Thanks to all for your input. I consider this problem solved and I will write
a little tutorial for those who might be interested.
I now will be moving to another simple problem and will post the code here
to go again with this process.
In this way, we can accumulate slowly simple, but usefull prob
흠.. make pdf. but ugly sorry.
http://onion.onionmixer.net/DeepIntoPharo_TranslateKorean_Draft.7z
this file.
if possible then i want get a TeX file. me can convert latex to xetex.
have xetex then can PDF more to good.
who can give TeX file to me?
On Wed, Apr 2, 2014 at 2:34 PM, nacho <0800na...@gmail.com> wrote:
> if you don't mind
I don't mind, go ahead. And don't hesitate to send us your future code
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusia
Pharo 3.0 comes with multiple Spec UIs for different tools, have a look at the
subclasses of ComposableModel, maybe there is something there that suits you.
On Apr 3, 2014, at 8:28 AM, Norbert Hartl wrote:
> Is there a rather complex example available that uses spec. I mean a sort of
> a com
Le 02/04/2014 20:44, MartinW a écrit :
First of all thank you for taking the time to explain all this to me! I
already learned a lot about working with the spec widgets..
You're giving me good code to work with, and the things I use are more
Morphic than Spec, which is more in my circle of c
Is there a rather complex example available that uses spec. I mean a sort of a
complex UI that solves some real use cases from where I can steal ideas and
patterns how things are done. I’m just a UI noop and like to have all the
guidance available :)
thanks,
Norbert
On 03 Apr 2014, at 12:50, Thomas Bany wrote:
>
> I will defenitly look into that. The "rebuild" may be missleading, is it also
> called at first building ?
That’s your own ,method, call it as/when you want
> Well, I can't even manage to tweak it through hardcoding stuff on the adapter
> :p
>
> The usual solution is to have a method looking like this on instance side
>
> rebuildMyLayout
>
> | layout |
> layout := self buildStateDependentLayout.
> self buildWithLayout: layout.
>
> buildStateDependentLayout
> ^ SpecLayout composed
> etc...
>
I will defenitly look into that. The "rebui
Reg Krock took a look at how difficult it would be to port Artefact to Gemstone.
He found that JPEG support uses a plugin based reader/writer, and seems to
render the JPEG using BitBlt and Form.
Why are JPEGs rendered? I’d think embedding them should be enough
(and be better for speed and image q
18 matches
Mail list logo
