smallwiki

smallwiki@list.inf.unibe.ch

2312 discussions

by Stephan Eggermont

We have builds on http://ci.inria.fr/pharo-contribution Pier3 Pier3Addons If you don't have specific needs, select the last green build of release3.1 of 30 to download the last successful build. You'll need a vm and sources with that. Cheers, Stephan

10 years

downloads doesn't work

by Nelson Garcia

Hi I try download Pier, but the links are broken http://www.piercms.com/download please can you fix it?

10 years

Re: Details section of QCMagritte Tutorial

by Stephan Eggermont

Hmm, that looks bad. It works better in the overview mode: I should fix the text. Suggestions welcome. Stephan

10 years

Details section of QCMagritte Tutorial

by Markus Fritsche

Hi, I am reading the QCMagritte Tutorial and I am a bit lost. The "Details" Item says: "This tutorial should teach you the most important features of QCMagritte. As you can see, you can go to details. Press details to see the details of this item." => Wat? I don't see any "Details" user interface item, what is the tutorial refering to? Best regards, Markus

10 years

Re: Write-Once description

by Stephan Eggermont

You can set a property in the description readonly: (self date notNil); Stephan

10 years, 2 months

Write-Once description

by Pierce Ng

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

10 years, 2 months

RE: 'Apparent loop in import expansion' Pharo3

by Stephan Eggermont

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

10 years, 2 months

'Apparent loop in import expansion' Pharo3

by Gareth Cox

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

10 years, 2 months

Metacello config for Magritte3

by Esteban A. Maringolo

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.

10 years, 2 months

DataTables jQuery plugin for Seaside and DTMagritteReport

by Esteban A. Maringolo

Hi folks, This mail is just a heads-up to anybody already using DataTables (https://datatables.net/) or that developed a Seaside wrapper for it. I just uploaded my initial working version of DataTables to STHub. If your current wrapper is better than mine we can merge our efforts. This initial version supports the basic features to instantiate a DataTables jQuery object, plus support for AJAX+JSON responses and also Server-side Processing (https://datatables.net/manual/server-side). I still have to write a proper example of how to use it, but if you load the DataTables-Magritte package it will include a DTMagritteReport that you can use to replace the "stock" MAReport. Once I have time I'll try to set up an example to show the different ways it can be used. Meanwhile look at the DTMagritteReport class to see a particular use case. It includes support for server side sorting (multiple columns), filtering, pagination, search. To load it with all the dependencies run: Gofer it smalltalkhubUser: 'emaringolo' project: 'DataTables'; package: 'ConfigurationOfDataTables'; load. (Smalltalk at: #ConfigurationOfDataTables)project development load: 'Magritte'. The STHub is: http://smalltalkhub.com/#!/~emaringolo/DataTables/ Regards! Esteban A. Maringolo

10 years, 3 months

← Newer
1
...
7
8
9
10
11
12
13
...
232
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

smallwiki