January 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] New in Graph-ET

by StÃ©phane Ducasse

Hi daniele Usman is on holidays and Iâm sure that he has some ideas. For me I do not really need animation. To me it is orthogonal I do not remember the feedback I gave you when I was visiting you now here is some: May be GraphET already does it if so ignore. - What would be good is to check that you can express as least what Eyesee was doing. boxplot, â¦.. different shade of color overlay. - Another point: it would be great to have a nice doc. We can pair write on a chapter together/with alex. - it would be nice to see how we can plug a service like Kontraktor to write compress text - Can we control the ticks spacing, height? - can you control how the label of the axis is placed? - rotated - how far from the top â¦. I think that all the little details are important. - how to support drill down. I see a chart how can I define interaction with its parts, Did you have a look at the PlotMorph (it is rudimentary but it is fun). On 02 Jan 2014, at 15:40, Daniel Aviv Notario <daniel_avivnotario(a)hotmail.com> wrote: > Hi guys! > > It's been a while since I posted in this list. > > The reason why I'm posting is because I finally finished my exams (yay!) and now I have some time to spare developing Graph-ET. I noticed a lot of you have been trying it, thank you for that :) I will try and answer all your questions regarding Graph-ET in the next few days. > > Meanwhile, today I did a little work on Scatterplots, you can go play with that, here's an example for you: > > | diag col | > > col := OrderedCollection new. > col add: (1@1). > col add: (1@2). > col add: (2@1). > col add: (2@2). > col add: (0.75(a)0.5) > col add: (0.6(a)1.5) > > diag := GETDiagramBuilder new. > (diag scatterplot) > models: col; > x: [ :mod | mod x ]; > y: [ :mod | mod y ]; > regularAxis. > > diag open > > It's really pretty basic, I think changing the size and shape of he object should be nice. > > In ESUG I was working in animations, but I dropped it, I'll try again soon, but not inmediatly. Other things I think I'll work is improving the axis values in the labels and various customizations and bug-fixing. > > Also, I would like to hear from you, what can I work on? I been recieving a lot of suggestions, and I'm glad. So if you have a request, doubt, complaint, comments or anything really you can contact me and I'll try and answer ASAP. > > Hope hearing from you! > Daniel

Jan. 4, 2014

Re: [Pharo-dev] Help us to have really cool Pharo 3 release!

by Norbert Hartl

Iâve started two weeks ago porting my first project to pharo3. Well, I donât know the real name for the action because it was not a real porting. It just loaded in pharo3 without any interaction by me. Ok, I think this is called âinstallationâ :) Very nice! Norbert Am 04.01.2014 um 11:17 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi guys, > > As you know, we are now in beta for Pharo 3. > That means we are just fixing bugs and improving stability (they are some attempts from some very impatient people to add yet new features, but so far we are managing them with the ability of a goal keeper :) ) > > What we need now is your help! How? > > 1) Is NOW the moment of porting your projects to Pharo 3. Yesâ¦ is not stable, but it improves everyday and if you help us catching bugs, it will in march, when the release should happen) > 2) Report BUGS. Yepâ¦ we still have many of them. Best way to report a bug is: to add a bug entry and to open a discussion in dev mailing list. Just one of both does not works fine because we are in the run, and: if you just open the bug, we can miss his importance, if you just start a thread, we are for sure owing to be covered of work and we will forget your important change. . > 3) If you feel in the mood, you can fix some of your annoying bugs by yourself. With the introduction of Komitter (thanks Ben!) you donât even need to work in a separate imageâ¦ it can be fixed in your working image and you can send a SLICE with just the changes you want. > 4) or you can just help us reviewing fixes (usually in status âFix Reviewed By The Monkeyâ, they need to be moved to âFix To Includeâ, and that in some cases (when is UI related, for instance) requires human intervention. > > Donât wait until tomorrow! > Pharo needs you TODAY! > > cheers, > Esteban

Jan. 4, 2014

Help us to have really cool Pharo 3 release!

by Esteban Lorenzano

Hi guys, As you know, we are now in beta for Pharo 3. That means we are just fixing bugs and improving stability (they are some attempts from some very impatient people to add yet new features, but so far we are managing them with the ability of a goal keeper :) ) What we need now is your help! How? 1) Is NOW the moment of porting your projects to Pharo 3. Yesâ¦ is not stable, but it improves everyday and if you help us catching bugs, it will in march, when the release should happen) 2) Report BUGS. Yepâ¦ we still have many of them. Best way to report a bug is: to add a bug entry and to open a discussion in dev mailing list. Just one of both does not works fine because we are in the run, and: if you just open the bug, we can miss his importance, if you just start a thread, we are for sure owing to be covered of work and we will forget your important change. . 3) If you feel in the mood, you can fix some of your annoying bugs by yourself. With the introduction of Komitter (thanks Ben!) you donât even need to work in a separate imageâ¦ it can be fixed in your working image and you can send a SLICE with just the changes you want. 4) or you can just help us reviewing fixes (usually in status âFix Reviewed By The Monkeyâ, they need to be moved to âFix To Includeâ, and that in some cases (when is UI related, for instance) requires human intervention. Donât wait until tomorrow! Pharo needs you TODAY! cheers, Esteban

Jan. 4, 2014

[pharo-project/pharo-core] 0a6476: 30670

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 0a6476aec185415cae70ae6936d103e224d9cfae https://github.com/pharo-project/pharo-core/commit/0a6476aec185415cae70ae69… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-04 (Sat, 04 Jan 2014) Changed paths: A FileSystem-Core.package/FileLocator.class/class/origins/temp.st A FileSystem-Core.package/MacOSResolver.class/instance/origins/temp.st A FileSystem-Core.package/PlatformResolver.class/instance/origins/temp.st M FileSystem-Core.package/PlatformResolver.class/instance/resolving/supportedOrigins.st R FileSystem-Core.package/UnixResolver.class/instance/as yet unclassified/supportedOrigins.st A FileSystem-Core.package/UnixResolver.class/instance/origins/temp.st A FileSystem-Core.package/UnixResolver.class/instance/resolving/supportedOrigins.st A FileSystem-Core.package/WindowsResolver.class/instance/origins/temp.st M Monticello.package/MCCacheRepository.class/class/defaults/defaultDirectory.st M MonticelloGUI.package/MCWorkingCopyBrowser.class/README.md R MonticelloGUI.package/MCWorkingCopyBrowser.class/class/as yet unclassified/showOnlyRepositoriesFromWorkingCopy.st R MonticelloGUI.package/MCWorkingCopyBrowser.class/class/as yet unclassified/showOnlyRepositoriesFromWorkingCopy_.st R MonticelloGUI.package/MCWorkingCopyBrowser.class/class/as yet unclassified/toggleShowOnlyRepositoriesFromWorkingCopy.st M MonticelloGUI.package/MCWorkingCopyBrowser.class/definition.st A MonticelloGUI.package/MCWorkingCopyBrowser.class/instance/actions/setShowOnlyRepositoriesFromWorkingCopy_.st M MonticelloGUI.package/MCWorkingCopyBrowser.class/instance/initialization/initialize.st M MonticelloGUI.package/MCWorkingCopyBrowser.class/instance/menu spec/widgetSpecs.st A MonticelloGUI.package/MCWorkingCopyBrowser.class/instance/morphic ui/currentShowOnlyRepositoriesFromWorkingCopy.st A MonticelloGUI.package/MCWorkingCopyBrowser.class/instance/morphic ui/getShowOnlyRepositoriesFromWorkingCopySettings.st M MonticelloGUI.package/MCWorkingCopyBrowser.class/instance/morphic ui/repositoryGroup.st M MonticelloGUI.package/MCWorkingCopyBrowser.class/instance/morphic ui/repositoryListMenu_.st R MonticelloGUI.package/MCWorkingCopyBrowser.class/instance/morphic ui/showOnlyRepositoriesFromWorkingCopy.st A MonticelloGUI.package/MCWorkingCopyBrowser.class/instance/morphic ui/showOnlyRepositoriesFromWorkingCopyField.st R MonticelloGUI.package/MCWorkingCopyBrowser.class/instance/morphic ui/showOnlyRepositoriesFromWorkingCopyString.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script323.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30670.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Settings-Monticello.package/MCSystemSettings.class/class/settings/showOnlyRepositoriesFromWorkingCopySettingOn_.st M Tools.package/FileList.class/instance/own services/basicDeleteDirectory.st M Tools.package/FileList.class/instance/volume list and pattern/volumeListIndex_.st Log Message: ----------- 30670 12520 Can not delete directory from File Browser https://pharo.fogbugz.com/f/cases/12520 10551 All Monticello Repositories are added to all Working Copies https://pharo.fogbugz.com/f/cases/10551 12467 Pharo crashes if Monticello can not create the package-cache directory https://pharo.fogbugz.com/f/cases/12467 http://files.pharo.org/image/30/30670.zip

Jan. 4, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30670 Home: https://github.com/pharo-project/pharo-core

Jan. 4, 2014

Re: [Pharo-dev] Soundplugin for Windows/Linux

by Esteban Lorenzano

is in my todo before releaseâ¦ but patience :) On 04 Jan 2014, at 00:12, Nicolai Hess <nicolaihess(a)web.de> wrote: > Can someone change PharoVM build configs > regarding issue 12493 > Sound does not work for Windows and Linux VMs because > > windows) PharoVMBuilder does not include soundplugin in the windows config > linux) vm-sound-alsa has unresolved externals -> can not be loaded > squeaks vm-sound-oss and vm-sound-pulse are working with pharo too > vm-sound-oss source is in pharos vm source, but not in pharovmbuilders > config, so it just isn't built. > > For me, it looks like it is solveable by just changing PharoVMBuilder configs. > > I built my own VMs for Windows (Windows 7 32Bit) and Linux (Ubuntu 10.04), > and it works. But I don't know if the exclusion of this plugins is on purpose > because they may make problems on other Win/Linux versions. > > Nicolai

Jan. 4, 2014

Re: [Pharo-dev] SIXX on "large" files

by Sven Van Caekenberghe

On 04 Jan 2014, at 00:38, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > I've discovered that its part of a JsonObject that holds the facebook profile associated with the user. > > SIXX is cool but I'm with the feeling that it's time to give fuel a chance Or STON ? https://github.com/svenvc/ston/blob/master/ston-paper.md > On Jan 3, 2014, at 8:01 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > >> On 3 January 2014 20:07, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: >>> It's probable unrelated to size as expected. >>> >>> For the record: >>> >>> I've changed the XMLParser and the new one complained about a problem on a >>> specific line that has this content >>> >>> <sixx.object sixx.id="1106" sixx.name="key" sixx.type="String" >>>> name</sixx.object> >>> <sixx.object sixx.id="1107" sixx.name="value" sixx.type="String" >>>> Like >>> Mark >>> Twain: >>>  >>> I've >>> never >>> let >>> my >>> school >>> interfere >>> with >>> my >>> education. >>> </sixx.object> >>> </sixx.object> >>> >>> looks like an encoding problem >> >> Was that originally a UTF-32 string or something? Three NULs followed >> by a character... (For the curious, it says 'Like Mark Twain: "I've >> never let my school interfere with my education. "') >> >> frank >> > >

Jan. 4, 2014

Re: [Pharo-dev] [Glass] printString and asString

by Yuriy Tymchuk

On 03 Jan 2014, at 21:55, Martin McClure <martin(a)hand2mouse.com> wrote: > On 01/03/2014 12:33 AM, Otto Behrens wrote: >> Hi, >> >> I've run into one of my favorite problems in Smalltalk and decided to >> try the list. Please don't shoot me on this one; perhaps you've run >> into it yourself. If there are discussions that I should read, please >> send me some info. > > Hi Otto, > > Well, you asked for comments. This is my personal opinion, which varies > quite a bit from most implementations, since it's a bit 'old-school > Smalltalk'. But I think the scheme below does fairly neatly distinguish > the purposes of the various messages, which have gotten muddied over the > years as new developers use the language somewhat differently. But maybe > it was never the way I think I remember it being. :-) > > > #printString and #printOn: > These should answer a human-readable description of the receiver. The > description does not need to include the class name, though it can. All > objects should respond to these messages. Generally, #printString should > be implemented in terms of #printOn: -- if you're writing to a stream > you may not want to pay the cost of creating an extra string. > #printString is the equivalent of other languages' toString(). > > #asString > There should not be an Object>>asString. This message is *only* for > converting string-like things to actual strings. So it would be > implemented in String (to return self) and in Symbol, and *maybe* in > things like ByteArray (where it does not *describe* the byte array, but > answers a string whose characters have the values of the bytes). And number, no? For me as* methods are for conversion between types. E.i. if you have string and want it as Integer you use asInteger. Uko > > #storeString > Produces legal Smalltalk source code that when executed will produce an > equivalent object to the receiver. Needs to be implemented only for > objects that can be specified as literals in Smalltalk syntax, but could > probably be implemented for a few other simple objects. > > #displayString and so on. > UI frameworks and applications will need to have their own ways of > textually representing objects, so will add their own messages such as > #displayString. The *only* messages that any application or framework > can depend on *all* objects responding to are those that it defines > itself, and #printString and #printOn:. > > Regards, > > -Martin >

Jan. 4, 2014

Re: [Pharo-dev] DateModel label width

by Sean P. DeNigris

Benjamin Van Ryseghem-2 wrote > I think we can do better :P (with still a workaround) I was being a bit dramatic ;) I ended up with a slightly less depressing: open | windowModel labelMorphs | windowModel := self new openWithSpec. labelMorphs := windowModel window allMorphs select: [ :e | e isKindOf: LabelMorph ]. labelMorphs do: [ :e | self workAroundLabelAlignmentOf: e ]. workAroundLabelAlignmentOf: aLabelMorph | isSpecLabel | isSpecLabel := aLabelMorph model isKindOf: LabelModel. isSpecLabel ifFalse: [ ^ self ]. aLabelMorph owner hResizing: #spaceFill; changeTableLayout; listDirection: #rightToLeft. aLabelMorph hResizing: #shrinkWrap; width: 155. No rush on this. I'm good for now. ----- Cheers, Sean -- View this message in context: http://forum.world.st/DateModel-label-width-tp4733674p4734026.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 4, 2014

Re: [Pharo-dev] Spotlight Demo

by Sean P. DeNigris

I love the item count - thanks. I saw the double jump too, but the cause wasn't obvious. And I see what you mean about the arrows; I'll look into it. I'm really enjoying the collaboration :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spotlight-Demo-tp4733076p4734023.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 4, 2014