Re: [Pharo-project] froze image just
Btw. Waiting for network timeout doesn't work. That is to say, waiting a night is not long enough Stephan Verstuurd vanaf mijn iPhone
Re: [Pharo-project] froze image just
Stef wrote: > trying to publish a slice on my harddisc without network…. > and I could not interrupt anything. > No cmd+. no interdiction sign did anything :( I've seen that a few times recently, with Moose 4.8 & Pharo 2.0 images. >So is it normal? > Not being able to interrupt something is a pain. +1 It definitely is a place where you want to be able to interrupt. Stephan
[Pharo-project] Videos: Selling Pharo-based solutions & Custom architectural assessment
Selling Pharo-based Solutions https://www.youtube.com/watch?v=v65L07qR-w4 Custom architectural assessment of a large enterprise system https://www.youtube.com/watch?v=Zzkd2D_WiVY Stephan
[Pharo-project] State of PharoConf videos
Chris wrote:
>I would like to show my talk ("Selling Pharo-based Solutions" at
>PharoConf) to my team and enhance it for the next time. Just out of
>curiosity: are you still working on those videos? Otherwise, would you
>mind to provide the video file somehow?
Too many distractions, so not enough speed.
I'll put it up.
Stephan
Re: [Pharo-project] Smart Suggestion Version 1
Norbert wrote: >First grey out things and the expert can switch them off to make disabled >entries invisible. That's not what experts do, btw. Expert menu behavior is based on muscle memory. Things always being in the same place is crucial. As well as predictable delays for submenus, consistent width & height of the menus. Options are evil from a usability pov I took a detailed look: Nautilus menu items are not as tall as the other menus? That makes them difficult to use, muscle memory fails here. "Add Matching Packages as Groups and Browse" is definitely too long. Any suggestions for a shorter text? A 2-dimensional menu (circle menu) would work better here, where the number of elements is so high. Currently, the mouse travel distance is too large Camillo wrote: >In the end, for most pro users, and by that I rely on my experience with very >complex 3D software, >menus are mostly there to learn the shortcuts. That means they do not have to >be super navigable >(e.g. one big list) but logically structured (e.g. submenus). That could be a reversal of cause and effect. I've seen too many complex old systems where the old dos menu structure was simply moved to a context menu. That does not work at all. Stephan
Re: [Pharo-project] files.pharo.org: Moving to new server
Ben wrote: >I have seen mentioned that SmalltalkHub is faster than previous >repositories, but I also wonder... is there any consideration (or value) >to hooking SmalltalkHub up with a CDN ? >All uploaded mcz files are effectively static content. In the long term p2p based distribution would be much better. That fits much better with a cached CI/CD environment. And as that takes time to set up, a CDN can solve the content availability problem much sooner Stephan
[Pharo-project] Videos: Quicksilver & Fuel+Tanker
I wondered how many views the movies would get without being announced: 0. Demo: Handling hierarchical datasets with Quicksilver https://www.youtube.com/watch?v=pOxKVVoCH3A Handling Objects with Fuel and Tanker https://www.youtube.com/watch?v=-UQ35SOsuaY rendering & uploading Custom architectural assessment of a large enterprise system Stephan
Re: [Pharo-project] Metacello configuration conventions
Frank wrote: >I'd argue that since you're declaring that a certain set of versions >of packages work together, you should _always_ use explicit versions. >The "optimistic" strategy leaves you vulnerable to third parties >making seemingly innocuous changes that break your code. (I've been >bitten by this, by making such an apparently innocuous change.) Thank you. That's a clear vulnerability of the optimistic strategy. That sounds nice, but also means getting a change rate that is the sum of that of all your dependencies. It is also not very nice when you are depending on things that have known bugs you know will be fixed soon. What does it mean that a certain set of versions work together? Implicit seems the assumption that #Pharo2x is #stable, and we don't talk about the vm version or even worse the non-smalltalk dependencies. I don't see Metacello descriptions specifying all loaded packages. Stephan
[Pharo-project] Metacello configuration conventions
Hi, While working with Diego on some configurations, we noticed two different styles of describing the latest non-baseline versions. In one, the versionString version of a dependency is used. That is a defensive strategy, where you want to specify the exact version that will be loaded (and has been tested). In the other the #stable version is used. That is an optimistic strategy. This is much less brittle (but might suddenly not work anymore). Seaside uses defensive/mixed, while Magritte uses optimistic Based on what criteria should I choose which one to use (in a Pharo context)? Stephan & Diego
Re: [Pharo-project] Videos: FileSystem-Git
Sean wrote: >Thank you Stephan! Will these be eventually matched up to the screencast (I >thought I read that somewhere), or is this the final product ( which is >already great :) )? Priorities are on getting the raw videos out. After they are done, I'll try to make some combined ones, preferably as nice as the one by Yuriy. Stephan
[Pharo-project] Videos: Pharo from the CommandLine
Not yet combined with the screencast Pharo from the CommandLine https://www.youtube.com/watch?v=T8RNcXD94jk now rendering & uploading: Fuel & Tanker
[Pharo-project] Videos: MongoDB
Taming MongoDB from Pharo https://www.youtube.com/watch?v=LOFygLIRLY8 now uploading: Pharo from the CommandLine
Re: [Pharo-project] Videos: FileSystem-Git
Max wrote: >I noticed that there's a transition in the middle of the video (rotating cube) >and then >the entire video is shown again. So the video contains the same sequence >twice. >What's the idea behind that? I'm sorry about that. No CI and lack of tests I'm afraid. It looked to me like all rendering was done before the machine ran out of disk space so I thought it safe to start uploading everything asap. I'll put out a fixed version. Stephan
[Pharo-project] Videos: FileSystem-Git
FileSystem-Git https://www.youtube.com/watch?v=4qld2mDIbg4 and uploading: Taming MongoDB from Pharo
[Pharo-project] Video uploads PharoConf & MooseDay resuming
Hi all, Raw versions of Building UIs with Spec https://www.youtube.com/watch?v=P98-qpLUvQQ Data Migration with Moose https://www.youtube.com/watch?v=8SGHV1lCry0 Pharo Roadmap https://www.youtube.com/watch?v=9xRVzzjgPu8 are now online Uploading now is FileSystem-Git
[Pharo-project] Videos delayed
Katja noticed that the rendering machine was running out of disk space. She might be able to free some up this afternoon Stephan Verstuurd vanaf mijn iPhone
[Pharo-project] PharoConf Videos: Pharo Roadmap video online (full)
https://www.youtube.com/watch?v=9xRVzzjgPu8 Rendering and uploading (probably 1 or 2 a day): Data Migration with Moose FileSystem-Git Pharo CLI Building UIs with Spec MongoDB Fuel & Tanker Others: later Stephan
[Pharo-project] Re; Videos of PharoConf & MooseDay: Presenters of show us your project
Max wrote: >I demoed FileSystem-Git on the first day. I was second last I think. Ok, you are next. Raw version, not merged with screencast yet. I assume having video fast, and fancy later is the way to do this. Stephan
[Pharo-project] Videos of PharoConf & MooseDay: Presenters of show us your project
Hmm, Just finished uploading one hour of Pharo Roadmap. Should be visible on youtube soon. Next: Diego's Data Migration with Moose (still rendering, could arrive somewhere late this night). I'll let my machine render and upload a few parts more. Fixing & cleaning is for later. They should take half a day each or so. I know a lot of Pharo people, but not all. Can anyone tell me, who presented what (and when) in the Show us your project? Cheers, Stephan
[Pharo-project] First 13 minutes of PharoConf
https://www.youtube.com/watch?v=qwc84HSkO1w More to come... Stephan
[Pharo-project] State of PharoConf videos
Hi, I'm very happy to see that the initiative to make video recordings of the PharoConf and MooseDay has resulted in so many screencasts already published. Great work! And now the first feedback: - Format conversion: 62 of 72 GB done, processing the whole weekend. - First 13 minute part currently encoding and uploading. Still about an hour and a half to go. - I would like to receive the presentation files to combine them with video. - Some of the material is difficult to use. Zoomed out too much it is difficult to follow the speaker and the beamer screen is not readable. Combining a screencast with the video only makes sense when zoomed in (talking head size). Why does this take so long? - the video is in a format that I cannot work with directly, so needs transcoding. I have been using VideoMonkey for this, which is based on ffmpeg. I have the impression that this ffmpeg is not using the GPU, but only the i5. I'm open for suggestions on better software for this in the future, as it takes the whole weekend. - I switched from iMovie to Final Cut Pro X. That allows non-linear editing, so I don't have to wait for rendering to cut the movies. It remains responsive even during the format conversion. - video is much larger than the equivalent length of screencast. That creates a upload bottleneck. 13 minutes of HD video is 733 MB. My home upload is 1Mbps (2 hours), so for uploading more material I'll ask someone at our local university. - I'm spending a limited amount of time during the weekend (and none next week). Stephan
Re: [Pharo-project] [Moose-dev] Re: Big thanks for the organization of the Pharo Conf and MooseDay
On 5 apr 2013, at 12:16, Tudor Girba wrote: > I would also want to thank the participants! The atmosphere was nice and the > presentation was interesting. > > I for one learnt quite a bit. > > The sessions were recorded, and once Stephan Eggermont will convert them, > they will be posted. And for some ideas on when that will be: I just got back from Diego with 72 GB of video files. This weekend I might find some time to proces them, but the whole week I'm at Accu2013 in Bristol. So what's not posted on monday, will take at least a week more. If anyone has other material (sheets, screencasts, other video) please let me know I'll keep you posted. Stephan
Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness
We seem to have a regression. In early may 2011 this was resolved. Tudor Girba wrote >This is not great at all. Please read this before going forward. > >We had this in OCompletion before and then it got changed to not use CR for a >reason. The problem is when using fluent APIs that are best read when written >on multiple lines. For example, >suppose that I want to type something like >this in Glamour: > >... >a tree >display: [ ... ] > >After typing "a tree", the first proposed item is "treeLayout" (see the >attached picture). If I press enter to go to the next line "tree" is replaced >with "treeLayout" and this is not the behavior I want. > >The problem is that CR has a useful meaning when typing a piece of text and >this makes it not good as a completion character.Tab on the other hand, is >only used in Smalltalk at the beginning of an >empty line so there is no >danger of overloading its functionality in the middle of a text. > > >Now, if you insist, I still believe there is a place for CR. Completion has >two modes: >1. one in which I write and the completion offers me something, and >2. one in which I am after I press the down arrow to select some completion >item. > >For 1. you do not want to have CR as a completion character. For 2. it is >probably ok because you enter explicitly in a temporary mode and thus you are >not typing anymore and this will not induce >the conflict. and Igor refined that to: >i agree, a completion should be non-intrusive (by default it should >handle enter as carriage return, >but if you selected an item (using up/down keys), then it should paste >the selection instead). >But as i said, i having a habit to use enter, when i see a popup menu >and hilighted menu item selected instead of tab. Stephan
Re: [Pharo-project] Renaming methods in the debugger
Igor wrote: >Sometimes you have to really fear of what you want :) >Yes, time to time, i also get annoyed by inability to do that... but... I know. I agree. It is just pushing the limits one small piece at a time... The case where I find I would like this most, is when I notice a test method has the wrong name. It is actually not doing what it says it does. Stephan
[Pharo-project] Renaming methods in the debugger
While presenting "Revenge of the Debugger, feedback addicted" at Devnology tonight with Willem van den Ende, we noticed that it would be nice to be able to rename methods in the debugger. Is that something we missed in only using the old Pharo 2.0 debugger? :) Stephan
Re: [Pharo-project] Looking for a Seaside 3.1 Configuration for Pharo 2.0
Stef wrote: >we would like to use seaside to validate the VM and also make sure that >Seaside31. works perfectly in Pharo2.0. >I saw that some of you have a working configuration. Where can we find it >because we would like to publish it in the >MetaRepoForPharo20. We have it working, but it does not have the Seaside Panel (& browser). At last Esug Seaside sprint I started redoing them in Spec, but never managed to spend more time on them. They are in the Seaside31 repository on squeaksource: Seaside-Pharo-Tools-Spec (might need renaming to Pharo20). Stephan
Re: [Pharo-project] in anybody out there? who uses 2.0?
Esteban wrote: >Here in Pharo headquarters we are shock that there are just 10 new bugs >reported for 2.0 after the release... >So... I wonder... is that because we made a really cool release, or just >because nobody is using it? It is a cool release and we are using it. Sorry about the lack of issues, I just added 10158 for you. We have been mostly doing a lot of work making our stuff work on Pharo 2.0. That mostly involves changing our code, not Pharo 2.0. So I'd say it is stable enough. Just keep up the speed. Cheers, Stephan
[Pharo-project] Not so nice refactoring behavior in Nautilus
Hi, We're moving some code to Pharo 2.0 and noticed the following. When removing a method with a selector that is found often in the system, the warnings come one at a time, instead of in one dialog for all. That slows refactoring down quite a bit. Cheers, Stephan & Diego
Re: [Pharo-project] Pharo 2.0 released!
Camillo wrote: >On 2013-03-19, at 10:58, Stephan Eggermont > I've been thinking about what would help Pharo development the most. >> I think making sure that everyone can get up-and-running with his >> own ci-server would help a lot. > >Just for the record, if you don't need a private CI server, we provide >one for the community: ci.inria.fr/pharo-contribution/ That is really nice, and I'm looking forward to using it for deltawerken, storyboard etc. We have some selenium tests for those (Parasol)... (an account would be great) There are many reasons to also want to have CI locally, from private projects to working in the train to depending on software not installed on the community server to having the fastest feedback cycle possible. Stephan
[Pharo-project] Pharo 2.0 released!
Great to see Pharo 2.0 released. Too bad I cannot make it to the Pharo/Moose days, but Diego will show some of the things we have been working on. I've been thinking about what would help Pharo development the most. I think making sure that everyone can get up-and-running with his own ci-server would help a lot. I noticed there are lots of parts available, I'm just missing the story about putting it all together. And I know that takes a lot of time to create these things, as the feedback cycle is much slower than with smalltalk development. Would it be possible to provide a virtualbox vm with an installed jenkins and a full set of jobs, or even better, chef/puppet/vagrant scripts to create them? At the Pharo conference would be perfect? Cheers, Stephan
[Pharo-project] https://pharo.fogbugz.com : can I have an account there?
And me too? Stephan
Re: [Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24
Sean wrote >- Proof-of-concept at ESUG to enhance FileTree/Cypress for VW <-> Pharo >porting, automatically converting between prefixes and namespaces; Cami and >I were able to load the newest version of Xstreams from VW, and then commit >it again in a cross platform format that could (I think, not tested) be >loaded in VW Great. Did you contact Christian Haider to try with his PDF library? That would solve one of the obstacles to getting a really good pdf library in Pharo. The other being of course the coupling to VW drawing. Stephan
Re: [Pharo-project] Debugger-driven development (was Re: WhatsUp from: 2013-03-11 until: 2013-03-24)
Frank wrote: >I'd love to hear more about your presentation. I've been thinking how >to run a kind've live-coding demonstration at work, showing how a >Smalltalk debugger is so clearly superior to what other folk have. It is inspired by Jason Ayers' session at SPA and XPDays Benelux. It will be a short session, as there will be 2 other presentations on non-intuitive subjects. Devnology has a diverse public with mostly java and c# developers. Agilists in those environments are likely to advocate writing a test instead of using a debugger, and are often unaware of the incremental development possibilities offered by the smalltalk debugger. >(Squeak trunk now lets you create methods not just on an MNU but also >where people have things like "self subclassResponsibility", "self >notYetImplemented" or "self shouldBeImplemented" flags such that you >can debug-edit-and-continue.) Yes, I saw your blog post yesterday. Cool. That's definitely something I would like to show. I haven't given much thought yet to which debugger I want to use. I'm tempted to use the GTDebugger and modify it during the session (to add your new extensions perhaps) but that is something I have to try and time first. It might be too much magic. Stephan
Re: [Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24
### Here's what I've been up to since the last WhatsUp: - Added a storymap view to StoryBoard. Stories can now be added to a goal of a stakeholder. (+Diego Lont) - Accepted proposal to show debugger-driven TDD at Devnology meetup April 3 in Eindhoven (+Willem van den Ende) - Created proposal for a distributed issue tracker GSoC with Diego - Did a spike for a distributed issue tracker with Diego - Convinced Diego to go to Pharo & Moose Days and show TutorialBrowser & Data Conversion with MOOSE - Did a spike with a gherkin glamour browser, tried moving it to latest pharo/MOOSE/vm :) ### What's next, until 2013-03-24 (*): - publish distributed issue tracker spike - prepare presentations with Diego - parse gherkin files, visualize as roassal nested polymetric views Stephan
Re: [Pharo-project] Latest pharo issue with Eliot's latest Cog
Esteban wrote: >Pharo 2.0 does not work with Eliot builds (and it will not work in some >scenarios). >In this case, the main reason is that we rebuild (and use) FilePlugin and it >is not >incorporated in Eliot branch of the vm... so the FileDialogWindow will take >years to open if opens at all. >You need to use one of our VM builds (anyone from last 6 months to now should >work) Ah, I didn't know the differences were already so that we need a Pharo-specific vm. nbcog-mac-latest.zip from 27-11-2012 doesn't crash. 15883 run, 15493 passes, 2 skipped, 88 expected failures, 207 failures, 95 errors, 0 unexpected passes Would it be possible to have the vm warning more informative? Something like "expected FilePlugIn, ..."? Stephan
[Pharo-project] Latest pharo issue with Eliot's latest Cog
The problem is not just with the MOOSE image, Pharo 20598 and Cog.app 2071 doesn't allow a file dialog to be opened. FileDialogWindow new open Stephan
Re: [Pharo-project] GSoC13: Distributed Issue Tracker
Göran wrote: >Would you like me to dig out the Gjallar codebase and share it with you? >With some annotations? There should be lots to pick/learn from it. I have a Gjallar0.4 image here. Any changes since then? Stephan
[Pharo-project] GSoC13: Distributed Issue Tracker
Distributed Issue Tracker Level: (intermediate, advanced) Possible mentor: Stephan Eggermont Possible second mentor: Diego Lont Description A native smalltalk distributed issue tracker. It should have basic issue tracking functionality including attaching files/pictures/code. It should have a native interface, a web interface and a scripting API. Primary development is in Pharo. Issue trackers have different kind of users. To make clear that different users have different needs, persona can be helpful. Isabelle is an information technology student looking for an interesting language and environment to learn. She wants to contribute to and learn from a smart community and needs interesting experiences on her cv. She has already learned the basics of a few mainstream languages and feels ready to try something more exotic. Smalltalk seems interesting as the origin of many inventions. Yann is the major developer of a web-based platform based on Pharo and Seaside. He needs to ensure the platform keeps working smoothly and is updated regularly with the latest changes. In production he uses the released versions. He fears the major clean-ups Pharo is making make it difficult for him to keep up. He is dependent on a few old unmaintained squeaksource packages. Janine just found an interesting old package on squeaksource. It was last changed in 2007. She has been using smalltalk for a few years, so knows what to expect when trying to load an unmaintained package. There are some missing classes that still exist in squeak. Tony is the developer of a package that is used with nearly all smalltalks. He mainly works with a commercial smalltalk and keeps just enough contact with the Pharo community to keep his package working. He has complained about some changes that made it necessary for him to change his package structure. He mainly updates the Pharo version on his way to and from the office in the train. Eve maintains a few of the crucial Pharo kernel packages. They are under heavy development and once in a while everything breaks, leading to a flood of issues. They mostly come from outsiders, as she talks daily with the Pharo core team. She has to close a lot of them as duplicates. She also has to review code that gets attached in one form or another to the issue. Daniel is a maintainer of the vm that forms the basis for the Pharo vm. The vm is used by many more projects. Lara is a release manager for a well known linux distribution. Pharo is just one of 30 languages that are included in the distribution. Before doing a release she scans the issue tracker for any show stoppers. She had to stop including environments because of security issues. Technical Details The recent decision by Google to deprecate and stop its API for the Google Issue Tracker used by a.o. the Pharo, Seaside, MOOSE and Metacello projects makes it necessary for those projects to select a different issue tracker. The timespan before this decision has to be made is too short for the development of a new issue tracker from scratch. Now most development in Smalltalk uses distributed version control systems, either Monticello or Git, the question arises why these projects still would want to use a centralized issue tracker. The long-standing problems in keeping squeaksource up-and-running are only one example of the problems of depending on centralized infrastructure. Other examples are the move of Lukas' repository and the number of times where the Pharo CI infrastructure was not available, especially on holidays and weekends. The currently used issue trackers cannot work disconnected. Integrating the issue tracker in the CI workflow of the projects is crucial. The goals of the persona should be translated into a storymap. Delivery should be iterative and incremental, driven by value to the community and technical risk. The student is expected to be active on the mailing list and discuss development there. This includes handling (source) contributions by others. There is a small prototype available. Benefits to the Student - getting to know the difficulties of issue tracking/the workflow of open source projects - experience with distributed systems - experience an agile open source environment Benefits to the Community - better integrated workflow - native issue tracker, accessible both in-image, web and automated - showcase for productive environment Questions Here are seven persona. Which ones are missing/should be fleshed out?
Re: [Pharo-project] where to report vm crashes? (while running Moose tests)
Phil wrote: >Eliot as a new VM as of yesterday > >http://www.mirandabanda.org/files/Cog/VM/VM.r2701/README.2701 > >That kind of fixes things. > >But I guess the Pharo team still has to integrate these fixes. This is with 2701. The Moose image is based on Pharo 20589 Stephan
Re: [Pharo-project] where to report vm crashes? (while running Moose tests)
Esteban wrote: > Eliot builds will always have the old vm warning, even if they are not old > :)... > you need one of the pharo builds (CogVM, NBCogVM or PharoVM) Well, Doru reported they crashed. Eliot's one doesn't: > 15875 run, 15472 passes, 2 skipped, 88 expected failures, 216 failures, 99 > errors, 0 unexpected passes On the other hand, not being able to add a monticello directory repository is also not helpful. No filedialog is shown (receiver of bitAt: is nil, looks like a problem with filesystem permissions) Stephan
Re: [Pharo-project] where to report vm crashes? (while running Moose tests)
>It would be good to have a parallel job, but the problem is that you will >get a message saying that the VM is too old for the Pharo 2.0 image. I started the latest MOOSE image on Eliots latest VM on mac. It still has the 'old vm' warning. Adding a monticello repository (directory) doesn't work. Tests are still running Stephan
[Pharo-project] TxTextMorph based on new text model
Sean wrote: Denis Kudriashov wrote >> Do you think that presenting any letter with real object (not just >> character) is sufficient for modern computers? I think not. Of course such >> model significantly simplified all logic around text layout stuff. But I >> think it is too expensive. In a case study on designing a document editor in 'Design Patterns (1995)' , there is a reference to a thesis from 1993 showing that using Flyweight or sharing commonality makes it fast enough. I assume that was c++, but 20 years of hardware improvements should be enough. Paul R Calder. Building User Interfaces with Lightweight Objects. PhD Thesis, Stanford University, 1993 >I don't know how efficient it would be, but how much text do we really >layout at once? If it makes the code simpler and more beautiful, then it >would be my starting point. Doing otherwise is premature optimization. One book at a time. In multiple columns, with tables. But we don't need to show more than one screenful at a time. I noticed the current strategy seems to be to make a very simple model work, and add abstractions late. That means a lot of refactorings will be needed. Cocoa fundamental abstractions are TextStorage, LayoutManager, TextContainer and TextView. LayoutManager uses TypeSetter(s) to layout glyphs in lines according to the dimensions of one or more text container objects in one or more text views, directs the GlyphGenerator to translate characters in the textstorage into glyphs... Stephan
Re: [Pharo-project] Experience using multiple images as a distributed datastore?
Hi Martin, Hmm, through google it works, and removing the ? isn't enough. It is a paper on resilient distributed datasets. Lazy distributed collections, basically. http://www.cs.berkeley.edu/~matei/papers/2012/nsdi_spark.pdf Stephan
[Pharo-project] Experience using multiple images as a distributed datastore?
Hi, I'm looking at alternative ways to break through the 4G 1 core border. Does anyone have recent experience storing data in multiple images and parallelizing calculations, perhaps similar to https://www.usenix.org/system/files/.../nsdi12-final138.pdf? With Ghost, Fuel and Zinc the building blocks seem to be there. Stephan
Re: [Pharo-project] Cross-classified methods
Hmm, it was not clear in which direction this works. I switched them for http://code.google.com/p/pharo/issues/detail?id=7379 Thanks for noting, Sean. So: the first set are methods where Squeak has no classification, and Pharo does. The second set has methods where Pharo has no classifications, and Squeak does. Stephan
Re: [Pharo-project] Cross-classified methods
Next step could be to compare the contents of the methods. Automation would allow the classification of a method in either to be propagated to the other. Stephan
[Pharo-project] Cross-classified methods
When I map the list of unclassified methods in Squeak 4.3 on class name & method name in Pharo 20498, I find the following classifications. First in Squeak for Pharo HttpUrlTest testHttps testing UUIDTesttestComparison testing TextAction analyze:testing TextAction dominatedByCmd0 testing TextAction emphasizeScanner: styling TextAction infoaccessing TextAction validate: testing TextAlignment = testing TextAlignment alignment accessing TextAlignment alignment: accessing TextAlignment dominates: testing TextAlignment emphasizeScanner: utils TextAlignment hashtesting TextAlignment writeScanOn:utils TextAttribute anchoredMorph accessing TextAttribute dominatedByCmd0 testing TextAttribute dominates: accessing TextAttribute emphasisCodestyling TextAttribute emphasizeScanner: styling TextAttribute forFontInStyle:do: styling TextAttribute mayBeExtended testing TextAttribute oldEmphasisCode:styling TextAttribute reset accessing TextAttribute set accessing TextDoItanalyze:testing TextDoItevalString: accessing TextDoItinfoaccessing TextDoItwriteScanOn:styling TextEmphasis= comparing TextEmphasisdominatedByCmd0 testing TextEmphasisdominates: accessing TextEmphasisemphasisCodestyling TextEmphasisemphasisCode: accessing TextEmphasisemphasizeScanner: styling TextEmphasishashcomparing TextEmphasisprintOn:printing TextEmphasisset accessing TextEmphasisturnOff accessing TextEmphasiswriteScanOn:styling TextLinkanalyze:testing TextLinkanalyze:with: testing TextLinkclassAndMethod: accessing TextLinkinfoaccessing TextLinkvalidate: testing TextLinkwriteScanOn:styling TextPrintIt writeScanOn:styling TextURL analyze:testing TextURL infoaccessing TextURL url:accessing TextURL writeScanOn:styling LayoutFrameTest testInset tests LayoutFrameTest testLeftTopAligned tests LayoutFrameTest testRightBottomQuadrant tests LayoutFrameTest testSpaceFill tests FileStreamTest testCachingNextChunkPut testing FileStreamTest testDetectFileDotesting FileStreamTest testFileTruncation testing FileStreamTest testNextChunkOutOfBoundstesting FileStreamTest testNextLinetesting HashAndEqualsTestCase setUp running HashAndEqualsTestCase testEqualitytesting HashAndEqualsTestCase testHashtesting MCClassDefinitionTest classAComment private MCClassDefinitionTest creationMessage private MCClassDefinitionTest tearDownrunning MCClassDefinitionTest testCannotLoad tests MCClassDefinitionTest testComparison tests MCClassDefinitionTest testCreationtests MCClassDefinitionTest testDefinitionStringtests MCClassDefinitionTest testEquals tests MCClassDefinitionTest testEqualsSensitivity tests MCClassDefinitionTest testKindOfSubclass tests MCClassDefinitionTest testLoadAndUnload tests MCDictionaryRepositoryTest addVersion: actions MCDictionaryRepositoryTest deleteNode: utility MCDictionaryRepositoryTest dictionary utility MCDictionaryRepositoryTest setUp running MCDirectoryRepositoryTest addVersion: actions MCDirectoryRepositoryTest directory accessing MCDirectoryRepositoryTest setUp running MCDirectoryRepositoryTest tearDownrunning MCOrganizationTest testReordering tests MCOrganizationTest testReorderingWithNoCategoriesInVersion tests MCOrganizationTest testReorderingWithRemovals tests MCPatchTest setUp running MCPatchTest tearDownrunning MCPatchTest testPatchContents tests MCSnapshotResource definitions accessing MCSnapshotResource setUp running MCSnapshotResource snapshotaccessing MCStReaderTest commentWithStyleutil MCStReaderTest commentWithoutStyle util MCStReaderTest methodWithStyle util MCStReaderTest testCommentWithStyletests MCStReaderTest testCommentWithoutStyle tests MCStReaderTest testMethodWithStyle tests MethodChangeRecord printOn:printing MCAddition inverse accessing MCAddition isClassPatchtesting MCChangeSelectionRequestdefaultAction *MonticelloGUI MCChangeSelectorwidgetSpecs as yet unclassified MCClassInstanceVariableDefinition isClassInstanceVariable testing MCClassTraitDefinition loadinstalling MCClassTraitParser addDefinitionsTo: actions MCClassVariableDefinition isClassVariable testing MCClassVariableDefinition isOrderDependendtesting MCDictionaryRepository morphicOpen:*MonticelloGUI MCDoItParseraddDefinitionsTo: actions MCDoItParsersour
Re: [Pharo-project] I hate 'as yet unclassified'
Norbert wrote: >To be honest I have problems understanding why method categorization is so >important. Often I don't care a single bit about categories because I don't >understand them. I often categorize just to >make lint happy :) >What is the use? Declaring usage patterns? Declaring visibility? Use as method >extensions marker? anything you like just classify? I can understand that it >can help making the access of certain >methods of a class easier. But that is >particular true for classes with a lot of methods. Most of the classes are >rather small. In most of my own developments I would consider most huge >classes a >design problem in my code. So I would try to fix that. >And finally it is not easy to learn about them because the browser is not >helping. If you browse through the methods of a class the category pane >doesn't get updated. So even if I want to learn by >getting used to them it is >hard. > >I would make the none categorized term weaker by naming it "uncategorizied" so >at least I have the change to deliberately not categorizing my methods without >being annoyed by someones >opinion about what is essential. Ok, that's fair. It is no real problem when all methods are visible in the class browser. When ignoring classes with <=10 methods, the results are : By package Polymorph-Widgets 988 Polymorph-Widgets-Windows 516 Polymorph-Tools-Diff258 Monticello-Repositories 176 NativeBoost-Core-Objects52 FreeTypeTests-cache 52 Monticello-Versioning 52 AST-Core-Visitors 48 Graphics-Fonts 42 Balloon-Fills 40 Polymorph-Widgets-Themes39 Morphic-MorphTreeWidget-Examples36 Monticello-Storing 34 Morphic-Text Support32 NOCompletion-Model 30 Collections-Streams 30 Monticello-Modeling 26 Morphic-MorphTreeWidget 26 MonticelloGUI 25 Text-Core 22 Morphic-Borders 22 Morphic-Explorer20 NativeBoost-Tests 19 Tests-Traits18 NativeBoost-Core-Types 16 Keymapping-Tests15 Keymapping-Shortcuts14 NativeBoost-Core14 Files-Kernel14 CollectionsTests-Strings12 CompilerTests 12 CollectionsTests-Arrayed12 CollectionsTests-Sequenceable 12 Morphic-Menus 10 Traits-Kernel 10 AsmJit-StackManagement 9 UnclassifiedMethods 9 Morphic-Pluggable Widgets 8 Morphic-Basic 8 KernelTests-Methods 6 Tools-Explorer 6 Monticello-Patching 6 SUnit-Core-Kernel 6 Spec-Widgets6 KernelTests-Chronology 6 ScriptLoader20 5 NativeBoost-Win32 4 FreeType-FontManager4 NativeBoost-Core-FFI4 NativeBoost-Core-Heap 4 Tools-Base 2 Spec-Bindings 2 Morphic-Support 2 Tools-Inspector 2 KernelTests-Numbers 2 FileSystem-Core-Kernel 2 MenuRegistration-Core 2 Kernel-Classes 2 CollectionsTests-Unordered 2 FileSystem-Core-Public 2 Graphics-Display Objects2 RPackage-Tests 2 Spec-Core 2 Morphic-Worlds 2 FuelTests 1 Refactoring-Tests-Critics 1 FileSystem-Disk 1 Ring-Tests-Kernel 1 UIManager 1 By author gvc 1307 GaryChambers195 186 AlainPlantec123 CamilloBruni89 stephaneducasse 78 SeanDeNigris72 avi 69 IgorStasenko61 tween 52 MarcusDenker50 GuillermoPolito 41 StephaneDucasse 39 Igor.Stasenko 39 ab 38 BenjaminVanRyseghem 32 FernandoOlivero 29 alain.plantec 27 RAA 26 nice25 tk 24 EstebanLorenzano23 rr 20 di 18 JMM 16 yo 14 PavelKrivanek 12 marcus.denker 12 sd 12 dvf 10 SvenVanCaekenberghe 10 HenrikSperreJohansen9 bf 9 nk 8 ar 8 StephanEggermont8 MarianoMartinezPeck 7 jrd 6 GastonDallOglio 6 noha6 stephane.ducasse5 TestRunner 4 bkv 4 DamienCassou4 lr 3 LukasRenggli2 abc 2 ls 2 ASB 2 cipt2 th 2 damienpollet2 ul 2 NorbertHartl2 cwp 2 dgd 2 GabrielOmarCotelli 2 al 2 mas 2 AlexandreBergel 2 SJCE1 DeboraFortini 1 The code I wrote is quick and dirty. Didn't think about class side & traits. Stephan UnclassifiedMethods-StephanEggermont.3.mcz Description: Binary data
Re: [Pharo-project] I hate 'as yet unclassified'
Sven wrote: >Euh, I want to fix some of them ! Good, that was the idea :) I was inspired by Doru's humane assessment primer. >Could you express this query in executable code ? >I am guessing you did this with Moose ? >Can it be done in plain Smalltalk ? I opened a Moose to take a look at the Mondrian examples, then copied that. This is the version that runs in both Squeak and Pharo. Open a workspace, Print-it on Unclassified new byAuthor Unclassified new byPackage This package intentionally contains some unclassified methods :) UnclassifiedMethods-SJCE.2.mcz Description: Binary data
Re: [Pharo-project] I hate 'as yet unclassified'
As there was a discussion on the Pharo mailing list on the number of these methods, I thought to check in the 4.3 one-click too. Some synchronisation would be possible by adding a hash over the method source, compare one method in the other system to see if it was classified there. Stephan #unclassified methods by package Etoys-Experimental 126 Morphic-Widgets 112 MorphicExtras-GeeMail 94 Collections-Text90 Monticello-Repositories 79 ToolsTests-Browser 76 Multilingual-Display76 Monticello-UI 72 Nebraska-Morphic-Collaborative 62 Monticello-Versioning 61 Tests-Monticello52 Multilingual-TextConversion 49 Monticello-Merging 46 MorphicExtras-Demo 46 Morphic-Windows 45 MorphicExtras-Books 39 Etoys-Outliner 35 Tools-Browser 33 Network-RemoteDirectory 33 Tests-Bugs 32 Compression-Streams 32 Monticello-Storing 31 Sound-Scores28 Tests-Monticello-Mocks 28 MorphicExtras-Navigators27 MorphicExtras-AdditionalSupport 25 Morphic-Explorer24 Nebraska-Morphic-Remote 22 Monticello-Patching 22 Tests-Files 20 Monticello-Chunk Format 20 Morphic-Text Support20 Nebraska-Morphic-Experimental 20 Exceptions-Kernel 16 MorphicExtras-Text Support 16 MorphicExtras-Support 15 Monticello-Modeling 15 Sound-Synthesis 14 Tools-Inspector 14 MorphicExtras-Palettes 11 MorphicExtras-SoundInterface10 Collections-Streams 10 TraitsTests-Kernel 10 Tests-Utilities 9 System-Changes 9 ST80-Pluggable Views9 MorphicExtras-AdditionalWidgets 8 Installer-Core 7 Compiler-Exceptions 7 Morphic-Menus-DockingBar7 Nebraska-Network-ObjectSocket 7 Files-Kernel7 Monticello-Loading 6 ST80-Views 6 MorphicExtras-Widgets 6 MorphicExtras-AdditionalMorphs 6 Tests-ObjectsAsMethods 6 Multilingual-Editor 5 SMBase-domain 5 MorphicTests-Widgets5 Nebraska-Audio Chat 5 MorphicTests-Kernel 5 ToolBuilder-Kernel 5 ST80-Controllers4 Etoys-Stacks4 Morphic-Menus 4 ST80-Framework 4 MorphicExtras-SqueakPage4 CollectionsTests-Weak 4 MorphicTests-Layouts4 Morphic-Pluggable Widgets 4 SUnit-Tests 4 Tests-Hex 4 ToolBuilder-SUnit 3 Etoys-Scripting 3 Graphics-Fonts 3 Kernel-Methods 3 Multilingual-Scanning 3 Files-Directories 3 SUnit-Extensions3 ToolBuilder-Morphic 3 SystemChangeNotification-Tests 3 Morphic-Basic 3 ST80-Support2 Network-Kernel 2 Etoys-Scripting Tiles 2 Kernel-Classes 2 Graphics-Primitives 2 Collections-Arrayed 2 MorphicExtras-Postscript Canvases 2 Services-Base 2 Graphics-Display Objects2 Balloon-Fills 2 NetworkTests-UUID 1 PackageInfo-Base1 Tools-FileList 1 CollectionsTests-Text 1 NetworkTests-RFC822 1 Services-Base-GUI 1 Tests-System-Support1 System-Support 1 ST80-Editors1 Etoys-Tile Scriptors1 System-FileRegistry 1 Etoys-Scripting Support 1 NetworkTests-Url1 Morphic-Kernel 1 ToolsTests-Inspector1 #unclassified methods by author RAA 438 stephaneducasse 145 ar 144 avi 99 yo 97 gvc 80 fbs 80 tk 80 di 76 nice73 ab 73 sd 58 jm 47 dgd 44 sw 41 ul 35 nk 35 cmm 27 27 cwp 26 bf 26 md 19 kb 12 wiz 12 jrp 11 kph 7 dvf 6 Tsutomu 6 ajh 6 mjr 6 ls 6 rej 6 apb 5 dtl 5 acg 4 gk 4 sbw 4 abc 4 bp 4 nb 4 jmv 3 spfa3 laza3 rr 3 JPF 3 MarcusDenker3 al 3 Igor.Stasenko 3 BG 2 tetha 2 pk 2 btc 2 jrd 2 eem 2 mha 2 tfel2 mir 1 jcg 1 mist1 LC 1 tlk 1 djp 1 sumim 1 DSM 1 TN 1 aoy 1 DF 1 alain.plantec 1 gm 1 th 1 bvs 1 sma 1 jf 1 sps 1 tonyg 1 hh 1 tak 1 '
Re: [Pharo-project] I hate 'as yet unclassified'
In Pharo 20498, sorted by package name Polymorph-Widgets 1116 Polymorph-Widgets-Windows 615 Polymorph-Tools-Diff260 Monticello-Repositories 240 Morphic-MorphTreeWidget-Examples192 Monticello-Versioning 144 NativeBoost-Core-Types 104 Monticello-Storing 66 NativeBoost-Core-Objects60 Graphics-Fonts 56 NativeBoost-Tests 55 Balloon-Fills 54 FreeTypeTests-cache 52 Text-Core 50 AST-Core-Visitors 48 Tests-Bugs 46 Collections-Streams 44 Morphic-Borders 44 Polymorph-Widgets-Themes42 Keymapping-Tests39 Monticello-Modeling 38 Tests-Traits38 Morphic-Text Support32 MonticelloGUI 31 NOCompletion-Model 30 Monticello-Patching 28 Morphic-Explorer28 Morphic-MorphTreeWidget 26 RPackage-Tests 22 Monticello-Mocks21 Tests-Monticello20 Keymapping-Shortcuts20 Polymorph-Geometry 20 NativeBoost-Core19 NativeBoost-Core-FFI18 Tests-Polymorph-Widgets 18 SUnit-Core-Utilities18 Compiler-Exceptions 18 Tools-Explorer 18 NativeBoost-Win32 16 Tests-SystemHistory 16 Files-Kernel14 CollectionsTests-Weak 14 CompilerTests 14 Tools-Inspector 12 CollectionsTests-Arrayed12 CollectionsTests-Sequenceable 12 NativeBoost-Core-Heap 12 CollectionsTests-Strings12 Tests-ObjectsAsMethods 12 Tests-System12 Traits-Kernel 10 Morphic-ProgressBar 10 MorphicTests-Kernel 10 NativeBoost-Core-Errors 10 Tools-Debugger 10 Morphic-Basic 10 KernelTests-Methods 10 Morphic-Menus 10 AsmJit-StackManagement 9 Morphic-Pluggable Widgets 8 Kernel-Exceptions 8 System-Changes 8 Tools-FileList 8 NautilusCommon-Refactor 8 Kernel-Methods 8 Morphic-Events 8 FileSystem-Core-Implementation 8 MorphicTests-Widgets6 NativeBoost-Mac 6 AST-Core-Nodes 6 ToolsTest-PointerFinder 6 FileSystem-Tests-Core 6 Kernel-Pragmas-Collector6 MonticelloMocks 6 Tests-TextEditors 6 KernelTests-Classes 6 SUnit-Core-Kernel 6 HudsonBuildTools20 6 System-Settings-Core6 KernelTests-Chronology 6 Spec-Widgets6 ScriptLoader20 5 NetworkTests-Protocols 4 Spec-Tests 4 FreeType-FontManager4 Morphic-Widgets 4 System-Announcements4 NautilusCommon-Plugin 4 Morphic-WindowNotification 4 Collections-Abstract4 Text-Edition4 Manifest-Resources-Tests3 UIManager-Support 2 Nautilus-Widgets2 KernelTests-Processes 2 Collections-Arithmetic 2 KernelTests-Numbers 2 Network-Protocols 2 Spec-Bindings 2 CollectionsTests-Unordered 2 Kernel-Classes 2 Network-Kernel 2 Tools-Base 2 Kernel-Processes2 NativeBoost-Examples2 NECompletion-Model 2 FileSystem-Zip 2 Tests-PackageInfo 2 Compression-Streams 2 FileSystem-Core-Public 2 MenuRegistration-Core 2 Tools-Finder2 FileSystem-Core-Kernel 2 System-FileRegistry 2 Zinc-Tests 2 Spec-Core 2 Graphics-Display Objects2 Morphic-Kernel 2 Network-URI 2 Nautilus-Tests 2 Collections-Support 2 System-FilePackage 2 Morphic-Support 2 Morphic-Worlds 2 FuelTests 2 NewClassOrganizer 1 Refactoring-Tests-Critics 1 CI-Core 1 Morphic 1 Ring-Tests-Kernel 1 Keymapping-Pragmas 1 UIManager 1 FileSystem-Disk 1
Re: [Pharo-project] I hate 'as yet unclassified'
In Pharo 20498, sorted by author in the method timestamp: gvc 1550 AlainPlantec320 216 GaryChambers215 CamilloBruni163 IgorStasenko159 stephaneducasse 152 avi 148 Igor.Stasenko 128 StephaneDucasse 85 SeanDeNigris81 MarcusDenker78 ab 75 GuillermoPolito 68 tween 52 BenjaminVanRyseghem 51 ar 46 di 40 RAA 38 alain.plantec 38 EstebanLorenzano35 FernandoOlivero 33 nice31 tk 29 nk 28 cwp 26 dvf 22 rr 20 PavelKrivanek 18 MarianoMartinezPeck 18 yo 18 sd 18 bf 16 SvenVanCaekenberghe 16 JMM 16 marcus.denker 14 wiz 12 ajh 12 mjr 12 cipt10 abc 10 md 10 HenrikSperreJohansen9 MikeRoberts 8 AndyKellens 6 LukasRenggli6 noha6 ClementBera 6 jrd 6 GastonDallOglio 6 2011-01-24T15:34:00+01:00 6 DeboraFortini 5 stephane.ducasse5 lr 5 2011-01-24T15:33:00+01:00 4 dgd 4 DamienCassou4 TestRunner 4 bkv 4 BG 4 Alexandre 4 AndrewBlack 4 sw 4 SimonAllier 3 DanielAvivEstebanAllende3 ASB 2 mas 2 pmm 2 simondenier 2 BernardoContreras 2 th 2 damienpollet2 NicoPaez2 CamilloBrui 2 sps 2 MiguelCoba 2 eem 2 NikoSchwarz 2 JavierPimas 2 GabrielOmarCotelli 2 mir 2 ul 2 2011-01-24T15:50:00+01:00 2 jf 2 c 2 ls 2 al 2 NorbertHartl2 djp 2 AdrianLienhard 2 TorstenBergmann 2 AlexandreBergel 2 tbn 2 DiogenesMoreira 2 GuyHylton 1 ThierryGoubier 1
[Pharo-project] FOSDEM diner & drinks?
Hi, Craig and I plan to arrive in Brussels-Midi 12:04 on saturday. We are up for diner & drinks saturday evening, and early diner on sunday. We'd like to travel back to the Netherlands at 19.00 or so. Any ideas? I liked the place Andy showed us last year, and it is perfect for sunday evening. Cheers, Stephan
Re: [Pharo-project] [ANN] Headless support for Cog Cocoa VM
Hi Mark, Should have read the man page for open instead of a web page. I had already tried the second version. Still crashes though, with the same error, on 10.6.8 (can try it on newer and older versions too, after finding a working version) Mariano: CogVM-sandard also has the illegal instruction Stephan
Re: [Pharo-project] [ANN] Headless support for Cog Cocoa VM
This doesn't work open CogVM-release-noflash-noArgs.app Pier3.image & Jan 19 11:20:51 Stephan-Eggermonts-iMac [0x0-0x2f92f9].org.seaside-project[36832]: This interpreter (vers. 6502) cannot read image file (vers. 6505). Jan 19 11:20:51 Stephan-Eggermonts-iMac [0x0-0x2f92f9].org.seaside-project[36832]: Press CR to quit... Jan 19 11:20:52 Stephan-Eggermonts-iMac ReportCrash[36836]: Failed to create CSSymbolicatorRef for launchd Jan 19 11:20:52 Stephan-Eggermonts-iMac com.apple.launchd.peruser.501[207] ([0x0-0x2fa2fa].org.squeakfoundation.Squeak[36835]): Job appears to have crashed: Segmentation fault Jan 19 11:20:52 Stephan-Eggermonts-iMac ReportCrash[36836]: Saved crash report for launchd[36835] version ??? (???) to /Users/stephan/Library/Logs/DiagnosticReports/launchd_2013-01-19-112052_Stephan-Eggermonts-iMac.crash
[Pharo-project] Fwd: Problem installing Neptuno
Frank Church wrote: >Is it okay for me to say that something isn't right here? Yes, you are right. Unfortunately, changing this takes time. The infrastructure to do automated builds is currently Jenkins based, and does not provide automated feedback upstream (the blame plugin is not suitable for a project with as many downstream projects as Pharo). The number of projects with automated builds is also still limited, and there are a lot of projects with insufficient maintenance. As a result many packages don't get updated regularly, only when users notice something is wrong. The good news is that it is already a lot better than a few years ago, and we see much better stability/possibilities to change in the packages that are build automatically. Unfortunately, Neptuno is not yet build like that. Ideally, every Pharo project would have its own automated build server that provides (test) feedback upstream. Stephan Eggermont
Re: [Pharo-project] FOSDEM 2013 Smalltalk devroom
Rafael wrote: >I've noticed that FOSDEM 2013 will host an Smalltalk devroom like the >previous year. Any idea about the scheduled sessions? > >I'd like to see tutorials related with Pharo, Seaside, Amber, Moose, etc. I'm working on finalizing the schedule now. We'll have presentation of the current state of Squeak & Pharo, experience report and getting started with Amber, the active filesystem, a workshop to get started with Smalltalk development, might have BabyMock/GOOS, Oak, Altitude & Etoilé,and some more time to talk than last year. I would welcome someone showing Moose. Need to finalize the schedule soon though. Cheers, Stephan Eggermont
Re: [Pharo-project] [Moose-dev] where was moose used for teaching/training?
Used in an industrial context for data conversion of a Cobol ERP system. Presented as workshop Visualizing Legacy Code & Data at Spa2012, XpDays Benelux 2012 and a Agile Holland meetup, with Willem van den Ende and Diego Lont Stephan Eggermont Sent from my iPad On 28 dec. 2012, at 00:29, Tudor Girba wrote: > Hi, > > I would be interested in putting together some figure about the impact of > Moose in academia and industry. > > If any of you have used Moose (or some of its subcomponents) for > teaching/training purposes, please send a quick note with the context in > which it happened. > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "It's not how it is, it is how we see it." > > > ___ > Moose-dev mailing list > moose-...@iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Re: [Pharo-project] is the date of 8th of February good for a sprint
Hi Stef, 2-3 Februari is FOSDEM, with a smalltalk devroom on sunday. (I would welcome ideas to present something there, btw) 1 or 4 would allow me to combine the trip. Cheers, Stephan Eggermont
Re: [Pharo-project] An excellent news
Stef wrote: > We mentioned it in the past but now this is really official. To support the > consortium, Inria is paying one full year > to Igor Stasenko. > > We want to thank Inria for its continuous support. Very good news. Thanks again for all your effort in realizing the Pharo Vision. Consortium membership is in the mail Stephan
[Pharo-project] Some Object methods that could be removed ?
A better way would be to get all source from all the repositories and extract all method sends and symbols, compare that to the list you'd want to remove and mark the packages you don't want to be able to load anymore. You'd still miss some, but at least get a much better idea of impact Stephan
[Pharo-project] Re; About new TxText text model
Hi Igor, The TxText model to me seems to mix two concerns. The storage of the text and manipulating it? Both cursor positioning and selection manipulation are view dependent, and there might be more than one. Stephan
Re: [Pharo-project] About new TxText text model
Hi, I've taken a look at the TxText text model, and it seems rather limited. I'm a bit confused about the expectations for this code: is this supposed to be just for editing smalltalk methods? The current Text system looks to me more like a limited implementation of the OpenStep/GNUStep/Cocoa text system. That separates concerns and allows high quality layouts. David Chisnall seems to know something about those systems http://www.informit.com/articles/article.aspx?p=1602820 Cheers, Stephan
Re: [Pharo-project] Breaking PDF into smaller PDFs
Aik-Siong Koh wrote: >Using Smalltalk, I would like to break a PDF with 500 pages into 500 PDFs of >one page each. > >How can I do that? I would assume Christian Haider's pdf library should be usable for that.I don't think that is ported from VW yet. Stephan
Re: [Pharo-project] Writing 16 times 1mb to a WriteStream takes 1s. Normal?
I've measured a few variations, with and without preallocation: (using new:streamContents:) your version: 207 ms 584 ms using a WordArray as destination: 1160 ms 2524 ms using a WordArray as both source and destination: 157 ms 522ms Stephan
[Pharo-project] Call for Participation in the Smalltalk Devroom at FOSDEM 2013
Call for Participation in the Smalltalk Devroom at FOSDEM 2013. http://www.fosdem.org " A devroom for the Pharo, Squeak, Amber, GST, Etoilé, Seaside, Moose Smalltalk projects & Newspeak as derived language. Smalltalk environments offer a very high development productivity, unmatched by their successors. Come do some pair programming with us and experience yourself the advantages of a real OO environment" The meetup will take place Sunday, February 3, 2013, from 9AM until 5PM, building AW. This room has 72 seats, a VGA video projector and wireless internet. More information will be available later. Proposals on content and format are welcome. People interested in running a session should announce that on the smalltalk-devroom mailing list, with the following information: - Their name - The project they are associated with - A short bio, to be put on the website along with their speaker name - (optionally) a picture of themselves - The title of their session (which will go on the website and in the booklet) - A abstract describing the session in further detail. - The desired length of the session. - The desired time slot in which they want to hold the session. Suggested values for the duration are 55min, 25min, 6m40 (Pecha Kucha). The desired time slot is meant to help you prevent conflicts with other dev rooms in which you might have a talk or your travel arrangements. There are alternative, non smalltalk-specific tracks available: lightning talk and the main track The deadline for submissions is December 31, 23:00 GMT+1. Discussion takes place on the smalltalk-devr...@lists.fosdem.org mailing list. Please subscribe if you are interested: https://lists.fosdem.org/listinfo/smalltalk-devroom The local VUB/ULB Smalltalkers have been asked to organize a sprint/BSUG meeting/Camp Smalltalk on Saturday February 2. Devroom related URLs: http://www.pharo-project.org http://www.squeak.org/ http://etoileos.com/ http://www.seaside.st/ http://smalltalk.gnu.org/ http://www.moosetechnology.org http://amber-lang.net http://newspeaklanguage.org/ http://www.esug.org
Re: [Pharo-project] File sharing on the network
Hilaire wrote: >Is there anyway to implement fileshareing with Dropbox or GoogleDrive on >a Pharo client application? I can see some use cases for a globally persistent peer-to-peer based system. Sort of a distributed github. Centralized systems tend to bring all kinds of nasty spam and privacy problems with them. Stephan
Re: [Pharo-project] Getting Started with Athens
Camillo wrote: >indeed just reproduced it. > >I guess I'll have to add a special OSX case. > >mv vm vm.app > >that should fix it when running from the UI. That fixes the start on drop-ability all right, but doesn't help with finding Cairo Stephan
Re: [Pharo-project] Getting Started with Athens
Camillo wrote:
>
>curl http://pharo.gforge.inria.fr/ci/ciPharo20NBCog.sh | bash
>
>./vm.sh Pharo.image config http://squeaksource.com/Athens
>ConfigurationOfAthens --install=1.4
>
It downloads and installs fine. But how do I need to start it to make it work
(10.7.5)?
The directory structure looks a bit of a mess. The vm directory contains some
34 files,
and dragging the image on NBCog doesn't work. Starting with vm/NBCog Pharo.image
starts the image, but trying to run an example:
Stephan
Error: failed to get a symbol address: cairo_image_surface_create
NativeBoostMac32(Object)>>error:
NativeBoostMac32(NativeBoostLinux32)>>getGlobalSymbolPointer:
NativeBoostMac32(NativeBoostLinux32)>>loadSymbol:fromModule:
NativeBoost class>>loadSymbol:fromModule:
Metaclass(Object)>>nbGetSymbolAddress:module:
NBFFICallout>>generateCall:module: in Block: [:gen | ...
BlockClosure>>valueWithPossibleArgs:
NBFFICallout>>generateInstructions: in Block: [aFunctionBodyBlock
valueWithPossibleArgs: {self. ...etc...
BlockClosure>>ensure:
AJx86Assembler>>decorateWith:during:
NBFFICallout>>generateInstructions: in Block: [:call | ...
AJx86Assembler>>performingCall:in:
NBFFICallout>>foreignCall:
NBFFICallout>>generateInstructions:
NBFFICallout>>generate:
NBFFICallout>>generateCall:module:
AthensCairoSurface class(Object)>>nbCall: in Block: [:gen | gen sender:
sender;...
NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry: in Block:
[bytes := aBlock...
BlockClosure>>on:do:
NBRecursionDetect class>>in:during:
NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry:
NBFFICallout class(NBNativeCodeGen class)>>handleFailureIn:nativeCode:
AthensCairoSurface class(Object)>>nbCall:
AthensCairoSurface class>>primImage:width:height:
AthensCairoSurface class>>extent:format:
AthensCairoSurface class>>extent:
AthensDemoMorph>>initialize
AthensDemoMorph class(Behavior)>>new
AthensDemoMorph class>>DoIt
Compiler>>evaluate:in:to:notifying:ifFail:logged:
[Pharo-project] Squeaksource memory
I was added as developer to PackageInfo 2 weeks ago, but am no longer able to commit... Stephan
[Pharo-project] How to export multiple Pharo packages to VW
The VW5PackageExporter allows the exporting of a package to the VW xml based fileout format. I've adapted the code to be less Seaside-specific, and am now able to export one package (Parasol-Core). If I try to export another package (Parasol-Tests), which depends on the earlier one, it fails to load. It can't resolve the dependency to a superclass defined in Parasol-Core. I've seen that Roassal puts all Pharo packages into one VW package. That would work, but is not very nice. A package in VW doesn't seem to register its dependencies in a fileout. Would creating a parcel help, or should I try something on basis of RPackage? Stephan
Re: [Pharo-project] Do you know any code that can be better understood with its test?
Stef wrote: >bitShift: > >look at the tests > > ((1 bitShift: 100) bitShift: -100) = 1 For even better understanding, add ((1 bitShift: -100) bitShift: 100) = 0 Stephan
Re: [Pharo-project] Interconnection of Morphic and Spec (was: [ANN] Phobos)
Igor wrote: >Anyways, UI stuff is tend to be complex no matter how nicely you wrap >it.. because it is UI. I'd have to disagree there. Building UIs with Glamour is easy. I'd say Spec is simply at too low an abstraction level for most UI work. We might need a different abstraction for different kind of applications (non-browsers, something like hotdraw comes to mind), but Glamour provides a very good base for most of the tools in the Pharo image. Stephan
[Pharo-project] Status of SmallPOS
I noticed the SmallPOS on ss3 is under MIT license. AFAIK, it was GPLv3. When did this relicensing happen? Stephan
Re: [Pharo-project] [Another sad day] a nice example of the mess with json in FileTree
Hannes wrote: > Some people however do not mind to do mappings from one data format to > another. That is right, and I prefer to keep my meditation separate from my programming. Stephan Eggermont
Re: [Pharo-project] No GUI on MacOSX 10.5.8 using Cocoa VM
http://stackoverflow.com/questions/1496788/building-for-10-5-in-xcode-3-2-on-snow-leopard-error
Re: [Pharo-project] Native UI bundle for Mac
Hi Pavel iMac 27 11.1, 10.6.8 works fine. Resizing the pharo window gives a screen with garbage and then mostly removes the pharo window. XUL stays up, but no longer switches views. Stephan
[Pharo-project] Default max heap size on OS-X
Hi I noticed the default SqueakMaxHeapSize on CI for Mac is 536870912 bytes. Is there a specific reason for the default to be so low? I know there used to be problems with the windows vm. Stephan
Re: [Pharo-project] nautilus speedup?
Camillo wrote: > I did a quick nautilus improvement: > > https://code.google.com/p/pharo/issues/detail?id=6667 > > CAVEAT: One thing I did was not showing all methods when opening the browser > on a class. > > For me this makes perfectly sense since I use the CMD-F + CMD-M shortcut > for searching for a method. Or go over all the protocol using the > arrow-keys on the selected protocol list. > > what do you think? It sounds like a perfect idea to get some traction for getting rid of method categories. Why would anyone want not to look at all methods in a class by default? In well refactored code, the number of methods is so limited that no scrolling should be needed. Not all code is like that, of course. Reading code is the most important activity of developing, and it is essential to limit the interaction needed to browse through code. Much better would be to show in the code pane which instance variables have accessors (r/w) and show all without accessors by default. > > However I can see that a "classical" user might be disturbed. This cut's down > the opening lag of a new browser from ~400ms to ~200ms on my machine, to me > thats quite worth it :). If the problem is performance, focus on performance. Why can not showing 30 items in a list make a difference of 200 ms? Stephan
Re: [Pharo-project] Sending email with Pharo
Hi Hilaire, There was a post from Scott Sproule on using Amazon SES with zinc and stunnel. Sven, you remember? From the response it was not clear to me if he managed to get everything working, and the need for stunnel might not be there with the current SSL support. SES is about 10% of the cost of postmaster. Attaching to mail is a well-known process. There are no problems there. Stephan
Re: [Pharo-project] New Text Completion suggestions
Camillo wrote: >So you're saying modifiable keyboard shortcuts are a bad design? Yes. That is to say, using them outside of developing a good set of key bindings (possibly for each language/keyboard). We need them to get to this consistent set. Options could be on the level of vi/wordstar/emacs style. Stephan
Re: [Pharo-project] New Text Completion suggestions
Doru wrote >I think an option would only add to the confusion. Please replace the >option with one decision. If some do not like it, they can shout and >the designer can take the input into account. But, it's the designer >that decides. +1 Stephan
[Pharo-project] Interest in another devroom at FOSDEM?
Hello, Feb. 2 & 3 2013 there will be FOSDEM again in Brussels. Last year I organized a devroom where all kind of smalltalk related developments were shown. If there is sufficient interest, I'll ask for one again. Please tell me if you'd like to come/present and what you'd like to see. Stephan Eggermont
Re: [Pharo-project] Memory usage
Guile wrote: >Yeap, but it I'd not call it an update :). It is more a complete refactor >to make it more understandable to newbies like me. >Anyway, I didn't migrate the code to write 64bit image, >and I'm not planning to do it in the short term... > If you want to take a look, the project is in ss3/ImageWriter The differences between SystemTracer2 and SystemTracer64 are rather limited. Should I expect that to be similar for ImageWriter? Stephan
Re: [Pharo-project] Memory usage
Dave wrote: >Please try the "64bitImage*64bitVM" image from John's site here: > ftp://ftp.smalltalkconsulting.com/experimental/64bit/ Loads and runs on my 10.7.3 MBA. >If you can run that VM on your Mac, it should do exactly what you need. >Try running that VM with one of your images. If it runs and gives you some >sort of error message about not understanding the image format, that's good! >That means all you need to do is trace your image to 64-bit object format, >which should be fairly easy to do. I loaded SystemTracing-dtl.23.mcz into a Pharo 1.4 one-click. SystemTracer2 writeImage: 'clone.image' results in a 88 byte clone image and hanging image, non-interuptable, caused by the popping up of a deprecation warning. Switching off the deprecation blocking leads to a debugger popup when trying to add the specialObjectArray. #'==' doesn't seem to work as a equalsBlock in Pharo. replaced by equalBlock: [:one :two | one == two]; The method SmalltalkImage extraVMMemory has been deprecated use Smalltalk vm extraVMMemory Then the tracing finishes. Trying to start the image results in 8/1/12 11:52:00.915 PM Squeak: openFile state 1 with file /Users/stephan/Documents/Sensus/sq64-dtl-32bitRGB/clone.image 8/1/12 11:52:01.098 PM Squeak: NSAlert is being used from a background thread, which is not safe. This is probably going to crash sometimes. Break on _NSAlertWarnUnsafeBackgroundThreadUsage to debug. This will be logged only once. This may break in the future. 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: Recursive not understood error encountered 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4423897840 SystemTracer2>writeImage: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4403075464 BlockClosure>ensure: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4407168048 SystemTracer2>writeImage: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4410156840 >writeImage: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4411453984 UndefinedObject>? 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4412035392 Compiler>evaluate:in:to:notifying:ifFail:logged: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4413449752 SmalltalkEditor>evaluateSelectionAndDo: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4414213432 BlockClosure>on:do: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4414486112 SmalltalkEditor>evaluateSelectionAndDo: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4414725120 SmalltalkEditor>evaluateSelection 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4414946416 SmalltalkEditor>doIt 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4415487880 SmalltalkEditor>doIt: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4415621456 TextEditor>performCmdActionsWith:shifted:return: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4416886344 TextEditor>dispatchCommandOn:return: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4416913992 TextEditor>dispatchOn: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4416972032 TextEditor>keystroke: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4416996176 TextEditor>handleKeystrokeAction: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417061696 TextEditor>handleEditionAction:fromKeyboardEvent: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417061880 TextEditor>keystroke: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417084280 TextMorph>basicKeyStroke: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417143280 TextMorph>handleInteraction: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417163504 TextMorphForEditView>handleInteraction: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417163720 TextMorph>basicKeyStroke: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417214616 TextMorph>keyStroke: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417234096 >codeCompletionAround:textMorph:keyStroke: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417279920 ToolRegistry>codeCompletionAround:textMorph:keyStroke: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417280104 TextMorph>keyStroke: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417299408 TextMorphForEditView>keyStroke: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417350856 TextMorph>handleKeystroke: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417369760 KeyboardEvent>sentTo: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417417472 Morph>handleEvent: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417435496 Morph>handleFocusEvent: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417476608 HandMorph>sendFocusEvent:to:clear: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].org.squeak.Squeak: 4417494152 PasteUpMorph>becomeActiveDuring: 8/1/12 11:52:04.044 PM [0x0-0x3c13c1].
[Pharo-project] Visualizing Legacy at SPA conference
Last week Willem and I presented a workshop Visualizing Legacy, using MOOSE, at SPA2012 in London. In a 150 minutes workshop we showed how to use glamour and mondrian to visualize the github repository data from 4 ruby projects and the code used for these analysis and the workshop itself. The exercises work toward the creation of a glamour browser with a mondrian pane showing custom visualizations not achievable by more static tools like Sonar. The answering of specific questions that arise during the analysis of the data show the strengths of the MOOSE toolchain. We started by showing some of the work Diego and I have done for the conversion of the data of a cobol ERP system to a modern ERP system. By creating (at least) one browser/visualization a day, we were able to make the subject matter expert, a very busy senior executive of the company, steer the conversion process to her satisfaction. By treating her as the bottleneck, and making it as easy as possible for her to see where we were, and what we still had to do/understand, she could effectively prioritize and decide. Then we asked the participants what they expected/wanted from visualizing their legacy code. The answers were a mix of things that tools like Sonar can easily provide, with very specific questions that need a programmable tool like MOOSE. As we expected, it took most of the about 14 participants quite a lot of effort and time to get to grips with the smalltalk environment to work in. So much so, that some asked for a separate smalltalk workshop to do before this one, or a larger timeslot for this workshop. The few participants experienced with Smalltalk had been using VW/VA and also had some problems finding their way around. In the end, the participants who managed to just follow the exercises achieved the goals without too much interventions needed. Inspired by ProfStef, we build a custom glamour browser for the workshop. The code can be found in the SpaTutorial project on ss3. (The ConfigurationOf… is no Metacello) http://ss3.gemstone.com/ss/SpaTutorial It is split in a generic part, allowing you to create tutorials, and a specific part for this workshop. We might want to extend it so the exercises can be done entirely in the custom browser. That might help the smalltalk newbies. Now the participants needed two class browsers in addition to the tutorial, one to edit the exercise code, and one to look at the domain model. We believe the learning curve can be flattened by extending the SpaTutorial browser so it can save code, and extracting some methods so the tutorial browser only shows the bits participants have to work on right now, gradually expanding the scope as it progresses. It uses the data collected for the SPA2011 great egg-race. http://chatley.com/posts/06-20-2011/spa-great-egg-race/ Git commit data was collected by Michael Feathers from four ruby projects, a.o. active_merchant and diaspora. After my holidays I'll put the data in a zip in https://github.com/StephanEggermont/repodepot-ruby For the 150 minute timeslot we focused on glamour and mondrian, although we also prepared an eyesee exercise. Next time we might switch the exercises around - mondrian looks more glamourous than glamour ;). A longer version may also be in the works if we can run it somewhere. It was only after the mondrian exercise that participants could start playing with the data on their own. Participants indicated they associatied mondrian more with visualization than glamour. Stephan Eggermont & Willem van den Ende
Re: [Pharo-project] Before-conference beer
Marcus wrote: >>On May 22, 2012, at 12:59 PM, Camillo Bruni wrote: >> otherwise a good meeting point is in front of the old trainstation Lille >> Flandres (about 200m / 1 metro stop from Lille Europe) > >Yes, in front of the main entrance of Lille Flanders is a good meeting spot. Ok. 20.00 I'll be at the front of the main entrance of Lille Flanders. Stephan
Re: [Pharo-project] Before-conference beer
I've checked my train ticket. I'll arrive at train station Lille-Europe at 19.52. I assume it has an info-point or so? Stephan
[Pharo-project] Before-conference beer?
I'm arriving wednesday evening about 21.00 hr. Anyone up for beer & talk? Stephan
Re: [Pharo-project] Place to sleep Lille
Hi Stef, Thanks. The Formule 1 still had a room (others didn't). What's the place to meet on wednesday evening for a beer & talk? I'll arrive 21.00 or so. Stephan
Re: [Pharo-project] Place to sleep Lille?
Damien wrote: >Try this one: > >Hotel ibis Lille Opéra >21 Rue Lepelletier, 59000 Lille, France >+33 3 20 06 21 95 Thank you. I already did. No space. Stephan
[Pharo-project] Place to sleep Lille?
Hi, Hmm. I'm a bit late to make a hotel reservation. Most hotels seem to be booked out. Anyone know an alternative? I'm arriving by train on wednesday. Couch would do. Stephan Eggermont
Re: [Pharo-project] dependency injection
Philippe wrote: > On 05/05/2012 10:04 AM, Milan Mimica wrote: >> What are you feelings about dependency injection? > > Oh oh, you brought up "the topic". We have about six different ways in > Seaside how we look up implementation classes. Anything from writing > them to a class variable to iterating over the subclasses and class > extensions. It would be really nice if we could replace them with one > approach. So that would be: afraid/angry, confused, despairing/hopeful? :)
Re: [Pharo-project] Artefact - a PDF framework
Why do we have so many ways to create pdfs, and why do most libraries/frameworks only provide a partial solution? At first it seems not to difficult to build something for what I need, so it makes sense to build it myself. But the pdf spec is large, and I don't use most of it. Building it myself makes more sense than trying to understand a current implementation. That is more complex than needed to solve the current problem, and building my own is a good way to understand the spec. Completing an implementation is hard to justify on project costs (as is mostly done for open source). More people seem to have followed the same road, so we end up with lots of partial solutions. Next time I need to create pdfs, I have different needs. Something with fonts, that seems like a lot of work. So I connect to a c library that already implements it. Only that has no way to create a document in-memory, just on disk… Artefact at the moment has very simple text layout and table algorithms. They are suitable for simple documents. High quality layout is complex as it needs to handle a.o. line breaking, justification, ligatures, kerning, hyphenation, text direction, text container shape, paragraph and page layout. PDF4Smalltalk is large because it is able to read and write pdfs, so it needs to have at least basic support for all pdf elements, and it contains lots of constants and mappings (glyph list, font metrics). Cairo (and Pango) by itself does not support reading pdfs. Stephan
Re: [Pharo-project] Artefact - a PDF framework
Hi Olivier, I've taken a look at the state of Artefact. Don't you think it would be much less work to port Christian Haider's work to Pharo? The namespace extensions to ring should be helpful to make two-way changes from both the VW and Pharo side. Stephan Eggermont
Re: [Pharo-project] How can I do literate programming?
You should probably use a MOOSE image if you want to do the modern equivalent of literate programming. Instead of comments, drive your code from (behavioural) tests, create glamour & mondrian browsers to visualize the design and quality attributes of the code and use magritte style descriptions to declaratively describe your domain. Then generate LaTeX & pictures from this for the paper trail. Stephan Eggermont
Re: [Pharo-project] [gsoc-mentors] One more project proposal for GSoC
On 2 apr 2012, at 19:41, Dennis Schetinin wrote: > The original idea is to build a two-tier Human-Machine Interface (HMI) system > (which can be used in a wide range of projects) with Pharo image as back-end > (where a model lives) and Amber-based client as a front-end. But this thing > seems to be "a little bit" too large for GSoC, isn't it? As long as he's able to define value-delivering small, concrete steps it is ok to have big goals. Stephan
Re: [Pharo-project] GSoC proposal: Naked Objects using Magritte
>Stephan, I can help as second Mentor if you still need one. >...Stan I haven't been able to reach Esteban yet. He is supposed to be moving this week. Thanks for the offer. Stephan
Re: [Pharo-project] International Workshop on Smalltalk Technologies 2011
Hello Alain, Are there links to the articles, instead of a paywall? Stephan
Re: [Pharo-project] Pharo Consortium Important Documents and Request for Feedback
A good document, Stef. The current focus of the documents is on developers. It might make sense to add something for the (corporate) users of Pharo-based software. Stephan
