The attached cs is a quick fix-up to get menu option "definition of word" working again. What is the recommended way to package/distribute such a change?
You can save it to
MCHttpRepository location: 'http://source.squeak.org/etoysinbox' user: '' password: ''
Karl
On Thu, Jun 3, 2010 at 12:48 AM, Derek O'Connell doc@doconnel.f9.co.ukwrote:
The attached cs is a quick fix-up to get menu option "definition of word" working again. What is the recommended way to package/distribute such a change?
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
Hi Karl, thanks for the answer. What I don't get is having created a new package entry in Monticello, how then to add just the changes I have made to existing classes?
-D
On 03/06/10 05:33, karl ramberg wrote:
You can save it to
MCHttpRepository location: 'http://source.squeak.org/etoysinbox' user: '' password: ''
Karl
On Thu, Jun 3, 2010 at 12:48 AM, Derek O'Connelldoc@doconnel.f9.co.ukwrote:
The attached cs is a quick fix-up to get menu option "definition of word" working again. What is the recommended way to package/distribute such a change?
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
You don't add a new package. Get a clean dev image, apply your changes, commit the modified package.
- Bert -
Am 03.06.2010 um 09:28 schrieb Derek O'Connell doc@doconnel.f9.co.uk:
Hi Karl, thanks for the answer. What I don't get is having created a new package entry in Monticello, how then to add just the changes I have made to existing classes?
-D
On 03/06/10 05:33, karl ramberg wrote:
You can save it to
MCHttpRepository location: 'http://source.squeak.org/etoysinbox' user: '' password: ''
Karl
On Thu, Jun 3, 2010 at 12:48 AM, Derek O'Connelldoc@doconnel.f9.co.ukwrote:
The attached cs is a quick fix-up to get menu option "definition of word" working again. What is the recommended way to package/distribute such a change?
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On 03/06/10 08:39, Bert Freudenberg wrote:
You don't add a new package. Get a clean dev image, apply your changes, commit the modified package.
Hmmm, yet another image? I already have etoys-to-go, etoys-dev and several other images going back several years and was hoping to concentrate everything in just one image. Only last week I migrated everything I was doing in etoys-to-go to etoys-dev on the basis that the latter has MC which I assumed meant that etoys-dev is *the* image to work in if I want to submit updates/ new stuff. I have yet to work up the enthusiasm for trawling the older images. What are my options if I do not want another image?
-D
- Bert -
Am 03.06.2010 um 09:28 schrieb Derek O'Connelldoc@doconnel.f9.co.uk:
Hi Karl, thanks for the answer. What I don't get is having created a new package entry in Monticello, how then to add just the changes I have made to existing classes?
-D
On 03/06/10 05:33, karl ramberg wrote:
You can save it to
MCHttpRepository location: 'http://source.squeak.org/etoysinbox' user: '' password: ''
Karl
On Thu, Jun 3, 2010 at 12:48 AM, Derek O'Connelldoc@doconnel.f9.co.ukwrote:
The attached cs is a quick fix-up to get menu option "definition of word" working again. What is the recommended way to package/distribute such a change?
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On Thu, Jun 3, 2010 at 5:08 PM, Derek O'Connell doc@doconnel.f9.co.uk wrote:
On 03/06/10 08:39, Bert Freudenberg wrote:
You don't add a new package. Get a clean dev image, apply your changes, commit the modified package.
Hmmm, yet another image? I already have etoys-to-go, etoys-dev and several other images going back several years and was hoping to concentrate everything in just one image. Only last week I migrated everything I was doing in etoys-to-go to etoys-dev on the basis that the latter has MC which I assumed meant that etoys-dev is *the* image to work in if I want to submit updates/ new stuff. I have yet to work up the enthusiasm for trawling the older images. What are my options if I do not want another image?
Derek, you could open ticket with your changeset in tracker. While we have moved to MC based development, proposing changeset via tracker is still welcome.
/Korakurider
-D
- Bert -
Am 03.06.2010 um 09:28 schrieb Derek O'Connelldoc@doconnel.f9.co.uk:
Hi Karl, thanks for the answer. What I don't get is having created a new package entry in Monticello, how then to add just the changes I have made to existing classes?
-D
On 03/06/10 05:33, karl ramberg wrote:
You can save it to
MCHttpRepository location: 'http://source.squeak.org/etoysinbox' user: '' password: ''
Karl
On Thu, Jun 3, 2010 at 12:48 AM, Derek O'Connelldoc@doconnel.f9.co.ukwrote:
The attached cs is a quick fix-up to get menu option "definition of word" working again. What is the recommended way to package/distribute such a change?
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On 03/06/10 09:58, Korakurider wrote:
On Thu, Jun 3, 2010 at 5:08 PM, Derek O'Connelldoc@doconnel.f9.co.uk wrote:
On 03/06/10 08:39, Bert Freudenberg wrote:
You don't add a new package. Get a clean dev image, apply your changes, commit the modified package.
Hmmm, yet another image? I already have etoys-to-go, etoys-dev and several other images going back several years and was hoping to concentrate everything in just one image. Only last week I migrated everything I was doing in etoys-to-go to etoys-dev on the basis that the latter has MC which I assumed meant that etoys-dev is *the* image to work in if I want to submit updates/ new stuff. I have yet to work up the enthusiasm for trawling the older images. What are my options if I do not want another image?
Derek, you could open ticket with your changeset in tracker. While we have moved to MC based development, proposing changesetvia tracker is still welcome.
/Korakurider
Done, thanks for the suggestion!
http://tracker.squeakland.org/browse/SQ-709
-D
- Bert -
Am 03.06.2010 um 09:28 schrieb Derek O'Connelldoc@doconnel.f9.co.uk:
Hi Karl, thanks for the answer. What I don't get is having created a new package entry in Monticello, how then to add just the changes I have made to existing classes?
-D
On 03/06/10 05:33, karl ramberg wrote:
You can save it to
MCHttpRepository location: 'http://source.squeak.org/etoysinbox' user: '' password: ''
Karl
On Thu, Jun 3, 2010 at 12:48 AM, Derek O'Connelldoc@doconnel.f9.co.ukwrote:
The attached cs is a quick fix-up to get menu option "definition of word" working again. What is the recommended way to package/distribute such a change?
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On Thursday 03 Jun 2010 1:38:53 pm Derek O'Connell wrote:
Hmmm, yet another image? I already have etoys-to-go, etoys-dev and several other images going back several years and was hoping to concentrate everything in just one image. Only last week I migrated everything I was doing in etoys-to-go to etoys-dev on the basis that the latter has MC which I assumed meant that etoys-dev is the image to work in if I want to submit updates/ new stuff. I have yet to work up the enthusiasm for trawling the older images. What are my options if I do not want another image?
I used to keep many images around to hold code and notes and the situation got out of hand. Now I only use two images - latest trunk and my own dev (which may lag trunk). Major work goes into MC at squeaksource and rest hang around in local directory as changesets.
Have you seen Bert's video tutorial at http://vimeo.com/7783848
FWIW .. Subbu
Hi Subbu! Hope you are well!
Thanks for the suggestion and the link to the video which I had bookmarked but completely forgot about, very instructive.
-D
On 03/06/10 12:44, K. K. Subramaniam wrote:
On Thursday 03 Jun 2010 1:38:53 pm Derek O'Connell wrote:
Hmmm, yet another image? I already have etoys-to-go, etoys-dev and several other images going back several years and was hoping to concentrate everything in just one image. Only last week I migrated everything I was doing in etoys-to-go to etoys-dev on the basis that the latter has MC which I assumed meant that etoys-dev is the image to work in if I want to submit updates/ new stuff. I have yet to work up the enthusiasm for trawling the older images. What are my options if I do not want another image?
I used to keep many images around to hold code and notes and the situation got out of hand. Now I only use two images - latest trunk and my own dev (which may lag trunk). Major work goes into MC at squeaksource and rest hang around in local directory as changesets.
Have you seen Bert's video tutorial at http://vimeo.com/7783848
FWIW .. Subbu
On 03.06.2010, at 10:08, Derek O'Connell wrote:
On 03/06/10 08:39, Bert Freudenberg wrote:
You don't add a new package. Get a clean dev image, apply your changes, commit the modified package.
Hmmm, yet another image? I already have etoys-to-go, etoys-dev and several other images going back several years and was hoping to concentrate everything in just one image. Only last week I migrated everything I was doing in etoys-to-go to etoys-dev on the basis that the latter has MC which I assumed meant that etoys-dev is *the* image to work in if I want to submit updates/ new stuff.
As long as the basic packages in that etoys-dev image of yours are clean, it's perfect for submitting stuff to the inbox. MC just cannot distinguish between changes you want to submit and private ones. The only way around that is to put private changes in a different package.
The way to check is that before committing to the etoys inbox, compare your changes against the etoys main repository.
- Bert -
I have yet to work up the enthusiasm for trawling the older images. What are my options if I do not want another image?
-D
- Bert -
Am 03.06.2010 um 09:28 schrieb Derek O'Connelldoc@doconnel.f9.co.uk:
Hi Karl, thanks for the answer. What I don't get is having created a new package entry in Monticello, how then to add just the changes I have made to existing classes?
-D
On 03/06/10 05:33, karl ramberg wrote:
You can save it to
MCHttpRepository location: 'http://source.squeak.org/etoysinbox' user: '' password: ''
Karl
On Thu, Jun 3, 2010 at 12:48 AM, Derek O'Connelldoc@doconnel.f9.co.ukwrote:
The attached cs is a quick fix-up to get menu option "definition of word" working again. What is the recommended way to package/distribute such a change?
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On 03/06/10 14:28, Bert Freudenberg wrote:
On 03.06.2010, at 10:08, Derek O'Connell wrote:
On 03/06/10 08:39, Bert Freudenberg wrote:
You don't add a new package. Get a clean dev image, apply your changes, commit the modified package.
Hmmm, yet another image? I already have etoys-to-go, etoys-dev and several other images going back several years and was hoping to concentrate everything in just one image. Only last week I migrated everything I was doing in etoys-to-go to etoys-dev on the basis that the latter has MC which I assumed meant that etoys-dev is *the* image to work in if I want to submit updates/ new stuff.
As long as the basic packages in that etoys-dev image of yours are clean, it's perfect for submitting stuff to the inbox. MC just cannot distinguish between changes you want to submit and private ones. The only way around that is to put private changes in a different package.
The way to check is that before committing to the etoys inbox, compare your changes against the etoys main repository.
- Bert -
ok, got it. I can see now that the safest way would be to keep a separate image for submitting changes so that's what I will do in future. And thanks for taking the time to create that video that Subbu linked to.
-D
I have yet to work up the enthusiasm for trawling the older images. What are my options if I do not want another image?
-D
- Bert -
Am 03.06.2010 um 09:28 schrieb Derek O'Connelldoc@doconnel.f9.co.uk:
Hi Karl, thanks for the answer. What I don't get is having created a new package entry in Monticello, how then to add just the changes I have made to existing classes?
-D
On 03/06/10 05:33, karl ramberg wrote:
You can save it to
MCHttpRepository location: 'http://source.squeak.org/etoysinbox' user: '' password: ''
Karl
On Thu, Jun 3, 2010 at 12:48 AM, Derek O'Connelldoc@doconnel.f9.co.ukwrote:
The attached cs is a quick fix-up to get menu option "definition of word" working again. What is the recommended way to package/distribute such a change?
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
etoys-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
Derek O'Connell -
K. K. Subramaniam -
karl ramberg -
Korakurider