- Moose-dev - INF Mailman

by Tudor Girba

Hi, Over the past week I worked on strengthening the new Jenkins infrastructure: - created multiple jobs for Moose subprojects like Fame, Glamour or PetitParser. We should continue to create such jobs for all projects. - Made the jobs to react on commits to the respective repositories, and to trigger the full Moose build. Like this we both ensure that every individual project is loadable as standalone, and we ensure that the integration tests are run after every commit. - created shortcuts: ci.moosetechnology.org -> https://ci.inria.fr/moose/ ci.moosetechnology.org//moose-latest-dev.zip -> https://ci.inria.fr/moose/job/moose-latest-dev-4.8/lastSuccessfulBuild/arti… Cheers, Doru -- www.tudorgirba.com "To utilize feedback, you first have to acquire it."

12 years, 3 months

3
2
0 0

Glamour Roassal edgesFrom in nested layout (4.8)

by Stephan Eggermont

Hi, I am trying to get the edges to superclass to cross the package boundary. Could be related to Issue 845 Cheers, Stephan a roassal title: 'Complexity'; painting: [:view| | packages classes allClasses | packages := RPackageOrganizer default packages select: [ :p | p packageName beginsWith: 'Inno-' ]. allClasses := IdentitySet new. packages do: [ :package | allClasses addAll: package classes ]. view shape rectangle. view nodes: packages forEach: [ :aPackage | view interaction action: #browse. view shape rectangle width: [:cls | cls instVarNames size * 3]; height: [:cls | cls methods size ]; fillColor: (RONColorLinearNormalizer inContext: (allClasses) withCommand: [:cls | cls methods inject: 0 into: [:sum :el | sum + el getSource lineCount]] lowColor: Color green highColor: Color red). view nodes: aPackage classes. view edgesFrom: #superclass. view treeLayout ]. view gridLayout ]

12 years, 3 months

2
1
0 0

Extra ^ test on petitparser compositeparsers?

by Stephan Eggermont

Hi, Would it make sense to test PPCompositeParser subclasses to not end with returnSelf for productions? Each time I start building a new parser I manage to forget a few ^'s I could either add some code to PPCompositeParserTest>parserInstance to check methods having same-named instance variables, or do the same to the PPCompositeParser itself Stephan

12 years, 3 months

1
0
0 0

Issue 920 in moose-technology: Petit parser UI shows only production rules that have an instance variable in the selected class

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 920 by norbert.hartl: Petit parser UI shows only production rules that have an instance variable in the selected class http://code.google.com/p/moose-technology/issues/detail?id=920 In the petit parser UI if I select a class I can see all production rules of that class. If I have a derived parser class that does not implement every of the production rules I get only those which are defined in the derived class. It would be good if the pane of the production rules list could show productions from every class in the hierarchie above the petit parser ones. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

12 years, 3 months

1
1
0 0

Build failed in Jenkins: moose-latest-dev-4.8 #91

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/91/> ------------------------------------------ Started by user tudor(a)tudorgirba.com Building remotely on moose-slave in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> Deleting project workspace... done [moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson8583979152805326.sh + bash + wget --quiet -O - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh Downloading the latest 2.0 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Pharo.changes + bash + wget --quiet -O - http://pharo.gforge.inria.fr/ci/script/ciPharoVMLatest.sh Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/pharo-linux-latest.zip vm/pharo Downloading PharoV10.sources: http://files.pharo.org/image//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/image//PharoV20.sources.zip Creating starter scripts vm.sh and vm-ui.sh Please install the 32bit libraries sudo aptitude install ia32-libs + ./vm.sh Pharo.image save moose-latest-dev-4.8 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./vm.sh moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m[31m==== Startup Error: MetacelloProjectSpecLoadError: No version found for #development of ConfigurationOfMondrian [0mMetacelloMCProjectSpec>>loadVersion: MetacelloMCProjectSpec>>load MetacelloProjectReferenceSpec>>loadUsing:gofer: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [:pkg | pkg loadUsing: self gofer: gofer] OrderedCollection>>do: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader>>atomicLoadPackageSpecs:repositories: in Block: [super linearLoadPackageSpecs: packageSpecs reposi...etc... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushAtomicLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>atomicLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [:dict | ^ self executeLoadFromArray: anArray] MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [self versionSpec loader: newLoader.... BlockClosure>>ensure: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [[self versionSpec loader: newLoader.... MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: Job>>run NonInteractiveUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: [0m[31mGot startup errors: [0m[31m MetacelloProjectSpecLoadError: No version found for #development of ConfigurationOfMondrian [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

12 years, 3 months

3
10
0 0

CI down?

by Yuriy Tymchuk

https://ci.inria.fr/moose 503 error -- View this message in context: http://moose-dev.97923.n3.nabble.com/CI-down-tp4026554.html Sent from the moose-dev mailing list archive at Nabble.com.

12 years, 3 months

1
0
0 0

Fwd: [Evol] Call for PhD candidates in the Software Composition Group, U Bern

by Tudor Girba

---------- Forwarded message ---------- From: Oscar Nierstrasz <oscar(a)iam.unibe.ch> Date: Tue, Mar 19, 2013 at 2:27 PM Subject: [Evol] Call for PhD candidates in the Software Composition Group, U Bern To: evol(a)lists.inf.unisi.ch Applications are invited for PhD candidates at the Software Composition Group, University of Bern, Switzerland. The Software Composition Group carries out research in software analysis and programming language design and implementation, with a view to enabling software evolution. The SCG is led by Prof. Oscar Nierstrasz and is part of the Institute of Computer Science and Applied Mathematics (IAM) at the University of Berne. Details about current and ongoing research can be found here: http://scg.unibe.ch/research/ The candidate must have a MSc in Computer Science (equivalent to a Swiss MSc), should demonstrate strong programming skills, and have research interests in several of the following areas: - software evolution - program understanding - software modeling - model-driven engineering - reverse engineering - domain specific languages - dynamic analysis - integrated development environments - programming language design - virtual machine technology To apply, please send an email including your CV, with references, to Prof. Oscar Nierstrasz (oscar(a)iam.unibe.ch), by April 15, 2013. Oscar Nierstrasz --- Prof. Dr. O. Nierstrasz -- oscar(a)iam.unibe.ch Software Composition Group -- http://scg.unibe.ch/oscar University of Bern -- Tel/Fax +41 31 631.4618/3355 _______________________________________________ Evol mailing list Evol(a)lists.inf.unisi.ch http://lists.inf.unisi.ch/mailman/listinfo/evol -- www.tudorgirba.com "Every thing has its own flow"

12 years, 3 months

1
0
0 0

Failing PetitSmalltalk tests

by Yuriy Tymchuk

Hi. In Pharo 2.0 PetitSmalltalk tests are failing. Firs of all there are real problems with parsing as some test fail because parser finishes to parse before the end of the stream. Right now I don't know what's causing the problem and how to solve it. Then there is a ton of deprecation warnings as PPToken>>#value became deprecated and it's recommended to use #inputValue. It's now hard to fix that, but there are two problems. 1) At places where #value message is sent, not only PPToken is used as a receiver, but sometimes RBToken is used instead. And RBToken does not understand the #inputValue message. This can be hacked by adding a protocol-extension that will return "self value" then, but it's not very nice. 2) Some #value messages are sent from methods in AST-Core package, and I don't know how we should deal with that. Any ideas for solutions? Uko -- View this message in context: http://moose-dev.97923.n3.nabble.com/Failing-PetitSmalltalk-tests-tp4026442… Sent from the moose-dev mailing list archive at Nabble.com.

12 years, 3 months

4
7
0 0

moose job on jenkins

by Tudor Girba

Hi, I put together a little description of how we built the Moose job on Jenkins using the CommandLine infrastructure. Perhaps it is useful for other people as well: http://www.tudorgirba.com/blog/moose-4-8-on-jenkins Cheers, Doru -- www.tudorgirba.com "Be rather willing to give than demanding to get."

12 years, 3 months

4
6
0 0

Migrated SmallDude now….

by Stéphane Ducasse

12 years, 3 months

2
1
0 0

[ANN] Pharo 2.0

by Esteban Lorenzano

We are proud to announce the release of Pharo 2.0! You can find information about Pharo at: http://www.pharo-project.org About this release ------------------ All in all, there were over 1600 issues treated in the issue tracker and 1350 improvements integrated into 2.0. http://code.google.com/p/pharo/issues/list?can=1&q=Milestone%3D2.0+status%3… Read it again, yes 1350 is huge, take two minutes and have a look at the list of improvements! Now you got the feel of the effort. And this was a true community effort. It is possible because people worldwide helped! We want to deeply thank them. We want to thank Inria for its constant support, in particular for the salary of Igor Stasenko and Esteban Lorenzano, and for the help in the infrastructure. We have accomplished this huge task for a better system because we were together. Do not forget that we are working on a consortium to support our system: - http://consortium.pharo.org (for companies and organizations) - http://association.pharo.org (for individuals) Our goal is to build a system so that we can make a living with our creativity and programming skills. You can find information about Pharo on http://www.pharo-project.org. In particular, you may be interested in: - Joining us and getting help http://www.pharo-project.org/community - Getting the Pharo By Example book (available as a free PDF): http://www.pharobyexample.org - Watching the screencasts http://www.pharocasts.com - Reporting problems http://www.pharo-project.org/community/issue-tracking - Reading the forth coming book http://rmod.lille.inria.fr/pbe2 - Reading the Pharo vision document http://bit.ly/HNkEru Thanks a lot for your participation, energy and fun. -- The Pharo Team Summarized issues for 2.0 ================== UI --- - Spec - Widget enhancements - Layout improvements/cleanups - Keybindings - New icons (famfam) - Growl style notifications - Revamp progress bar Developer tools --------------- - Nautilus browser - Critics browser - Improved version diff browsing - Spotlight - Revamp Code Completion and smart chars - Interactive navigation using ctrl/cmd+click over classes/methods - Shout themes - Andreas profiler Networking ----------- - Update Zinc - Zodiac (SSL) System ------- - System Announcer - RPackage replacing PackageInfo - Command line tools / Headless mode - Native boost - Update Ring metamodel - Fuel serializer - Freetype fonts Kernel ------ - DateAndTime refactoring - Updated FileSystem and replaced FileDirectory VM -- - Latests cog builds - SSLPlugin - FilePlugin enhancements - SocketPlugin fixes - Included libraries: freetype2, cairo Cleanups ------------- - FileDirectory removed (replaced by FileSystem) - SmartRefStream and ReferenceStream removed (replaced by Fuel) - PackageInfo deprecated (replaced by RPackage) Other ------- - Zeroconf scripts - Continuous Integration for every aspect of our release process. Not all the changes are reported here, but this is to give you an impression, you can find better explanation here: https://code.google.com/p/pharo/wiki/ActionsInPharo20

12 years, 3 months

1
0
0 0

pharoconf | mooseday | 2013 - call for participation

by Tudor Girba

(please distribute) We are happy to invite you to the PharoConf | MooseDay | 2013: http://scg.unibe.ch/wiki/events/pharoconf-mooseday-2013 The conference will take place at the University of Bern during April 2-4: - PharoConf (April 2,3) - MooseDay (April 4) The conference will be free and will even include a free lunch. Yes, free lunch. No trick. We only kindly ask you to register online for each event as soon as possible. STUDENT SPONSORSHIPS: ESUG will sponsor the travel of up to 10 students with 150 EUR / person. Please apply for sponsorship by mail at esug-info(a)esug.org. First-come, first-served. The conference sponsors will sponsor the travel of up to 10 students with up to 200 CHF / person. Please apply for sponsorship before the conference by mail at tudor(a)tudorgirba.com. First-come, first-served. IMPORTANT If you are a student, please bring your student cards with you to help us limit the lunch costs. Cheers, The organizers

12 years, 3 months

1
0
0 0

configuration of roeltyper is broken

by Tudor Girba

Hi, The ConfigurationOfRoelTyper is broken because version 1.0 tries to load as a package that does not exist. I wanted to commit the fix, but the project is hosted in the RMoD team for some reason and I do not have access there. The correct definition would be: version100: spec <version: '1.0' imports: #('1.0-baseline') > spec for: #common do: [ spec blessing: #release. spec description: 'Migration to SmalltalkHub'. spec package: 'RoelTyper' with: 'RoelTyper-StephaneDucasse.86' ] Can anyone perform this modification? Afterwards we can put it back into the ConfigurationOfMoose. Cheers, Doru -- www.tudorgirba.com "Speaking louder won't make the point worthier."

12 years, 3 months

3
2
0 0

branded moose-dev image

by Tudor Girba

Hi, I improved the build infrastructure and now we have a branded image with the Moose logo and the GLMUITheme installed: https://ci.inria.fr/moose/job/moose-latest-dev-4.8/lastSuccessfulBuild/arti… The way I solved it was to introduce the MooseImageSetupCommandLineHandler that - installs the logo image from http://www.moosetechnology.org/res/media/logo100x240.png - installs the theme - closes all windows The setup is triggered from the build script via (after installing the code): ./vm.sh $JOB_NAME.image mooseimagesetup If we want a different setup we can easily control it from now on by extending this command. It's really cool to have everything in Smalltalk :). Cheers, Doru -- www.tudorgirba.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

12 years, 3 months

2
1
0 0

migrating roassal to sthub

by Tudor Girba

Hi Alex, Do you plan to migrate Roassal to STHub, or should someone else do it? Cheers, Doru -- www.tudorgirba.com "Reasonable is what we are accustomed with."

12 years, 3 months

3
2
0 0

Re: Issue 382 in moose-technology: CMD + W does not close Mondrian window

by moose-technology＠googlecode.com

Comment #1 on issue 382 by tudor.gi...(a)gmail.com: CMD + W does not close Mondrian window http://code.google.com/p/moose-technology/issues/detail?id=382 This is still an issue and it hinders usability. Alex, could you take a look at it?

12 years, 3 months

1
1
0 0

Issue 871 in moose-technology: One click distribution has old vms

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium OpSys-All Milestone-4.7 New issue 871 by tu...(a)tudorgirba.com: One click distribution has old vms http://code.google.com/p/moose-technology/issues/detail?id=871 We need to update the VMs for the one click distribution.

12 years, 3 months

1
1
0 0

Issue 905 in moose-technology: The rendering of ListPresentation should not raise error when setting the selection to a value outside of the visible elements

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: usman.bh...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour New issue 905 by tu...(a)tudorgirba.com: The rendering of ListPresentation should not raise error when setting the selection to a value outside of the visible elements http://code.google.com/p/moose-technology/issues/detail?id=905 testSettingSelectionOutsideOfVisibleElementsShouldNotRaiseError | browser items | browser := GLMTabulator withStatusbar. browser column: #one; column: #two. browser transmit to: #one; andShow: [ :a | a tree showOnly: 30 ]. window := browser openOn: (1 to: 100). self shouldnt: [((browser paneNamed: #one) port:#selection) value: 40] raise: Error.

12 years, 3 months

1
6
0 0

grease-core extensions that exist in pharo 2.0

by Tudor Girba

Hi, (sorry for the cross-post, but I was not quite sure where to send it) In Grease-Core, there are a couple of String extensions (trimBoth, trimBoth:, trimLeft, trimLeft: trimRight, trimRight:, trimLeft:right:) that already exist in Pharo 2.0. I would like to remove them and let platform-specific extension packages add them if needed. Unfortunately, I do not have an account for the www.squeaksource.com/Seaside30.html repository. Can anyone give me access to the repository? Cheers, Doru -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

12 years, 3 months

2
1
0 0

roassal still loads fuel

by Tudor Girba

Hi, Roassal still loads Fuel in Pharo 2.0, and this makes the package dirty, because it already exists in Pharo. Cheers, Doru -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

12 years, 3 months

3
10
0 0

cleaning moose

by Tudor Girba

Hi, I am continuing the cleaning of Moose. In the process I have removed several class extensions that were already present in the Pharo 2.0 image. Now we have only 2 packages dirty (Kernel and Collections-Strings) and they are due to Grease which is loaded by Magritte which is loaded by Glamour. Anyone wants to take a look at them? Cheers, Doru -- www.tudorgirba.com "Every thing should have the right to be different."

12 years, 3 months

1
0
0 0

Build failed in Jenkins: moose-latest-dev #1293

by admin＠moosetechnology.org

See <http://ci.moosetechnology.org:8020/job/moose-latest-dev/1293/> ------------------------------------------ Started by timer Building in workspace <http://ci.moosetechnology.org:8020/job/moose-latest-dev/ws/> [workspace] $ /bin/sh -xe /tmp/hudson4533343565087546929.sh + rm -rf <http://ci.moosetechnology.org:8020/job/moose-latest-dev/ws/moose> <http://ci.moosetechnology.org:8020/job/moose-latest-dev/ws/moose-tests> + /srv/ci.moosetechnology.org/builder/build.sh -i Pharo-1.4 -s monticello-fix-for-14 -s moose -s glamorous-theme -s moose-clean -s glamorous-toolkit -s cleanupforrelease -o moose [31m[33m =============================================================================== Notice: Errors in script loaded from <http://ci.moosetechnology.org:8020/job/moose-latest-dev/1293/artifact/moose…> =============================================================================== [0m[0m[31m==== Startup Error: Error: Name not found: FuelTestsCompatibilityBeforePharo20 [0mMetacelloMCVersionSpec(Object)>>error: MetacelloMCVersionSpec>>resolveToLoadableSpec:forMap:packages: in Block: [^ self error: 'Name not found: ' , aString] MetacelloMCVersionSpec>>packageNamed:forMap:ifAbsent: MetacelloMCVersionSpec>>resolveToLoadableSpec:forMap:packages: MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: in Block: [:req | (self... Set>>do: MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: MetacelloMCVersionSpec>>resolveToLoadableSpecs: MetacelloMCVersionSpec>>expandToLoadableSpecNames: in Block: [:cache | ... MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [:dict | ... [0m[31mGot startup errors: [0m[31m Error: Name not found: FuelTestsCompatibilityBeforePharo20 [0m blockNoContextSwitchOffset != null 9102 + /srv/ci.moosetechnology.org/builder/build.sh -i moose -s patch-inputsensor -s testrunner -s moose-tests -o moose-tests [31m[33m =============================================================================== Notice: Errors in script loaded from <http://ci.moosetechnology.org:8020/job/moose-latest-dev/ws/moose-tests/moos…> =============================================================================== [0m[0m[31m==== Startup Error: MessageNotUnderstood: receiver of "new" is nil [0mUndefinedObject(Object)>>doesNotUnderstand: #new UndefinedObject>>DoIt Compiler>>evaluate:in:to:notifying:ifFail:logged: Compiler class>>evaluate:for:notifying:logged: Compiler class>>evaluate:for:logged: Compiler class>>evaluate:logged: FileSystemFileStream(PositionableStream)>>fileInAnnouncing: in Block: [| chunk | val := (self peekFor: $!)... BlockClosure>>on:do: FileSystemFileStream(PositionableStream)>>fileInAnnouncing: in Block: [:bar | ... NonInteractiveUIManager(CommandLineUIManager)>>progressInitiationExceptionDefaultAction: [0m[31mGot startup errors: [0m[31m MessageNotUnderstood: receiver of "new" is nil [0m blockNoContextSwitchOffset != null 9102 + /srv/ci.moosetechnology.org/builder/build-oneclick.sh -i moose -o moose_suite-4_7_dev -n Moose -t 'Moose Suite 4.7 Development ' -v 4.7 -c Moose cp: cannot stat `/srv/ci.moosetechnology.org/builder/oneclick-icons/Moose.png': No such file or directory cp: cannot stat `/srv/ci.moosetechnology.org/builder/oneclick-icons/Moose.ico': No such file or directory cp: cannot stat `/srv/ci.moosetechnology.org/builder/oneclick-icons/Moose.icns': No such file or directory /srv/ci.moosetechnology.org/builder/build-oneclick.sh: line 170: zip: command not found Recording test results No test report files were found. Configuration error? Build step 'Publish JUnit test result report' changed build result to FAILURE Archiving artifacts

12 years, 3 months

1
13
0 0

strongSelectin in Glamour

by Nicolas Anquetil

Hi, I have a browser with some kind of "buffer" where I can hold a value selected from one of several list in the browser. The buffer itself is implemented as a pane containing a list with only one element in it, it is populated when I strongSelect (double click) in one of the source list: (browser transmit) to: #buffer; from: #PackagePane port: #strongSelection; andShow: [:a | a list display: [:anEntity | {anEntity} ] ]. (browser transmit) to: #buffer; from: #ClassPane port: #strongSelection; andShow: [:a | a list display: [:anEntity | {anEntity} ] ]. I also transmit from one list to the other with simple selection (click) (browser transmit) to: #ClassPane; from: #PackagePane; andShow: [:b | | gmlList | gmlList := b list. gmlList display: [:anEntity | anEntity classes]]; It works "thusly" : if I click on a package in the PackagePane, its class appear in the ClassPane. If I double click on a package or a class, then it also appears in the "buffer" However, if I double click on a class, it goes correctly in the buffer, but if after I single click on a package, the "buffer" is wiped. This is not the intended behavior ... Bug or feature? and if it is a feature, how to get the feature I want? nicolas -- Nicolas Anquetil -- RMod research team (Inria)

12 years, 3 months

2
3
0 0

missing pharo sources warning in Moose 4.8

by Usman Bhatti

There is a warning in Moose 4.8 regarding the absence of pharo sources. I had added these sources in the build (the artifacts produced by the build). Did someone modify the job to remove the sources from the latest Moose build? usman [image: Inline image 2]

12 years, 3 months

2
1
0 0

Moose logo and glamour-theme?

by Usman Bhatti

Moose 4.8 image does not have a moose logo and glamour-related theme. Do we want to continue the settings from 1.4 (a custom moose logo and glamour-theme) or should we just use the logo and the look/theme that comes with Pharo? usman

12 years, 3 months

2
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev