Hi,
I see that Keith has released some Seaside + Magma integration monticellos.
Since he and I are not (yet?) sychronising our efforts, I have posted my integration change set to
http://minnow.cc.gatech.edu/squeak/5817.
This version is compatible with Chris's latest release; the wiki page has all the instructions.
Evaluate "WAStore workspace" if the workspace does not open.
I am sticking with the change set approach as it highlights (to me anyway) how little needs to change to modify the Seaside demo to have a Magma repository.
Comments are welcomed.
Brent
Brent Pinkney wrote:
Hi,
I see that Keith has released some Seaside + Magma integration monticellos.
Since he and I are not (yet?) sychronising our efforts, I have posted my integration change set
I am confused, in order to synchronise efforts we both need to use the same repository, thats what (as far as I am aware) monticello is for. Within monticello there is scope for forking and merging. This happens frequently in the seaside pier repositories. Users like myself tweak a few things and then the maintainer merges in those tweaks into the most recent version which is taken as the 'final' word. I.e. anything with .lr in the pier stream is taken as good ;-)
My releases to monticello is me saying "here you are here is some code, have a go see what you think feedback invited etc", that is my part in the "synchronisation". By you using the changeset approach you seem to be saying that you are not wanting to play.
Monticello is right there, and the user feedback from users using monticello is actually quite good. I got 12 emails telling me what worked and what didnt only yesterday (admittedly from one person). I have a mouse that only goes to the left, a keyboard whose keys stick frequently and the 'w' only works when it wants to. Added to that I am supposed to be a 'carer' now not a 'coder', and life at home is extremely stressful.
How does the changeset approach manage changes to the environment, for example the fix that Lukas provided for FileDirectory for use with seasidehosting?
I am quite dismayed (indeed embarrassed) at how long it is taking me to get pier-magma support working on seasidehosting.
I shall have a look at your changeset, as soon as I am able.
best regards
Keith
___________________________________________________________ All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine http://uk.docs.yahoo.com/nowyoucan.html
Hi Brent, I hope that you and Keith will find a way to synchronise.
Personally, I think Monticello is much more suited to multi-developer work than change sets simply because it tracks the ancestry tree.
I am sticking with the change set approach as it highlights (to me anyway) how little needs to change to modify the Seaside demo to have a Magma repository.
Are you talking about the ability to "Browse code" from Squeaks file-manager so one can see just the deltas? Monticello pretty much offers this too via the "Merge" function. It doesn't provide it in a nice class-like browser, but it does highlight where methods are actually new or modified; to see that in the changeset Code browser you have to select every method.
Unless there's something else about changesets I'm missing, I really don't see any disadvantage to using Monticello..
magma@lists.squeakfoundation.org