Hi,
is there any photo gallery available for Pier? I mean a widget where I
could upload pictures and they are rendered in a nice way. I started
one 4 years ago but I abandoned it.
Bye
--
Damien Cassou
http://damiencassou.seasidehosting.st
Hi all,
I am prototyping an idea using QCMagritte. First time trying QCMagritte.
First time using Magritte seriously, really. :-)
I have a need for a write-once description. Suppose my domain object has two
attributes: a label and a date. Here I want date to be write-once. Meaning,
when instantiating a new object using QCMagritte's add screen, I want to enter
the label and the date. Subsequently, when I edit that object through
QCMagritte, I want date to be read only.
I am ok to be able to change the date using an inspector within Smalltalk.
Here are some possibilities I see:
- Test for nil in the date setter and signal an error when not nil. This isn't
so nice because the UI should not allow the date to be edited in the first
place when it is no longer nil.
- Dynamically change the instance's date description to beReadonly once date
has been set. Is this considered good style?
Hints appreciated.
Pierce
Gareth wrote:
>I will look into the problem and see whats causing it, but my bigger issue is that you can't have failing installs by default.
The current design of configuration browser can not, and does not work. Configurations are not independent,
so just installing default stable results in missing packages. The well-known example is loading configurations
of Seaside and Magritte.
The manual copying of configurations from their canonical location to the metarepo is also a problem.
I've done some updates.
Stephan
Hi All
I downloaded Pharo3, Opened it, first thing I did was go to
configuration browser, select pier3 and click "install stable version"
I then get 'Apparent loop in import expansion'
I will look into the problem and see whats causing it, but my bigger
issue is that you can't have failing installs by default.
Users cannot be expected to know how to fiddle and try figure out how to
fix everything when they simply want to install and use something.
Stack below:
MetacelloVersionConstructor(Object)>>error:
MetacelloVersionConstructor>>collectAllVersionsFromVersionImportPragmasInto:using:satisfiedPragmas:
MetacelloVersionConstructor>>calculate:project:
MetacelloVersionConstructor>>on:project: in Block: [ :cache | ...
MetacelloPharo30Platform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing:
in Block: [ :dict | ...
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary:
in Block: [ ^ aBlock value: dict ]
BlockClosure>>on:do:
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary:
MetacelloPharo30Platform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing:
MetacelloPharo30Platform(MetacelloPlatform)>>stackCacheFor:at:doing:
MetacelloVersionConstructor>>on:project:
MetacelloVersionConstructor class>>on:project:
ConfigurationOfSeaside3>>project
MetacelloMCProjectSpec>>projectClassProject
MetacelloMCProjectSpec>>version
MetacelloMCProjectSpec(MetacelloProjectSpec)>>versionOrNil in Block: [
self version ]
BlockClosure>>on:do:
MetacelloMCProjectSpec(MetacelloProjectSpec)>>versionOrNil
MetacelloMCProjectSpec>>compareCurrentVersion:targetVersionStatus:using:
MetacelloMCVersionSpecLoader>>load in Block: [ :pkg | ...
Array(SequenceableCollection)>>do:
MetacelloMCVersionSpecLoader>>load
MetacelloMCVersion>>executeLoadFromArray:
MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ :dict | ^ self
executeLoadFromArray: anArray ]
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary:
in Block: [ ^ aBlock value: dict ]
BlockClosure>>on:do:
MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary:
MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ ...
BlockClosure>>ensure:
MetacelloMCVersion>>fetchRequiredFromArray: in Block: [ ...
Kind Regards
--
Gareth Cox
IT Manager/Developer
Inspired Org (PTY) Ltd
email: gareth(a)inspired.org <mailto:gareth@inspired.org>
tell: +27 (0)21 531 5404
cell: +27 (0)78 374 9035
Hi,
I just uploaded a new version of Magritte-Seaside, which only modifies
MADescribedColumn, to what, I think was a bug in the default
implementation that didn't take into consideration whether or not the
Magritte description was configured as sortable or not.
Name: Magritte-Seaside-EstebanMaringolo.359
Author: EstebanMaringolo
Time: 1 October 2014, 5:02:04.404911 pm
UUID: ae6b6270-d42f-4984-8bac-735a1f57f201
Ancestors: Magritte-Seaside-StephanEggermont.358
Adds #isSortable testing to MADescribedColumn delegating to its
Magritte description whether it is sortable or not.
However I don't know in which version it should be included.
In my opinion it should go both in 3.1 and 3.2 versions, but I don't
know what is the policy.
Can somebody please give me instructions or update the
ConfigurationOfMagritte3 to include this change?
Regards!
Esteban A. Maringolo
ps: the issue tracker of magritte at
https://code.google.com/p/magritte-metamodel/issues/list seems
outdated, so I didn't add an issue for this.
