- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Loading Nautilus / Spec in 1.4

by StÃ©phane Ducasse

Yes I got bitten by that today this is a problem you should remove the instance variable from the superclass then load and remove it from buttonModel and add it to its superclass. Now I suggest not to use nautilus for 1.4. Stef On Jul 30, 2012, at 7:02 PM, Patrik Sundberg wrote: > Hi, > > Loading nautilus #stable in 1.4 I get: > DuplicatedVariableError: helpHolder is already defined in AbstractBasicWidget > > Looks to come when loading the dependency Spec-Widgets-BenjaminVanRyseghem.48. > > Any ideas? > > I can provide more of the stack trace if it's useful (I'd assume so), but would like a pointer what the best way to get that info in an emailable format (not obvious to me how I can just copy-paste it). > > This is the summer release. > > Thanks, > Patrik >

July 30, 2012

[Pharo-project] Loading Nautilus / Spec in 1.4

by Patrik Sundberg

Hi, Loading nautilus #stable in 1.4 I get: DuplicatedVariableError: helpHolder is already defined in AbstractBasicWidget Looks to come when loading the dependency Spec-Widgets-BenjaminVanRyseghem.48. Any ideas? I can provide more of the stack trace if it's useful (I'd assume so), but would like a pointer what the best way to get that info in an emailable format (not obvious to me how I can just copy-paste it). This is the summer release. Thanks, Patrik

July 30, 2012

Re: [Pharo-project] Going meta (VM development)

by Dale Henrichs

----- Original Message ----- | From: "Igor Stasenko" <siguctua(a)gmail.com> | Another thing, which i discussed locally , i thinking about creating | a | dedicated blog for VM developers, where we can share the news and | describe | details about changes and stuff.. | In a way, that it will serve as a source of information about VM , | jenkins , configurations, settings , building etc etc.. | Because all of the bits of knowledge , which we collected till now is | kind of floating in the air, and like any energy it tends to | dissipate | (things we remember and forget, the more things we should keep in | head, the faster it happens). | Also, blog is preferable to just simple CHANGELOG file (or similar), | because it is two-way communication , and people can comment and | discuss things. Igor, You might find GitHub as a very good place for this. GitHub has a number of collaboration features that play very well together: source code control with git issues where you can report bugs, but also host conversations wiki for documentation although I like markdown for documentation since the docs are then versioned with the code When you view code diffs you can make line by line comments/questions that are visible to other developers who can in turn comment on your comments ... talk about real two-way communication:) The real advantage is that all of these things are versioned together ... code/documentation/articles ... Anyway, it's worth considering:) Dale

July 30, 2012

Re: [Pharo-project] Going meta (VM development)

by phil＠highoctane.be

Good. And adding an iOS entry for a StackVM version (or CogARM one of these days) would be great. Phil 2012/7/30 Patrik Sundberg <patrik.sundberg(a)gmail.com> > On Mon, Jul 30, 2012 at 3:18 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> Another thing, which i discussed locally , i thinking about creating a >> dedicated blog for VM developers, where we can share the news and >> describe >> details about changes and stuff.. >> In a way, that it will serve as a source of information about VM , >> jenkins , configurations, settings , building etc etc.. >> Because all of the bits of knowledge , which we collected till now is >> kind of floating in the air, and like any energy it tends to dissipate >> (things we remember and forget, the more things we should keep in >> head, the faster it happens). >> Also, blog is preferable to just simple CHANGELOG file (or similar), >> because it is two-way communication , and people can comment and >> discuss things. >> >> > Sounds like an excellent idea. Great for a newcomer like myself to have > (in the future) an archive of blog posts to get oriented through. > >

July 30, 2012

Re: [Pharo-project] Going meta (VM development)

by Patrik Sundberg

On Mon, Jul 30, 2012 at 3:18 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Another thing, which i discussed locally , i thinking about creating a > dedicated blog for VM developers, where we can share the news and > describe > details about changes and stuff.. > In a way, that it will serve as a source of information about VM , > jenkins , configurations, settings , building etc etc.. > Because all of the bits of knowledge , which we collected till now is > kind of floating in the air, and like any energy it tends to dissipate > (things we remember and forget, the more things we should keep in > head, the faster it happens). > Also, blog is preferable to just simple CHANGELOG file (or similar), > because it is two-way communication , and people can comment and > discuss things. > > Sounds like an excellent idea. Great for a newcomer like myself to have (in the future) an archive of blog posts to get oriented through.

July 30, 2012

[Pharo-project] Going meta (VM development)

by Igor Stasenko

Hello, spent another day building VM, i found that our setup is still far from being simple.. the jenkins jobs right now using a page-long scripts to configure & build vm, and grown with many bells and whistless.. one of my goals when i created a configurations was to avoid that.. and keep these things 1-liners.. one of the reasons for doing that is that you can reproduce the whole build on local machine from command line by typing a simple commands like make , as well as simple doits in VMMaker image. So, here some of my suggestions: - create a single PharoVMBuilder class, which will encompass all the details of platform-specificness, and will pick the right configuration & default plugins based on our preference and target platform. By issuing: PharoVMBuilder generate. - it should generate sources - it should generate cmake files, based on environment variable set (btw, can we access an environment variables in our VMs now?) if not, then based on platform that image runs now , which is not good for cross-platform builds, but since now we don't have cross-builds, it will work fine. The approach , again is the same: lets encapsulate the information we need in edible form, not like this one: #!bash -lex # # build-vm.sh -- Builds Cog Virtual Machine. Have to be used together with Jenkins. # # Copyright (c) 2012 Christophe Demarey # export PHARO_VM=`$WORKSPACE/pharo-shell-scripts/fetchLatestVM.sh` if [ -z "$PHARO_VM" ] ; then echo "PHARO_VM environment variable is not set." exit 1 fi # Set environment ============================================================ PROCESS_PLUGIN="UnixOSProcessPlugin" EXTERNAL_PLUGINS="FT2Plugin" ZIP_FILTER='*' if [ "$OS" == "win" ]; then set -e # Stop the execution if a command fails! CONFIGNAME="CogWindowsConfig" PROCESS_PLUGIN="Win32OSProcessPlugin" ZIP_FILTER=' *.exe *.dll' elif [ "$OS" == "mac" ]; then CONFIGNAME="CogCocoaIOSConfig" export MACOSX_DEPLOYMENT_TARGET=10.5 export CC=/usr/bin/gcc-4.2 export CXX=/usr/bin/g++-4.2 else # [ "$OS" == "linux" ]; then CONFIGNAME="CogUnixConfig" export EXTERNAL_PLUGINS="SqueakSSLPlugin $EXTERNAL_PLUGINS" fi # Unpack sources ============================================================= cd "$WORKSPACE" rm -rf cog tar -xzf cog.tar.gz || echo # echo needed for Windows build (error on symlinks creation) mkdir -p cog/build mkdir -p cog/image cd cog/image unzip -o ../../vmmaker-image.zip # Generate sources =========================================================== echo "$CONFIGNAME new addExternalPlugins: #( $EXTERNAL_PLUGINS ); addInternalPlugins: #( $PROCESS_PLUGIN ); generateSources; generate. Smalltalk snapshot: false andQuit: true." > ./script.st "$PHARO_VM" -headless generator.image script.st -headless cd ../../ tar -czf ${CONFIGNAME}-sources.tar.gz -C cog . # Compile ==================================================================== cd cog/build if [ "$OS" == "win" ]; then cmake -G "MSYS Makefiles" . else cmake . fi make if [ "$OS" == "mac" ]; then make install fi cd .. # Install SSL Plugin ========================================================= SSL_PLUGIN_URL='http://squeakssl.googlecode.com/files/SqueakSSL-bin-0.1.5.zip' SSL_PLUGIN_ZIP='SqueakSSL-bin-0.1.5.zip' SSL_PLUGIN_OUT='SqueakSSL-bin' test -e 'SqueakSSL-bin-0.1.5.zip' || \ ($WORKSPACE/download.sh $SSL_PLUGIN_ZIP $SSL_PLUGIN_URL && unzip -o $SSL_PLUGIN_ZIP) if [ "$OS" == "win" ]; then cp $SSL_PLUGIN_OUT/win/* results/ #elif [ "$OS" == "linux" ]; then # cp $SSL_PLUGIN_OUT/unix/so.SqueakSSL results/libSqueakSSL.so fi rm -rf $SSL_PLUGIN_OUT # Archive ==================================================================== cd results COG_ZIP_FILE="Cog-${OS}.zip" zip -r $COG_ZIP_FILE $ZIP_FILTER mv -f $COG_ZIP_FILE ../../ #if [ "$OS" == "mac" ]; then # zip -r ../build/CogVM.zip CogVM.app # mv -f ../build/CogVM.zip ../../ #else # zip -r Cog.zip $ZIP_FILTER # mv Cog.zip ../../ #fi # success exit 0 Another thing, which i discussed locally , i thinking about creating a dedicated blog for VM developers, where we can share the news and describe details about changes and stuff.. In a way, that it will serve as a source of information about VM , jenkins , configurations, settings , building etc etc.. Because all of the bits of knowledge , which we collected till now is kind of floating in the air, and like any energy it tends to dissipate (things we remember and forget, the more things we should keep in head, the faster it happens). Also, blog is preferable to just simple CHANGELOG file (or similar), because it is two-way communication , and people can comment and discuss things. -- Best regards, Igor Stasenko.

July 30, 2012

Re: [Pharo-project] Delete workspace before build starts

by Sean P. DeNigris

Igor Stasenko wrote > > It was never public (only logged users can navigate workspace contents). > That's right -- View this message in context: http://forum.world.st/Delete-workspace-before-build-starts-tp4642104p464214… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 30, 2012

Re: [Pharo-project] Delete workspace before build starts

by Igor Stasenko

On 29 July 2012 23:32, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > as I see, there is a new job configuration option "Delete workspace > before build starts". From what plugin does it come? I want to notice > that now workspaces on Jenkins are not visible to public. > It was never public (only logged users can navigate workspace contents). .. if i don't mistaken. > -- Pavel > -- Best regards, Igor Stasenko.

July 30, 2012

[Pharo-project] Delete workspace before build starts

by Pavel Krivanek

Hi, as I see, there is a new job configuration option "Delete workspace before build starts". From what plugin does it come? I want to notice that now workspaces on Jenkins are not visible to public. -- Pavel

July 29, 2012

Re: [Pharo-project] System package

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/detail?id=6476 :)

July 29, 2012