http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
I'm trying to automate more and more of the build/release process. See https://github.com/frankshearar/squeak-ci/tree/download-vms for details. (I'll merge this branch back into master at some point in the near future.)
frank
On 23 December 2012 19:09, Frank Shearar frank.shearar@gmail.com wrote:
http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
I'm trying to automate more and more of the build/release process. See https://github.com/frankshearar/squeak-ci/tree/download-vms for details. (I'll merge this branch back into master at some point in the near future.)
This does _not_ address Bert's issue about the positioning of the Squeak window; it's just an illustration of yet another piece of automation. I like automation.
frank
On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com wrote:
On 23 December 2012 19:09, Frank Shearar frank.shearar@gmail.com wrote:
http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
I'm trying to automate more and more of the build/release process. See https://github.com/frankshearar/squeak-ci/tree/download-vms for details. (I'll merge this branch back into master at some point in the near future.)
This does _not_ address Bert's issue about the positioning of the Squeak window; it's just an illustration of yet another piece of automation. I like automation.
I see three dirty packages, all dirty - apparently - because of package restructurings.
* FlexibleVocabularies - FlexibleVocabularies-Info removed? * Multilingual - Multilingual-Editor added? * SMLoader - looks like SMLoader-Models was removed?
(I may have the situation reversed; I'm not sure whether "old" refers to the blue strikeout text or the red, nor whether "old" refers to the image or to trunk.)
frank
Though it has version number 12324 it still shows the rice-paper background and has a 'welcome to Squeak 4.3' workspace.
--Hannes
On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote:
On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com wrote:
On 23 December 2012 19:09, Frank Shearar frank.shearar@gmail.com wrote:
http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
I'm trying to automate more and more of the build/release process. See https://github.com/frankshearar/squeak-ci/tree/download-vms for details. (I'll merge this branch back into master at some point in the near future.)
This does _not_ address Bert's issue about the positioning of the Squeak window; it's just an illustration of yet another piece of automation. I like automation.
I see three dirty packages, all dirty - apparently - because of package restructurings.
- FlexibleVocabularies - FlexibleVocabularies-Info removed?
- Multilingual - Multilingual-Editor added?
- SMLoader - looks like SMLoader-Models was removed?
(I may have the situation reversed; I'm not sure whether "old" refers to the blue strikeout text or the red, nor whether "old" refers to the image or to trunk.)
frank
On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com wrote:
Though it has version number 12324 it still shows the rice-paper background and has a 'welcome to Squeak 4.3' workspace.
Oh crumbs. Thanks, Hannes, I must have an error in my script.
frank
--Hannes
On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote:
On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com wrote:
On 23 December 2012 19:09, Frank Shearar frank.shearar@gmail.com wrote:
http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
I'm trying to automate more and more of the build/release process. See https://github.com/frankshearar/squeak-ci/tree/download-vms for details. (I'll merge this branch back into master at some point in the near future.)
This does _not_ address Bert's issue about the positioning of the Squeak window; it's just an illustration of yet another piece of automation. I like automation.
I see three dirty packages, all dirty - apparently - because of package restructurings.
- FlexibleVocabularies - FlexibleVocabularies-Info removed?
- Multilingual - Multilingual-Editor added?
- SMLoader - looks like SMLoader-Models was removed?
(I may have the situation reversed; I'm not sure whether "old" refers to the blue strikeout text or the red, nor whether "old" refers to the image or to trunk.)
frank
On 24 December 2012 09:18, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com wrote:
Though it has version number 12324 it still shows the rice-paper background and has a 'welcome to Squeak 4.3' workspace.
Oh crumbs. Thanks, Hannes, I must have an error in my script.
http://squeakci.org/job/ReleaseSqueakTrunk/17/
frank
--Hannes
On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote:
On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com wrote:
On 23 December 2012 19:09, Frank Shearar frank.shearar@gmail.com wrote:
http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
I'm trying to automate more and more of the build/release process. See https://github.com/frankshearar/squeak-ci/tree/download-vms for details. (I'll merge this branch back into master at some point in the near future.)
This does _not_ address Bert's issue about the positioning of the Squeak window; it's just an illustration of yet another piece of automation. I like automation.
I see three dirty packages, all dirty - apparently - because of package restructurings.
- FlexibleVocabularies - FlexibleVocabularies-Info removed?
- Multilingual - Multilingual-Editor added?
- SMLoader - looks like SMLoader-Models was removed?
(I may have the situation reversed; I'm not sure whether "old" refers to the blue strikeout text or the red, nor whether "old" refers to the image or to trunk.)
frank
Frank,
where can I have a look at the build script?
And the console output is not very talkative....
http://squeakci.org/job/ReleaseSqueakTrunk/17/console
--Hannes
On 12/24/12, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 09:18, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com wrote:
Though it has version number 12324 it still shows the rice-paper background and has a 'welcome to Squeak 4.3' workspace.
Oh crumbs. Thanks, Hannes, I must have an error in my script.
http://squeakci.org/job/ReleaseSqueakTrunk/17/
frank
--Hannes
On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote:
On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com wrote:
On 23 December 2012 19:09, Frank Shearar frank.shearar@gmail.com wrote:
http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
I'm trying to automate more and more of the build/release process. See https://github.com/frankshearar/squeak-ci/tree/download-vms for details. (I'll merge this branch back into master at some point in the near future.)
This does _not_ address Bert's issue about the positioning of the Squeak window; it's just an illustration of yet another piece of automation. I like automation.
I see three dirty packages, all dirty - apparently - because of package restructurings.
- FlexibleVocabularies - FlexibleVocabularies-Info removed?
- Multilingual - Multilingual-Editor added?
- SMLoader - looks like SMLoader-Models was removed?
(I may have the situation reversed; I'm not sure whether "old" refers to the blue strikeout text or the red, nor whether "old" refers to the image or to trunk.)
frank
On 27 December 2012 11:00, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
where can I have a look at the build script?
And the console output is not very talkative....
* https://github.com/frankshearar/squeak-ci/blob/download-vms/release.sh * https://github.com/frankshearar/squeak-ci/blob/download-vms/release.st
No, the scripts are not talkative at all. I'm really not sure how to make them more talkative. Obviously in the shell scripts you can use echo, but those do hardly anything. Really what I want is something that writes to the Transcript when headful and to stdout/stderr when headless. I don't think we have such a thing at the moment.
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
frank
--Hannes
On 12/24/12, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 09:18, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com wrote:
Though it has version number 12324 it still shows the rice-paper background and has a 'welcome to Squeak 4.3' workspace.
Oh crumbs. Thanks, Hannes, I must have an error in my script.
http://squeakci.org/job/ReleaseSqueakTrunk/17/
frank
--Hannes
On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote:
On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com wrote:
On 23 December 2012 19:09, Frank Shearar frank.shearar@gmail.com wrote: > http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ... > > I'm trying to automate more and more of the build/release process. > See > https://github.com/frankshearar/squeak-ci/tree/download-vms for > details. (I'll merge this branch back into master at some point in > the > near future.)
This does _not_ address Bert's issue about the positioning of the Squeak window; it's just an illustration of yet another piece of automation. I like automation.
I see three dirty packages, all dirty - apparently - because of package restructurings.
- FlexibleVocabularies - FlexibleVocabularies-Info removed?
- Multilingual - Multilingual-Editor added?
- SMLoader - looks like SMLoader-Models was removed?
(I may have the situation reversed; I'm not sure whether "old" refers to the blue strikeout text or the red, nor whether "old" refers to the image or to trunk.)
frank
Frank,
On 12/27/12, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:00, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
where can I have a look at the build script?
And the console output is not very talkative....
OK, so the following bash script
#! /bin/sh
# This script takes the output of builtastic.sh and creates a releasable # artifact.
SRC=$(cd $(dirname "$0"); pwd) . "${SRC}/versions.sh" . "${SRC}/functions.sh"
SQUEAK_VERSION=`cat ${SRC}/target/TrunkImage.version` BASENAME=Squeak4.4-${SQUEAK_VERSION}
build_interpreter_vm
echo Using ${INTERPRETER_VM} echo Preparing ${BASENAME}... cp ${SRC}/target/TrunkImage.changes ${SRC}/target/${BASENAME}.changes cp ${SRC}/target/TrunkImage.image ${SRC}/target/${BASENAME}.image
chmod +w ${SRC}/target/${BASENAME}.changes chmod +w ${SRC}/target/${BASENAME}.image
echo Releasing ${BASENAME}... ${INTERPRETER_VM} -vm-sound-null -vm-display-null ${SRC}/target /${BASENAME}.image ${SRC}/release.st
echo Zipping ${BASENAME}... # Previous runs might leave a zip lying around. rm ${SRC}/target/${BASENAME}.zip (cd ${SRC}/target; zip -j ${BASENAME}.zip ${BASENAME}.changes ${BASENAME}.image)
CALLS the SMALLTALK script
Form openAsBackground: (FileDirectory default / '..' / 'resources/wallpaper.png') pathName. Workspace allInstances do: [:w | w topView delete]. ReleaseBuilderFor4dot4 prepareNewBuild. Smalltalk snapshot: true andQuit: true.
Just by inspection (and with the knowledge that the version number of the resulting image is correct) it seems that the error might be in the Smalltalk script.
NOTE: Anybody who downloads the latest trunk image and executes the above Smalltalk script is in the position to find the error....... (hint, hint to everybody...)
No, the scripts are not talkative at all. I'm really not sure how to make them more talkative. Obviously in the shell scripts you can use echo, but those do hardly anything. Really what I want is something that writes to the Transcript when headful and to stdout/stderr when headless. I don't think we have such a thing at the moment.
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
I am actually very fine with the scaffolding script in the image, reason see the note above.
And in addition this is what Andreas suggested in his memo which is cited in the welcome window. External packages configurations / scripts which are community supported should be in the image...
--Hannes
frank
--Hannes
On 12/24/12, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 09:18, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com wrote:
Though it has version number 12324 it still shows the rice-paper background and has a 'welcome to Squeak 4.3' workspace.
Oh crumbs. Thanks, Hannes, I must have an error in my script.
http://squeakci.org/job/ReleaseSqueakTrunk/17/
frank
--Hannes
On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote:
On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com wrote: > On 23 December 2012 19:09, Frank Shearar frank.shearar@gmail.com > wrote: >> http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ... >> >> I'm trying to automate more and more of the build/release process. >> See >> https://github.com/frankshearar/squeak-ci/tree/download-vms for >> details. (I'll merge this branch back into master at some point in >> the >> near future.) > > This does _not_ address Bert's issue about the positioning of the > Squeak window; it's just an illustration of yet another piece of > automation. I like automation.
I see three dirty packages, all dirty - apparently - because of package restructurings.
- FlexibleVocabularies - FlexibleVocabularies-Info removed?
- Multilingual - Multilingual-Editor added?
- SMLoader - looks like SMLoader-Models was removed?
(I may have the situation reversed; I'm not sure whether "old" refers to the blue strikeout text or the red, nor whether "old" refers to the image or to trunk.)
frank
On 27 December 2012 11:48, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
On 12/27/12, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:00, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
where can I have a look at the build script?
And the console output is not very talkative....
OK, so the following bash script
#! /bin/sh # This script takes the output of builtastic.sh and creates a releasable # artifact. SRC=$(cd $(dirname "$0"); pwd) . "${SRC}/versions.sh" . "${SRC}/functions.sh" SQUEAK_VERSION=`cat ${SRC}/target/TrunkImage.version` BASENAME=Squeak4.4-${SQUEAK_VERSION} build_interpreter_vm echo Using ${INTERPRETER_VM} echo Preparing ${BASENAME}... cp ${SRC}/target/TrunkImage.changes ${SRC}/target/${BASENAME}.changes cp ${SRC}/target/TrunkImage.image ${SRC}/target/${BASENAME}.image chmod +w ${SRC}/target/${BASENAME}.changes chmod +w ${SRC}/target/${BASENAME}.image echo Releasing ${BASENAME}... ${INTERPRETER_VM} -vm-sound-null -vm-display-null ${SRC}/target/${BASENAME}.image ${SRC}/release.st
echo Zipping ${BASENAME}... # Previous runs might leave a zip lying around. rm ${SRC}/target/${BASENAME}.zip (cd ${SRC}/target; zip -j ${BASENAME}.zip ${BASENAME}.changes${BASENAME}.image)
CALLS the SMALLTALK script
Form openAsBackground: (FileDirectory default / '..' /'resources/wallpaper.png') pathName. Workspace allInstances do: [:w | w topView delete]. ReleaseBuilderFor4dot4 prepareNewBuild. Smalltalk snapshot: true andQuit: true.
Just by inspection (and with the knowledge that the version number of the resulting image is correct) it seems that the error might be in the Smalltalk script.
What error? There _was_ an error, that you reported a few days, but that should be fixed. Have you looked at output of the latestSuccessfulBuild for that job?
frank
NOTE: Anybody who downloads the latest trunk image and executes the above Smalltalk script is in the position to find the error....... (hint, hint to everybody...)
No, the scripts are not talkative at all. I'm really not sure how to make them more talkative. Obviously in the shell scripts you can use echo, but those do hardly anything. Really what I want is something that writes to the Transcript when headful and to stdout/stderr when headless. I don't think we have such a thing at the moment.
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
I am actually very fine with the scaffolding script in the image, reason see the note above.
And in addition this is what Andreas suggested in his memo which is cited in the welcome window. External packages configurations / scripts which are community supported should be in the image...
--Hannes
frank
--Hannes
On 12/24/12, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 09:18, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com wrote:
Though it has version number 12324 it still shows the rice-paper background and has a 'welcome to Squeak 4.3' workspace.
Oh crumbs. Thanks, Hannes, I must have an error in my script.
http://squeakci.org/job/ReleaseSqueakTrunk/17/
frank
--Hannes
On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote: > On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com > wrote: >> On 23 December 2012 19:09, Frank Shearar frank.shearar@gmail.com >> wrote: >>> http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ... >>> >>> I'm trying to automate more and more of the build/release process. >>> See >>> https://github.com/frankshearar/squeak-ci/tree/download-vms for >>> details. (I'll merge this branch back into master at some point in >>> the >>> near future.) >> >> This does _not_ address Bert's issue about the positioning of the >> Squeak window; it's just an illustration of yet another piece of >> automation. I like automation. > > I see three dirty packages, all dirty - apparently - because of > package restructurings. > > * FlexibleVocabularies - FlexibleVocabularies-Info removed? > * Multilingual - Multilingual-Editor added? > * SMLoader - looks like SMLoader-Models was removed? > > (I may have the situation reversed; I'm not sure whether "old" refers > to the blue strikeout text or the red, nor whether "old" refers to > the > image or to trunk.) > > frank > >
On 27 December 2012 11:55, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:48, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
On 12/27/12, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:00, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
where can I have a look at the build script?
And the console output is not very talkative....
OK, so the following bash script
#! /bin/sh # This script takes the output of builtastic.sh and creates a releasable # artifact. SRC=$(cd $(dirname "$0"); pwd) . "${SRC}/versions.sh" . "${SRC}/functions.sh" SQUEAK_VERSION=`cat ${SRC}/target/TrunkImage.version` BASENAME=Squeak4.4-${SQUEAK_VERSION} build_interpreter_vm echo Using ${INTERPRETER_VM} echo Preparing ${BASENAME}... cp ${SRC}/target/TrunkImage.changes ${SRC}/target/${BASENAME}.changes cp ${SRC}/target/TrunkImage.image ${SRC}/target/${BASENAME}.image chmod +w ${SRC}/target/${BASENAME}.changes chmod +w ${SRC}/target/${BASENAME}.image echo Releasing ${BASENAME}... ${INTERPRETER_VM} -vm-sound-null -vm-display-null ${SRC}/target/${BASENAME}.image ${SRC}/release.st
echo Zipping ${BASENAME}... # Previous runs might leave a zip lying around. rm ${SRC}/target/${BASENAME}.zip (cd ${SRC}/target; zip -j ${BASENAME}.zip ${BASENAME}.changes${BASENAME}.image)
CALLS the SMALLTALK script
Form openAsBackground: (FileDirectory default / '..' /'resources/wallpaper.png') pathName. Workspace allInstances do: [:w | w topView delete]. ReleaseBuilderFor4dot4 prepareNewBuild. Smalltalk snapshot: true andQuit: true.
Just by inspection (and with the knowledge that the version number of the resulting image is correct) it seems that the error might be in the Smalltalk script.
What error? There _was_ an error, that you reported a few days, but that should be fixed. Have you looked at output of the latestSuccessfulBuild for that job?
Er, right. Maybe it would have helped me _saying_ that I'd fixed the error you reported!
frank
NOTE: Anybody who downloads the latest trunk image and executes the above Smalltalk script is in the position to find the error....... (hint, hint to everybody...)
No, the scripts are not talkative at all. I'm really not sure how to make them more talkative. Obviously in the shell scripts you can use echo, but those do hardly anything. Really what I want is something that writes to the Transcript when headful and to stdout/stderr when headless. I don't think we have such a thing at the moment.
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
I am actually very fine with the scaffolding script in the image, reason see the note above.
And in addition this is what Andreas suggested in his memo which is cited in the welcome window. External packages configurations / scripts which are community supported should be in the image...
--Hannes
frank
--Hannes
On 12/24/12, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 09:18, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com wrote: > Though it has version number 12324 it still shows the rice-paper > background and has a 'welcome to Squeak 4.3' workspace.
Oh crumbs. Thanks, Hannes, I must have an error in my script.
http://squeakci.org/job/ReleaseSqueakTrunk/17/
frank
> --Hannes > > On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote: >> On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com >> wrote: >>> On 23 December 2012 19:09, Frank Shearar frank.shearar@gmail.com >>> wrote: >>>> http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ... >>>> >>>> I'm trying to automate more and more of the build/release process. >>>> See >>>> https://github.com/frankshearar/squeak-ci/tree/download-vms for >>>> details. (I'll merge this branch back into master at some point in >>>> the >>>> near future.) >>> >>> This does _not_ address Bert's issue about the positioning of the >>> Squeak window; it's just an illustration of yet another piece of >>> automation. I like automation. >> >> I see three dirty packages, all dirty - apparently - because of >> package restructurings. >> >> * FlexibleVocabularies - FlexibleVocabularies-Info removed? >> * Multilingual - Multilingual-Editor added? >> * SMLoader - looks like SMLoader-Models was removed? >> >> (I may have the situation reversed; I'm not sure whether "old" refers >> to the blue strikeout text or the red, nor whether "old" refers to >> the >> image or to trunk.) >> >> frank >> >> >
You mean I have to re-download http://www.squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/... ?
I would have expected a note and/or a higher version number....
On 12/27/12, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:55, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:48, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
On 12/27/12, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:00, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
where can I have a look at the build script?
And the console output is not very talkative....
https://github.com/frankshearar/squeak-ci/blob/download-vms/release.sh
OK, so the following bash script
#! /bin/sh # This script takes the output of builtastic.sh and creates areleasable # artifact.
SRC=$(cd $(dirname "$0"); pwd) . "${SRC}/versions.sh" . "${SRC}/functions.sh" SQUEAK_VERSION=`cat ${SRC}/target/TrunkImage.version` BASENAME=Squeak4.4-${SQUEAK_VERSION} build_interpreter_vm echo Using ${INTERPRETER_VM} echo Preparing ${BASENAME}... cp ${SRC}/target/TrunkImage.changes${SRC}/target/${BASENAME}.changes cp ${SRC}/target/TrunkImage.image ${SRC}/target/${BASENAME}.image
chmod +w ${SRC}/target/${BASENAME}.changes chmod +w ${SRC}/target/${BASENAME}.image echo Releasing ${BASENAME}... ${INTERPRETER_VM} -vm-sound-null -vm-display-null ${SRC}/target/${BASENAME}.image ${SRC}/release.st
echo Zipping ${BASENAME}... # Previous runs might leave a zip lying around. rm ${SRC}/target/${BASENAME}.zip (cd ${SRC}/target; zip -j ${BASENAME}.zip ${BASENAME}.changes${BASENAME}.image)
CALLS the SMALLTALK script
https://github.com/frankshearar/squeak-ci/blob/download-vms/release.st
Form openAsBackground: (FileDirectory default / '..' /'resources/wallpaper.png') pathName. Workspace allInstances do: [:w | w topView delete]. ReleaseBuilderFor4dot4 prepareNewBuild. Smalltalk snapshot: true andQuit: true.
Just by inspection (and with the knowledge that the version number of the resulting image is correct) it seems that the error might be in the Smalltalk script.
What error? There _was_ an error, that you reported a few days, but that should be fixed. Have you looked at output of the latestSuccessfulBuild for that job?
Er, right. Maybe it would have helped me _saying_ that I'd fixed the error you reported!
frank
NOTE: Anybody who downloads the latest trunk image and executes the above Smalltalk script is in the position to find the error....... (hint, hint to everybody...)
No, the scripts are not talkative at all. I'm really not sure how to make them more talkative. Obviously in the shell scripts you can use echo, but those do hardly anything. Really what I want is something that writes to the Transcript when headful and to stdout/stderr when headless. I don't think we have such a thing at the moment.
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
I am actually very fine with the scaffolding script in the image, reason see the note above.
And in addition this is what Andreas suggested in his memo which is cited in the welcome window. External packages configurations / scripts which are community supported should be in the image...
--Hannes
frank
--Hannes
On 12/24/12, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 09:18, Frank Shearar frank.shearar@gmail.com wrote: > On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com > wrote: >> Though it has version number 12324 it still shows the rice-paper >> background and has a 'welcome to Squeak 4.3' workspace. > > Oh crumbs. Thanks, Hannes, I must have an error in my script.
http://squeakci.org/job/ReleaseSqueakTrunk/17/
> frank > >> --Hannes >> >> On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote: >>> On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com >>> wrote: >>>> On 23 December 2012 19:09, Frank Shearar >>>> frank.shearar@gmail.com >>>> wrote: >>>>> http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ... >>>>> >>>>> I'm trying to automate more and more of the build/release >>>>> process. >>>>> See >>>>> https://github.com/frankshearar/squeak-ci/tree/download-vms for >>>>> details. (I'll merge this branch back into master at some point >>>>> in >>>>> the >>>>> near future.) >>>> >>>> This does _not_ address Bert's issue about the positioning of the >>>> Squeak window; it's just an illustration of yet another piece of >>>> automation. I like automation. >>> >>> I see three dirty packages, all dirty - apparently - because of >>> package restructurings. >>> >>> * FlexibleVocabularies - FlexibleVocabularies-Info removed? >>> * Multilingual - Multilingual-Editor added? >>> * SMLoader - looks like SMLoader-Models was removed? >>> >>> (I may have the situation reversed; I'm not sure whether "old" >>> refers >>> to the blue strikeout text or the red, nor whether "old" refers to >>> the >>> image or to trunk.) >>> >>> frank >>> >>> >>
Indeed, 4.4
as of http://www.squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/...
now shows the '4.4 Welcome screen'. The script is fixed.
Thank you, Frank
--Hannes
On 12/27/12, H. Hirzel hannes.hirzel@gmail.com wrote:
You mean I have to re-download http://www.squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/... ?
I would have expected a note and/or a higher version number....
On 12/27/12, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:55, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:48, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
On 12/27/12, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:00, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
where can I have a look at the build script?
And the console output is not very talkative....
https://github.com/frankshearar/squeak-ci/blob/download-vms/release.sh
OK, so the following bash script
#! /bin/sh # This script takes the output of builtastic.sh and creates areleasable # artifact.
SRC=$(cd $(dirname "$0"); pwd) . "${SRC}/versions.sh" . "${SRC}/functions.sh" SQUEAK_VERSION=`cat ${SRC}/target/TrunkImage.version` BASENAME=Squeak4.4-${SQUEAK_VERSION} build_interpreter_vm echo Using ${INTERPRETER_VM} echo Preparing ${BASENAME}... cp ${SRC}/target/TrunkImage.changes${SRC}/target/${BASENAME}.changes cp ${SRC}/target/TrunkImage.image ${SRC}/target/${BASENAME}.image
chmod +w ${SRC}/target/${BASENAME}.changes chmod +w ${SRC}/target/${BASENAME}.image echo Releasing ${BASENAME}... ${INTERPRETER_VM} -vm-sound-null -vm-display-null ${SRC}/target/${BASENAME}.image ${SRC}/release.st
echo Zipping ${BASENAME}... # Previous runs might leave a zip lying around. rm ${SRC}/target/${BASENAME}.zip (cd ${SRC}/target; zip -j ${BASENAME}.zip ${BASENAME}.changes${BASENAME}.image)
CALLS the SMALLTALK script
https://github.com/frankshearar/squeak-ci/blob/download-vms/release.st
Form openAsBackground: (FileDirectory default / '..' /'resources/wallpaper.png') pathName. Workspace allInstances do: [:w | w topView delete]. ReleaseBuilderFor4dot4 prepareNewBuild. Smalltalk snapshot: true andQuit: true.
Just by inspection (and with the knowledge that the version number of the resulting image is correct) it seems that the error might be in the Smalltalk script.
What error? There _was_ an error, that you reported a few days, but that should be fixed. Have you looked at output of the latestSuccessfulBuild for that job?
Er, right. Maybe it would have helped me _saying_ that I'd fixed the error you reported!
frank
NOTE: Anybody who downloads the latest trunk image and executes the above Smalltalk script is in the position to find the error....... (hint, hint to everybody...)
No, the scripts are not talkative at all. I'm really not sure how to make them more talkative. Obviously in the shell scripts you can use echo, but those do hardly anything. Really what I want is something that writes to the Transcript when headful and to stdout/stderr when headless. I don't think we have such a thing at the moment.
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
I am actually very fine with the scaffolding script in the image, reason see the note above.
And in addition this is what Andreas suggested in his memo which is cited in the welcome window. External packages configurations / scripts which are community supported should be in the image...
--Hannes
frank
--Hannes
On 12/24/12, Frank Shearar frank.shearar@gmail.com wrote: > On 24 December 2012 09:18, Frank Shearar frank.shearar@gmail.com > wrote: >> On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com >> wrote: >>> Though it has version number 12324 it still shows the rice-paper >>> background and has a 'welcome to Squeak 4.3' workspace. >> >> Oh crumbs. Thanks, Hannes, I must have an error in my script. > > http://squeakci.org/job/ReleaseSqueakTrunk/17/ > >> frank >> >>> --Hannes >>> >>> On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote: >>>> On 23 December 2012 19:14, Frank Shearar >>>> frank.shearar@gmail.com >>>> wrote: >>>>> On 23 December 2012 19:09, Frank Shearar >>>>> frank.shearar@gmail.com >>>>> wrote: >>>>>> http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ... >>>>>> >>>>>> I'm trying to automate more and more of the build/release >>>>>> process. >>>>>> See >>>>>> https://github.com/frankshearar/squeak-ci/tree/download-vms for >>>>>> details. (I'll merge this branch back into master at some point >>>>>> in >>>>>> the >>>>>> near future.) >>>>> >>>>> This does _not_ address Bert's issue about the positioning of >>>>> the >>>>> Squeak window; it's just an illustration of yet another piece of >>>>> automation. I like automation. >>>> >>>> I see three dirty packages, all dirty - apparently - because of >>>> package restructurings. >>>> >>>> * FlexibleVocabularies - FlexibleVocabularies-Info removed? >>>> * Multilingual - Multilingual-Editor added? >>>> * SMLoader - looks like SMLoader-Models was removed? >>>> >>>> (I may have the situation reversed; I'm not sure whether "old" >>>> refers >>>> to the blue strikeout text or the red, nor whether "old" refers >>>> to >>>> the >>>> image or to trunk.) >>>> >>>> frank >>>> >>>> >>> > >
On 27 December 2012 12:29, H. Hirzel hannes.hirzel@gmail.com wrote:
You mean I have to re-download http://www.squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/... ?
I would have expected a note and/or a higher version number....
The version number is the update number. Since the error was in the release script, fixing the error didn't result in pushing anything to the Trunk, hence no new update, hence the version number remained the same.
Something else the release script/s need is better diagnostics: the problem was that something went wrong and the scripts didn't bail out.
Oh, and you're right re the scripts: the release.sh feeds the release.st as a startup script into the image to be released. The Smalltalk then executes as DoIts. You can see these if you try Recover Changes.
frank
On 12/27/12, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:55, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:48, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
On 12/27/12, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:00, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
where can I have a look at the build script?
And the console output is not very talkative....
https://github.com/frankshearar/squeak-ci/blob/download-vms/release.sh
OK, so the following bash script
#! /bin/sh # This script takes the output of builtastic.sh and creates areleasable # artifact.
SRC=$(cd $(dirname "$0"); pwd) . "${SRC}/versions.sh" . "${SRC}/functions.sh" SQUEAK_VERSION=`cat ${SRC}/target/TrunkImage.version` BASENAME=Squeak4.4-${SQUEAK_VERSION} build_interpreter_vm echo Using ${INTERPRETER_VM} echo Preparing ${BASENAME}... cp ${SRC}/target/TrunkImage.changes${SRC}/target/${BASENAME}.changes cp ${SRC}/target/TrunkImage.image ${SRC}/target/${BASENAME}.image
chmod +w ${SRC}/target/${BASENAME}.changes chmod +w ${SRC}/target/${BASENAME}.image echo Releasing ${BASENAME}... ${INTERPRETER_VM} -vm-sound-null -vm-display-null ${SRC}/target/${BASENAME}.image ${SRC}/release.st
echo Zipping ${BASENAME}... # Previous runs might leave a zip lying around. rm ${SRC}/target/${BASENAME}.zip (cd ${SRC}/target; zip -j ${BASENAME}.zip ${BASENAME}.changes${BASENAME}.image)
CALLS the SMALLTALK script
https://github.com/frankshearar/squeak-ci/blob/download-vms/release.st
Form openAsBackground: (FileDirectory default / '..' /'resources/wallpaper.png') pathName. Workspace allInstances do: [:w | w topView delete]. ReleaseBuilderFor4dot4 prepareNewBuild. Smalltalk snapshot: true andQuit: true.
Just by inspection (and with the knowledge that the version number of the resulting image is correct) it seems that the error might be in the Smalltalk script.
What error? There _was_ an error, that you reported a few days, but that should be fixed. Have you looked at output of the latestSuccessfulBuild for that job?
Er, right. Maybe it would have helped me _saying_ that I'd fixed the error you reported!
frank
NOTE: Anybody who downloads the latest trunk image and executes the above Smalltalk script is in the position to find the error....... (hint, hint to everybody...)
No, the scripts are not talkative at all. I'm really not sure how to make them more talkative. Obviously in the shell scripts you can use echo, but those do hardly anything. Really what I want is something that writes to the Transcript when headful and to stdout/stderr when headless. I don't think we have such a thing at the moment.
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
I am actually very fine with the scaffolding script in the image, reason see the note above.
And in addition this is what Andreas suggested in his memo which is cited in the welcome window. External packages configurations / scripts which are community supported should be in the image...
--Hannes
frank
--Hannes
On 12/24/12, Frank Shearar frank.shearar@gmail.com wrote: > On 24 December 2012 09:18, Frank Shearar frank.shearar@gmail.com > wrote: >> On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com >> wrote: >>> Though it has version number 12324 it still shows the rice-paper >>> background and has a 'welcome to Squeak 4.3' workspace. >> >> Oh crumbs. Thanks, Hannes, I must have an error in my script. > > http://squeakci.org/job/ReleaseSqueakTrunk/17/ > >> frank >> >>> --Hannes >>> >>> On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote: >>>> On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com >>>> wrote: >>>>> On 23 December 2012 19:09, Frank Shearar >>>>> frank.shearar@gmail.com >>>>> wrote: >>>>>> http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ... >>>>>> >>>>>> I'm trying to automate more and more of the build/release >>>>>> process. >>>>>> See >>>>>> https://github.com/frankshearar/squeak-ci/tree/download-vms for >>>>>> details. (I'll merge this branch back into master at some point >>>>>> in >>>>>> the >>>>>> near future.) >>>>> >>>>> This does _not_ address Bert's issue about the positioning of the >>>>> Squeak window; it's just an illustration of yet another piece of >>>>> automation. I like automation. >>>> >>>> I see three dirty packages, all dirty - apparently - because of >>>> package restructurings. >>>> >>>> * FlexibleVocabularies - FlexibleVocabularies-Info removed? >>>> * Multilingual - Multilingual-Editor added? >>>> * SMLoader - looks like SMLoader-Models was removed? >>>> >>>> (I may have the situation reversed; I'm not sure whether "old" >>>> refers >>>> to the blue strikeout text or the red, nor whether "old" refers to >>>> the >>>> image or to trunk.) >>>> >>>> frank >>>> >>>> >>> > >
Just installed 4.4 RC3 on FreeBSD 9.1 RC3 and it comes up fine. No time just now to try things out. Looking forward to improvements in the text editing ... this was driving be bananas. Thanks, all!!
On Thu, Dec 27, 2012 at 1:48 AM, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
On 12/27/12, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:00, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
where can I have a look at the build script?
And the console output is not very talkative....
OK, so the following bash script
#! /bin/sh # This script takes the output of builtastic.sh and creates areleasable # artifact.
SRC=$(cd $(dirname "$0"); pwd) . "${SRC}/versions.sh" . "${SRC}/functions.sh" SQUEAK_VERSION=`cat ${SRC}/target/TrunkImage.version` BASENAME=Squeak4.4-${SQUEAK_VERSION} build_interpreter_vm echo Using ${INTERPRETER_VM} echo Preparing ${BASENAME}... cp ${SRC}/target/TrunkImage.changes ${SRC}/target/${BASENAME}.changes cp ${SRC}/target/TrunkImage.image ${SRC}/target/${BASENAME}.image chmod +w ${SRC}/target/${BASENAME}.changes chmod +w ${SRC}/target/${BASENAME}.image echo Releasing ${BASENAME}... ${INTERPRETER_VM} -vm-sound-null -vm-display-null ${SRC}/target/${BASENAME}.image ${SRC}/release.st
echo Zipping ${BASENAME}... # Previous runs might leave a zip lying around. rm ${SRC}/target/${BASENAME}.zip (cd ${SRC}/target; zip -j ${BASENAME}.zip ${BASENAME}.changes${BASENAME}.image)
CALLS the SMALLTALK script
Form openAsBackground: (FileDirectory default / '..' /'resources/wallpaper.png') pathName. Workspace allInstances do: [:w | w topView delete]. ReleaseBuilderFor4dot4 prepareNewBuild. Smalltalk snapshot: true andQuit: true.
Just by inspection (and with the knowledge that the version number of the resulting image is correct) it seems that the error might be in the Smalltalk script.
NOTE: Anybody who downloads the latest trunk image and executes the above Smalltalk script is in the position to find the error....... (hint, hint to everybody...)
No, the scripts are not talkative at all. I'm really not sure how to make them more talkative. Obviously in the shell scripts you can use echo, but those do hardly anything. Really what I want is something that writes to the Transcript when headful and to stdout/stderr when headless. I don't think we have such a thing at the moment.
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
I am actually very fine with the scaffolding script in the image, reason see the note above.
And in addition this is what Andreas suggested in his memo which is cited in the welcome window. External packages configurations / scripts which are community supported should be in the image...
--Hannes
frank
--Hannes
On 12/24/12, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 09:18, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com wrote:
Though it has version number 12324 it still shows the rice-paper background and has a 'welcome to Squeak 4.3' workspace.
Oh crumbs. Thanks, Hannes, I must have an error in my script.
http://squeakci.org/job/ReleaseSqueakTrunk/17/
frank
--Hannes
On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote: > On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com > wrote: >> On 23 December 2012 19:09, Frank Shearar frank.shearar@gmail.com >> wrote: >>>
http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
>>> >>> I'm trying to automate more and more of the build/release process. >>> See >>> https://github.com/frankshearar/squeak-ci/tree/download-vms for >>> details. (I'll merge this branch back into master at some point in >>> the >>> near future.) >> >> This does _not_ address Bert's issue about the positioning of the >> Squeak window; it's just an illustration of yet another piece of >> automation. I like automation. > > I see three dirty packages, all dirty - apparently - because of > package restructurings. > > * FlexibleVocabularies - FlexibleVocabularies-Info removed? > * Multilingual - Multilingual-Editor added? > * SMLoader - looks like SMLoader-Models was removed? > > (I may have the situation reversed; I'm not sure whether "old"
refers
> to the blue strikeout text or the red, nor whether "old" refers to > the > image or to trunk.) > > frank > >
OK, just loaded one of my projects and started poking around. This is by no means exhaustive, just what I happened to notice. On the "welcome" screen it says "Cleanup and simplification of Morphic text editing" but an old "feature" (bug) is still there. If I type "The second word is bold" and want to make the second word bold I double-click on "second" to select the word, then right-click to bring up a pop-up menu where I expect to be able to do that. The options available are
set font ... (k) set style ... (k) set alignment ... (u)
Setting a word bold should be on the style option, but when I select it I get a font selection tool. The first choice also leads to a font setting tool, although it is different. Neither offers bold, underline, italic, etc. The alignment choice does offer alignment options. If I halo the text and click Brown FF I get what I want, plus options to set alignment. Here is a clue: both of the first two options on the pop-menu show the same keyboard shortcut of k, which actually does what "set font" does. Seems as though the definition for the "set style" choice needs some adjustment.
On Thu, Dec 27, 2012 at 4:18 PM, Open Slate openslateproj@gmail.com wrote:
Just installed 4.4 RC3 on FreeBSD 9.1 RC3 and it comes up fine. No time just now to try things out. Looking forward to improvements in the text editing ... this was driving be bananas. Thanks, all!!
On Thu, Dec 27, 2012 at 1:48 AM, H. Hirzel hannes.hirzel@gmail.comwrote:
Frank,
On 12/27/12, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:00, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
where can I have a look at the build script?
And the console output is not very talkative....
https://github.com/frankshearar/squeak-ci/blob/download-vms/release.sh
OK, so the following bash script
#! /bin/sh # This script takes the output of builtastic.sh and creates areleasable # artifact.
SRC=$(cd $(dirname "$0"); pwd) . "${SRC}/versions.sh" . "${SRC}/functions.sh" SQUEAK_VERSION=`cat ${SRC}/target/TrunkImage.version` BASENAME=Squeak4.4-${SQUEAK_VERSION} build_interpreter_vm echo Using ${INTERPRETER_VM} echo Preparing ${BASENAME}... cp ${SRC}/target/TrunkImage.changes ${SRC}/target/${BASENAME}.changes cp ${SRC}/target/TrunkImage.image ${SRC}/target/${BASENAME}.image chmod +w ${SRC}/target/${BASENAME}.changes chmod +w ${SRC}/target/${BASENAME}.image echo Releasing ${BASENAME}... ${INTERPRETER_VM} -vm-sound-null -vm-display-null ${SRC}/target/${BASENAME}.image ${SRC}/release.st
echo Zipping ${BASENAME}... # Previous runs might leave a zip lying around. rm ${SRC}/target/${BASENAME}.zip (cd ${SRC}/target; zip -j ${BASENAME}.zip ${BASENAME}.changes${BASENAME}.image)
CALLS the SMALLTALK script
https://github.com/frankshearar/squeak-ci/blob/download-vms/release.st
Form openAsBackground: (FileDirectory default / '..' /'resources/wallpaper.png') pathName. Workspace allInstances do: [:w | w topView delete]. ReleaseBuilderFor4dot4 prepareNewBuild. Smalltalk snapshot: true andQuit: true.
Just by inspection (and with the knowledge that the version number of the resulting image is correct) it seems that the error might be in the Smalltalk script.
NOTE: Anybody who downloads the latest trunk image and executes the above Smalltalk script is in the position to find the error....... (hint, hint to everybody...)
No, the scripts are not talkative at all. I'm really not sure how to make them more talkative. Obviously in the shell scripts you can use echo, but those do hardly anything. Really what I want is something that writes to the Transcript when headful and to stdout/stderr when headless. I don't think we have such a thing at the moment.
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
I am actually very fine with the scaffolding script in the image, reason see the note above.
And in addition this is what Andreas suggested in his memo which is cited in the welcome window. External packages configurations / scripts which are community supported should be in the image...
--Hannes
frank
--Hannes
On 12/24/12, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 09:18, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com
wrote:
> Though it has version number 12324 it still shows the rice-paper > background and has a 'welcome to Squeak 4.3' workspace.
Oh crumbs. Thanks, Hannes, I must have an error in my script.
http://squeakci.org/job/ReleaseSqueakTrunk/17/
frank
> --Hannes > > On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote: >> On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com >> wrote: >>> On 23 December 2012 19:09, Frank Shearar <frank.shearar@gmail.com
>>> wrote: >>>>
http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
>>>> >>>> I'm trying to automate more and more of the build/release
process.
>>>> See >>>> https://github.com/frankshearar/squeak-ci/tree/download-vms for >>>> details. (I'll merge this branch back into master at some point
in
>>>> the >>>> near future.) >>> >>> This does _not_ address Bert's issue about the positioning of the >>> Squeak window; it's just an illustration of yet another piece of >>> automation. I like automation. >> >> I see three dirty packages, all dirty - apparently - because of >> package restructurings. >> >> * FlexibleVocabularies - FlexibleVocabularies-Info removed? >> * Multilingual - Multilingual-Editor added? >> * SMLoader - looks like SMLoader-Models was removed? >> >> (I may have the situation reversed; I'm not sure whether "old"
refers
>> to the blue strikeout text or the red, nor whether "old" refers to >> the >> image or to trunk.) >> >> frank >> >> >
-- Gary Dunn Open Slate Project http://openslate.org/
OK, just loaded one of my projects and started poking around. This is by no means exhaustive, just what I happened to notice. On the "welcome" screen it says "Cleanup and simplification of Morphic text editing" but an old "feature" (bug) is still there. If I type "The second word is bold" and want to make the second word bold I double-click on "second" to select the word, then right-click to bring up a pop-up menu where I expect to be able to do that. The options available are
set font ... (k) set style ... (k) set alignment ... (u)
Setting a word bold should be on the style option, but when I select it I get a font selection tool. The first choice also leads to a font setting
Hmm, I agree. That's strange they both seem to bring up the same thing.
tool, although it is different. Neither offers bold, underline, italic, etc. The alignment choice does offer alignment options. If I halo the text and click Brown FF I get what I want, plus options to set alignment. Here is a clue: both of the first two options on the pop-menu show the same keyboard shortcut of k, which actually does what "set font" does. Seems as though the definition for the "set style" choice needs some adjustment.
I do think one of them is a capital K, the other is the lowercase variation.
I think most folks are so used to using the hot-keys for bold, underline, etc. that this little bug just went unnoticed. Someone will probably sweep it up in 4.5. The hot-key activation for bold does work. (See World menu | help... | command-key help for the full listing).
On Thu, Dec 27, 2012 at 4:18 PM, Open Slate openslateproj@gmail.com wrote:
Just installed 4.4 RC3 on FreeBSD 9.1 RC3 and it comes up fine. No time just now to try things out. Looking forward to improvements in the text editing ... this was driving be bananas. Thanks, all!!
On Thu, Dec 27, 2012 at 1:48 AM, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
On 12/27/12, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:00, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
where can I have a look at the build script?
And the console output is not very talkative....
https://github.com/frankshearar/squeak-ci/blob/download-vms/release.sh
OK, so the following bash script
#! /bin/sh # This script takes the output of builtastic.sh and creates areleasable # artifact.
SRC=$(cd $(dirname "$0"); pwd) . "${SRC}/versions.sh" . "${SRC}/functions.sh" SQUEAK_VERSION=`cat ${SRC}/target/TrunkImage.version` BASENAME=Squeak4.4-${SQUEAK_VERSION} build_interpreter_vm echo Using ${INTERPRETER_VM} echo Preparing ${BASENAME}... cp ${SRC}/target/TrunkImage.changes ${SRC}/target/${BASENAME}.changes cp ${SRC}/target/TrunkImage.image ${SRC}/target/${BASENAME}.image chmod +w ${SRC}/target/${BASENAME}.changes chmod +w ${SRC}/target/${BASENAME}.image echo Releasing ${BASENAME}... ${INTERPRETER_VM} -vm-sound-null -vm-display-null ${SRC}/target/${BASENAME}.image ${SRC}/release.st
echo Zipping ${BASENAME}... # Previous runs might leave a zip lying around. rm ${SRC}/target/${BASENAME}.zip (cd ${SRC}/target; zip -j ${BASENAME}.zip ${BASENAME}.changes${BASENAME}.image)
CALLS the SMALLTALK script
https://github.com/frankshearar/squeak-ci/blob/download-vms/release.st
Form openAsBackground: (FileDirectory default / '..' /'resources/wallpaper.png') pathName. Workspace allInstances do: [:w | w topView delete]. ReleaseBuilderFor4dot4 prepareNewBuild. Smalltalk snapshot: true andQuit: true.
Just by inspection (and with the knowledge that the version number of the resulting image is correct) it seems that the error might be in the Smalltalk script.
NOTE: Anybody who downloads the latest trunk image and executes the above Smalltalk script is in the position to find the error....... (hint, hint to everybody...)
No, the scripts are not talkative at all. I'm really not sure how to make them more talkative. Obviously in the shell scripts you can use echo, but those do hardly anything. Really what I want is something that writes to the Transcript when headful and to stdout/stderr when headless. I don't think we have such a thing at the moment.
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
I am actually very fine with the scaffolding script in the image, reason see the note above.
And in addition this is what Andreas suggested in his memo which is cited in the welcome window. External packages configurations / scripts which are community supported should be in the image...
--Hannes
frank
--Hannes
On 12/24/12, Frank Shearar frank.shearar@gmail.com wrote:
On 24 December 2012 09:18, Frank Shearar frank.shearar@gmail.com wrote: > On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com > wrote: >> Though it has version number 12324 it still shows the rice-paper >> background and has a 'welcome to Squeak 4.3' workspace. > > Oh crumbs. Thanks, Hannes, I must have an error in my script.
http://squeakci.org/job/ReleaseSqueakTrunk/17/
> frank > >> --Hannes >> >> On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote: >>> On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com >>> wrote: >>>> On 23 December 2012 19:09, Frank Shearar >>>> frank.shearar@gmail.com >>>> wrote: >>>>> >>>>> http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ... >>>>> >>>>> I'm trying to automate more and more of the build/release >>>>> process. >>>>> See >>>>> https://github.com/frankshearar/squeak-ci/tree/download-vms for >>>>> details. (I'll merge this branch back into master at some point >>>>> in >>>>> the >>>>> near future.) >>>> >>>> This does _not_ address Bert's issue about the positioning of the >>>> Squeak window; it's just an illustration of yet another piece of >>>> automation. I like automation. >>> >>> I see three dirty packages, all dirty - apparently - because of >>> package restructurings. >>> >>> * FlexibleVocabularies - FlexibleVocabularies-Info removed? >>> * Multilingual - Multilingual-Editor added? >>> * SMLoader - looks like SMLoader-Models was removed? >>> >>> (I may have the situation reversed; I'm not sure whether "old" >>> refers >>> to the blue strikeout text or the red, nor whether "old" refers to >>> the >>> image or to trunk.) >>> >>> frank >>> >>> >>
-- Gary Dunn Open Slate Project http://openslate.org/
-- Gary Dunn Open Slate Project http://openslate.org/
On 28 December 2012 03:44, Chris Muller asqueaker@gmail.com wrote:
OK, just loaded one of my projects and started poking around. This is by no means exhaustive, just what I happened to notice. On the "welcome" screen it says "Cleanup and simplification of Morphic text editing" but an old "feature" (bug) is still there. If I type "The second word is bold" and want to make the second word bold I double-click on "second" to select the word, then right-click to bring up a pop-up menu where I expect to be able to do that. The options available are
set font ... (k) set style ... (k) set alignment ... (u)
Setting a word bold should be on the style option, but when I select it I get a font selection tool. The first choice also leads to a font setting
Hmm, I agree. That's strange they both seem to bring up the same thing.
tool, although it is different. Neither offers bold, underline, italic, etc. The alignment choice does offer alignment options. If I halo the text and click Brown FF I get what I want, plus options to set alignment. Here is a clue: both of the first two options on the pop-menu show the same keyboard shortcut of k, which actually does what "set font" does. Seems as though the definition for the "set style" choice needs some adjustment.
I do think one of them is a capital K, the other is the lowercase variation.
I think most folks are so used to using the hot-keys for bold, underline, etc. that this little bug just went unnoticed. Someone will probably sweep it up in 4.5. The hot-key activation for bold does work. (See World menu | help... | command-key help for the full listing).
It'll be much easier to sweep up if there's a Mantis report :)
frank
On Thu, Dec 27, 2012 at 4:18 PM, Open Slate openslateproj@gmail.com wrote:
Just installed 4.4 RC3 on FreeBSD 9.1 RC3 and it comes up fine. No time just now to try things out. Looking forward to improvements in the text editing ... this was driving be bananas. Thanks, all!!
On Thu, Dec 27, 2012 at 1:48 AM, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
On 12/27/12, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:00, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
where can I have a look at the build script?
And the console output is not very talkative....
https://github.com/frankshearar/squeak-ci/blob/download-vms/release.sh
OK, so the following bash script
#! /bin/sh # This script takes the output of builtastic.sh and creates areleasable # artifact.
SRC=$(cd $(dirname "$0"); pwd) . "${SRC}/versions.sh" . "${SRC}/functions.sh" SQUEAK_VERSION=`cat ${SRC}/target/TrunkImage.version` BASENAME=Squeak4.4-${SQUEAK_VERSION} build_interpreter_vm echo Using ${INTERPRETER_VM} echo Preparing ${BASENAME}... cp ${SRC}/target/TrunkImage.changes ${SRC}/target/${BASENAME}.changes cp ${SRC}/target/TrunkImage.image ${SRC}/target/${BASENAME}.image chmod +w ${SRC}/target/${BASENAME}.changes chmod +w ${SRC}/target/${BASENAME}.image echo Releasing ${BASENAME}... ${INTERPRETER_VM} -vm-sound-null -vm-display-null ${SRC}/target/${BASENAME}.image ${SRC}/release.st
echo Zipping ${BASENAME}... # Previous runs might leave a zip lying around. rm ${SRC}/target/${BASENAME}.zip (cd ${SRC}/target; zip -j ${BASENAME}.zip ${BASENAME}.changes${BASENAME}.image)
CALLS the SMALLTALK script
https://github.com/frankshearar/squeak-ci/blob/download-vms/release.st
Form openAsBackground: (FileDirectory default / '..' /'resources/wallpaper.png') pathName. Workspace allInstances do: [:w | w topView delete]. ReleaseBuilderFor4dot4 prepareNewBuild. Smalltalk snapshot: true andQuit: true.
Just by inspection (and with the knowledge that the version number of the resulting image is correct) it seems that the error might be in the Smalltalk script.
NOTE: Anybody who downloads the latest trunk image and executes the above Smalltalk script is in the position to find the error....... (hint, hint to everybody...)
No, the scripts are not talkative at all. I'm really not sure how to make them more talkative. Obviously in the shell scripts you can use echo, but those do hardly anything. Really what I want is something that writes to the Transcript when headful and to stdout/stderr when headless. I don't think we have such a thing at the moment.
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
I am actually very fine with the scaffolding script in the image, reason see the note above.
And in addition this is what Andreas suggested in his memo which is cited in the welcome window. External packages configurations / scripts which are community supported should be in the image...
--Hannes
frank
--Hannes
On 12/24/12, Frank Shearar frank.shearar@gmail.com wrote: > On 24 December 2012 09:18, Frank Shearar frank.shearar@gmail.com > wrote: >> On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com >> wrote: >>> Though it has version number 12324 it still shows the rice-paper >>> background and has a 'welcome to Squeak 4.3' workspace. >> >> Oh crumbs. Thanks, Hannes, I must have an error in my script. > > http://squeakci.org/job/ReleaseSqueakTrunk/17/ > >> frank >> >>> --Hannes >>> >>> On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote: >>>> On 23 December 2012 19:14, Frank Shearar frank.shearar@gmail.com >>>> wrote: >>>>> On 23 December 2012 19:09, Frank Shearar >>>>> frank.shearar@gmail.com >>>>> wrote: >>>>>> >>>>>> http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ... >>>>>> >>>>>> I'm trying to automate more and more of the build/release >>>>>> process. >>>>>> See >>>>>> https://github.com/frankshearar/squeak-ci/tree/download-vms for >>>>>> details. (I'll merge this branch back into master at some point >>>>>> in >>>>>> the >>>>>> near future.) >>>>> >>>>> This does _not_ address Bert's issue about the positioning of the >>>>> Squeak window; it's just an illustration of yet another piece of >>>>> automation. I like automation. >>>> >>>> I see three dirty packages, all dirty - apparently - because of >>>> package restructurings. >>>> >>>> * FlexibleVocabularies - FlexibleVocabularies-Info removed? >>>> * Multilingual - Multilingual-Editor added? >>>> * SMLoader - looks like SMLoader-Models was removed? >>>> >>>> (I may have the situation reversed; I'm not sure whether "old" >>>> refers >>>> to the blue strikeout text or the red, nor whether "old" refers to >>>> the >>>> image or to trunk.) >>>> >>>> frank >>>> >>>> >>> > >
-- Gary Dunn Open Slate Project http://openslate.org/
-- Gary Dunn Open Slate Project http://openslate.org/
Thanks Chris for pointing out that on is a lowercase k and the other an uppercase K. My old eyes just didn't register the difference.
But my basic issue remains, both "set font" and "set style" bring up font selection tools and no way to set attributes such as bold and italic.
Frank, I dug up my moldy Mantis password and made an entry, http://bugs.squeak.org/view.php?id=7712
Have a terrific and safe new year celebration, everyone.
On Fri, Dec 28, 2012 at 2:47 AM, Frank Shearar frank.shearar@gmail.comwrote:
On 28 December 2012 03:44, Chris Muller asqueaker@gmail.com wrote:
OK, just loaded one of my projects and started poking around. This is
by no
means exhaustive, just what I happened to notice. On the "welcome"
screen it
says "Cleanup and simplification of Morphic text editing" but an old "feature" (bug) is still there. If I type "The second word is bold" and
want
to make the second word bold I double-click on "second" to select the
word,
then right-click to bring up a pop-up menu where I expect to be able to
do
that. The options available are
set font ... (k) set style ... (k) set alignment ... (u)
Setting a word bold should be on the style option, but when I select it
I
get a font selection tool. The first choice also leads to a font setting
Hmm, I agree. That's strange they both seem to bring up the same thing.
tool, although it is different. Neither offers bold, underline, italic,
etc.
The alignment choice does offer alignment options. If I halo the text
and
click Brown FF I get what I want, plus options to set alignment. Here
is a
clue: both of the first two options on the pop-menu show the same
keyboard
shortcut of k, which actually does what "set font" does. Seems as
though the
definition for the "set style" choice needs some adjustment.
I do think one of them is a capital K, the other is the lowercase
variation.
I think most folks are so used to using the hot-keys for bold, underline, etc. that this little bug just went unnoticed. Someone will probably sweep it up in 4.5. The hot-key activation for bold does work. (See World menu | help... | command-key help for the full listing).
It'll be much easier to sweep up if there's a Mantis report :)
frank
On Thu, Dec 27, 2012 at 4:18 PM, Open Slate openslateproj@gmail.com
wrote:
Just installed 4.4 RC3 on FreeBSD 9.1 RC3 and it comes up fine. No time just now to try things out. Looking forward to improvements in the text editing ... this was driving be bananas. Thanks, all!!
On Thu, Dec 27, 2012 at 1:48 AM, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
On 12/27/12, Frank Shearar frank.shearar@gmail.com wrote:
On 27 December 2012 11:00, H. Hirzel hannes.hirzel@gmail.com
wrote:
> Frank, > > where can I have a look at the build script? > > And the console output is not very talkative.... > > http://squeakci.org/job/ReleaseSqueakTrunk/17/console
https://github.com/frankshearar/squeak-ci/blob/download-vms/release.sh
OK, so the following bash script
#! /bin/sh # This script takes the output of builtastic.sh and creates areleasable # artifact.
SRC=$(cd $(dirname "$0"); pwd) . "${SRC}/versions.sh" . "${SRC}/functions.sh" SQUEAK_VERSION=`cat ${SRC}/target/TrunkImage.version` BASENAME=Squeak4.4-${SQUEAK_VERSION} build_interpreter_vm echo Using ${INTERPRETER_VM} echo Preparing ${BASENAME}... cp ${SRC}/target/TrunkImage.changes${SRC}/target/${BASENAME}.changes
cp ${SRC}/target/TrunkImage.image ${SRC}/target/${BASENAME}.image chmod +w ${SRC}/target/${BASENAME}.changes chmod +w ${SRC}/target/${BASENAME}.image echo Releasing ${BASENAME}... ${INTERPRETER_VM} -vm-sound-null -vm-display-null ${SRC}/target/${BASENAME}.image ${SRC}/release.st
echo Zipping ${BASENAME}... # Previous runs might leave a zip lying around. rm ${SRC}/target/${BASENAME}.zip (cd ${SRC}/target; zip -j ${BASENAME}.zip ${BASENAME}.changes${BASENAME}.image)
CALLS the SMALLTALK script
https://github.com/frankshearar/squeak-ci/blob/download-vms/release.st
Form openAsBackground: (FileDirectory default / '..' /'resources/wallpaper.png') pathName. Workspace allInstances do: [:w | w topView delete]. ReleaseBuilderFor4dot4 prepareNewBuild. Smalltalk snapshot: true andQuit: true.
Just by inspection (and with the knowledge that the version number of the resulting image is correct) it seems that the error might be in the Smalltalk script.
NOTE: Anybody who downloads the latest trunk image and executes the above Smalltalk script is in the position to find the error....... (hint, hint to everybody...)
No, the scripts are not talkative at all. I'm really not sure how to make them more talkative. Obviously in the shell scripts you can use echo, but those do hardly anything. Really what I want is something that writes to the Transcript when headful and to stdout/stderr when headless. I don't think we have such a thing at the moment.
I also think that the ReleaseBuilder stuff doesn't belong in the
Trunk
image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd
like
scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
I am actually very fine with the scaffolding script in the image, reason see the note above.
And in addition this is what Andreas suggested in his memo which is cited in the welcome window. External packages configurations / scripts which are community supported should be in the image...
--Hannes
frank
> --Hannes > > On 12/24/12, Frank Shearar frank.shearar@gmail.com wrote: >> On 24 December 2012 09:18, Frank Shearar <frank.shearar@gmail.com
>> wrote: >>> On 24 December 2012 07:48, H. Hirzel hannes.hirzel@gmail.com >>> wrote: >>>> Though it has version number 12324 it still shows the rice-paper >>>> background and has a 'welcome to Squeak 4.3' workspace. >>> >>> Oh crumbs. Thanks, Hannes, I must have an error in my script. >> >> http://squeakci.org/job/ReleaseSqueakTrunk/17/ >> >>> frank >>> >>>> --Hannes >>>> >>>> On 12/23/12, Frank Shearar frank.shearar@gmail.com wrote: >>>>> On 23 December 2012 19:14, Frank Shearar <
frank.shearar@gmail.com>
>>>>> wrote: >>>>>> On 23 December 2012 19:09, Frank Shearar >>>>>> frank.shearar@gmail.com >>>>>> wrote: >>>>>>> >>>>>>>
http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
>>>>>>> >>>>>>> I'm trying to automate more and more of the build/release >>>>>>> process. >>>>>>> See >>>>>>> https://github.com/frankshearar/squeak-ci/tree/download-vmsfor >>>>>>> details. (I'll merge this branch back into master at some
point
>>>>>>> in >>>>>>> the >>>>>>> near future.) >>>>>> >>>>>> This does _not_ address Bert's issue about the positioning of
the
>>>>>> Squeak window; it's just an illustration of yet another piece
of
>>>>>> automation. I like automation. >>>>> >>>>> I see three dirty packages, all dirty - apparently - because of >>>>> package restructurings. >>>>> >>>>> * FlexibleVocabularies - FlexibleVocabularies-Info removed? >>>>> * Multilingual - Multilingual-Editor added? >>>>> * SMLoader - looks like SMLoader-Models was removed? >>>>> >>>>> (I may have the situation reversed; I'm not sure whether "old" >>>>> refers >>>>> to the blue strikeout text or the red, nor whether "old"
refers to
>>>>> the >>>>> image or to trunk.) >>>>> >>>>> frank >>>>> >>>>> >>>> >> >> >
-- Gary Dunn Open Slate Project http://openslate.org/
-- Gary Dunn Open Slate Project http://openslate.org/
But my basic issue remains, both "set font" and "set style" bring up font selection tools and no way to set attributes such as bold and italic.
No way through those dialogs, yes. But no way at all, no -- Until it's fixed you can use Command+6 to change color, Command+7 for bold, Command+8 for italic, Command+_ for underline, Command+0 to make normal.
I guess that with Squeak having such a long and rich life there are times when a goal of making it more like other environments just doesn't make sense. My intent is to make Squeak's text edit interaction more like Windows ... select, right-click, set style, bold ... but one could argue that individual hot keys are far more powerful. I would even argue that Windows would do well to be more like Squeak.
On Fri, Dec 28, 2012 at 10:53 AM, Chris Muller asqueaker@gmail.com wrote:
But my basic issue remains, both "set font" and "set style" bring up font selection tools and no way to set attributes such as bold and italic.
No way through those dialogs, yes. But no way at all, no -- Until it's fixed you can use Command+6 to change color, Command+7 for bold, Command+8 for italic, Command+_ for underline, Command+0 to make normal.
On 12/27/12 8:34 AM, "Frank Shearar" frank.shearar@gmail.com wrote:
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
For years I beg we MUST have a SqueakCore .
I made 3.10 and proud of it, the first step in modular Squeak. Can't made 3.11... I attach the last script for it, see unloadSomeMore. I hope you success taking the code and improving. Made a SqueakCore and any Squeaker could decide which packages load later. Also is time to have new .sources and if we have a cleaner and small system ....
If you have time see the .cs. I apply it to Squeak , Cuis and Pharo and you could see the results in http://squeakros.org/3dot11 http://squeakros.org/Cuis3dot2 http://squeakros.org/Pharo1dot4
If we have a SqueakKernel , as Pavel made for Pharo and sure could build for us if we send a nice mail to he, could load the classes we need
Edgar
Yes, Edgar,
I assume everybody agrees with going for a smaller base image and loading packages on top of it. In particular as we now have this nice www.squeakci.org infrastructure.
We need to get
Smalltalk unloadAllPackages
to work again in 4.4. See the corresponding thread.
--Hannes
On 12/28/12, Edgar J. De Cleene edgardec2005@gmail.com wrote:
On 12/27/12 8:34 AM, "Frank Shearar" frank.shearar@gmail.com wrote:
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
For years I beg we MUST have a SqueakCore .
I made 3.10 and proud of it, the first step in modular Squeak. Can't made 3.11... I attach the last script for it, see unloadSomeMore. I hope you success taking the code and improving. Made a SqueakCore and any Squeaker could decide which packages load later. Also is time to have new .sources and if we have a cleaner and small system ....
If you have time see the .cs. I apply it to Squeak , Cuis and Pharo and you could see the results in http://squeakros.org/3dot11 http://squeakros.org/Cuis3dot2 http://squeakros.org/Pharo1dot4
If we have a SqueakKernel , as Pavel made for Pharo and sure could build for us if we send a nice mail to he, could load the classes we need
Edgar
BTW is one of the Pharo builds a minimal build?
In case we have Smalltalk unloadAllPackages
working
Frank or somebody else can set up a script for www.squeakci.org to produce a minimal release.
Actually the goal might not be far away....
--Hannes
On 12/28/12, H. Hirzel hannes.hirzel@gmail.com wrote:
Yes, Edgar,
I assume everybody agrees with going for a smaller base image and loading packages on top of it. In particular as we now have this nice www.squeakci.org infrastructure.
We need to get
Smalltalk unloadAllPackagesto work again in 4.4. See the corresponding thread.
--Hannes
On 12/28/12, Edgar J. De Cleene edgardec2005@gmail.com wrote:
On 12/27/12 8:34 AM, "Frank Shearar" frank.shearar@gmail.com wrote:
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
For years I beg we MUST have a SqueakCore .
I made 3.10 and proud of it, the first step in modular Squeak. Can't made 3.11... I attach the last script for it, see unloadSomeMore. I hope you success taking the code and improving. Made a SqueakCore and any Squeaker could decide which packages load later. Also is time to have new .sources and if we have a cleaner and small system ....
If you have time see the .cs. I apply it to Squeak , Cuis and Pharo and you could see the results in http://squeakros.org/3dot11 http://squeakros.org/Cuis3dot2 http://squeakros.org/Pharo1dot4
If we have a SqueakKernel , as Pavel made for Pharo and sure could build for us if we send a nice mail to he, could load the classes we need
Edgar
On 12/28/12 8:37 AM, "H. Hirzel" hannes.hirzel@gmail.com wrote:
BTW is one of the Pharo builds a minimal build?
https://ci.inria.fr/pharo/view/Pharo-Kernel-2.0/
Maybe the future is here?
Too bad they focus in 2.0 which is almost incompatible with Squeak and do not ends 1.4 which is not
Edgar
On 12/28/12, Edgar J. De Cleene edgardec2005@gmail.com wrote:
On 12/28/12 8:37 AM, "H. Hirzel" hannes.hirzel@gmail.com wrote:
BTW is one of the Pharo builds a minimal build?
The image is less then 3MB and has no GUI. Probably too small at the moment.
Maybe the future is here?
Too bad they focus in 2.0 which is almost incompatible with Squeak and do not ends 1.4 which is not
It is mainly the addition of FileSystem in Pharo 2.0 and and this is something which is considered as well for Squeak 4.5.
So Depending on the library you are working on the porting effort is not all that big.
There are porting issued but they may be addressed fairly easily depending on the type of library.
The same actually applies for Cuis.
General libraries have to be made independent of the distribution. Some libraries will only be available on a particular distribution because the porting effort is high.
--Hannes
P.S. Maybe this is not a priority for people in regards to Squeak. There is Cuis 4.1 available which fulfills much of this goal. http://www.jvuletich.org/Cuis/Index.html https://github.com/jvuletich/Cuis
And the number of packages available for Cuis is growing. https://gist.github.com/4387924
And having Environments in Squeak 4.5 is probably a higher priority....
--Hannes
On 12/28/12, H. Hirzel hannes.hirzel@gmail.com wrote:
On 12/28/12, Edgar J. De Cleene edgardec2005@gmail.com wrote:
On 12/28/12 8:37 AM, "H. Hirzel" hannes.hirzel@gmail.com wrote:
BTW is one of the Pharo builds a minimal build?
The image is less then 3MB and has no GUI. Probably too small at the moment.
Maybe the future is here?
Too bad they focus in 2.0 which is almost incompatible with Squeak and do not ends 1.4 which is not
It is mainly the addition of FileSystem in Pharo 2.0 and and this is something which is considered as well for Squeak 4.5.
So Depending on the library you are working on the porting effort is not all that big.
There are porting issued but they may be addressed fairly easily depending on the type of library.
The same actually applies for Cuis.
General libraries have to be made independent of the distribution. Some libraries will only be available on a particular distribution because the porting effort is high.
--Hannes
On Fri, Dec 28, 2012 at 1:00 PM, Edgar J. De Cleene edgardec2005@gmail.com wrote:
On 12/28/12 8:37 AM, "H. Hirzel" hannes.hirzel@gmail.com wrote:
BTW is one of the Pharo builds a minimal build?
https://ci.inria.fr/pharo/view/Pharo-Kernel-2.0/
Maybe the future is here?
Too bad they focus in 2.0 which is almost incompatible with Squeak and do not ends 1.4 which is not
Edgar
Hi,
two weeks ago the list looked much more nicer because we had only one failing job and less failing tests.
Should Squeak be based on Pharo Kernel and basic packages? There were several discussions on this topic. Technically it is doable but it is politically impassable.
Should Squeak have own Squeak minimal image? How to reach that? Firstly I must say that Squeak Board should anwer this. You and Hannes are not members of the Board.
I'm ready to help you with several simple conditions: The image will be official - the next release will simply be this minimal image + packages, the "full" image will always be produced from the minimal image by the build server, the patches will be reviewed by two other persons and integrated quickly. I simply do not want to work on a project with uncertain future. Because from my point of view it is redoing of the same work that I did several times and to look into Squeak is like to look into the past from the remodularization perspective.
Cheers, -- Pavel
Hi Pavel!
On Fri, Dec 28, 2012 at 7:58 AM, Pavel Krivanek squeak1@continentalbrno.cz wrote:
Should Squeak be based on Pharo Kernel and basic packages? There were several discussions on this topic. Technically it is doable but it is politically impassable.
Sure, technically doable. Politically, it clashes with the goal of having a kernel image based on Spoon, which has been the long-term plan for Squeak.
Should Squeak have own Squeak minimal image? How to reach that? Firstly I must say that Squeak Board should anwer this. You and Hannes are not members of the Board.
Well, the Board generally tries to avoid making technical/aspirational decisions of this nature. This is for the community at large to decide. In practice, that means if there are no strenuous objections and if somebody is willing to do the work, the project can go forward.
I can also say that the Board regularly discusses modularity and various options for reducing he size of the core image, so I doubt there will be any objections.
I'm ready to help you with several simple conditions: The image will be official - the next release will simply be this minimal image + packages, the "full" image will always be produced from the minimal image by the build server, the patches will be reviewed by two other persons and integrated quickly. I simply do not want to work on a project with uncertain future. Because from my point of view it is redoing of the same work that I did several times and to look into Squeak is like to look into the past from the remodularization perspective.
Well, as a volunteer for the 4.5 release team, I'd be happy to accept your help, and commit to releasing a core image + an automatically-built full image. This has long been a goal of the Squeak community, we just make slower progress because we're not willing to break existing functionality in Morphic and Etoys.
Thanks for speaking up Pavel, it's good to see you on squeak-dev again!
Colin
On 12/28/12 12:28 PM, "Colin Putney" colin@wiresong.com wrote:
Hi Pavel!
On Fri, Dec 28, 2012 at 7:58 AM, Pavel Krivanek squeak1@continentalbrno.cz wrote:
Should Squeak be based on Pharo Kernel and basic packages? There were several discussions on this topic. Technically it is doable but it is politically impassable.
Sure, technically doable. Politically, it clashes with the goal of having a kernel image based on Spoon, which has been the long-term plan for Squeak.
Should Squeak have own Squeak minimal image? How to reach that? Firstly I must say that Squeak Board should anwer this. You and Hannes are not members of the Board.
Well, the Board generally tries to avoid making technical/aspirational decisions of this nature. This is for the community at large to decide. In practice, that means if there are no strenuous objections and if somebody is willing to do the work, the project can go forward.
I can also say that the Board regularly discusses modularity and various options for reducing he size of the core image, so I doubt there will be any objections.
I'm ready to help you with several simple conditions: The image will be official - the next release will simply be this minimal image + packages, the "full" image will always be produced from the minimal image by the build server, the patches will be reviewed by two other persons and integrated quickly. I simply do not want to work on a project with uncertain future. Because from my point of view it is redoing of the same work that I did several times and to look into Squeak is like to look into the past from the remodularization perspective.
Well, as a volunteer for the 4.5 release team, I'd be happy to accept your help, and commit to releasing a core image + an automatically-built full image. This has long been a goal of the Squeak community, we just make slower progress because we're not willing to break existing functionality in Morphic and Etoys.
Thanks for speaking up Pavel, it's good to see you on squeak-dev again!
Colin
For the record, thanks Pavel for your good will and support. Thanks Colin for take this seriously, ready to help with any task.
Edgar
Hi Colin,
On Fri, Dec 28, 2012 at 4:28 PM, Colin Putney colin@wiresong.com wrote:
Hi Pavel!
On Fri, Dec 28, 2012 at 7:58 AM, Pavel Krivanek squeak1@continentalbrno.cz wrote:
Should Squeak be based on Pharo Kernel and basic packages? There were several discussions on this topic. Technically it is doable but it is politically impassable.
Sure, technically doable. Politically, it clashes with the goal of having a kernel image based on Spoon, which has been the long-term plan for Squeak.
Should Squeak have own Squeak minimal image? How to reach that? Firstly I must say that Squeak Board should anwer this. You and Hannes are not members of the Board.
Well, the Board generally tries to avoid making technical/aspirational decisions of this nature. This is for the community at large to decide. In practice, that means if there are no strenuous objections and if somebody is willing to do the work, the project can go forward.
I can also say that the Board regularly discusses modularity and various options for reducing he size of the core image, so I doubt there will be any objections.
I'm ready to help you with several simple conditions: The image will be official - the next release will simply be this minimal image + packages, the "full" image will always be produced from the minimal image by the build server, the patches will be reviewed by two other persons and integrated quickly. I simply do not want to work on a project with uncertain future. Because from my point of view it is redoing of the same work that I did several times and to look into Squeak is like to look into the past from the remodularization perspective.
Well, as a volunteer for the 4.5 release team, I'd be happy to accept your help, and commit to releasing a core image + an automatically-built full image. This has long been a goal of the Squeak community, we just make slower progress because we're not willing to break existing functionality in Morphic and Etoys.
Thanks for speaking up Pavel, it's good to see you on squeak-dev again!
Well, some important preparation steps need to be done, firstly improve packages granularity: - remove empty MC packages (FlexibleVocabularies, Squeak-Version), code to get them:
MCWorkingCopy allInstances select: [:wc | wc package snapshot definitions isEmpty]
- split System package to packages corresponding to its categories (System-Applications, System-Change Notification, System-Changes...) and unregister System package - split Multilingual package to packages corresponding to its categories and unregister Multilingual package
Can you do that? -- Pavel
Colin
On Sat, Dec 29, 2012 at 7:57 AM, Pavel Krivanek squeak1@continentalbrno.cz wrote:
Well, some important preparation steps need to be done, firstly improve packages granularity:
- remove empty MC packages (FlexibleVocabularies, Squeak-Version),
code to get them:
MCWorkingCopy allInstances select: [:wc | wc package snapshot definitions isEmpty]
- split System package to packages corresponding to its categories
(System-Applications, System-Change Notification, System-Changes...) and unregister System package
- split Multilingual package to packages corresponding to its
categories and unregister Multilingual package
Can you do that?
Sure. But let's wait until 4.4 is released and the trunk is switched over to 4.5 alpha.
In the meantime, can you describe your overall plan?
Hi All,
Potential overall plan for your consideration.
Summary: Having a minimal Squeak Core image that enables users to easily find and load components to build a functional system has been a goal of the community for some time. The goal is to remove dependencies from packages (to the extent that it is possible) so that discrete components can act as Objects that are interchangeable. Because the API of objects is not always identical and because different implementations of core system components may provide features that are not identical, the final end point and dependencies of functioning systems may not always be compatible to other functioning systems. The results of this philosophy-of-componentization are that the community is enabled to build best of breed systems much like we see today. The mission of this project is to enable those that want to participate to easily integrate the best and right implementation of core components to build the best possible functioning system, to make the steps for creating a functioning systems easily repeatable from a single core image, and to make the steps for contributing to the modification of components that build systems transparent so that newer versions of components can be adopted by system builders (or replaced by newer implementations) easily. In short we want to exploit and support the Object in Object Oriented Programming.
Detail requirements:
1. Squeak Core image that allows developers of systems to select and easily load core components. 2. System configurations that identify core dependencies, including versions, packages, and external resources that are needed to easily rebuild a functioning system from Squeak Core. 3. The ability to update, replace, or remove components to build new configurations of a functioning system. 4. For the benefit of system developers: The ability to announce upgrades to component objects and application packages. 5. For the benefit of end users: The ability to announce upgrades to system configurations.
All the best,
Ron Teitelbaum Head Of Engineering 3d Immersive Collaboration Consulting ron@3dicc.com Follow Me On Twitter: @RonTeitelbaum www.3dicc.com
Ron, thanks for starting with clarification of our _rationale and requirements_ rather than solutions. Those sound great!
Potential overall plan for your consideration.
Summary: Having a minimal Squeak Core image that enables users to easily find and load components to build a functional system has been a goal of the community for some time. The goal is to remove dependencies from packages (to the extent that it is possible) so that discrete components can act as Objects that are interchangeable. Because the API of objects is not always identical and because different implementations of core system components may provide features that are not identical, the final end point and dependencies of functioning systems may not always be compatible to other functioning systems. The results of this philosophy-of-componentization are that the community is enabled to build best of breed systems much like we see today. The mission of this project is to enable those that want to participate to easily integrate the best and right implementation of core components to build the best possible functioning system, to make the steps for creating a functioning systems easily repeatable from a single core image, and to make the steps for contributing to the modification of components that build systems transparent so that newer versions of components can be adopted by system builders (or replaced by newer implementations) easily. In short we want to exploit and support the Object in Object Oriented Programming.
Detail requirements:
- Squeak Core image that allows developers of systems to select and easily
load core components. 2. System configurations that identify core dependencies, including versions, packages, and external resources that are needed to easily rebuild a functioning system from Squeak Core. 3. The ability to update, replace, or remove components to build new configurations of a functioning system. 4. For the benefit of system developers: The ability to announce upgrades to component objects and application packages. 5. For the benefit of end users: The ability to announce upgrades to system configurations.
All the best,
Ron Teitelbaum Head Of Engineering 3d Immersive Collaboration Consulting ron@3dicc.com Follow Me On Twitter: @RonTeitelbaum www.3dicc.com
On 12/29/12 12:46 PM, "Ron Teitelbaum" ron@usmedrec.com wrote:
Hi All,
Potential overall plan for your consideration.
Summary: Having a minimal Squeak Core image that enables users to easily find and load components to build a functional system has been a goal of the community for some time. The goal is to remove dependencies from packages (to the extent that it is possible) so that discrete components can act as Objects that are interchangeable. Because the API of objects is not always identical and because different implementations of core system components may provide features that are not identical, the final end point and dependencies of functioning systems may not always be compatible to other functioning systems. The results of this philosophy-of-componentization are that the community is enabled to build best of breed systems much like we see today. The mission of this project is to enable those that want to participate to easily integrate the best and right implementation of core components to build the best possible functioning system, to make the steps for creating a functioning systems easily repeatable from a single core image, and to make the steps for contributing to the modification of components that build systems transparent so that newer versions of components can be adopted by system builders (or replaced by newer implementations) easily. In short we want to exploit and support the Object in Object Oriented Programming.
Detail requirements:
- Squeak Core image that allows developers of systems to select and easily
load core components. 2. System configurations that identify core dependencies, including versions, packages, and external resources that are needed to easily rebuild a functioning system from Squeak Core. 3. The ability to update, replace, or remove components to build new configurations of a functioning system. 4. For the benefit of system developers: The ability to announce upgrades to component objects and application packages. 5. For the benefit of end users: The ability to announce upgrades to system configurations.
All the best,
Ron Teitelbaum Head Of Engineering 3d Immersive Collaboration Consulting ron@3dicc.com Follow Me On Twitter: @RonTeitelbaum www.3dicc.com
Can't say better. +1
Edgar
On Sat, Dec 29, 2012 at 2:48 PM, Colin Putney colin@wiresong.com wrote:
On Sat, Dec 29, 2012 at 7:57 AM, Pavel Krivanek squeak1@continentalbrno.cz wrote:
Well, some important preparation steps need to be done, firstly improve packages granularity:
- remove empty MC packages (FlexibleVocabularies, Squeak-Version),
code to get them:
MCWorkingCopy allInstances select: [:wc | wc package snapshot definitions isEmpty]
- split System package to packages corresponding to its categories
(System-Applications, System-Change Notification, System-Changes...) and unregister System package
- split Multilingual package to packages corresponding to its
categories and unregister Multilingual package
Can you do that?
Sure. But let's wait until 4.4 is released and the trunk is switched over to 4.5 alpha.
ok, it is not a problem until we will want to try to load things back to the core.
In the meantime, can you describe your overall plan?
The overall plan is the same as in case of Pharo: - take full image and unload all packages that are not essential for the system including Monticello and network support, generate headless image without GUI that can can process incoming scripts - clean obsolete classes and undeclared in this image to have reasonably clean image - load network, monticello and possibly metacello to this image - load and initialize the rest of the system using monticello, create metacello configuration for it - repackage tests - ensure this shrinking - reloading process is repeatable - declare updatable image with metacello as the base image - continue in remodularization
Cheers, -- Pavel
On Sat, 29 Dec 2012, Pavel Krivanek wrote:
Hi Colin,
On Fri, Dec 28, 2012 at 4:28 PM, Colin Putney colin@wiresong.com wrote:
Hi Pavel!
On Fri, Dec 28, 2012 at 7:58 AM, Pavel Krivanek squeak1@continentalbrno.cz wrote:
Should Squeak be based on Pharo Kernel and basic packages? There were several discussions on this topic. Technically it is doable but it is politically impassable.
Sure, technically doable. Politically, it clashes with the goal of having a kernel image based on Spoon, which has been the long-term plan for Squeak.
Should Squeak have own Squeak minimal image? How to reach that? Firstly I must say that Squeak Board should anwer this. You and Hannes are not members of the Board.
Well, the Board generally tries to avoid making technical/aspirational decisions of this nature. This is for the community at large to decide. In practice, that means if there are no strenuous objections and if somebody is willing to do the work, the project can go forward.
I can also say that the Board regularly discusses modularity and various options for reducing he size of the core image, so I doubt there will be any objections.
I'm ready to help you with several simple conditions: The image will be official - the next release will simply be this minimal image + packages, the "full" image will always be produced from the minimal image by the build server, the patches will be reviewed by two other persons and integrated quickly. I simply do not want to work on a project with uncertain future. Because from my point of view it is redoing of the same work that I did several times and to look into Squeak is like to look into the past from the remodularization perspective.
Well, as a volunteer for the 4.5 release team, I'd be happy to accept your help, and commit to releasing a core image + an automatically-built full image. This has long been a goal of the Squeak community, we just make slower progress because we're not willing to break existing functionality in Morphic and Etoys.
Thanks for speaking up Pavel, it's good to see you on squeak-dev again!
Well, some important preparation steps need to be done, firstly improve packages granularity:
- remove empty MC packages (FlexibleVocabularies, Squeak-Version),
Squeak-Version is intentionally empty. We use it to ensure that the system's version number is increasing.
Levente
code to get them:
MCWorkingCopy allInstances select: [:wc | wc package snapshot definitions isEmpty]
- split System package to packages corresponding to its categories
(System-Applications, System-Change Notification, System-Changes...) and unregister System package
- split Multilingual package to packages corresponding to its
categories and unregister Multilingual package
Can you do that? -- Pavel
Colin
On Thu, Dec 27, 2012 at 11:34:32AM +0000, Frank Shearar wrote:
On 27 December 2012 11:00, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
where can I have a look at the build script?
And the console output is not very talkative....
- https://github.com/frankshearar/squeak-ci/blob/download-vms/release.sh
- https://github.com/frankshearar/squeak-ci/blob/download-vms/release.st
No, the scripts are not talkative at all. I'm really not sure how to make them more talkative. Obviously in the shell scripts you can use echo, but those do hardly anything. Really what I want is something that writes to the Transcript when headful and to stdout/stderr when headless. I don't think we have such a thing at the moment.
Try something like this in your Smalltalk scripts:
"Define a block to take a single string parameter and write a message to both the console stdout and to the Transcript" log := [:msg | | str | str := DateAndTime now printString, ': ', msg. FileStream stdout nextPutAll: str; nextPut: Character lf; flush. Transcript cr; show: str].
"Then sprinkle the rest of your script with things like this" log value: 'Begin loading my package from SqueakSource'.
log value: 'My package is loaded now'.
Dave
Hi,
Squeak 4.4-12324,
Help Menu ,set languages,
missing method, #availableLanguageLocaleIDs?
Best Regards
Bing Liang
-- View this message in context: http://forum.world.st/New-release-candidate-4-4-12324-tp4660766p4660989.html Sent from the Squeak - Dev mailing list archive at Nabble.com.
On Thu, Dec 27, 2012 at 06:54:30AM -0800, liang bing wrote:
Hi,
Squeak 4.4-12324,
Help Menu ,set languages,
missing method, #availableLanguageLocaleIDs?
Best Regards
Bing Liang
The problem is: Project current chooseNaturalLanguage ==> DNU
MorphicProject>chooseNaturalLanguage sends NaturalLanguageTranslator class>>availableLanguageLocaleIDs. This should probably be sent to InternalTranslator rather than to NaturalLanguageTranslator (its abstract superclass).
However, I have no language options present in my image, so I cannot say for sure if this is correct.
I will fix the DNU problem in trunk, but if someone more familiar with language translation can check this and see if it really works, I'd appreciate it.
Thanks, Dave
to evaluate (InternalTranslator newLocaleID: LocaleID current)
it seems OK.
But a lot of wrong message 'self beep' in LanguageEditor class
-- View this message in context: http://forum.world.st/New-release-candidate-4-4-12324-tp4660766p4663916.html Sent from the Squeak - Dev mailing list archive at Nabble.com.
Hi Liang,
I imagine you get the same errors in the final 4.4-12327 release?
frank
On 17 Jan 2013, at 14:18, liang bing liangbing64@gmail.com wrote:
to evaluate (InternalTranslator newLocaleID: LocaleID current)
it seems OK.
But a lot of wrong message 'self beep' in LanguageEditor class
-- View this message in context: http://forum.world.st/New-release-candidate-4-4-12324-tp4660766p4663916.html Sent from the Squeak - Dev mailing list archive at Nabble.com.
Hi Frank, Yes, same problem in 12327. I am trying to let 12327 work in my chinese windows .
Hope 4.4 better!
Liang
-- View this message in context: http://forum.world.st/New-release-candidate-4-4-12324-tp4660766p4664071.html Sent from the Squeak - Dev mailing list archive at Nabble.com.
On 1/18/13, liang bing liangbing64@gmail.com wrote:
Hi Frank, Yes, same problem in 12327. I am trying to let 12327 work in my chinese windows .
Hope 4.4 better!
Liang
Unfortunately the build 12327 _is_ what people consider to be the 4.4 release (though not announced on the web page). It had not been tested with the Chinese MSWindow system so far.
What can be done about this?
--Hannes
On 18 January 2013 08:53, H. Hirzel hannes.hirzel@gmail.com wrote:
On 1/18/13, liang bing liangbing64@gmail.com wrote:
Hi Frank, Yes, same problem in 12327. I am trying to let 12327 work in my chinese windows .
Hope 4.4 better!
Liang
Unfortunately the build 12327 _is_ what people consider to be the 4.4 release (though not announced on the web page). It had not been tested with the Chinese MSWindow system so far.
What can be done about this?
Just to be clear, you mean that it's unfortunate that www.squeak.org doesn't make it obvious that there's a 4.4 release? That's fair enough, but it can't really until we decide what an All-in-One looks like and how it can be made. So far, it's not clear to me how to make one of those in an entirely automated fashion. Once we have that, we can brighten up the top right corner with a 4.4.
Otherwise, we can only support Chinese + Windows if we have tests. (And ideally, build slaves). I'm not trying to avoid responsibility here. We just have very limited resources.
frank
--Hannes
On 1/18/13, Frank Shearar frank.shearar@gmail.com wrote:
On 18 January 2013 08:53, H. Hirzel hannes.hirzel@gmail.com wrote:
On 1/18/13, liang bing liangbing64@gmail.com wrote:
Hi Frank, Yes, same problem in 12327. I am trying to let 12327 work in my chinese windows .
Hope 4.4 better!
Liang
Unfortunately the build 12327 _is_ what people consider to be the 4.4 release (though not announced on the web page). It had not been tested with the Chinese MSWindow system so far.
What can be done about this?
Just to be clear, you mean that it's unfortunate that www.squeak.org doesn't make it obvious that there's a 4.4 release?
Yes.
That's fair enough, but it can't really until we decide what an All-in-One looks like and how it can be made.
So far, it's not clear to me how to make one of those in an entirely automated fashion. Once we have that, we can brighten up the top right corner with a 4.4.
I still wonder why we can't copy the build script which Pharo has?
Otherwise, we can only support Chinese + Windows if we have tests. (And ideally, build slaves).
Yes.
I'm not trying to avoid responsibility here. We just have very limited resources.
frank
Yes, indeed, and thank you very much for your continued extraordinary contributions.
--Hannes
On 18 January 2013 10:34, H. Hirzel hannes.hirzel@gmail.com wrote:
On 1/18/13, Frank Shearar frank.shearar@gmail.com wrote:
On 18 January 2013 08:53, H. Hirzel hannes.hirzel@gmail.com wrote:
On 1/18/13, liang bing liangbing64@gmail.com wrote:
Hi Frank, Yes, same problem in 12327. I am trying to let 12327 work in my chinese windows .
Hope 4.4 better!
Liang
Unfortunately the build 12327 _is_ what people consider to be the 4.4 release (though not announced on the web page). It had not been tested with the Chinese MSWindow system so far.
What can be done about this?
Just to be clear, you mean that it's unfortunate that www.squeak.org doesn't make it obvious that there's a 4.4 release?
Yes.
That's fair enough, but it can't really until we decide what an All-in-One looks like and how it can be made.
So far, it's not clear to me how to make one of those in an entirely automated fashion. Once we have that, we can brighten up the top right corner with a 4.4.
I still wonder why we can't copy the build script which Pharo has?
For the All-in-One? I *cough*. Yes, we should just do that.
frank
Otherwise, we can only support Chinese + Windows if we have tests. (And ideally, build slaves).
Yes.
I'm not trying to avoid responsibility here. We just have very limited resources.
frank
Yes, indeed, and thank you very much for your continued extraordinary contributions.
--Hannes
Hi Frank,
I let chinese running on 12327 now.
My experience,
1. 4.4 runs faster than 4.3 2. FreeType Font not stable, textPane becomes red. i choose install TTC font 3. NaturalLanguageTranslator class variable /Translator/ and InternalTranslator class variable /CachedTranslations/ are initialized out of sync. that leads (Locale switchTo: locale) doesnot work.
I know there are few people using chinese Squeak, enjoy myself .
Thank You Very Much!
Liang
-- View this message in context: http://forum.world.st/New-release-candidate-4-4-12324-tp4660766p4664398.html Sent from the Squeak - Dev mailing list archive at Nabble.com.
On 21 January 2013 14:16, liang bing liangbing64@gmail.com wrote:
Hi Frank,
I let chinese running on 12327 now.
My experience,
- 4.4 runs faster than 4.3
- FreeType Font not stable, textPane becomes red. i choose install TTC font
- NaturalLanguageTranslator class variable /Translator/ and InternalTranslator class variable /CachedTranslations/ are initialized
out of sync. that leads (Locale switchTo: locale) doesnot work.
I know there are few people using chinese Squeak, enjoy myself .
Thank You Very Much!
Liang
Thanks for your kind words, Liang.
If there's any way I can help make Chinese work better in Squeak, let me know!
frank
hi, Frank
Thank you very much!
after install VMMaker for 4.4, and update new FreeTypeFont. Chinese Character is okay now with FreeType.
Best Regards!
liang
-- View this message in context: http://forum.world.st/New-release-candidate-4-4-12324-tp4660766p4671009.html Sent from the Squeak - Dev mailing list archive at Nabble.com.
squeak-dev@lists.squeakfoundation.org
-
Chris Muller -
Colin Putney -
David T. Lewis -
Edgar J. De Cleene -
Frank Shearar -
H. Hirzel -
Levente Uzonyi -
liang bing -
Open Slate -
Pavel Krivanek -
Ron Teitelbaum