> 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 [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
