Re: [Pharo-project] A trend and an unfair comparison about js everywhere
Dne 16. 10. 2012 20:43, piše Igor Stasenko: > IMO, the fundamental difference between personal computer apps, that > they rely on capabilities of your personal computer. While web-apps, > obviously not. > Web-apps mainly relocating the computation onto another computer, > effectively making your personal one to serve as a remote (even if > media-rich) terminal, connected to mainframe. > > Perhaps web was the catalyst for emergence of cloud-computing. But > conceptually, cloud computing is completely orthogonal to 'web', it is > just turning computing power into easily accessible commodity. > Web, of course, can enjoy exploiting this new approach, as well as any > others too. Nowadays web apps are more and more autonomous and client-centric, connecting not just to one server but *many* different services and resources somewhere from the cloud *at once*. Such app is therefore not server-centric anymore but client-centric, as this article explains nicely: Why The Future Of Software And Apps Is Serverless http://www.readwriteweb.com/cloud/2012/10/why-the-future-of-software-and-apps-is-serverless.php Where Smalltalk can find its place in such future? 1. Providing services from the cloud (that's why all cloud related Smalltalk initiatives needs to be supported) 2. Client-centric web apps (that's why Amber and related initiatives are so important) Note also that classic Smalltalk environments like Pharo are still useful and needed in both cases, because we can *develop* both cloud services and client web apps on classic environments with their superior tools, but *deploy* them both in cloud (headless) and on the client (like by Amber generating/emitting JS code to the client). Best regards Janko -- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
[Pharo-project] [update 2.0] #20345
20345 - Issue 6818: All test runners for 2.0 are red on jenkins http://code.google.com/p/pharo/issues/detail?id=6818 Issue 6785: Do we really need to cache DebuggerMethodMap? http://code.google.com/p/pharo/issues/detail?id=6785 Issue 6814: Adde simple Color Scheme Setting http://code.google.com/p/pharo/issues/detail?id=6814 Diff information: http://ss3.gemstone.com/ss/Pharo20/Tests-MarcusDenker.469.diff http://ss3.gemstone.com/ss/Pharo20/System-Support-MarcusDenker.719.diff http://ss3.gemstone.com/ss/Pharo20/Shout-MarcusDenker.156.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1213.diff http://ss3.gemstone.com/ss/Pharo20/CompilerTests-MarcusDenker.125.diff -- Marcus Denker -- http://marcusdenker.de
[Pharo-project] pharo-2.0-tests » mac - Build # 416 - Still Failing!
BUILD FAILUREBuild URLhttps://ci.lille.inria.fr/pharo/job/pharo-2.0-tests/./label_exp=mac/416/Project:label_exp=macDate of build:Wed, 17 Oct 2012 11:12:35 +0200Build duration:7 min 37 secCHANGESNo ChangesCONSOLE OUTPUT[...truncated 142 lines...]2012-10-17 11:18:27.630 CogVM[51222:903] invalid pixel format2012-10-17 11:18:27.633 CogVM[51222:903] invalid context2012-10-17 11:18:27.637 CogVM[51222:903] invalid pixel format2012-10-17 11:18:27.640 CogVM[51222:903] invalid context2012-10-17 11:18:33.998 CogVM[51222:903] invalid pixel format2012-10-17 11:18:34.091 CogVM[51222:903] invalid context2012-10-17 11:18:34.150 CogVM[51222:903] invalid pixel format2012-10-17 11:18:34.153 CogVM[51222:903] invalid context2012-10-17 11:18:38.774 CogVM[51222:903] invalid pixel format2012-10-17 11:18:38.864 CogVM[51222:903] invalid context2012-10-17 11:18:38.900 CogVM[51222:903] invalid pixel format2012-10-17 11:18:38.904 CogVM[51222:903] invalid context2012-10-17 11:18:38.907 CogVM[51222:903] invalid pixel format2012-10-17 11:18:38.910 CogVM[51222:903] invalid context2012-10-17 11:18:38.913 CogVM[51222:903] invalid pixel format2012-10-17 11:18:38.916 CogVM[51222:903] invalid context2012-10-17 11:18:38.919 CogVM[51222:903] invalid pixel format2012-10-17 11:18:38.923 CogVM[51222:903] invalid context2012-10-17 11:18:38.926 CogVM[51222:903] invalid pixel format2012-10-17 11:18:38.929 CogVM[51222:903] invalid context2012-10-17 11:18:39.146 CogVM[51222:903] invalid pixel format2012-10-17 11:18:39.235 CogVM[51222:903] invalid context2012-10-17 11:18:39.274 CogVM[51222:903] invalid pixel format2012-10-17 11:18:39.277 CogVM[51222:903] invalid context2012-10-17 11:18:39.281 CogVM[51222:903] invalid pixel format2012-10-17 11:18:39.284 CogVM[51222:903] invalid context2012-10-17 11:18:39.287 CogVM[51222:903] invalid pixel format2012-10-17 11:18:39.290 CogVM[51222:903] invalid context2012-10-17 11:18:39.293 CogVM[51222:903] invalid pixel format2012-10-17 11:18:39.296 CogVM[51222:903] invalid context2012-10-17 11:18:39.299 CogVM[51222:903] invalid pixel format2012-10-17 11:18:39.302 CogVM[51222:903] invalid context./build.sh: line 155: 51222 Bus error "$PHARO_VM" $PHARO_PARAM "$OUTPUT_IMAGE" "$OUTPUT_SCRIPT" -headlessBuild step 'Execute shell' marked build as failureArchiving artifactsRecording test resultsERROR: Failed to archive test reportshudson.util.IOException2: remote file operation failed: /Users/hudson/jenkins/workspace/pharo-2.0-tests/label_exp/mac at hudson.remoting.Channel@44c75ba4:pharo-build-mac.lille.inria.fr at hudson.FilePath.act(FilePath.java:847) at hudson.FilePath.act(FilePath.java:824) at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:122) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:134) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:807) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:782) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:729) at hudson.model.Run.execute(Run.java:1541) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236)Caused by: hudson.util.IOException2: Failed to read /Users/hudson/jenkins/workspace/pharo-2.0-tests/label_exp/mac/Pharo-2.0-AfterRunningTests/Tests-Monticello-Test.xml at hudson.tasks.junit.TestResult.parse(TestResult.java:244) at hudson.tasks.junit.TestResult.parse(TestResult.java:163) at hudson.tasks.junit.TestResult.parse(TestResult.java:140) at hudson.tasks.junit.TestResult.(TestResult.java:116) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:117) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2308) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680)Caused by: org.dom4j.DocumentException: Error on line 339 of document file:///Users/hudson/jenkins/workspace/pharo-2.0-tests/label_exp/mac/Pharo-2.0-AfterRunningTests/Tests-Monticello-Test.xml : XML document structures must start and end within the same entity. Nested exception: XML document structures mus
[Pharo-project] [update 2.0] #20346
20346 - Issue 6827: add Solarized style text color scheme http://code.google.com/p/pharo/issues/detail?id=6827 Issue 6824: Nautilus Issue Creation Improvements: accept on enter & no autocompletion http://code.google.com/p/pharo/issues/detail?id=6824 Issue 6823: SliceMaker should trim pasted nonDigit Characters from IssueNumber http://code.google.com/p/pharo/issues/detail?id=6823 Issue 6821: Fix Nautilus Shortcut Browse Restricted Shortcut http://code.google.com/p/pharo/issues/detail?id=6821 Diff information: http://ss3.gemstone.com/ss/Pharo20/Shout-MarcusDenker.157.diff http://ss3.gemstone.com/ss/Pharo20/Nautilus-MarcusDenker.366.diff http://ss3.gemstone.com/ss/Pharo20/MonticelloGUI-MarcusDenker.193.diff http://ss3.gemstone.com/ss/Pharo20/CI-Core-MarcusDenker.46.diff -- Marcus Denker -- http://marcusdenker.de
[Pharo-project] pharo-2.0-tests » win - Build # 416 - Still Failing!
BUILD FAILUREBuild URLhttps://ci.lille.inria.fr/pharo/job/pharo-2.0-tests/./label_exp=win/416/Project:label_exp=winDate of build:Wed, 17 Oct 2012 11:12:35 +0200Build duration:15 minCHANGESNo ChangesJUnit TestsName: AST.Tests.Core Failed: 0 test(s), Passed: 79 test(s), Skipped: 0 test(s), Total: 79 test(s)Name: AST.Tests.Semantic Failed: 0 test(s), Passed: 25 test(s), Skipped: 0 test(s), Total: 25 test(s)Name: Announcements.Tests.Core Failed: 0 test(s), Passed: 29 test(s), Skipped: 0 test(s), Total: 29 test(s)Name: BalloonTests.Collections Failed: 0 test(s), Passed: 34 test(s), Skipped: 0 test(s), Total: 34 test(s)Name: CollectionsTests.Arrayed Failed: 0 test(s), Passed: 553 test(s), Skipped: 0 test(s), Total: 553 test(s)Name: CollectionsTests.Atomic Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s)Name: CollectionsTests.Sequenceable Failed: 0 test(s), Passed: 912 test(s), Skipped: 0 test(s), Total: 912 test(s)Name: CollectionsTests.SplitJoin Failed: 0 test(s), Passed: 27 test(s), Skipped: 0 test(s), Total: 27 test(s)Name: CollectionsTests.Stack Failed: 0 test(s), Passed: 16 test(s), Skipped: 0 test(s), Total: 16 test(s)Name: CollectionsTests.Streams Failed: 0 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 37 test(s)Name: CollectionsTests.Strings Failed: 0 test(s), Passed: 606 test(s), Skipped: 0 test(s), Total: 606 test(s)Name: CollectionsTests.Support Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s)Name: CollectionsTests.Unordered Failed: 0 test(s), Passed: 1954 test(s), Skipped: 0 test(s), Total: 1954 test(s)Name: CollectionsTests.Weak Failed: 0 test(s), Passed: 739 test(s), Skipped: 0 test(s), Total: 739 test(s)Name: CompilerTests Failed: 0 test(s), Passed: 180 test(s), Skipped: 0 test(s), Total: 180 test(s)Name: CompressionTests.Archive Failed: 2 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 7 test(s)Failed: CompressionTests.Archive.ZipArchiveTest.testCreateWithRelativeNamesFailed: CompressionTests.Archive.ZipArchiveTest.testZipName: Deprecated20 Failed: 0 test(s), Passed: 7 test(s), Skipped: 0 test(s), Total: 7 test(s)Name: FileSystem.Tests.Core Failed: 0 test(s), Passed: 185 test(s), Skipped: 0 test(s), Total: 185 test(s)Name: FileSystem.Tests.Disk Failed: 0 test(s), Passed: 53 test(s), Skipped: 0 test(s), Total: 53 test(s)Name: FileSystem.Tests.Memory Failed: 0 test(s), Passed: 50 test(s), Skipped: 0 test(s), Total: 50 test(s)Name: FreeTypeTests.cache Failed: 0 test(s), Passed: 23 test(s), Skipped: 0 test(s), Total: 23 test(s)Name: FuelMetalevelTests Failed: 0 test(s), Passed: 155 test(s), Skipped: 0 test(s), Total: 155 test(s)Name: FuelTests Failed: 0 test(s), Passed: 246 test(s), Skipped: 0 test(s), Total: 246 test(s)Name: FuelTests.Collections Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s)Name: FuelTests.Streams Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)Name: Gofer.Tests Failed: 7 test(s), Passed: 35 test(s), Skipped: 0 test(s), Total: 42 test(s)Failed: Gofer.Tests.GoferOperationTest.testLocalChangesFailed: Gofer.Tests.GoferOperationTest.testMergeFailed: Gofer.Tests.GoferOperationTest.testReinitializeFailed: Gofer.Tests.GoferOperationTest.testRemoteChangesFailed: Gofer.Tests.GoferOperationTest.testRevertFailed: Gofer.Tests.GoferOperationTest.testUnloadFailed: Gofer.Tests.GoferOperationTest.testUpdateName: Graphics.Tests.Files Failed: 0 test(s), Passed: 47 test(s), Skipped: 0 test(s), Total: 47 test(s)Name: Graphics.Tests.Primitives Failed: 0 test(s), Passed: 57 test(s), Skipped: 0 test(s), Total: 57 test(s)Name: HelpSystem.Tests.Builders Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s)Name: HelpSystem.Tests.Core.Model Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s)Name: HelpSystem.Tests.Core.UI Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: HelpSystem.Tests.Core.Utilities Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: KernelTests.Chronology Failed: 0 test(s), Passed: 583 test(s), Skipped: 0 test(s), Total: 583 test(s)Name: KernelTests.Classes Failed: 0 test(s), Passed: 68 test(s), Skipped: 0 test(s), Total: 68 test(s)Name: KernelTests.Exception Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)Name: KernelTests.Methods Failed: 0 test(s), Passed: 180 test(s), Skipped: 0 test(s), Total: 180 test(s)Name: KernelTests.Numbers Failed: 0 test(s), Passed: 276 test(s), Skipped: 0 test(s), Total: 276 test(s)Name: KernelTests.Objects Failed: 0 test(s), Passed: 87 test(s), Skipped: 0 test(s), Total: 87 test(s)Name: KernelTests.Pragmas Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)Name: KernelTests.Processes Failed: 0 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 37 test(s)Name: Keymapping.Tests Failed: 0 test(s), Passed: 38 test(s), Skipped: 0 test(s), Total: 38 test(s)Name: MorphicTests.Basic Failed
[Pharo-project] pharo-2.0-tests » mac - Build # 417 - Still Failing!
BUILD FAILUREBuild URLhttps://ci.lille.inria.fr/pharo/job/pharo-2.0-tests/./label_exp=mac/417/Project:label_exp=macDate of build:Wed, 17 Oct 2012 11:29:11 +0200Build duration:6 min 20 secCHANGESNo ChangesCONSOLE OUTPUT[...truncated 150 lines...]2012-10-17 11:36:42.427 CogVM[51470:903] invalid pixel format2012-10-17 11:36:42.496 CogVM[51470:903] invalid context2012-10-17 11:36:42.499 CogVM[51470:903] invalid pixel format2012-10-17 11:36:42.502 CogVM[51470:903] invalid context2012-10-17 11:36:51.109 CogVM[51470:903] invalid pixel format2012-10-17 11:36:51.113 CogVM[51470:903] invalid context2012-10-17 11:36:51.116 CogVM[51470:903] invalid pixel format2012-10-17 11:36:51.131 CogVM[51470:903] invalid context2012-10-17 11:36:58.549 CogVM[51470:903] invalid pixel format2012-10-17 11:36:58.552 CogVM[51470:903] invalid context2012-10-17 11:36:58.555 CogVM[51470:903] invalid pixel format2012-10-17 11:36:58.558 CogVM[51470:903] invalid context2012-10-17 11:36:58.562 CogVM[51470:903] invalid pixel format2012-10-17 11:36:58.565 CogVM[51470:903] invalid context2012-10-17 11:36:58.568 CogVM[51470:903] invalid pixel format2012-10-17 11:36:58.572 CogVM[51470:903] invalid context2012-10-17 11:36:58.575 CogVM[51470:903] invalid pixel format2012-10-17 11:36:58.578 CogVM[51470:903] invalid context2012-10-17 11:36:58.581 CogVM[51470:903] invalid pixel format2012-10-17 11:36:58.585 CogVM[51470:903] invalid context2012-10-17 11:36:59.131 CogVM[51470:903] invalid pixel format2012-10-17 11:36:59.134 CogVM[51470:903] invalid context2012-10-17 11:36:59.137 CogVM[51470:903] invalid pixel format2012-10-17 11:36:59.141 CogVM[51470:903] invalid context2012-10-17 11:36:59.144 CogVM[51470:903] invalid pixel format2012-10-17 11:36:59.147 CogVM[51470:903] invalid context2012-10-17 11:36:59.150 CogVM[51470:903] invalid pixel format2012-10-17 11:36:59.153 CogVM[51470:903] invalid context2012-10-17 11:36:59.156 CogVM[51470:903] invalid pixel format2012-10-17 11:36:59.159 CogVM[51470:903] invalid context2012-10-17 11:36:59.162 CogVM[51470:903] invalid pixel format2012-10-17 11:36:59.165 CogVM[51470:903] invalid context./build.sh: line 155: 51470 Bus error "$PHARO_VM" $PHARO_PARAM "$OUTPUT_IMAGE" "$OUTPUT_SCRIPT" -headlessBuild step 'Execute shell' marked build as failureArchiving artifactsRecording test resultsERROR: Failed to archive test reportshudson.util.IOException2: remote file operation failed: /Users/hudson/jenkins/workspace/pharo-2.0-tests/label_exp/mac at hudson.remoting.Channel@44c75ba4:pharo-build-mac.lille.inria.fr at hudson.FilePath.act(FilePath.java:847) at hudson.FilePath.act(FilePath.java:824) at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:122) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:134) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:807) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:782) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:729) at hudson.model.Run.execute(Run.java:1541) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236)Caused by: hudson.util.IOException2: Failed to read /Users/hudson/jenkins/workspace/pharo-2.0-tests/label_exp/mac/Pharo-2.0-AfterRunningTests/Tests-Monticello-Test.xml at hudson.tasks.junit.TestResult.parse(TestResult.java:244) at hudson.tasks.junit.TestResult.parse(TestResult.java:163) at hudson.tasks.junit.TestResult.parse(TestResult.java:140) at hudson.tasks.junit.TestResult.(TestResult.java:116) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:117) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2308) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680)Caused by: org.dom4j.DocumentException: Error on line 339 of document file:///Users/hudson/jenkins/workspace/pharo-2.0-tests/label_exp/mac/Pharo-2.0-AfterRunningTests/Tests-Monticello-Test.xml : XML document structures must start and end within the same entity. Nested exception: XML document structures mus
[Pharo-project] pharo-2.0-tests » win - Build # 417 - Still Failing!
BUILD FAILUREBuild URLhttps://ci.lille.inria.fr/pharo/job/pharo-2.0-tests/./label_exp=win/417/Project:label_exp=winDate of build:Wed, 17 Oct 2012 11:29:11 +0200Build duration:15 minCHANGESNo ChangesJUnit TestsName: AST.Tests.Core Failed: 0 test(s), Passed: 79 test(s), Skipped: 0 test(s), Total: 79 test(s)Name: AST.Tests.Semantic Failed: 0 test(s), Passed: 25 test(s), Skipped: 0 test(s), Total: 25 test(s)Name: Announcements.Tests.Core Failed: 0 test(s), Passed: 29 test(s), Skipped: 0 test(s), Total: 29 test(s)Name: BalloonTests.Collections Failed: 0 test(s), Passed: 34 test(s), Skipped: 0 test(s), Total: 34 test(s)Name: CollectionsTests.Arrayed Failed: 0 test(s), Passed: 553 test(s), Skipped: 0 test(s), Total: 553 test(s)Name: CollectionsTests.Atomic Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s)Name: CollectionsTests.Sequenceable Failed: 0 test(s), Passed: 912 test(s), Skipped: 0 test(s), Total: 912 test(s)Name: CollectionsTests.SplitJoin Failed: 0 test(s), Passed: 27 test(s), Skipped: 0 test(s), Total: 27 test(s)Name: CollectionsTests.Stack Failed: 0 test(s), Passed: 16 test(s), Skipped: 0 test(s), Total: 16 test(s)Name: CollectionsTests.Streams Failed: 0 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 37 test(s)Name: CollectionsTests.Strings Failed: 0 test(s), Passed: 606 test(s), Skipped: 0 test(s), Total: 606 test(s)Name: CollectionsTests.Support Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s)Name: CollectionsTests.Unordered Failed: 0 test(s), Passed: 1954 test(s), Skipped: 0 test(s), Total: 1954 test(s)Name: CollectionsTests.Weak Failed: 0 test(s), Passed: 739 test(s), Skipped: 0 test(s), Total: 739 test(s)Name: CompilerTests Failed: 0 test(s), Passed: 180 test(s), Skipped: 0 test(s), Total: 180 test(s)Name: CompressionTests.Archive Failed: 2 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 7 test(s)Failed: CompressionTests.Archive.ZipArchiveTest.testCreateWithRelativeNamesFailed: CompressionTests.Archive.ZipArchiveTest.testZipName: Deprecated20 Failed: 0 test(s), Passed: 7 test(s), Skipped: 0 test(s), Total: 7 test(s)Name: FileSystem.Tests.Core Failed: 0 test(s), Passed: 185 test(s), Skipped: 0 test(s), Total: 185 test(s)Name: FileSystem.Tests.Disk Failed: 0 test(s), Passed: 53 test(s), Skipped: 0 test(s), Total: 53 test(s)Name: FileSystem.Tests.Memory Failed: 0 test(s), Passed: 50 test(s), Skipped: 0 test(s), Total: 50 test(s)Name: FreeTypeTests.cache Failed: 0 test(s), Passed: 23 test(s), Skipped: 0 test(s), Total: 23 test(s)Name: FuelMetalevelTests Failed: 0 test(s), Passed: 155 test(s), Skipped: 0 test(s), Total: 155 test(s)Name: FuelTests Failed: 0 test(s), Passed: 246 test(s), Skipped: 0 test(s), Total: 246 test(s)Name: FuelTests.Collections Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s)Name: FuelTests.Streams Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)Name: Gofer.Tests Failed: 7 test(s), Passed: 35 test(s), Skipped: 0 test(s), Total: 42 test(s)Failed: Gofer.Tests.GoferOperationTest.testLocalChangesFailed: Gofer.Tests.GoferOperationTest.testMergeFailed: Gofer.Tests.GoferOperationTest.testReinitializeFailed: Gofer.Tests.GoferOperationTest.testRemoteChangesFailed: Gofer.Tests.GoferOperationTest.testRevertFailed: Gofer.Tests.GoferOperationTest.testUnloadFailed: Gofer.Tests.GoferOperationTest.testUpdateName: Graphics.Tests.Files Failed: 0 test(s), Passed: 47 test(s), Skipped: 0 test(s), Total: 47 test(s)Name: Graphics.Tests.Primitives Failed: 0 test(s), Passed: 57 test(s), Skipped: 0 test(s), Total: 57 test(s)Name: HelpSystem.Tests.Builders Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s)Name: HelpSystem.Tests.Core.Model Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s)Name: HelpSystem.Tests.Core.UI Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: HelpSystem.Tests.Core.Utilities Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: KernelTests.Chronology Failed: 0 test(s), Passed: 583 test(s), Skipped: 0 test(s), Total: 583 test(s)Name: KernelTests.Classes Failed: 0 test(s), Passed: 68 test(s), Skipped: 0 test(s), Total: 68 test(s)Name: KernelTests.Exception Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)Name: KernelTests.Methods Failed: 0 test(s), Passed: 180 test(s), Skipped: 0 test(s), Total: 180 test(s)Name: KernelTests.Numbers Failed: 0 test(s), Passed: 276 test(s), Skipped: 0 test(s), Total: 276 test(s)Name: KernelTests.Objects Failed: 0 test(s), Passed: 87 test(s), Skipped: 0 test(s), Total: 87 test(s)Name: KernelTests.Pragmas Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)Name: KernelTests.Processes Failed: 0 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 37 test(s)Name: Keymapping.Tests Failed: 0 test(s), Passed: 38 test(s), Skipped: 0 test(s), Total: 38 test(s)Name: MorphicTests.Basic Failed
[Pharo-project] terminate process immediately
http://stackoverflow.com/questions/12930980/terminate-process-immediately
Re: [Pharo-project] Fuel for Squeak stupid questions
On Tue, Oct 16, 2012 at 2:06 PM, Max Leske wrote: > Edgar, > > There is indeed a bug in Fuel, namely Fuel ignores the local time zone. > The reason why I didn't detect that in my image is that Squeak seems to > have some problems of its own in determining the correct time zone… :) > > Mm is this Squeak only or also in Pharo? > I'll write a fix for that. > > Cheers, > Max > > On 16.10.2012, at 12:55, Edgar J. De Cleene > wrote: > > > > > > > > > On 10/16/12 3:52 AM, "Max Leske" wrote: > > > >> I checked against build 11925 (found here: http://ftp.squeak.org/trunk/). > Did > >> you get your image from somewhere else? > >> I can take a look at the image if you like. You'd just have to put it > >> somewhere for me to download (together with the changes of course). > >> > >> Max > >> > > > > Changes was grouped into 'SL' ChangeSet > > > > These days try to learn from Fuel and from Phobos to get into this image, > > currently I use modify HV2 as light web framework > > > > The .image is saved as NO Cog format and runs with both Elliot and > Esteban > > or with old John, in my case I have old hardware (that's why I saved and > > updated with Squeak 4.2.5beta1U ) > > > > I send direct to you as this is very preliminar for going public > > > > Very thanks > > > > Edgar > > > > > > > -- Mariano http://marianopeck.wordpress.com
[Pharo-project] RPackage by-hand code
Hi, I have a problem in Pharo 2.0, among the recent updates, RPackage lost most of the code in one of my packages. Would someone know how to write a small script to force a reload in RPackage of a Smalltalk Category ? The code is still there, in the right system category, but neither Nautilus nor Monticello sees it, and I'm afraid of doing anything like saving the package which would erase most of what is in it. My Pharo version is 20346. Thanks in advance, Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
[Pharo-project] what is your pharo story?
Hey there, I'm collecting some stories from smalltalkers to tell people how exciting this is. Have something to share? What's your story with it? What got you excited? why it worked for you? sebastian o/ pd: I'm going to mention mainly about pharo and amber
Re: [Pharo-project] Fuel for Squeak stupid questions
The Fuel bug also exists in Pharo (Fuel simply doesn't write out the local offset information) but the timezones seem to be fine. On 17.10.2012, at 12:32, Mariano Martinez Peck wrote: > > > On Tue, Oct 16, 2012 at 2:06 PM, Max Leske wrote: > Edgar, > > There is indeed a bug in Fuel, namely Fuel ignores the local time zone. > The reason why I didn't detect that in my image is that Squeak seems to have > some problems of its own in determining the correct time zone… :) > > > Mm is this Squeak only or also in Pharo? > > > I'll write a fix for that. > > Cheers, > Max > > On 16.10.2012, at 12:55, Edgar J. De Cleene wrote: > > > > > > > > > On 10/16/12 3:52 AM, "Max Leske" wrote: > > > >> I checked against build 11925 (found here: http://ftp.squeak.org/trunk/). > >> Did > >> you get your image from somewhere else? > >> I can take a look at the image if you like. You'd just have to put it > >> somewhere for me to download (together with the changes of course). > >> > >> Max > >> > > > > Changes was grouped into 'SL' ChangeSet > > > > These days try to learn from Fuel and from Phobos to get into this image, > > currently I use modify HV2 as light web framework > > > > The .image is saved as NO Cog format and runs with both Elliot and Esteban > > or with old John, in my case I have old hardware (that's why I saved and > > updated with Squeak 4.2.5beta1U ) > > > > I send direct to you as this is very preliminar for going public > > > > Very thanks > > > > Edgar > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com >
Re: [Pharo-project] RPackage by-hand code
You can try RPackageOrganizer initialize but that does not always work :/ On 2012-10-17, at 13:41, Goubier Thierry wrote: > Hi, > > I have a problem in Pharo 2.0, among the recent updates, RPackage lost most > of the code in one of my packages. Would someone know how to write a small > script to force a reload in RPackage of a Smalltalk Category ? > > The code is still there, in the right system category, but neither Nautilus > nor Monticello sees it, and I'm afraid of doing anything like saving the > package which would erase most of what is in it. > > My Pharo version is 20346. > > Thanks in advance, > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des Systèmes Temps Réel Embarqués > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >
Re: [Pharo-project] RPackage by-hand code
Hi, RPackageOrganizer initialize. should do it. Esteban On Oct 17, 2012, at 1:41 PM, Goubier Thierry wrote: > Hi, > > I have a problem in Pharo 2.0, among the recent updates, RPackage lost most > of the code in one of my packages. Would someone know how to write a small > script to force a reload in RPackage of a Smalltalk Category ? > > The code is still there, in the right system category, but neither Nautilus > nor Monticello sees it, and I'm afraid of doing anything like saving the > package which would erase most of what is in it. > > My Pharo version is 20346. > > Thanks in advance, > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des Systèmes Temps Réel Embarqués > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >
Re: [Pharo-project] RPackage by-hand code
Le 17/10/2012 13:49, Esteban Lorenzano a écrit : Hi, RPackageOrganizer initialize. should do it. Esteban It doesn't. Trust me, I tried. Multiple times :( Thierry On Oct 17, 2012, at 1:41 PM, Goubier Thierry wrote: Hi, I have a problem in Pharo 2.0, among the recent updates, RPackage lost most of the code in one of my packages. Would someone know how to write a small script to force a reload in RPackage of a Smalltalk Category ? The code is still there, in the right system category, but neither Nautilus nor Monticello sees it, and I'm afraid of doing anything like saving the package which would erase most of what is in it. My Pharo version is 20346. Thanks in advance, Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Re: [Pharo-project] RPackage by-hand code
is there an MCWorkingCopy of your code package? MCWorkingCopy allManagers. and a package info? PackageIngo allPackages. Esteban On Oct 17, 2012, at 1:56 PM, Goubier Thierry wrote: > Le 17/10/2012 13:49, Esteban Lorenzano a écrit : >> Hi, >> >> RPackageOrganizer initialize. >> >> should do it. >> >> Esteban > > It doesn't. > > Trust me, I tried. Multiple times :( > > Thierry > >> On Oct 17, 2012, at 1:41 PM, Goubier Thierry wrote: >> >>> Hi, >>> >>> I have a problem in Pharo 2.0, among the recent updates, RPackage lost most >>> of the code in one of my packages. Would someone know how to write a small >>> script to force a reload in RPackage of a Smalltalk Category ? >>> >>> The code is still there, in the right system category, but neither Nautilus >>> nor Monticello sees it, and I'm afraid of doing anything like saving the >>> package which would erase most of what is in it. >>> >>> My Pharo version is 20346. >>> >>> Thanks in advance, >>> >>> Thierry >>> -- >>> Thierry Goubier >>> CEA list >>> Laboratoire des Fondations des Systèmes Temps Réel Embarqués >>> 91191 Gif sur Yvette Cedex >>> France >>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>> >> >> >> >> > > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des Systèmes Temps Réel Embarqués > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >
Re: [Pharo-project] RPackage by-hand code
I also would like to collect how your methods were missing... it is reproducible? Esteban On Oct 17, 2012, at 1:58 PM, Esteban Lorenzano wrote: > is there an MCWorkingCopy of your code package? > > MCWorkingCopy allManagers. > > and a package info? > > PackageIngo allPackages. > > Esteban > > On Oct 17, 2012, at 1:56 PM, Goubier Thierry wrote: > >> Le 17/10/2012 13:49, Esteban Lorenzano a écrit : >>> Hi, >>> >>> RPackageOrganizer initialize. >>> >>> should do it. >>> >>> Esteban >> >> It doesn't. >> >> Trust me, I tried. Multiple times :( >> >> Thierry >> >>> On Oct 17, 2012, at 1:41 PM, Goubier Thierry wrote: >>> Hi, I have a problem in Pharo 2.0, among the recent updates, RPackage lost most of the code in one of my packages. Would someone know how to write a small script to force a reload in RPackage of a Smalltalk Category ? The code is still there, in the right system category, but neither Nautilus nor Monticello sees it, and I'm afraid of doing anything like saving the package which would erase most of what is in it. My Pharo version is 20346. Thanks in advance, Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>> >>> >>> >>> >> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des Systèmes Temps Réel Embarqués >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> >
Re: [Pharo-project] what is your pharo story?
On Oct 17, 2012, at 2:05 PM, Mariano Martinez Peck wrote: > > > Hi. One of things that people outside of the community was most impressed > from the stuff I show/write is how we can serialize stacks/debuggers and move > them to another image. This is a combination of a lot of stuff, but > basically, a great dynamic language, with decent reflection capabilities, > stack reified from the language side, and cool libraries that take that into > account. > Some links about this: > > http://marianopeck.wordpress.com/2012/01/19/moving-contexts-and-debuggers-between-images-with-fuel/ > http://marianopeck.wordpress.com/2012/07/25/reviving-ci-test-failures-in-local-machine/ > > What I am most happy about is that we started (slowly) a feedback loop: Improving something gets easier because of an improvement we did. For me, this was one of the reasons to do Pharo... to not always destroy every improvement by saying: "No, this is not good enough". It is sad that especially intelligent people are very good at seeing the faults, but not realizing that building a feedback loop is more important than being perfect with the first iteration... Marcus -- Marcus Denker -- http://marcusdenker.de
Re: [Pharo-project] what is your pharo story?
On Wed, Oct 17, 2012 at 1:43 PM, Sebastian Sastre wrote: > Have something to share? > > What's your story with it? > > What got you excited? why it worked for you? FWIW: http://www.pharo-project.org/about/success-stories -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
Re: [Pharo-project] what is your pharo story?
I am a blender developer , using python to make blender addons. My latest complete one is Gyes and Random Material and Texture Generator. http://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/System/Gyes Since I was a child I was dreaming of making a system that would use GUIs like the one that I saw in many spaceship movies, fluid futuristic GUIs that could issue way more complex commands than our modern window type GUIs. It was a childs dream, filed as too ambitious and stored there with the rest of too far fetched child dreams. And it was early this year that I was introduced to Smalltalk. I really like python but it was obvious to me that I needed something a lot more. It was that itch I had to scratch. I was very impressed with morphic and squeak and the whole enviroment and of course pharo. I was looking for a live coding enviroment with an ephasis on visual side and I think smalltalk fit like a glove for me. Morphic fit exactly my lego brick logic, I am a very synthetic person I like to keep things minimal and simple and synthesize complex structures out of them. Its a workflow I follow with my entire life not just coding. So I started a thread in Blenderartists forum ( http://blenderartists.org/forum/showthread.php?250375-A-Visual-Programming-Language-and-a-new-GUI-for-Blender-your-thoughts ) about how people saw the possibility of implementing a visual programming enviroment for blender with a very flexible GUI. I thought it would be one of those threads that none really cared and people would say "we have python why bother with a visual coding enviroment at all, python is very easy to learn" or "why should I care about coding at all I am merely a user". And of course I had such reactions but to my surprise the thread just went viral and people seems very excited with the ideas of Ephestos. So we sat down with another developer using Morphic code from a smalltalk coder , that he made for python and pygame and we tried to port to Blender libraries instead. Code wise it went much better in our side , suprisingly enough both he and found Morphic very easy to understand. But we came across some severe bugs and limitations at blender side that make it evident that if I wanted to keep this in python I had to dirty my hands with some C and diving inside Blender source. It also became more and more evident that squeak and pharo already implemented many of the ideas I had for Ephestos, and there was no way I could port all the features both offered to python just me and another coder in our free time. So I did the logical thing. Droped the idea of keeping the project pure python and now I have slowly started to porting it to Squeak/Pharo and I am using sockets to communicate with blender. The goal is of course Visual Coding together with several other ideas I have for RAD. Its not something bound by goals but more an exploration of potential. If the project progress well, I think it will be a win for both blender and squeak/pharo. At one side Blender developer will be exposed to the true power and flexibility of smalltalk, at the other hand the smalltalk community will have access to such a powerful amazing 3d application as blender. So I think it will be a double win. My preference towards pharo has to do with Nativeboost , I think that it may play an important role in the future and of course there are libraries like Athens that I would love to explore but ideally I would like to make Ephestos compatible with both squeak and pharo. In essense squeak and pharo have been an inspiration for Ephestos and the true driving force for making it reality and I can see myself making Ephestos a life project because Its just pure fun for me working on something like that. From: Sebastian Sastre To: "pharo-project@lists.gforge.inria.fr" Sent: Wednesday, 17 October 2012, 14:43 Subject: [Pharo-project] what is your pharo story? Hey there, I'm collecting some stories from smalltalkers to tell people how exciting this is. Have something to share? What's your story with it? What got you excited? why it worked for you? sebastian o/ pd: I'm going to mention mainly about pharo and amber
Re: [Pharo-project] RPackage by-hand code
Le 17/10/2012 13:58, Esteban Lorenzano a écrit : is there an MCWorkingCopy of your code package? MCWorkingCopy allManagers. Yes. and a package info? PackageIngo allPackages. No. Thierry Esteban On Oct 17, 2012, at 1:56 PM, Goubier Thierry wrote: Le 17/10/2012 13:49, Esteban Lorenzano a écrit : Hi, RPackageOrganizer initialize. should do it. Esteban It doesn't. Trust me, I tried. Multiple times :( Thierry On Oct 17, 2012, at 1:41 PM, Goubier Thierry wrote: Hi, I have a problem in Pharo 2.0, among the recent updates, RPackage lost most of the code in one of my packages. Would someone know how to write a small script to force a reload in RPackage of a Smalltalk Category ? The code is still there, in the right system category, but neither Nautilus nor Monticello sees it, and I'm afraid of doing anything like saving the package which would erase most of what is in it. My Pharo version is 20346. Thanks in advance, Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Re: [Pharo-project] RPackage by-hand code
Le 17/10/2012 14:16, Esteban Lorenzano a écrit : I also would like to collect how your methods were missing... it is reproducible? I don't know. It happened apparently during a RPackageOrganizer initialize in the past 8 or 10 updates, but I don't know if I can reproduce it. It may have started when I added a companion MC package (a package with, as name, an extension to the main package) to the main one and the code was appearing in both the main package and the companion. Thierry Esteban On Oct 17, 2012, at 1:58 PM, Esteban Lorenzano wrote: is there an MCWorkingCopy of your code package? MCWorkingCopy allManagers. and a package info? PackageIngo allPackages. Esteban On Oct 17, 2012, at 1:56 PM, Goubier Thierry wrote: Le 17/10/2012 13:49, Esteban Lorenzano a écrit : Hi, RPackageOrganizer initialize. should do it. Esteban It doesn't. Trust me, I tried. Multiple times :( Thierry On Oct 17, 2012, at 1:41 PM, Goubier Thierry wrote: Hi, I have a problem in Pharo 2.0, among the recent updates, RPackage lost most of the code in one of my packages. Would someone know how to write a small script to force a reload in RPackage of a Smalltalk Category ? The code is still there, in the right system category, but neither Nautilus nor Monticello sees it, and I'm afraid of doing anything like saving the package which would erase most of what is in it. My Pharo version is 20346. Thanks in advance, Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Re: [Pharo-project] what is your pharo story?
great point! sebastian o/ On 17/10/2012, at 09:05, Mariano Martinez Peck wrote: > > > On Wed, Oct 17, 2012 at 1:43 PM, Sebastian Sastre > wrote: > Hey there, > > I'm collecting some stories from smalltalkers to tell people how exciting > this is. > > Have something to share? > > What's your story with it? > > What got you excited? why it worked for you? > > > Hi. One of things that people outside of the community was most impressed > from the stuff I show/write is how we can serialize stacks/debuggers and move > them to another image. This is a combination of a lot of stuff, but > basically, a great dynamic language, with decent reflection capabilities, > stack reified from the language side, and cool libraries that take that into > account. > Some links about this: > > http://marianopeck.wordpress.com/2012/01/19/moving-contexts-and-debuggers-between-images-with-fuel/ > http://marianopeck.wordpress.com/2012/07/25/reviving-ci-test-failures-in-local-machine/ > > Good luck! > > > > sebastian > > o/ > > pd: I'm going to mention mainly about pharo and amber > > > > -- > Mariano > http://marianopeck.wordpress.com >
Re: [Pharo-project] what is your pharo story?
fantastic feedback loop absolutely key sebastian o/ On 17/10/2012, at 09:16, Marcus Denker wrote: > > On Oct 17, 2012, at 2:05 PM, Mariano Martinez Peck > wrote: >> >> >> Hi. One of things that people outside of the community was most impressed >> from the stuff I show/write is how we can serialize stacks/debuggers and >> move them to another image. This is a combination of a lot of stuff, but >> basically, a great dynamic language, with decent reflection capabilities, >> stack reified from the language side, and cool libraries that take that into >> account. >> Some links about this: >> >> http://marianopeck.wordpress.com/2012/01/19/moving-contexts-and-debuggers-between-images-with-fuel/ >> http://marianopeck.wordpress.com/2012/07/25/reviving-ci-test-failures-in-local-machine/ >> >> > > What I am most happy about is that we started (slowly) a feedback loop: > Improving something gets easier because of an improvement we did. > > For me, this was one of the reasons to do Pharo... to not always destroy > every improvement by saying: "No, this is not good enough". > > It is sad that especially intelligent people are very good at seeing the > faults, but not realizing that building a feedback loop is more important > than being perfect with the first iteration... > >Marcus > > -- > Marcus Denker -- http://marcusdenker.de > >
Re: [Pharo-project] [PROVENANCE INTERNET] Re: RPackage by-hand code
Le 17/10/2012 15:04, Goubier Thierry a écrit : Le 17/10/2012 14:16, Esteban Lorenzano a écrit : I also would like to collect how your methods were missing... it is reproducible? I don't know. It happened apparently during a RPackageOrganizer initialize in the past 8 or 10 updates, but I don't know if I can reproduce it. Ok. In fact, I can reproduce it in a 20341 image (and probably in a later one as well). It's my Jejak package (code tracer) combined with the Jejak-Alt-Browser-Integration package. It loads fine, appear in the MC browser. Browse in MC Browser shows the four system categories (Jejak-Alt-Browser-Integration shouldn't be there, however, since there is a package of that name loaded). Now, if I do RPackageOrganizer initialize And I browse Jejak from the MC Browser, I get Jejak empty (no code, no extensions) Jejak-Alt-Browser-Integration empty (no code, no extension) (Nautilus contains nothing for Jejak, and nothing in _Unpackaged. Browser shows all the code). Thierry Esteban On Oct 17, 2012, at 1:58 PM, Esteban Lorenzano wrote: is there an MCWorkingCopy of your code package? MCWorkingCopy allManagers. and a package info? PackageIngo allPackages. Esteban On Oct 17, 2012, at 1:56 PM, Goubier Thierry wrote: Le 17/10/2012 13:49, Esteban Lorenzano a écrit : Hi, RPackageOrganizer initialize. should do it. Esteban It doesn't. Trust me, I tried. Multiple times :( Thierry On Oct 17, 2012, at 1:41 PM, Goubier Thierry wrote: Hi, I have a problem in Pharo 2.0, among the recent updates, RPackage lost most of the code in one of my packages. Would someone know how to write a small script to force a reload in RPackage of a Smalltalk Category ? The code is still there, in the right system category, but neither Nautilus nor Monticello sees it, and I'm afraid of doing anything like saving the package which would erase most of what is in it. My Pharo version is 20346. Thanks in advance, Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
[Pharo-project] [update 2.0] #20347
20347 - Issue 6829: New Spec version http://code.google.com/p/pharo/issues/detail?id=6829 Diff information: http://ss3.gemstone.com/ss/Pharo20/Spec-Widgets-EstebanLorenzano.69.diff http://ss3.gemstone.com/ss/Pharo20/Spec-Tools-EstebanLorenzano.60.diff http://ss3.gemstone.com/ss/Pharo20/Spec-Core-EstebanLorenzano.60.diff http://ss3.gemstone.com/ss/Pharo20/Spec-Bindings-EstebanLorenzano.16.diff
Re: [Pharo-project] what is your pharo story?
awesome Dimitri visual processing is the most powerful part in our brain (dedicated to senses) so whatever you do, if isn't visual is wasting opportunities thanks for sharing, great point and intriguing project child's dreams are the best sebastian o/ On 17/10/2012, at 09:43, dimitris chloupis wrote: > > I am a blender developer , using python to make blender addons. My latest > complete one is Gyes and Random Material and Texture Generator. > http://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/System/Gyes > > Since I was a child I was dreaming of making a system that would use GUIs > like the one that I saw in many spaceship movies, fluid futuristic GUIs that > could issue way more complex commands than our modern window type GUIs. It > was a childs dream, filed as too ambitious and stored there with the rest of > too far fetched child dreams. And it was early this year that I was > introduced to Smalltalk. I really like python but it was obvious to me that I > needed something a lot more. It was that itch I had to scratch. I was very > impressed with morphic and squeak and the whole enviroment and of course > pharo. I was looking for a live coding enviroment with an ephasis on visual > side and I think smalltalk fit like a glove for me. Morphic fit exactly my > lego brick logic, I am a very synthetic person I like to keep things minimal > and simple and synthesize complex structures out of them. Its a workflow I > follow with my entire life not just coding. > > So I started a thread in Blenderartists forum ( > http://blenderartists.org/forum/showthread.php?250375-A-Visual-Programming-Language-and-a-new-GUI-for-Blender-your-thoughts > ) about how people saw the possibility of implementing a visual programming > enviroment for blender with a very flexible GUI. I thought it would be one of > those threads that none really cared and people would say "we have python why > bother with a visual coding enviroment at all, python is very easy to learn" > or "why should I care about coding at all I am merely a user". And of course > I had such reactions but to my surprise the thread just went viral and people > seems very excited with the ideas of Ephestos. > > So we sat down with another developer using Morphic code from a smalltalk > coder , that he made for python and pygame and we tried to port to Blender > libraries instead. Code wise it went much better in our side , suprisingly > enough both he and found Morphic very easy to understand. But we came across > some severe bugs and limitations at blender side that make it evident that if > I wanted to keep this in python I had to dirty my hands with some C and > diving inside Blender source. > > It also became more and more evident that squeak and pharo already > implemented many of the ideas I had for Ephestos, and there was no way I > could port all the features both offered to python just me and another coder > in our free time. So I did the logical thing. Droped the idea of keeping the > project pure python and now I have slowly started to porting it to > Squeak/Pharo and I am using sockets to communicate with blender. > > The goal is of course Visual Coding together with several other ideas I have > for RAD. Its not something bound by goals but more an exploration of > potential. If the project progress well, I think it will be a win for both > blender and squeak/pharo. > > At one side Blender developer will be exposed to the true power and > flexibility of smalltalk, at the other hand the smalltalk community will have > access to such a powerful amazing 3d application as blender. So I think it > will be a double win. > > My preference towards pharo has to do with Nativeboost , I think that it may > play an important role in the future and of course there are libraries like > Athens that I would love to explore but ideally I would like to make Ephestos > compatible with both squeak and pharo. > > In essense squeak and pharo have been an inspiration for Ephestos and the > true driving force for making it reality and I can see myself making Ephestos > a life project because Its just pure fun for me working on something like > that. > > > > > From: Sebastian Sastre > To: "pharo-project@lists.gforge.inria.fr" > > Sent: Wednesday, 17 October 2012, 14:43 > Subject: [Pharo-project] what is your pharo story? > > Hey there, > > I'm collecting some stories from smalltalkers to tell people how exciting > this is. > > Have something to share? > > What's your story with it? > > What got you excited? why it worked for you? > > sebastian > > o/ > > pd: I'm going to mention mainly about pharo and amber > >
[Pharo-project] pharo-2.0-tests » mac - Build # 418 - Still Failing!
BUILD FAILUREBuild URLhttps://ci.lille.inria.fr/pharo/job/pharo-2.0-tests/./label_exp=mac/418/Project:label_exp=macDate of build:Wed, 17 Oct 2012 15:42:20 +0200Build duration:6 min 13 secCHANGESNo ChangesCONSOLE OUTPUT[...truncated 154 lines...]2012-10-17 15:45:34.501 CogVM[54786:903] invalid pixel format2012-10-17 15:45:34.503 CogVM[54786:903] invalid context2012-10-17 15:45:34.508 CogVM[54786:903] invalid pixel format2012-10-17 15:45:34.512 CogVM[54786:903] invalid context2012-10-17 15:45:40.414 CogVM[54786:903] invalid pixel format2012-10-17 15:45:40.503 CogVM[54786:903] invalid context2012-10-17 15:45:40.508 CogVM[54786:903] invalid pixel format2012-10-17 15:45:40.510 CogVM[54786:903] invalid context2012-10-17 15:45:48.215 CogVM[54786:903] invalid pixel format2012-10-17 15:45:48.253 CogVM[54786:903] invalid context2012-10-17 15:45:48.257 CogVM[54786:903] invalid pixel format2012-10-17 15:45:48.261 CogVM[54786:903] invalid context2012-10-17 15:45:48.265 CogVM[54786:903] invalid pixel format2012-10-17 15:45:48.268 CogVM[54786:903] invalid context2012-10-17 15:45:48.272 CogVM[54786:903] invalid pixel format2012-10-17 15:45:48.275 CogVM[54786:903] invalid context2012-10-17 15:45:48.279 CogVM[54786:903] invalid pixel format2012-10-17 15:45:48.283 CogVM[54786:903] invalid context2012-10-17 15:45:48.286 CogVM[54786:903] invalid pixel format2012-10-17 15:45:48.290 CogVM[54786:903] invalid context2012-10-17 15:45:48.577 CogVM[54786:903] invalid pixel format2012-10-17 15:45:48.580 CogVM[54786:903] invalid context2012-10-17 15:45:48.584 CogVM[54786:903] invalid pixel format2012-10-17 15:45:48.588 CogVM[54786:903] invalid context2012-10-17 15:45:48.592 CogVM[54786:903] invalid pixel format2012-10-17 15:45:48.595 CogVM[54786:903] invalid context2012-10-17 15:45:48.598 CogVM[54786:903] invalid pixel format2012-10-17 15:45:48.603 CogVM[54786:903] invalid context2012-10-17 15:45:48.606 CogVM[54786:903] invalid pixel format2012-10-17 15:45:48.610 CogVM[54786:903] invalid context2012-10-17 15:45:48.613 CogVM[54786:903] invalid pixel format2012-10-17 15:45:48.617 CogVM[54786:903] invalid context./build.sh: line 155: 54786 Bus error "$PHARO_VM" $PHARO_PARAM "$OUTPUT_IMAGE" "$OUTPUT_SCRIPT" -headlessBuild step 'Execute shell' marked build as failureArchiving artifactsRecording test resultsERROR: Failed to archive test reportshudson.util.IOException2: remote file operation failed: /Users/hudson/jenkins/workspace/pharo-2.0-tests/label_exp/mac at hudson.remoting.Channel@44c75ba4:pharo-build-mac.lille.inria.fr at hudson.FilePath.act(FilePath.java:847) at hudson.FilePath.act(FilePath.java:824) at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:122) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:134) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:807) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:782) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:729) at hudson.model.Run.execute(Run.java:1541) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236)Caused by: hudson.util.IOException2: Failed to read /Users/hudson/jenkins/workspace/pharo-2.0-tests/label_exp/mac/Pharo-2.0-AfterRunningTests/Tests-Monticello-Test.xml at hudson.tasks.junit.TestResult.parse(TestResult.java:244) at hudson.tasks.junit.TestResult.parse(TestResult.java:163) at hudson.tasks.junit.TestResult.parse(TestResult.java:140) at hudson.tasks.junit.TestResult.(TestResult.java:116) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:117) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2308) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680)Caused by: org.dom4j.DocumentException: Error on line 339 of document file:///Users/hudson/jenkins/workspace/pharo-2.0-tests/label_exp/mac/Pharo-2.0-AfterRunningTests/Tests-Monticello-Test.xml : XML document structures must start and end within the same entity. Nested exception: XML document structures mus
Re: [Pharo-project] RPackage by-hand code
Le 17/10/2012 14:16, Esteban Lorenzano a écrit : I also would like to collect how your methods were missing... it is reproducible? It's even worse than I thought. I'm now loosing the code in three packages when I do RPackageOrganize initialize They just don't appear at all in Nautilus; as if they didn't exist. Thierry Esteban On Oct 17, 2012, at 1:58 PM, Esteban Lorenzano wrote: is there an MCWorkingCopy of your code package? MCWorkingCopy allManagers. and a package info? PackageIngo allPackages. Esteban On Oct 17, 2012, at 1:56 PM, Goubier Thierry wrote: Le 17/10/2012 13:49, Esteban Lorenzano a écrit : Hi, RPackageOrganizer initialize. should do it. Esteban It doesn't. Trust me, I tried. Multiple times :( Thierry On Oct 17, 2012, at 1:41 PM, Goubier Thierry wrote: Hi, I have a problem in Pharo 2.0, among the recent updates, RPackage lost most of the code in one of my packages. Would someone know how to write a small script to force a reload in RPackage of a Smalltalk Category ? The code is still there, in the right system category, but neither Nautilus nor Monticello sees it, and I'm afraid of doing anything like saving the package which would erase most of what is in it. My Pharo version is 20346. Thanks in advance, Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
[Pharo-project] pharo-2.0-tests » win - Build # 418 - Still Failing!
BUILD FAILUREBuild URLhttps://ci.lille.inria.fr/pharo/job/pharo-2.0-tests/./label_exp=win/418/Project:label_exp=winDate of build:Wed, 17 Oct 2012 15:42:20 +0200Build duration:13 minCHANGESNo ChangesJUnit TestsName: AST.Tests.Core Failed: 0 test(s), Passed: 79 test(s), Skipped: 0 test(s), Total: 79 test(s)Name: AST.Tests.Semantic Failed: 0 test(s), Passed: 25 test(s), Skipped: 0 test(s), Total: 25 test(s)Name: Announcements.Tests.Core Failed: 0 test(s), Passed: 29 test(s), Skipped: 0 test(s), Total: 29 test(s)Name: BalloonTests.Collections Failed: 0 test(s), Passed: 34 test(s), Skipped: 0 test(s), Total: 34 test(s)Name: CollectionsTests.Arrayed Failed: 0 test(s), Passed: 553 test(s), Skipped: 0 test(s), Total: 553 test(s)Name: CollectionsTests.Atomic Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s)Name: CollectionsTests.Sequenceable Failed: 0 test(s), Passed: 912 test(s), Skipped: 0 test(s), Total: 912 test(s)Name: CollectionsTests.SplitJoin Failed: 0 test(s), Passed: 27 test(s), Skipped: 0 test(s), Total: 27 test(s)Name: CollectionsTests.Stack Failed: 0 test(s), Passed: 16 test(s), Skipped: 0 test(s), Total: 16 test(s)Name: CollectionsTests.Streams Failed: 0 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 37 test(s)Name: CollectionsTests.Strings Failed: 0 test(s), Passed: 606 test(s), Skipped: 0 test(s), Total: 606 test(s)Name: CollectionsTests.Support Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s)Name: CollectionsTests.Unordered Failed: 0 test(s), Passed: 1954 test(s), Skipped: 0 test(s), Total: 1954 test(s)Name: CollectionsTests.Weak Failed: 0 test(s), Passed: 739 test(s), Skipped: 0 test(s), Total: 739 test(s)Name: CompilerTests Failed: 0 test(s), Passed: 180 test(s), Skipped: 0 test(s), Total: 180 test(s)Name: CompressionTests.Archive Failed: 2 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 7 test(s)Failed: CompressionTests.Archive.ZipArchiveTest.testCreateWithRelativeNamesFailed: CompressionTests.Archive.ZipArchiveTest.testZipName: Deprecated20 Failed: 0 test(s), Passed: 7 test(s), Skipped: 0 test(s), Total: 7 test(s)Name: FileSystem.Tests.Core Failed: 0 test(s), Passed: 185 test(s), Skipped: 0 test(s), Total: 185 test(s)Name: FileSystem.Tests.Disk Failed: 0 test(s), Passed: 53 test(s), Skipped: 0 test(s), Total: 53 test(s)Name: FileSystem.Tests.Memory Failed: 0 test(s), Passed: 50 test(s), Skipped: 0 test(s), Total: 50 test(s)Name: FreeTypeTests.cache Failed: 0 test(s), Passed: 23 test(s), Skipped: 0 test(s), Total: 23 test(s)Name: FuelMetalevelTests Failed: 0 test(s), Passed: 155 test(s), Skipped: 0 test(s), Total: 155 test(s)Name: FuelTests Failed: 0 test(s), Passed: 246 test(s), Skipped: 0 test(s), Total: 246 test(s)Name: FuelTests.Collections Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s)Name: FuelTests.Streams Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)Name: Gofer.Tests Failed: 7 test(s), Passed: 35 test(s), Skipped: 0 test(s), Total: 42 test(s)Failed: Gofer.Tests.GoferOperationTest.testLocalChangesFailed: Gofer.Tests.GoferOperationTest.testMergeFailed: Gofer.Tests.GoferOperationTest.testReinitializeFailed: Gofer.Tests.GoferOperationTest.testRemoteChangesFailed: Gofer.Tests.GoferOperationTest.testRevertFailed: Gofer.Tests.GoferOperationTest.testUnloadFailed: Gofer.Tests.GoferOperationTest.testUpdateName: Graphics.Tests.Files Failed: 0 test(s), Passed: 47 test(s), Skipped: 0 test(s), Total: 47 test(s)Name: Graphics.Tests.Primitives Failed: 0 test(s), Passed: 57 test(s), Skipped: 0 test(s), Total: 57 test(s)Name: HelpSystem.Tests.Builders Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s)Name: HelpSystem.Tests.Core.Model Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s)Name: HelpSystem.Tests.Core.UI Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: HelpSystem.Tests.Core.Utilities Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: KernelTests.Chronology Failed: 0 test(s), Passed: 583 test(s), Skipped: 0 test(s), Total: 583 test(s)Name: KernelTests.Classes Failed: 0 test(s), Passed: 68 test(s), Skipped: 0 test(s), Total: 68 test(s)Name: KernelTests.Exception Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)Name: KernelTests.Methods Failed: 0 test(s), Passed: 180 test(s), Skipped: 0 test(s), Total: 180 test(s)Name: KernelTests.Numbers Failed: 0 test(s), Passed: 276 test(s), Skipped: 0 test(s), Total: 276 test(s)Name: KernelTests.Objects Failed: 0 test(s), Passed: 87 test(s), Skipped: 0 test(s), Total: 87 test(s)Name: KernelTests.Pragmas Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)Name: KernelTests.Processes Failed: 0 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 37 test(s)Name: Keymapping.Tests Failed: 0 test(s), Passed: 38 test(s), Skipped: 0 test(s), Total: 38 test(s)Name: MorphicTests.Basic Failed
Re: [Pharo-project] RPackage by-hand code
can I have your image to explore? (if there are some "private" code, I can sign whatever confidentiality agreement you want :P) Esteban On Oct 17, 2012, at 3:56 PM, Goubier Thierry wrote: > Le 17/10/2012 14:16, Esteban Lorenzano a écrit : >> I also would like to collect how your methods were missing... it is >> reproducible? > > It's even worse than I thought. I'm now loosing the code in three packages > when I do > > RPackageOrganize initialize > > They just don't appear at all in Nautilus; as if they didn't exist. > > Thierry > >> Esteban >> >> On Oct 17, 2012, at 1:58 PM, Esteban Lorenzano wrote: >> >>> is there an MCWorkingCopy of your code package? >>> >>> MCWorkingCopy allManagers. >>> >>> and a package info? >>> >>> PackageIngo allPackages. >>> >>> Esteban >>> >>> On Oct 17, 2012, at 1:56 PM, Goubier Thierry wrote: >>> Le 17/10/2012 13:49, Esteban Lorenzano a écrit : > Hi, > > RPackageOrganizer initialize. > > should do it. > > Esteban It doesn't. Trust me, I tried. Multiple times :( Thierry > On Oct 17, 2012, at 1:41 PM, Goubier Thierry > wrote: > >> Hi, >> >> I have a problem in Pharo 2.0, among the recent updates, RPackage lost >> most of the code in one of my packages. Would someone know how to write >> a small script to force a reload in RPackage of a Smalltalk Category ? >> >> The code is still there, in the right system category, but neither >> Nautilus nor Monticello sees it, and I'm afraid of doing anything like >> saving the package which would erase most of what is in it. >> >> My Pharo version is 20346. >> >> Thanks in advance, >> >> Thierry >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des Systèmes Temps Réel Embarqués >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > > > > -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>> >> >> >> > > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des Systèmes Temps Réel Embarqués > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >
Re: [Pharo-project] RPackage by-hand code
Le 17/10/2012 16:08, Esteban Lorenzano a écrit : can I have your image to explore? (if there are some "private" code, I can sign whatever confidentiality agreement you want :P) I have two images: a brand new 20346 image with a minimum of packages loaded (the one just before RPackageOrganizer initialize), and the one where I saw the problem in the first place. There is nothing private in there; all the packages are on ss3. The simpler is probably the new one (it's also a bit smaller). Thierry Esteban On Oct 17, 2012, at 3:56 PM, Goubier Thierry wrote: Le 17/10/2012 14:16, Esteban Lorenzano a écrit : I also would like to collect how your methods were missing... it is reproducible? It's even worse than I thought. I'm now loosing the code in three packages when I do RPackageOrganize initialize They just don't appear at all in Nautilus; as if they didn't exist. Thierry Esteban On Oct 17, 2012, at 1:58 PM, Esteban Lorenzano wrote: is there an MCWorkingCopy of your code package? MCWorkingCopy allManagers. and a package info? PackageIngo allPackages. Esteban On Oct 17, 2012, at 1:56 PM, Goubier Thierry wrote: Le 17/10/2012 13:49, Esteban Lorenzano a écrit : Hi, RPackageOrganizer initialize. should do it. Esteban It doesn't. Trust me, I tried. Multiple times :( Thierry On Oct 17, 2012, at 1:41 PM, Goubier Thierry wrote: Hi, I have a problem in Pharo 2.0, among the recent updates, RPackage lost most of the code in one of my packages. Would someone know how to write a small script to force a reload in RPackage of a Smalltalk Category ? The code is still there, in the right system category, but neither Nautilus nor Monticello sees it, and I'm afraid of doing anything like saving the package which would erase most of what is in it. My Pharo version is 20346. Thanks in advance, Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
[Pharo-project] what is your pharo story?
Pick one ... STORY 1: What I like most is that I do not rely on IDE vendors or tools to do measure things like: TestCase allSubclasses size inspect things like: Account allInstances collect: [:each | each value > 10 ] or script my environment: TestCase allSubclasses do: [:each | each removeFromSystem ] Try all this in any of the other "static" environments. And yes - one can shoot itself in the foot: true become: false but I like the freedom. STORY 2: === In any program environment you have to use a debugger. In Smalltalk you can just save the image and continue the next work day on exactly the same point you left. In other environments you usually close the IDE in the evening and start to debug the program the next day again until you are at this point, have the stack and variables in the same state. Lots of wasted time and developer resources in static world... STORY 3: "Rethinking the typing" as you can see http://astares.blogspot.de/2006/08/rethinking-typing.html STORY 4: When I tell people that Smalltalk is not a language - just a dynamic object system with a language built on top of it. A method, a class ... anything is an object. So if you need additions you just implement them without waiting for the next language spec or vendors. Need traits, interfaces, namespaces, ... just add them. Embed other languages: just add them (see Helvetica) http://astares.blogspot.de/2009/11/helvetia-embedding-languages.html) New control structures? Just implement them. An example: Pascal hat a REPEAT UNTIL. C/C++/Java language family and Smalltalk does not have such a construct. The difference: in Smalltalk I can just add a new method #repeatUntil: to BlockClosure if I really need it. STORY X: ...
[Pharo-project] Progress bar in 2.0
Why do we need this icon on the updater progress bar? IMHO it looks awfull and we should remove it. Thx T.
Re: [Pharo-project] Progress bar in 2.0
click on it and you'll know. Now you can interrupt any background process and either kill/debug it. awfull is very subjective, it might not have the right size right now, but it's highly usefull. we still need to properly run the progress in a separate ui thread to enable proper interaction. On 2012-10-17, at 16:27, "Torsten Bergmann" wrote: > Why do we need this icon on the updater > progress bar? IMHO it looks awfull and we > should remove it. > > Thx > T. >
Re: [Pharo-project] Progress bar in 2.0
it is supposed to be closable... but in case the update is not modal. in case the update is modal, I also would like to have it centered (since we cannot do anything else anyway) and btw... we should think on a unique place/area of the window to show notifications... showing at any point that looks cool can quickly guide us into a messy UI (well... a "more messy" UI) Esteban On Oct 17, 2012, at 4:27 PM, "Torsten Bergmann" wrote: > Why do we need this icon on the updater > progress bar? IMHO it looks awfull and we > should remove it. > > Thx > T. >
Re: [Pharo-project] what is your pharo story?
hahaha XD great stuff dynamic vs. static isn't an issue anymore dynamic won hands down already and years ago the thing now is to expand people's vision of what can be done with it and these are good points (to talk to engineers) the audience has other people too so I need more stories from the trenches :) sebastian o/ - Original Message - From: "Torsten Bergmann" To: pharo-project@lists.gforge.inria.fr Sent: Wednesday, October 17, 2012 11:19:26 AM Subject: [Pharo-project] what is your pharo story? Pick one ... STORY 1: What I like most is that I do not rely on IDE vendors or tools to do measure things like: TestCase allSubclasses size inspect things like: Account allInstances collect: [:each | each value > 10 ] or script my environment: TestCase allSubclasses do: [:each | each removeFromSystem ] Try all this in any of the other "static" environments. And yes - one can shoot itself in the foot: true become: false but I like the freedom. STORY 2: === In any program environment you have to use a debugger. In Smalltalk you can just save the image and continue the next work day on exactly the same point you left. In other environments you usually close the IDE in the evening and start to debug the program the next day again until you are at this point, have the stack and variables in the same state. Lots of wasted time and developer resources in static world... STORY 3: "Rethinking the typing" as you can see http://astares.blogspot.de/2006/08/rethinking-typing.html STORY 4: When I tell people that Smalltalk is not a language - just a dynamic object system with a language built on top of it. A method, a class ... anything is an object. So if you need additions you just implement them without waiting for the next language spec or vendors. Need traits, interfaces, namespaces, ... just add them. Embed other languages: just add them (see Helvetica) http://astares.blogspot.de/2009/11/helvetia-embedding-languages.html) New control structures? Just implement them. An example: Pascal hat a REPEAT UNTIL. C/C++/Java language family and Smalltalk does not have such a construct. The difference: in Smalltalk I can just add a new method #repeatUntil: to BlockClosure if I really need it. STORY X: ...
[Pharo-project] [update 2.0] #20348
20348 - Issue 6761: Class side Trait methods don't work in Nautilus http://code.google.com/p/pharo/issues/detail?id=6761 Issue 6831: unload monticello package breaks RPackage http://code.google.com/p/pharo/issues/detail?id=6831 Issue 6539: Integrate Metacello http://code.google.com/p/pharo/issues/detail?id=6539 Diff information: http://ss3.gemstone.com/ss/Pharo20/Ring-Core-Kernel-EstebanLorenzano.80.diff http://ss3.gemstone.com/ss/Pharo20/NautilusCommon-EstebanLorenzano.95.diff http://ss3.gemstone.com/ss/Pharo20/Nautilus-EstebanLorenzano.368.diff http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.724.diff
Re: [Pharo-project] [update 2.0] #20348
On 2012-10-17, at 18:05, Esteban Lorenzano wrote: > 20348 > - > > Issue 6761: Class side Trait methods don't work in Nautilus > http://code.google.com/p/pharo/issues/detail?id=6761 > > Issue 6831: unload monticello package breaks RPackage > http://code.google.com/p/pharo/issues/detail?id=6831 > > Issue 6539: Integrate Metacello > http://code.google.com/p/pharo/issues/detail?id=6539 awesome! :D > Diff information: > http://ss3.gemstone.com/ss/Pharo20/Ring-Core-Kernel-EstebanLorenzano.80.diff > http://ss3.gemstone.com/ss/Pharo20/NautilusCommon-EstebanLorenzano.95.diff > http://ss3.gemstone.com/ss/Pharo20/Nautilus-EstebanLorenzano.368.diff > http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.724.diff > >
Re: [Pharo-project] what is your pharo story?
Hi Sebastian, this is the way I use to present Smalltalk: - open Xerox Smalltalk-80 image (using Hobes) - show this UI, how scrollbars work, how you have to specify window regions, basics of window management etc. Tell them few words about visit of Steve Jobs in Xerox and how it influenced the next development of personal computers. Almost nobody had an opportunity to see it in action so you will gain their attention. - then mention the date in Transcript (31 May 1983). Tell them about an image, VM, snapshoting, that you resume the program after almost 30 years on different computer architecture in the different millenium :-) - tell that Smalltalk-80 is a combination of OS, IDE and programming language and that you will show some examples - show 3+4 - print it - Pen example - do it, open Browser and show them this method - use explain command on "Pen" - open a class browser on it - then show: MessageTally spyOn: [Pen example], profiling is quite interesting property in such old environment - evaluate 1/0, open debugger, change value of dividend to 2 and continue with the evaluation - evaluate 1/0 again, open debugger and then change the method to return 0 instead of rising the error, continue. Then do several next divisions by zero to show that you changed behavior of the whole system. - evaluate Display inspect and show inspector, inspecting of instance variables and their modification. - evaluate String allInstances size - evaluate (String allInstances asSortedCollection: [:a :b | a size <= b size]) last inspect (it doesn't have detect: message) - show an example of become: message, that you changed all references to the object. - show the browser capabilities - senders, implementors, implementations of used messages. - tell them that all you did you did on system without attached source codes, that the code you have seen and changed were all decompiled - finally ask yourself: when Smalltalk-80 was able to do all this things in the year 1983, what it can do now? ;-) Cheers, -- Pavel On Wed, Oct 17, 2012 at 4:58 PM, wrote: > hahaha XD > > great stuff > > dynamic vs. static isn't an issue anymore > > dynamic won hands down already and years ago > > the thing now is to expand people's vision of what can be done with it > > and these are good points (to talk to engineers) > > the audience has other people too so I need more stories from the trenches :) > > sebastian > > o/ > > > - Original Message - > From: "Torsten Bergmann" > To: pharo-project@lists.gforge.inria.fr > Sent: Wednesday, October 17, 2012 11:19:26 AM > Subject: [Pharo-project] what is your pharo story? > > Pick one ... > > > STORY 1: > > > What I like most is that I do not rely on IDE vendors or tools > to do measure things like: > > TestCase allSubclasses size > > inspect things like: > > Account allInstances collect: [:each | each value > 10 ] > > or script my environment: > > TestCase allSubclasses do: [:each | each removeFromSystem ] > > Try all this in any of the other "static" environments. > And yes - one can shoot itself in the foot: > > true become: false > > but I like the freedom. > > > STORY 2: > === > In any program environment you have to use a debugger. In Smalltalk you > can just save the image and continue the next work day on exactly the > same point you left. > > In other environments you usually close the IDE in the evening and > start to debug the program the next day again until you are at > this point, have the stack and variables in the same state. > Lots of wasted time and developer resources in static world... > > STORY 3: > > "Rethinking the typing" as you can see > http://astares.blogspot.de/2006/08/rethinking-typing.html > > STORY 4: > > When I tell people that Smalltalk is not a language - just > a dynamic object system with a language built on top of it. > A method, a class ... anything is an object. > > So if you need additions you just implement them without > waiting for the next language spec or vendors. > > Need traits, interfaces, namespaces, ... just add them. > > Embed other languages: just add them (see Helvetica) > http://astares.blogspot.de/2009/11/helvetia-embedding-languages.html) > > New control structures? Just implement them. An example: > Pascal hat a REPEAT UNTIL. C/C++/Java language family and > Smalltalk does not have such a construct. > > The difference: in Smalltalk I can just add a new > method #repeatUntil: to BlockClosure if I really need it. > > STORY X: > > ... > > > > > > > >
[Pharo-project] pharo-2.0-tests » win - Build # 419 - Still Failing!
BUILD FAILUREBuild URLhttps://ci.lille.inria.fr/pharo/job/pharo-2.0-tests/./label_exp=win/419/Project:label_exp=winDate of build:Wed, 17 Oct 2012 18:36:19 +0200Build duration:12 minCHANGESNo ChangesJUnit TestsName: AST.Tests.Core Failed: 0 test(s), Passed: 79 test(s), Skipped: 0 test(s), Total: 79 test(s)Name: AST.Tests.Semantic Failed: 0 test(s), Passed: 25 test(s), Skipped: 0 test(s), Total: 25 test(s)Name: Announcements.Tests.Core Failed: 0 test(s), Passed: 29 test(s), Skipped: 0 test(s), Total: 29 test(s)Name: BalloonTests.Collections Failed: 0 test(s), Passed: 34 test(s), Skipped: 0 test(s), Total: 34 test(s)Name: CollectionsTests.Arrayed Failed: 0 test(s), Passed: 553 test(s), Skipped: 0 test(s), Total: 553 test(s)Name: CollectionsTests.Atomic Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s)Name: CollectionsTests.Sequenceable Failed: 0 test(s), Passed: 912 test(s), Skipped: 0 test(s), Total: 912 test(s)Name: CollectionsTests.SplitJoin Failed: 0 test(s), Passed: 27 test(s), Skipped: 0 test(s), Total: 27 test(s)Name: CollectionsTests.Stack Failed: 0 test(s), Passed: 16 test(s), Skipped: 0 test(s), Total: 16 test(s)Name: CollectionsTests.Streams Failed: 0 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 37 test(s)Name: CollectionsTests.Strings Failed: 0 test(s), Passed: 606 test(s), Skipped: 0 test(s), Total: 606 test(s)Name: CollectionsTests.Support Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s)Name: CollectionsTests.Unordered Failed: 0 test(s), Passed: 1954 test(s), Skipped: 0 test(s), Total: 1954 test(s)Name: CollectionsTests.Weak Failed: 0 test(s), Passed: 739 test(s), Skipped: 0 test(s), Total: 739 test(s)Name: CompilerTests Failed: 0 test(s), Passed: 180 test(s), Skipped: 0 test(s), Total: 180 test(s)Name: CompressionTests.Archive Failed: 2 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 7 test(s)Failed: CompressionTests.Archive.ZipArchiveTest.testCreateWithRelativeNamesFailed: CompressionTests.Archive.ZipArchiveTest.testZipName: Deprecated20 Failed: 0 test(s), Passed: 7 test(s), Skipped: 0 test(s), Total: 7 test(s)Name: FileSystem.Tests.Core Failed: 0 test(s), Passed: 185 test(s), Skipped: 0 test(s), Total: 185 test(s)Name: FileSystem.Tests.Disk Failed: 0 test(s), Passed: 53 test(s), Skipped: 0 test(s), Total: 53 test(s)Name: FileSystem.Tests.Memory Failed: 0 test(s), Passed: 50 test(s), Skipped: 0 test(s), Total: 50 test(s)Name: FreeTypeTests.cache Failed: 0 test(s), Passed: 23 test(s), Skipped: 0 test(s), Total: 23 test(s)Name: FuelMetalevelTests Failed: 0 test(s), Passed: 155 test(s), Skipped: 0 test(s), Total: 155 test(s)Name: FuelTests Failed: 0 test(s), Passed: 246 test(s), Skipped: 0 test(s), Total: 246 test(s)Name: FuelTests.Collections Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s)Name: FuelTests.Streams Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)Name: Gofer.Tests Failed: 0 test(s), Passed: 42 test(s), Skipped: 0 test(s), Total: 42 test(s)Name: Graphics.Tests.Files Failed: 0 test(s), Passed: 47 test(s), Skipped: 0 test(s), Total: 47 test(s)Name: Graphics.Tests.Primitives Failed: 0 test(s), Passed: 57 test(s), Skipped: 0 test(s), Total: 57 test(s)Name: HelpSystem.Tests.Builders Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s)Name: HelpSystem.Tests.Core.Model Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s)Name: HelpSystem.Tests.Core.UI Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: HelpSystem.Tests.Core.Utilities Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: KernelTests.Chronology Failed: 0 test(s), Passed: 583 test(s), Skipped: 0 test(s), Total: 583 test(s)Name: KernelTests.Classes Failed: 0 test(s), Passed: 68 test(s), Skipped: 0 test(s), Total: 68 test(s)Name: KernelTests.Exception Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)Name: KernelTests.Methods Failed: 0 test(s), Passed: 180 test(s), Skipped: 0 test(s), Total: 180 test(s)Name: KernelTests.Numbers Failed: 0 test(s), Passed: 276 test(s), Skipped: 0 test(s), Total: 276 test(s)Name: KernelTests.Objects Failed: 0 test(s), Passed: 87 test(s), Skipped: 0 test(s), Total: 87 test(s)Name: KernelTests.Pragmas Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)Name: KernelTests.Processes Failed: 0 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 37 test(s)Name: Keymapping.Tests Failed: 0 test(s), Passed: 38 test(s), Skipped: 0 test(s), Total: 38 test(s)Name: MorphicTests.Basic Failed: 0 test(s), Passed: 16 test(s), Skipped: 0 test(s), Total: 16 test(s)Name: MorphicTests.Event Failed: 0 test(s), Passed: 9 test(s), Skipped: 0 test(s), Total: 9 test(s)Name: MorphicTests.Kernel Failed: 0 test(s), Passed: 8 test(s), Skipped: 0 test(s), Total: 8 test(s)Name: MorphicTests.Text Support Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), To
Re: [Pharo-project] what is your pharo story?
Great description, Pavel ! On 17 Oct 2012, at 18:36, Pavel Krivanek wrote: > - open Xerox Smalltalk-80 image (using Hobes) I would want to try that myself ;-) Where can I get this, please ? -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill
Re: [Pharo-project] what is your pharo story?
I think that the examples related with stuff invented 30 years ago will depend on the audience. Most programmers, young ones in particular, have a deep lack of knowledge about the history of technology , they barely know about the tools they use everyday, and they don't have interest in learning about them either. So saying to them that Smalltalk invented BitBlt, is like talking them about punched cards. At least that is my experience. About the points, one thing that I found really useful is doing actual TDD or programming in the debugger, sometimes I get impressed myself when while having an open debugger I add an instance variable in another Browser (or even in the debugger), and have such modification already available to all the instances I have in the context of debugging (and the image, of course). Showing how productive you can be is something that also gets the interest of newcomers, unfortunately being productive is not building greater things with the same or less effort, but building the same with less efforts, hence the proliferation of one-liners and viral code snippets to attract naive programmers or people looking for something different, and are lazy to embrace something with a steep learning curve. Another good point is that when you develop using Smalltalk you (or at least I do) feel like you're inside your system, you program "from the inside", it is an immersive experience. With other tools, even with really advanced IDE's you never get that immersion, you feel like moving levers, and manipulating a machine, and advanced and most of the times decent machine, but the experience is less "humane" (using Tudor's use of the word) and not immersive. My points are not based Pharo stories, but are backed by 10 years of Smalltalk use, starting with Squeak, and passing through VW, VisualSmalltalk, VAST and Dolphin. I use Pharo, and enjoy it, though I'm not Kent Beck. Best regards, -- Esteban M. -- View this message in context: http://forum.world.st/what-is-your-pharo-story-tp4651692p4651732.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
