Color values range from 0.0 to 1.0 use
(Color r: 255 g: 255 b: 122 range: 255) alpha: 1.0
instead ;-)
Regards, Gary
- Original Message -
From: Esteban Lorenzano esteba...@gmail.com
To: Pharo-project@lists.gforge.inria.fr Development
pharo-project@lists.gforge.inria.fr
Sent:
Hi Mariano,
I've been using RPackage so i stumbled on the same problem.
RPackage maps System Categories (one to one), thus your problem
happens because there's no category named 'RPackage'.
For example evaluate (RPackageOrganizer default packageNamed: 'RPackage-Core')
Saludos,
Fernando
On
On Thu, Aug 9, 2012 at 1:25 PM, Fernando Olivero fernando.oliv...@usi.chwrote:
Hi Mariano,
I've been using RPackage so i stumbled on the same problem.
RPackage maps System Categories (one to one), thus your problem
happens because there's no category named 'RPackage'.
But for the rest it
The fix is committed in the new version :-)
Noury
On 8 août 2012, at 16:41, Noury Bouraqadi wrote:
On 7 août 2012, at 22:32, Mariano Martinez Peck wrote:
On Tue, Aug 7, 2012 at 10:29 PM, Noury Bouraqadi bouraq...@gmail.com wrote:
Hi,
Group creation raises a DNU.
Replacing messages
All in all, Spec is *much* easier to work with than PolyMorph directly. The
builder alone makes for much less code, as we only have to specify the
attributes we care about. Ben, thanks for all the great work so far!
While pushing on it, I ran into a few problems...
1. Issue 6547: [BUG Spec]:
Hi,
I created a graveyard for packages removed from 2.0.
It is at:
http://smalltalkhub.com/#!/~Pharo/Graveyard20
The purpose of the graveyard is to keep removed packages to allow users to
migrate their code.
Sadly, not all packages removed will be there, because there are some so
willing
why this is logic? shouldn't be enough just using r:g:b:alpha:?
sorry, my graphics skills are close to zero so... no idea if what I'm saying
has any sense :)
On Aug 9, 2012, at 11:44 AM, Gary Chambers gazzagu...@btinternet.com wrote:
Color values range from 0.0 to 1.0 use
(Color r: 255 g:
Hi Esteban,
It's a matter of percentage, meaning that you can chose an percentage
of r, of g, and of b, and by default the values go from 0.0 to 1.0.
If you want to use 255 as the max (as 1.0), then do as Gary posted.
Fernando
On Thu, Aug 9, 2012 at 4:32 PM, Esteban Lorenzano
This is an excellent idea
Alexandre
On Aug 9, 2012, at 10:28 AM, Esteban Lorenzano esteba...@gmail.com wrote:
Hi,
I created a graveyard for packages removed from 2.0.
It is at:
http://smalltalkhub.com/#!/~Pharo/Graveyard20
The purpose of the graveyard is to keep removed
You're right! But notice that the RPackage logic of one to one mapping
with categories, only
breaks when it only provides extension methods as in the case of
'AST-Core' and 'RPackage'.
| p |
p := RPackageOrganizer default packageNamed: 'AST-Core'.
( p extensionMethods size = 2 ) ( p
20249
-
Issue 6535: New Nautilus version
http://code.google.com/p/pharo/issues/detail?id=6535
Issue 6496: Remove Source Code Authors
http://code.google.com/p/pharo/issues/detail?id=6496
Issue 6452: Few Morphic fixes
Issue 6551: [ENH Spec]: Spec-ify DropListModel
http://code.google.com/p/pharo/issues/detail?id=6551
Currently:
self instantiateModels: #(dropList #DropListModel).
item1 := DropListItem named: 'Red morph' do: self redMorphBlock.
item2 := DropListItem named: 'Blue
Sean P. DeNigris wrote
It seems that (in 1.4, not sure about 2.0) if an image is launched with a
script (e.g. cogvm my.image my.st), StartupPreferences are never run. Is
that what's intended?
After experimenting a bit, it seems that preferences are loaded after script
arguments are
+1, preferences should be loaded before any laod scripts.
On 09/08/12 12:20, Sean P. DeNigris wrote:
Sean P. DeNigris wrote
It seems that (in 1.4, not sure about 2.0) if an image is launched with a
script (e.g. cogvm my.image my.st), StartupPreferences are never run. Is
that what's intended?
FileSystem compat
-
During my train trip today I ported (AKA copied) the whole FileSystem package
from 2.0 to 1.4 and fixed some tests:
- the 2.0 FS works almost perfectly in 1.4
- some Tests related to DateAndTime fail!
Furthermore I created a dumb FileDirectory interface for 2.0
which version of Pharo/VM are you using?
Cause in my latest 1.4 and latest 2.0 this seems to work...
String streamContents: [ :s| -0.55s2 printOn: s ] yields the expected
'-0.55s2'
I remember Mariano once had a strange integer issue since he accidentally used
once of
is own compiled VMs which
On 2012-08-09, at 22:54, Francois Stephany tulipe.mouta...@gmail.com wrote:
+1, preferences should be loaded before any laod scripts.
indeed, so we have to change the order in the startup list...
On 09/08/12 12:20, Sean P. DeNigris wrote:
Sean P. DeNigris wrote
It seems that (in 1.4,
Cami,
Silly me 1.1.1. I should obviously be up to date.
Thanks
Guy
On 10/08/2012, at 10:04 AM, Camillo Bruni wrote:
which version of Pharo/VM are you using?
Cause in my latest 1.4 and latest 2.0 this seems to work...
String streamContents: [ :s| -0.55s2 printOn: s ] yields the expected
Camillo Bruni-3 wrote
FileSystem compat
Is the FS 2.0 API backward-compatible with the current 1.4 FS? If not, (and
I /really/ want to have the latest FS in 1.4), I think it should be loadable
via Metacello as not to create a mess for our users... maybe
ConfigurationOfFilesystem20.
Camillo
On 2012-08-10, at 00:15, Sean P. DeNigris s...@clipperadams.com wrote:
Camillo Bruni-3 wrote
FileSystem compat
Is the FS 2.0 API backward-compatible with the current 1.4 FS? If not, (and
I /really/ want to have the latest FS in 1.4), I think it should be loadable
via Metacello as not to
Cami,
If you can let me know where to find your new FS code, I can take it for a spin
...
I've already spent time inventing a Grease-like layer that I can use with
FileDirectory and FileSystem, but if your FileDirectory will be available and
will fulfill my needs I can toss out the work I've
21 matches
Mail list logo
