ConfigurationOfCitezen
Locked
 
|
Hello all,
Maybe I am simply getting confused by reading code from an "old" image, but I am trying to install Citezen. As I read the configuration, it was written in terms of Seaside 2.8, but it looks like 3.0 is being installed. Any ideas? I am open to thinking about Seaside 3, but my packages will fail to load due to the configuration changes. So far, all I have found is that I need to "change to the new system" but not much more than that. Perhaps the answer is to comment out the offending #initialize code, load everything, and then worry about how to get them registered. As slick as it is to be able to use Seaside to configure my Seaside apps, I do not want to trust myself on that front; I want them to be secured from the beginning, and temporarily re-configured for development as needed, and then programmatically switched back to secure-or-nothing. Semi-rhetorical question: should Citezen be loading Seaside? Could/should there be a Citezen-base or something that just reads BibTeX, and then other things that do all of the web-enabled work? All I do with it is parse entries, for which is very valuable. Bill _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
> Hello all, > > Maybe I am simply getting confused by reading code from an "old" image, but I am trying to install Citezen. As I read the configuration, it was written in terms of Seaside 2.8, but it looks like 3.0 is being installed. Any ideas? I think that conifguration OfCitezen load lastest dev (as mention in the class comment) load seaside30 > > I am open to thinking about Seaside 3, but my packages will fail to load due to the configuration changes. So far, all I have found is that I need to "change to the new system" but not much more than that. Perhaps the answer is to comment out the offending #initialize code, load everything, and then worry about how to get them registered. As slick as it is to be able to use Seaside to configure my Seaside apps, I do not want to trust myself on that front; I want them to be secured from the beginning, and temporarily re-configured for development as needed, and then programmatically switched back to secure-or-nothing. > > Semi-rhetorical question: should Citezen be loading Seaside? Could/should there be a Citezen-base or something that just reads BibTeX, and then other things that do all of the web-enabled work? All I do with it is parse entries, for which is very valuable. indeed we could have a citezen base and a citezen for web Damien can reply to you when he reappear from his teaching duties :) not sure that this is not 8 h per day this week Setf _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
Hello,
I published a new version of ConfigurationOfCitezen. All Citezen can be loaded by evaluating: ConfigurationOfCitezen load. Citezen without Seaside, Magritte and Pier, evaluate: ConfigurationOfCitezen loadNoWeb. Adrien. > From: [hidden email] > Date: Mon, 14 Jun 2010 20:38:05 +0200 > To: [hidden email] > Subject: Re: [Pharo-project] ConfigurationOfCitezen > > > > > Hello all, > > > > Maybe I am simply getting confused by reading code from an "old" image, but I am trying to install Citezen. As I read the configuration, it was written in terms of Seaside 2.8, but it looks like 3.0 is being installed. Any ideas? > > > I think that conifguration OfCitezen load lastest dev (as mention in the class comment) > load seaside30 > > > > > I am open to thinking about Seaside 3, but my packages will fail to load due to the configuration changes. So far, all I have found is that I need to "change to the new system" but not much more than that. Perhaps the answer is to comment out the offending #initialize code, load everything, and then worry about how to get them registered. As slick as it is to be able to use Seaside to configure my Seaside apps, I do not want to trust myself on that front; I want them to be secured from the beginning, and temporarily re-configured for development as needed, and then programmatically switched back to secure-or-nothing. > > > > Semi-rhetorical question: should Citezen be loading Seaside? Could/should there be a Citezen-base or something that just reads BibTeX, and then other things that do all of the web-enabled work? All I do with it is parse entries, for which is very valuable. > > indeed we could have a citezen base and a citezen for web > > Damien can reply to you when he reappear from his teaching duties :) > not sure that this is not 8 h per day this week > > Setf > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project Vous voulez protéger votre vie privée ? La solution avec Internet Explorer 8 _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
THANKS!!!!
________________________________________ From: [hidden email] [[hidden email]] On Behalf Of Adrien BARREAU [[hidden email]] Sent: Wednesday, June 16, 2010 4:45 AM To: [hidden email] Subject: Re: [Pharo-project] ConfigurationOfCitezen Hello, I published a new version of ConfigurationOfCitezen. All Citezen can be loaded by evaluating: ConfigurationOfCitezen load. Citezen without Seaside, Magritte and Pier, evaluate: ConfigurationOfCitezen loadNoWeb. Adrien. > From: [hidden email] > Date: Mon, 14 Jun 2010 20:38:05 +0200 > To: [hidden email] > Subject: Re: [Pharo-project] ConfigurationOfCitezen > > > > > Hello all, > > > > Maybe I am simply getting confused by reading code from an "old" image, but I am trying to install Citezen. As I read the configuration, it was written in terms of Seaside 2.8, but it looks like 3.0 is being installed. Any ideas? > > > I think that conifguration OfCitezen load lastest dev (as mention in the class comment) > load seaside30 > > > > > I am open to thinking about Seaside 3, but my packages will fail to load due to the configuration changes. So far, all I have found is that I need to "change to the new system" but not much more than that. Perhaps the answer is to comment out the offending #initialize code, load everything, and then worry about how to get them registered. As slick as it is to be able to use Seaside to configure my Seaside apps, I do not want to trust myself on that front; I want them to be secured from the beginning, and temporarily re-configured for development as needed, and then programmatically switched back to secure-or-nothing. > > > > Semi-rhetorical question: should Citezen be loading Seaside? Could/should there be a Citezen-base or something that just reads BibTeX, and then other things that do all of the web-enabled work? All I do with it is parse entries, for which is very valuable. > > indeed we could have a citezen base and a citezen for web > > Damien can reply to you when he reappear from his teaching duties :) > not sure that this is not 8 h per day this week > > Setf > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ________________________________ Vous voulez protéger votre vie privée ? La solution avec Internet Explorer 8<http://clk.atdmt.com/FRM/go/232102477/direct/01/> _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
In reply to this post by Adrien BARREAU
I got this to load in a 1.1 image of some description; it looks like a pharo-dev rc2, but no promises :) #loadNoWeb seems to work, but the tests are not acting properly. On running them, but via the run tests menu option and by selecting the category in the test runner, I get walkbacks in the resource's #setUp. I don't use resources much or at all(??), and so I don't recall whether an error in a test resource should bring things to a halt as is happening here. The problem is that #trimBoth is not present in the image.
Bill ________________________________________ From: [hidden email] [[hidden email]] On Behalf Of Adrien BARREAU [[hidden email]] Sent: Wednesday, June 16, 2010 4:45 AM To: [hidden email] Subject: Re: [Pharo-project] ConfigurationOfCitezen Hello, I published a new version of ConfigurationOfCitezen. All Citezen can be loaded by evaluating: ConfigurationOfCitezen load. Citezen without Seaside, Magritte and Pier, evaluate: ConfigurationOfCitezen loadNoWeb. Adrien. > From: [hidden email] > Date: Mon, 14 Jun 2010 20:38:05 +0200 > To: [hidden email] > Subject: Re: [Pharo-project] ConfigurationOfCitezen > > > > > Hello all, > > > > Maybe I am simply getting confused by reading code from an "old" image, but I am trying to install Citezen. As I read the configuration, it was written in terms of Seaside 2.8, but it looks like 3.0 is being installed. Any ideas? > > > I think that conifguration OfCitezen load lastest dev (as mention in the class comment) > load seaside30 > > > > > I am open to thinking about Seaside 3, but my packages will fail to load due to the configuration changes. So far, all I have found is that I need to "change to the new system" but not much more than that. Perhaps the answer is to comment out the offending #initialize code, load everything, and then worry about how to get them registered. As slick as it is to be able to use Seaside to configure my Seaside apps, I do not want to trust myself on that front; I want them to be secured from the beginning, and temporarily re-configured for development as needed, and then programmatically switched back to secure-or-nothing. > > > > Semi-rhetorical question: should Citezen be loading Seaside? Could/should there be a Citezen-base or something that just reads BibTeX, and then other things that do all of the web-enabled work? All I do with it is parse entries, for which is very valuable. > > indeed we could have a citezen base and a citezen for web > > Damien can reply to you when he reappear from his teaching duties :) > not sure that this is not 8 h per day this week > > Setf > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ________________________________ Vous voulez protéger votre vie privée ? La solution avec Internet Explorer 8<http://clk.atdmt.com/FRM/go/232102477/direct/01/> _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
Since the trim** methods can not be added in core for the moment, I hade grease core as a dependency of Citezen.
ConfigurationOfCitezen loadNoWeb works fine. Adrien. Vous voulez protéger votre vie privée ? La solution avec Internet Explorer 8 _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
Dear all,
2010/6/25 Adrien BARREAU <[hidden email]>: > Since the trim** methods can not be added in core for the moment, I hade > grease core as a dependency of Citezen. > ConfigurationOfCitezen loadNoWeb > works fine. the #trimBoth method is still a requirement of Citezen and is not present in the image. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |