Stéphane Ducasse stephane.duca...@inria.fr writes:
Check the settings because you can say to the window manager that it should
stagger or position them in another way.
Else have a look at TWM
Stef
I tried to change the window positioning but that was not what I wanted
to have I want in the
On Jul 22, 2011, at 10:10 PM, Nicolas Cellier wrote:
Pharo 1.4 is not easily accessible from the site
http://www.pharo-project.org/home
Also true for the new Jenkins continuous integration server
https://ci.lille.inria.fr/pharo/
Pharo 1.3 is listed as unstable, and not in released. Hasn't
Just playing with Laurent's example contact manager.
So next logical step - how to validate the fields?
E.g. both first name and surname must have a value.
Is there a method to override? Something I need to implement in the model
class?
Got any hints? :-)
--
View this message in context:
You could set the regex for the field
E.g.
the field morph converter regexString: '.+'
That would hilight any invalid fields. Still need to check on OK, or make
that button's enablement
depend on whether the model is valid.
Regards, Gary
- Original Message -
From: Jeff Gray
Some trickyness.
Use of a combined accessor vs. separate get/set selectors may cause some
problems since less flexible.
Users exist in Slider subclasses and DiffMorph. Plus the TEasilyThemed and
UITheme helpers.
Regards, Gary
- Original Message -
From: Stéphane Ducasse
Hi (Marcus),
I was looking for a Pharo 1.3 Seaside 'client' build on the CI server(s) but
couldn't find it.
It used to be available for 1.2.x (this seems to be gone as well).
I think that for good reciprocal relations with Seaside, it would be very good
to have a tested build of the current
+1 on having the Hudson/Jenkins load Seaside.
From: pharo-project-boun...@lists.gforge.inria.fr
[pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Sven Van
Caekenberghe [s...@beta9.be]
Sent: Monday, July 25, 2011 10:31 AM
To: An open mailing
On Mon, Jul 25, 2011 at 4:31 PM, Sven Van Caekenberghe s...@beta9.bewrote:
PS: Another questions is: is 1.3 'released', if so where are the links on
the website, where is the 'noise' ?
To paraphrase the famous quote: Pharo code is never released, it escapes!
--
Cheers,
Peter
Hello,
TWM stands for Tiling Windows Manager, check screencasts at the author's
blog to see it in action:
http://magaloma.blogspot.com/.
I think it could cover you needs pretty well ;)
On Mon, Jul 25, 2011 at 9:50 AM, Friedrich Dominicus
fr...@q-software-solutions.de wrote:
Stéphane Ducasse
Did you check what we did?
Because it would give us some confidence :)
Stef
On Jul 25, 2011, at 4:21 PM, Gary Chambers wrote:
Some trickyness.
Use of a combined accessor vs. separate get/set selectors may cause some
problems since less flexible.
Users exist in Slider subclasses and
Yes!!!
Stef
On Jul 25, 2011, at 4:31 PM, Sven Van Caekenberghe wrote:
Hi (Marcus),
I was looking for a Pharo 1.3 Seaside 'client' build on the CI server(s) but
couldn't find it.
It used to be available for 1.2.x (this seems to be gone as well).
I think that for good reciprocal
I think I know what Friedrich means, groups of items under a single taskbar
entry (with popup shortlist).
Unfortunately there is no formal mechanism for identifying individual windows
as belonging to a a group.
Any window can have whatever title/label it wants, models are not either
present or
I did check. Having a single accessor (with mutation) does not cover all the
cases. Some users require *no* getter, for instance, so would be erroneous
to update in response to a change.
Regards, Gary
- Original Message -
From: Stéphane Ducasse stephane.duca...@inria.fr
To:
Yep TWM detect some types of windows, browsers, workspaces, monticello and
propose a menu to list them and tile only this type.
By the way, this could be cool to enable arbitrary window group in TWM ;)
On Mon, Jul 25, 2011 at 6:06 PM, Gary Chambers gazzagu...@btinternet.comwrote:
**
I think
On Jul 25, 2011, at 6:08 PM, Gary Chambers wrote:
I did check. Having a single accessor (with mutation) does not cover all the
cases. Some users require *no* getter, for instance, so would be erroneous to
update in response to a change.
Ok I finally got it :)
we are open to change :) our
Hi guys
I will be offline or busy with kids for some days and I wanted to make a list
of todos for when I want to do something.
- Integrate FS
- step one add FS packages
- step two integrated = use FS
- Add RBengine
- step one add RBEngine packages
- step two
Hi Stef,
- Add RBengine
- step one add RBEngine packages
what is RBEngine?
#Luc
- step two (check RPackage changes)
- Add OCompletion
- Add Ecompletion
- Integrate SystemAnnouncer
- step one load package
- would be cool to convert
Are we talking about events/announcements? I ask because the Dolphin way of
doing things like this is that #value: triggers events, #setValue: does not -
more or less. It is a very nice system.
Caveat emptor: Dolphin also makes a lot of use of comparison policies (identity
and equality being
Hi Doru,
=== Integrate TWM windows grouping mechanism
- I know that for it to work, it requires some changesets that need to be
filed in.
- It would be great if they were integrated :)
in 1.3 ? They have been integrated in 1.4.
Laurent.
- See thread:
We were talking about a kind of value holder which was played by MorphicModel
and that was using a kind of accessor ( asymbol) and that gary extended.
And we are thinking that having a good one would be better to the accessor one.
But we discovered that while cleaning slider.
Stef
On Jul 25,
Hi,
On 25 Jul 2011, at 23:28, laurent laffont wrote:
Hi Doru,
=== Integrate TWM windows grouping mechanism
- I know that for it to work, it requires some changesets that need to be
filed in.
- It would be great if they were integrated :)
in 1.3 ? They have been integrated in 1.4.
21 matches
Mail list logo
