Hi Johan,
I depend on Bootstrap from my Config's baseline:
project: 'Bootstrap' with: [
spec
className: 'ConfigurationOfBootstrap';
repository: 'http://smalltalkhub.com/mc/TorstenBergmann/Bootstrap/main/';
versionString: #stable ];
Which depends on Seaside in its baselin
Hi Sven,
I have (not yet) tried Pharo6, but I saw some people did update the
configuration for that.
How are you loading the project? Are you using the Metacello load API ?
Johan
> On 20 Feb 2017, at 19:52, Sven Van Caekenberghe wrote:
>
> Hi,
>
> In my main project I depend on Torsten's Boo
Many thanks for your valuable vote Hayatou :)
- Jigyasa
--
View this message in context:
http://forum.world.st/Seeking-support-Vote-for-Jigyasa-Grover-for-Red-Hat-International-Women-in-Open-Source-Academic-Awar7-tp4934824p4935144.html
Sent from the Pharo Smalltalk Users mailing list archive
Hi,
In my main project I depend on Torsten's Bootstrap project which then loads
Seaside. I tried this today on Pharo 6 and it did not work (some internal
Seaside dependency could not be resolved). I also noticed that the last commits
on Bootstrap were from April 2016.
My question now is: is t
Hi,
I have three questions regarding these two options.
As a matter of analogy to what I know, for me a Voyage repo is like a
database and collections like tables in relational db world.
So what is the argument to use multiple repo for an application domain?
When using two repo A and B, is it ok
Dale,
I try out the lock feature on an archived image, the seaside uprade was
still operating :(
I updated this image with latest Metacello, then I locked it as:
Metacello image
configuration: 'Seaside3';
version: '3.1.4.2'; "most recent 3.1.x version"
lock.
It was the version ret
An improved ?? construct is part of the public API now. It can be used to
attach predicates to node tests:
xmlNode / 'foo' / ('bar' ?? 10).
or to filter result node sets like this:
(xmlNode / 'foo' / 'bar') ?? 10.
xmlNode / 'foo' / 'bar' ?? 10. "same because of precedence"
Thanks Denis.
> There is refactoring which sadly not available from menu. But you can
> evaluate it manually:
>
> (RBGenerateEqualHashRefactoring className: #YourClass variables: #(var1
> var2)) execute
My problem is display in this image.
In the left the inspector display all the items in t
Works marvels indeed.
I have made some more Seaside integrations for this one.
But Pharo3. Need to upgrade to latest Seaside and Pharo.
Phil
On Mon, Feb 20, 2017 at 3:06 PM, Hernán Morales Durand <
hernan.mora...@gmail.com> wrote:
> Hi Sergio,
>
> Have a look at the ApplicationSecurity packa
Hi Sergio,
Have a look at the ApplicationSecurity package:
http://80738163270632.blogspot.com/2014/03/application-security-presentation.html
http://80738163270632.blogspot.com/2014/10/application-security-2-checkpoint.html
http://80738163270632.blogspot.com/2015/02/application-security-3-setting-
I have been tasked with throwing together a small web app that will hold
the passwords to different projects for my company.
I would like to use seaside to do this, but the biggest requirement is that
we need to be able to either:
- encrypt the entire database, so that if the machine was compromi
There is refactoring which sadly not available from menu. But you can
evaluate it manually:
(RBGenerateEqualHashRefactoring className: #YourClass variables: #(var1
var2)) execute
2017-02-20 13:46 GMT+01:00 Trussardi Dario Romano <
dario.trussa...@tiscali.it>:
> Ciao,
>
> i works with Ph
Ciao,
i works with Pharo 4.0 environment.
I have a class Product with some instance variable and the =
method set to:
= anItem
anItem ifNil:[^false].
anItem class = self class ifFalse:[ ^false].
^ rfrConsegna = an
2017-02-18 8:53 GMT+01:00 itli...@schrievkrom.de :
> Sadly this is gone or simply only badly implemented. E.g. in Pharo you
> can select a package - fine, but to know, what has been extended in this
> package ?. The name of the method categories also define in which
> package this method is locat
I will try to get a look at your lock feature, and report.
Thanks
Hilaire
Le 19/02/2017 à 18:50, Dale Henrichs a écrit :
> I mentioned last night that I thought that there was a better solution
> to your problem and I think that if you load the latest Metacello and
> then lock Seaside3:
--
Dr.
Le 20/02/2017 à 08:19, Stephan Eggermont a écrit :
>> May be it is more a policy problem on the quality of the configuration
>> than a tool problem, a lot can be learn from Debian packaging.
>
> I don't have that impression. They seem to have the same problem with
> old and less-used stuff.
As lo
16 matches
Mail list logo
