Thinking about Seaside installation and pages on the homepage, I started to think about putting a Seaside installation script in SqueakMap. [1] (This script loads with no server, I don’t think, so I figure it’s incomplete. Does anybody have a more complete one?)
Maybe I’d create two new pages: Seaside; and, Installation. (That URI - Installation - is from the old site). And then add links to SqueakMap and SqueakSource on that page. But then it made me think I’d have to find out who the Seaside maintainers are to ask them to put in a new script. But Seaside should be what we were calling a few years ago a Community Supported Package. Is it a CSM in SqueakMap? How does that work? It seems to me that creating a Seaside page and slapping a Metacello installation script on it is a short sighted solution. Perhaps the notion of a CSM could be explored at this juncture. Chris [1] (Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfSeaside3'. ((ConfigurationOfSeaside3 project) version: #stable) load. |
On Sat, Dec 13, 2014 at 11:58:15AM -0500, Chris Cunnington wrote:
> Thinking about Seaside installation and pages on the homepage, I started to think about putting a Seaside installation script in SqueakMap. [1] (This script loads with no server, I don???t think, so I figure it???s incomplete. Does anybody have a more complete one?) > Maybe I???d create two new pages: Seaside; and, Installation. (That URI - Installation - is from the old site). And then add links to SqueakMap and SqueakSource on that page. > But then it made me think I???d have to find out who the Seaside maintainers are to ask them to put in a new script. But Seaside should be what we were calling a few years ago a Community Supported Package. Is it a CSM in SqueakMap? How does that work? > It seems to me that creating a Seaside page and slapping a Metacello installation script on it is a short sighted solution. Perhaps the notion of a CSM could be explored at this juncture. > > Chris > [1] > (Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfSeaside3'. > ((ConfigurationOfSeaside3 project) version: #stable) load. I think that Tobias Pape and Stephan Eggermont have given a good starting point. I tried the Metacello configuration, and that works fine. If I want to get started on Seaside (which in fact I do), I would want to start first with Tobias' latest prepared image, even if it's not updated to the latest trunk level. If we can get the squeak.org site to point to the information that Tobias and Stephan provide, that's probably the most important thing to do right now. I like your idea of getting the SqueakMap entry updated, although I'd be inclined to follow up on that issue later. How about January 1 as a new years resolution? Dang, we have a lot of outdated entries on SqueakMap, we really need to clean that up. New Seaside users are going to start at the Seaside home page, so we want to make sure that the download link for "Squeak Smalltalk" points to the information that Tobias and Stephan have provided. Right now it is pointing to "404 Not Found" which is not exactly the message that we want to be sending to the world. If I could start at the seaside.st home page and follow the download link for Squeak to find the Metacello configuration that Stephan provided, and the prepared image that Todias provides, I would be a happy camper :-) Thanks, Dave |
OK, let’s leave community supported packages for later. I’l make a page for Seaside today.
Chris > On Dec 13, 2014, at 6:44 PM, David T. Lewis <[hidden email]> wrote: > > On Sat, Dec 13, 2014 at 11:58:15AM -0500, Chris Cunnington wrote: >> Thinking about Seaside installation and pages on the homepage, I started to think about putting a Seaside installation script in SqueakMap. [1] (This script loads with no server, I don???t think, so I figure it???s incomplete. Does anybody have a more complete one?) >> Maybe I???d create two new pages: Seaside; and, Installation. (That URI - Installation - is from the old site). And then add links to SqueakMap and SqueakSource on that page. >> But then it made me think I???d have to find out who the Seaside maintainers are to ask them to put in a new script. But Seaside should be what we were calling a few years ago a Community Supported Package. Is it a CSM in SqueakMap? How does that work? >> It seems to me that creating a Seaside page and slapping a Metacello installation script on it is a short sighted solution. Perhaps the notion of a CSM could be explored at this juncture. >> >> Chris >> [1] >> (Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfSeaside3'. >> ((ConfigurationOfSeaside3 project) version: #stable) load. > > > I think that Tobias Pape and Stephan Eggermont have given a good starting > point. I tried the Metacello configuration, and that works fine. If I want > to get started on Seaside (which in fact I do), I would want to start first > with Tobias' latest prepared image, even if it's not updated to the latest > trunk level. > > If we can get the squeak.org site to point to the information that Tobias > and Stephan provide, that's probably the most important thing to do right > now. > > I like your idea of getting the SqueakMap entry updated, although I'd be > inclined to follow up on that issue later. How about January 1 as a new > years resolution? Dang, we have a lot of outdated entries on SqueakMap, > we really need to clean that up. > > New Seaside users are going to start at the Seaside home page, so we want > to make sure that the download link for "Squeak Smalltalk" points to the > information that Tobias and Stephan have provided. Right now it is pointing > to "404 Not Found" which is not exactly the message that we want to be > sending to the world. > > If I could start at the seaside.st home page and follow the download link > for Squeak to find the Metacello configuration that Stephan provided, and > the prepared image that Todias provides, I would be a happy camper :-) > > Thanks, > > Dave > > |
Cool. Thanks!!!
Dave > OK, letâs leave community supported packages for later. Iâl make a > page for Seaside today. > > Chris >> On Dec 13, 2014, at 6:44 PM, David T. Lewis <[hidden email]> wrote: >> >> On Sat, Dec 13, 2014 at 11:58:15AM -0500, Chris Cunnington wrote: >>> Thinking about Seaside installation and pages on the homepage, I >>> started to think about putting a Seaside installation script in >>> SqueakMap. [1] (This script loads with no server, I don???t think, so I >>> figure it???s incomplete. Does anybody have a more complete one?) >>> Maybe I???d create two new pages: Seaside; and, Installation. (That URI >>> - Installation - is from the old site). And then add links to SqueakMap >>> and SqueakSource on that page. >>> But then it made me think I???d have to find out who the Seaside >>> maintainers are to ask them to put in a new script. But Seaside should >>> be what we were calling a few years ago a Community Supported Package. >>> Is it a CSM in SqueakMap? How does that work? >>> It seems to me that creating a Seaside page and slapping a Metacello >>> installation script on it is a short sighted solution. Perhaps the >>> notion of a CSM could be explored at this juncture. >>> >>> Chris >>> [1] >>> (Installer ss project: 'MetacelloRepository') install: >>> 'ConfigurationOfSeaside3'. >>> ((ConfigurationOfSeaside3 project) version: #stable) load. >> >> >> I think that Tobias Pape and Stephan Eggermont have given a good >> starting >> point. I tried the Metacello configuration, and that works fine. If I >> want >> to get started on Seaside (which in fact I do), I would want to start >> first >> with Tobias' latest prepared image, even if it's not updated to the >> latest >> trunk level. >> >> If we can get the squeak.org site to point to the information that >> Tobias >> and Stephan provide, that's probably the most important thing to do >> right >> now. >> >> I like your idea of getting the SqueakMap entry updated, although I'd be >> inclined to follow up on that issue later. How about January 1 as a new >> years resolution? Dang, we have a lot of outdated entries on SqueakMap, >> we really need to clean that up. >> >> New Seaside users are going to start at the Seaside home page, so we >> want >> to make sure that the download link for "Squeak Smalltalk" points to the >> information that Tobias and Stephan have provided. Right now it is >> pointing >> to "404 Not Found" which is not exactly the message that we want to be >> sending to the world. >> >> If I could start at the seaside.st home page and follow the download >> link >> for Squeak to find the Metacello configuration that Stephan provided, >> and >> the prepared image that Todias provides, I would be a happy camper :-) >> >> Thanks, >> >> Dave >> >> > > |
In reply to this post by Chris Cunnington-4
Hi Chris,
> But then it made me think I’d have to find out who the Seaside maintainers > are to ask them to put in a new script. But Seaside should be what we were > calling a few years ago a Community Supported Package. Is it a CSM in > SqueakMap? Yes. Here is the current list of Community Supported packages on SqueakMap. http://map.squeak.org/category/0ae2a689-f7bb-4ea5-9c32-84d0aa48a9e3 . Seaside is there, and its "3.1.1" version is designated for 4.5. It should still be working; if not, we should definitely fix it. > How does that work? When I did the work for this, I needed to have a clear understanding of the requirement first so I forced myself to write it out as simply as I could: "The ability to resurrect projects that are owned by members who have long-since departed the community while protecting the original archival legacy of the original author. Currently-active members should be able to post new-and-improved releases that work for the latest version of the Squeak image." [1] The easiest way to implement it was to use the admin interface to add a new SMCategory called "Community Supported" along with a testing method for it; #isCommunitySupported to SMCategorizableObject. Conveniently, Package and PackageRelease were already CategorizableObject's, so I only needed to update #canUpdateRelease:using: to include the first two lines of logic below: canUpdateRelease: aSMPackageRelease using: aHVHtmlBuilder "Only allow aSMPackageRelease to be updated if it is owned by the currentAccount, or if it isCommunitySupported and if the user is only trying to save a NEW release (vs. replacing existing). Or, allow for SqueakMap administrators." ^ ((aHVHtmlBuilder submitted: 'Save as new release') and: [ aSMPackageRelease isCommunitySupported ]) or: [ self currentAccount = aSMPackageRelease package owner or: [ self currentAccount isAdmin ] ] So, if it has the Community Supported category and is a NEW Release being added, it's allowed. Otherwise, only the owner or admin could update the legacy versions. So the Seaside package on SqueakMap is already rocking as a CSP right now. But the entries are only current up to 3.1.1, we should add the latest (3.1.3?). - Chris [1] -- Enshrined as requirement 9 at http://wiki.squeak.org/squeak/6183. > It seems to me that creating a Seaside page and slapping a Metacello > installation script on it is a short sighted solution. Perhaps the notion of > a CSM could be explored at this juncture. > > Chris > > [1] > > (Installer ss project: 'MetacelloRepository') install: > 'ConfigurationOfSeaside3'. > ((ConfigurationOfSeaside3 project) version: #stable) load. > > > > > |
In reply to this post by David T. Lewis
> I like your idea of getting the SqueakMap entry updated, although I'd be
> inclined to follow up on that issue later. How about January 1 as a new > years resolution? Dang, we have a lot of outdated entries on SqueakMap, > we really need to clean that up. Each entry is designated for a specific version of Squeak, so the entries themselves cannot be "outdated". However, you may be referring to the fact that not many new entries were made for 4.5 after it came out. True. |
Free forum by Nabble | Edit this page |