September 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Slice-MCDependenciesDialogPlagueFixed-ab.1.mcz

by Henrik Sperre Johansen

On 09.09.2009 00:11, Andrew P. Black wrote: > Ideally, what I think we want is for all of the packages to be written > atomically. > However, that is something that MC does not currently know how to do. > > Next best would be to collect all of he log messages ahead of doing > any of the writing to the repository. > That would also require some major changes, but at least I can see how > to do it. Yes, that's what I imagined would be most intuitive, never looked at how much work it'd be though... > > Providing the checkbox is s mere matter of morphic programming ... > perhaps, if the box is not checked, and the user cancels one of the > ensuing dialogs, the > behaviour should be to reuse the log message from the Slice? > > Andrew I don't know about you, but when I press cancel, it's usually because I realize I've screwed something up, and want to abort :) Might also be abit confusing having different behaviour for the cancel button depending on whether you press it on the first Dialog compared to the rest. Cheers, Henry

Sept. 8, 2009

[Pharo-project] Error log - acculate call stacks

by Schwab,Wilhelm K

Hello all, At least a few of us have expressed a desire to not overwrite the contents of the error log. The attached seems to work. The usual caveats about not filing this into your only copy of a mission-critical image apply. Bill

Sept. 8, 2009

Re: [Pharo-project] CLFramework-UIBuilder

by nullPointer

>Ehm, my bad, I didn't mean "old" values, I meant the current values of >the morph. Anchors and Style were the only ones, I believe. ahhh now understand :) I believe is best in that case put the options as toolbar action, above. of that way the change of styles and anchors work with various morphs in a one time. > >> - The menu editor was very nice (a bit unintuituve that you had to >> ctrl-s after entering data before navigating away though, yet autosaving >> on icon selection. Also, only icon changes were accepted when you chose >> a new icon, the rest (label etc.) were lost) >> > IÂ´m not be good tester i believe. IÂ´m cannot reproduce the error. Note the > text value, or help text only is updated in the treeview when the intro > key > is pressed in the textbox. > In the first moment the value of textbox was changed for each key press, and updated in treeview.But in two last versions of Pharo after each keypress the cursor of textbox was put in the first character. I have search a solution for that.The Control-Save in Windows or intro Is possible change the order of tabsIndex in Polymorph? If exists a way perhaps i could incorporate too in the designer. Regards -- View this message in context: http://n2.nabble.com/CLFramework-UIBuilder-tp3594252p3606541.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 8, 2009

Re: [Pharo-project] Slice-MCDependenciesDialogPlagueFixed-ab.1.mcz

by Andrew P. Black

Ideally, what I think we want is for all of the packages to be written atomically. However, that is something that MC does not currently know how to do. Next best would be to collect all of he log messages ahead of doing any of the writing to the repository. That would also require some major changes, but at least I can see how to do it. Providing the checkbox is s mere matter of morphic programming ... perhaps, if the box is not checked, and the user cancels one of the ensuing dialogs, the behaviour should be to reuse the log message from the Slice? Andrew On 8 Sep 2009, at 11:39, Henrik Johansen wrote: > My point was, ideally, I'd like to be able to set individual comments > for each package if I want to(checkbox), and not have it break if I > cancel one of the later ones. > And that, if I had to choose between being able to set comment per > package but risking an incomplete save if I cancel one of them, and > having the same comment for all of them, I'd rather have the latter.

Sept. 8, 2009

Re: [Pharo-project] CLFramework-UIBuilder

by Henrik Sperre Johansen

On 08.09.2009 23:00, nullPointer wrote: > Thanks for probe and conseils :) > > >> It might be nice with a tab of its own for an editor of a morphs >> LayoutFrame, which could replace the current properties Anchors, >> Position and Extent >> > Im not sure of understand correct way (my english is poor). Want you say a > button around the selected morph for edit position, extent and anchors? I > think in something similar but working with an new halo. > No, an extra tab on the left, where you can edit the values of the Morphs LayoutFrame (top/left/right/bottom offset and fraction). It's a much more flexible way of defining a position that will behave nicely when you resize the widget than what can be done currently (albeit abit more complicated) Try: Morph allSubInstances collect: [:each | each layoutFrame ] thenSelect: [:each | each notNil] editing the instance variables of such an instance for the current morph is what I'd like :) > >> - The attributes are quite easy to edit (except not remembering old >> values for a few of them if I navigated away, then back again) >> > I could try that, but iÂ´m dont know do it with actual controls.A simple > change of text launch the valueChanged event of controls ( textboxes > properties ). When i can save for retrieve an old value? > Ehm, my bad, I didn't mean "old" values, I meant the current values of the morph. Anchors and Style were the only ones, I believe. > >> - The menu editor was very nice (a bit unintuituve that you had to >> ctrl-s after entering data before navigating away though, yet autosaving >> on icon selection. Also, only icon changes were accepted when you chose >> a new icon, the rest (label etc.) were lost) >> > IÂ´m not be good tester i believe. IÂ´m cannot reproduce the error. Note the > text value, or help text only is updated in the treeview when the intro key > is pressed in the textbox. > I make a new menu item, type in text, and select a new field. if I select the other item without ctrl-s (in Windows) while Text input field is focused, I loose the change. Also, the tabbing order is kind of backwards, going up instead of down (Name field -> press tab -> Focus goes to Help text instead of Action Selector) Cheers, Henry

Sept. 8, 2009

[Pharo-project] [ANN] one-click prototype...

by Marcus Denker

Hi, I did a very first one-click prototype. https://gforge.inria.fr/frs/download.php/23093/Pharo1.0-10440-BETAdev09.09O… This is the latest DEV, copied into the structure of the one-click of a long time ago. Than I added the files from these VM packages: Windows VM: SqueakVM-Win32-3.11.4-bin Mac VM: Squeak 4.2.1beta1U.app.zip Linux VM: pharo-vm-0.15.2d-linux.zip I edited the config for Mac to the point that it works. I am sure the rest does not work at all. So we can use this for iterating. Marcus -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Sept. 8, 2009

Re: [Pharo-project] bug report: 1197 can't quit

by Henrik Sperre Johansen

On 08.09.2009 22:38, Lawson English wrote: > http://code.google.com/p/pharo/issues/detail?id=1197 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > That's a Lumiere bug. Cheers, Henry

Sept. 8, 2009

Re: [Pharo-project] CLFramework-UIBuilder

by nullPointer

Exists some manual or tuto for explanation of use? I see a tuto of Cincom Smalltalk, but im not sure of understand it :| StÃ©phane Ducasse-2 wrote: > > > On Sep 7, 2009, at 2:37 PM, nullPointer wrote: > >> >> >> >>> What do you mean? >>> That you use Announcements? >> >> I use #triggerEvent: mechanism, but hided. I dont know of >> Announcements ; >> what is the difference? > > with announcement you get an object around and not just a symbol. > For the future use announcement since it is the new standard for > notification > in Smalltalk > >> >> Basically the control when want launch a event (for example the >> click) call >> the message #raiseOnClick:args: >> where the first parameter is the sender of event, and the second >> parameter >> is the click event.That is always works of that way in the widgets >> events. >> >> Regards >> -- >> View this message in context: >> http://n2.nabble.com/CLFramework-UIBuilder-tp3594252p3597137.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- View this message in context: http://n2.nabble.com/CLFramework-UIBuilder-tp3594252p3606145.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 8, 2009

Re: [Pharo-project] CLFramework-UIBuilder

by nullPointer

Thanks for probe and conseils :) >It might be nice with a tab of its own for an editor of a morphs >LayoutFrame, which could replace the current properties Anchors, >Position and Extent Im not sure of understand correct way (my english is poor). Want you say a button around the selected morph for edit position, extent and anchors? I think in something similar but working with an new halo. >- The attributes are quite easy to edit (except not remembering old >values for a few of them if I navigated away, then back again) I could try that, but iÂ´m dont know do it with actual controls.A simple change of text launch the valueChanged event of controls ( textboxes properties ). When i can save for retrieve an old value? >- The menu editor was very nice (a bit unintuituve that you had to >ctrl-s after entering data before navigating away though, yet autosaving >on icon selection. Also, only icon changes were accepted when you chose >a new icon, the rest (label etc.) were lost) IÂ´m not be good tester i believe. IÂ´m cannot reproduce the error. Note the text value, or help text only is updated in the treeview when the intro key is pressed in the textbox. >As for widgets, the only one I was really missing was a splitter. I believe i could add the next weekend :) Thanks to all for probes :)) -- View this message in context: http://n2.nabble.com/CLFramework-UIBuilder-tp3594252p3606132.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 8, 2009

[Pharo-project] bug report: 1197 can't quit

by Lawson English

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

Sept. 8, 2009