Re: [Pharo-project] a plea for save and quit
Why not Lukas' proposal? Other mails argued that we should not add save and quit because it increases the menu size. But with Lukas' suggestion the number of menu items stay the same, hence this argument does not hold. Mike argued he needs save as new version at least once a day. This is not lost as Save as does the trick. Adrian On Jun 11, 2009, at 02:28 , Nicolas Cellier wrote: How to customize the menus? Customization == Preference, OK these are synonyms. Among the propositions so far: 1) override a method 2) some specific hard-wired Preferences 3) automatic some drawbacks: 1) require maintenance at each update 2) why a Preference for an item and not another ? 3) changing menus are painful (MS lacks some inertia for sure...) So far, I agree on 4) keep a simple static menu ...unless customization be accessible right from the menu (halos?) rather than from an obscure path. And easily undo-able (for example, items could be there but just undisplayed...) Nicolas 2009/6/11 Mariano Martinez Peck marianop...@gmail.com: what about having a preference to enable/disable save and quite from menu? On Wed, Jun 10, 2009 at 6:30 PM, Brian Brown br...@ablelinktech.com wrote: On Jun 10, 2009, at 2:56 PM, Michael Rueger wrote: Nicolas Cellier wrote: What about auto-adaptative menus learning your habits. X most used items on top. Y often used items following. Every other less used items in submenus. you mean the most horrible idea MS ever had, changing menus? -10^age of the universe ;-) Hah! I agree wholeheartedly. Changing menus are not fun. I use Save and Quit all the time... this is starting to smell like a preference. If you want super short menus, then turn it off, if you want the convenience, then have it on... what say? - Brian Michael ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] a plea for save and quit
No preference. Preferences are for the weak :) We want to have design decision no absence of decision by preference plague. So guys come up with a good solution and we will use it but no preference. So I could not understand the proposals except this one: -'Save' -'Save ...' - 'Save as', 'Save as new version', 'Save and Quit' -'Quit' So could you use this pattern to explain what you think/want? Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] a plea for save and quit
which could also be from what I understand -'Save and Quit' -'Save ...' - 'Save', 'Save as ', 'Save as new version' -'Quit' On Jun 11, 2009, at 9:25 AM, Stéphane Ducasse wrote: No preference. Preferences are for the weak :) We want to have design decision no absence of decision by preference plague. So guys come up with a good solution and we will use it but no preference. So I could not understand the proposals except this one: -'Save' -'Save ...' - 'Save as', 'Save as new version', 'Save and Quit' -'Quit' So could you use this pattern to explain what you think/want? Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] a plea for save and quit
OK, here again the proposal of Lukas that I think is the best so far. - Save Save as... Save and quit Quit - The behavior of Save as... would be modified to automatically pick the next version number (but still lets you edit the file name). Like this, Save as next version is not needed anymore. Adrian On Jun 11, 2009, at 09:25 , Stéphane Ducasse wrote: No preference. Preferences are for the weak :) We want to have design decision no absence of decision by preference plague. So guys come up with a good solution and we will use it but no preference. So I could not understand the proposals except this one: -'Save' -'Save ...' - 'Save as', 'Save as new version', 'Save and Quit' -'Quit' So could you use this pattern to explain what you think/want? Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] a plea for save and quit
Hi, I like very much the idea of Save as to provide the new version name by default. But, I have there is a usability problem with Save and quit being spatially close to Quit. The difference between is quite large, and you want to use them for very different scenarios: - I want to use Quit and not save when I perform experiment changes on objects that I do not want to keep with me (for example when I have some expensive computation and then want to play with some variation at the end). - You would want to use Save and quit typically when you work on code and want to keep it The problem is that because they are close, it will be easy to click on the other one by mistake (it happens all the time with long menu and small fonts). So, if you really want to reintroduce Save and quit it should at least not be close to Quit. A minimal defense would be a separator between Save and quit and Quit: Save Save as... Save and quit - Quit But, here is another idea. In VisualWorks we introduced a small add-on that prompts you to save the image after publishing in the repository, and when closing the image. Like this we instill the good practice of publishing and saving the code so that even if the image crashes, you are in sync with the repository. So, as a result you can always quit without saving. Would it not be better to prompt for saving the image after you save something in a Monticello repository? Cheers, Doru On 11 Jun 2009, at 09:46, Adrian Lienhard wrote: OK, here again the proposal of Lukas that I think is the best so far. - Save Save as... Save and quit Quit - The behavior of Save as... would be modified to automatically pick the next version number (but still lets you edit the file name). Like this, Save as next version is not needed anymore. Adrian On Jun 11, 2009, at 09:25 , Stéphane Ducasse wrote: No preference. Preferences are for the weak :) We want to have design decision no absence of decision by preference plague. So guys come up with a good solution and we will use it but no preference. So I could not understand the proposals except this one: -'Save' -'Save ...' - 'Save as', 'Save as new version', 'Save and Quit' -'Quit' So could you use this pattern to explain what you think/want? Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com The coherence of a trip is given by the clearness of the goal. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Fwd: First try of Pharo
tx torsten could you come up with a little text that we could put on the pharo-project web site to explain to people how to get the news without been flooded by emails :)? Stef BTW: If you are afraid of the traffic on the mailinglist just subscribe but set option to not get emails. Then you can browse the archive to read but still post questions. See [3] [1] http://pharo-project.org/download [2] https://gforge.inria.fr/frs/download.php/22410/setup_pharo_0.0.0.3.exe [3] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-June/009617.html -- GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate und Telefonanschluss für nur 17,95 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02 ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] space analysis
SpaceTally new printSpaceAnalysis: 1 on: 'space.txt'. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] #IdentityIncludes: for FloatArray
try to inspect: (FloatArray new:1)at: 1 put: 2.5 ; yourself and print: self identityIncludes: self anyOne It returns false. Is it a 'normal' comportment ? ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] #IdentityIncludes: for FloatArray
FloatArray is a raw array of bits interpreted as single precision (32 bits) floats. It does not contain any object pointer, only the content (value). At each access #at: will create a new Float (64 bits). So you have (self at: 1) ~~ (self at: 1). Does that explain? Nicolas 2009/6/11 Cyrille Delaunay cyrille.delau...@etudiant.univ-lille1.fr: try to inspect: (FloatArray new:1)at: 1 put: 2.5 ; yourself and print: self identityIncludes: self anyOne It returns false. Is it a 'normal' comportment ? ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] a plea for save and quit
whilst we are debating 'quit' can we move 'Quit do not save' so it is not the first item in the native OS X File menu. I have accidentally clicked it a few times and it is a disaster. It is also quite different from platform semantics where are you would normally be prompted if a quit would discard changes. It should be at the bottom of the menu at the very least. Dare I ask if we need it at all... thanks Mike ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] a plea for save and quit
you mean quit should be always asking to save? On Jun 11, 2009, at 12:21 PM, Michael Roberts wrote: whilst we are debating 'quit' can we move 'Quit do not save' so it is not the first item in the native OS X File menu. I have accidentally clicked it a few times and it is a disaster. It is also quite different from platform semantics where are you would normally be prompted if a quit would discard changes. It should be at the bottom of the menu at the very least. Dare I ask if we need it at all... thanks Mike ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] a plea for save and quit
No. Sometimes we want: - Save and Quit and sometimes we want - Quit without saving but they should not be located where we can too easily click the wrong thing. They should not be next to each other, and they should not be in the default location of a File Menu. I know, I have done this too, more than once. - on On Jun 11, 2009, at 13:11, Stéphane Ducasse wrote: you mean quit should be always asking to save? On Jun 11, 2009, at 12:21 PM, Michael Roberts wrote: whilst we are debating 'quit' can we move 'Quit do not save' so it is not the first item in the native OS X File menu. I have accidentally clicked it a few times and it is a disaster. It is also quite different from platform semantics where are you would normally be prompted if a quit would discard changes. It should be at the bottom of the menu at the very least. Dare I ask if we need it at all... thanks Mike ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] a plea for save and quit
I agree with Oscar. one of the challenges is how does the image know it has any active changes? it's not as easy as editing a document say. This could be an interesting technical challenge. Ideally you would ask for 'quit' and if there are no changes, it would not save. if there were it would prompt you to save them. However, in absence of such sophistication in our object world I would at least lay the menu out a little more safely. thanks Mike On Thu, Jun 11, 2009 at 12:22 PM, Oscar Nierstraszos...@iam.unibe.ch wrote: No. Sometimes we want: - Save and Quit and sometimes we want - Quit without saving but they should not be located where we can too easily click the wrong thing. They should not be next to each other, and they should not be in the default location of a File Menu. I know, I have done this too, more than once. - on On Jun 11, 2009, at 13:11, Stéphane Ducasse wrote: you mean quit should be always asking to save? On Jun 11, 2009, at 12:21 PM, Michael Roberts wrote: whilst we are debating 'quit' can we move 'Quit do not save' so it is not the first item in the native OS X File menu. I have accidentally clicked it a few times and it is a disaster. It is also quite different from platform semantics where are you would normally be prompted if a quit would discard changes. It should be at the bottom of the menu at the very least. Dare I ask if we need it at all... thanks Mike ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] a plea for save and quit
Tudor Girba a écrit : Save Save as... Save and quit - Quit Hi all, I like this simple proposition. We still have 'recover lost changes' in the case of unwanted quit without saving. alain ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] a plea for save and quit
Hm. Isn't it as simple as this? Author initialsPerSe isEmpty Or is that too naive? ;-) - on On Jun 11, 2009, at 14:12, Michael Roberts wrote: one of the challenges is how does the image know it has any active changes? it's not as easy as editing a document say. This could be an interesting technical challenge. Ideally you would ask for 'quit' and if there are no changes, it would not save. if there were it would prompt you to save them. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] multiple native windows
Besides programming effort, is there a reason why squeak/pharo shouldn't consider going to a GUI model that includes real multiple native windows? I'm not a c/c++ programmer and wouldn't know where to begin with that piece, but inside of smalltalk it seems it wouldn't be all that difficult of a refactoring. I only bring this up as this would put pharo/squeak more in line with many other conventional languages (with respect to user interfaces), and get it back in the game so to speak for when technologies are being considered for business solutions. You could include in this 1) Native support for drag and drop and 2) support for embedded native controls. Something like SWT and Jide now both support. Sorry if I've overlooked something with this and the con is obvious. thanks sw ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
Besides programming effort, is there a reason why squeak/pharo shouldn't consider going to a GUI model that includes real multiple native windows? I would love to have that we should have a look at ffenestria and fix it. So this is just that somebody should do it. I'm not a c/c++ programmer and wouldn't know where to begin with that piece, but inside of smalltalk it seems it wouldn't be all that difficult of a refactoring. I only bring this up as this would put pharo/squeak more in line with many other conventional languages (with respect to user interfaces), and get it back in the game so to speak for when technologies are being considered for business solutions. You could include in this 1) Native support for drag and drop and 2) support for embedded native controls. Something like SWT and Jide now both support. Sorry if I've overlooked something with this and the con is obvious. thanks sw Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
Steve Wirts wrote: Besides programming effort, is there a reason why squeak/pharo shouldn't consider going to a GUI model that includes real multiple native windows? Yes, Morphic ;-) Would be pretty hard to make it work with multiple windows. At least that's the consensus... The infrastructure is basically in place and has been used for prototypes. Also the GTK bindings and Newspeak use native windows (I think?). Michael ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
On Thu, Jun 11, 2009 at 4:38 PM, Michael Ruegerm.rue...@acm.org wrote: Also the GTK bindings and Newspeak use native windows (I think?). Newspeak uses either native or morphic windows, depending on the wishes of the user. -- Damien Cassou http://damiencassou.seasidehosting.st Lambdas are relegated to relative obscurity until Java makes them popular by not having them. James Iry ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] a plea for save and quit
You can remove that from the menu using the os-x mac menu api that is used to modify the menu at startup time, so at startup time an additonal step is needed. It's left there because some people wanted a way to quit the image without any squeak image involvement, it could of course be made a preference. As for the quit and prompt there is a change notification that is broadcast when a method is changed I think it's register SystemChangeNotifier uniqueInstance notify: self ofSystemChangesOfItem: #method change: #Added using: #modified:; notify: self ofSystemChangesOfItem: #method change: #Modified using: #modified:; notify: self ofSystemChangesOfItem: #method change: #Removed using: #modified: But ensuring you have all the cases would be debatable. On 11-Jun-09, at 3:21 AM, Michael Roberts wrote: whilst we are debating 'quit' can we move 'Quit do not save' so it is not the first item in the native OS X File menu. I have accidentally clicked it a few times and it is a disaster. It is also quite different from platform semantics where are you would normally be prompted if a quit would discard changes. It should be at the bottom of the menu at the very least. Dare I ask if we need it at all... thanks Mike -- = = = John M. McIntosh john...@smalltalkconsulting.com Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
Perhaps you can join forces with the rest of the present alternatives. For example, *squeakgtk* I think there is a lot of people that wants native windows so that being able to create desktop applications. Cheers, Mariano 2009/6/11 Steve Wirts stevewi...@gmail.com If the primitives existed in pharo that would allow someone to create and control native windows, I would be more than happy to take the time to try and massage morphic into working cleanly/elegantly with multiple windows. On Thu, Jun 11, 2009 at 10:44 AM, Damien Cassou damien.cas...@gmail.comwrote: On Thu, Jun 11, 2009 at 4:38 PM, Michael Ruegerm.rue...@acm.org wrote: Also the GTK bindings and Newspeak use native windows (I think?). Newspeak uses either native or morphic windows, depending on the wishes of the user. -- Damien Cassou http://damiencassou.seasidehosting.st Lambdas are relegated to relative obscurity until Java makes them popular by not having them. James Iry ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
I used Visualworks and Squeak, and frankly, I prefer to have embedded morphic windows in a unique native window, as it is now in Pharo. Application switching is easier in my opinion and I do not feel a need to have an email clients between two code browsers. As the discussion on save and quit testified, people have radically different habits when programming. Even for simple things. Interesting. Cheers, Alexandre On 11 Jun 2009, at 10:58, Steve Wirts wrote: If the primitives existed in pharo that would allow someone to create and control native windows, I would be more than happy to take the time to try and massage morphic into working cleanly/ elegantly with multiple windows. On Thu, Jun 11, 2009 at 10:44 AM, Damien Cassou damien.cas...@gmail.com wrote: On Thu, Jun 11, 2009 at 4:38 PM, Michael Ruegerm.rue...@acm.org wrote: Also the GTK bindings and Newspeak use native windows (I think?). Newspeak uses either native or morphic windows, depending on the wishes of the user. -- Damien Cassou http://damiencassou.seasidehosting.st Lambdas are relegated to relative obscurity until Java makes them popular by not having them. James Iry ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
Alexandre Bergel wrote: I used Visualworks and Squeak, and frankly, I prefer to have embedded morphic windows in a unique native window, as it is now in Pharo. Application switching is easier in my opinion and I do not feel a need to have an email clients between two code browsers. As the discussion on save and quit testified, people have radically different habits when programming. Even for simple things. Interesting. Indeed. Alos worth noting that the Adobe suite of products basically uses the Squeak mode. But, there is still a case for native windows and if only for dialog boxes ;-) Usage across multiple screens is another argument for having the technical ability for multiple windows. Michael ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
Thanks Mariano, I wasn't aware of squeakgtk. It looks like this project (a large project) is trying to create a toolkit of heavyweight controls for squeakers. Something similar to wxSqueak. I'm thinking of something different; all the widget implementation should be left to pharo, morphic is great, and there already exists lots of gui code. I believe the only thing we would need would be the ability create and control a native window(decorated and undecorated), not every kind of native widget. 2009/6/11 Mariano Martinez Peck marianop...@gmail.com Perhaps you can join forces with the rest of the present alternatives. For example, *squeakgtk* I think there is a lot of people that wants native windows so that being able to create desktop applications. Cheers, Mariano 2009/6/11 Steve Wirts stevewi...@gmail.com If the primitives existed in pharo that would allow someone to create and control native windows, I would be more than happy to take the time to try and massage morphic into working cleanly/elegantly with multiple windows. On Thu, Jun 11, 2009 at 10:44 AM, Damien Cassou damien.cas...@gmail.comwrote: On Thu, Jun 11, 2009 at 4:38 PM, Michael Ruegerm.rue...@acm.org wrote: Also the GTK bindings and Newspeak use native windows (I think?). Newspeak uses either native or morphic windows, depending on the wishes of the user. -- Damien Cassou http://damiencassou.seasidehosting.st Lambdas are relegated to relative obscurity until Java makes them popular by not having them. James Iry ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] [update] #10334
#10334 == Issue 877: CollectionisZero use deprecatedDescrition: instead of deprecated Issue 686: Remove dice methods in Random Issue 631: API Consistency on MIMEDocument -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
Would it be ok if this was configurable via a user preference, meaning pharo supported both? A VisualWorks multiple-native-window capability would open up the possibility of creating a different class of applications. Alot of my work revolves around integration with legacy systems. Having a smalltalk with multiple native windows would allow me to more seamlessly introduce it into the world of tools at my company. thanks sw On Thu, Jun 11, 2009 at 11:33 AM, Alexandre Bergel alexan...@bergel.euwrote: I used Visualworks and Squeak, and frankly, I prefer to have embedded morphic windows in a unique native window, as it is now in Pharo. Application switching is easier in my opinion and I do not feel a need to have an email clients between two code browsers. As the discussion on save and quit testified, people have radically different habits when programming. Even for simple things. Interesting. Cheers, Alexandre On 11 Jun 2009, at 10:58, Steve Wirts wrote: If the primitives existed in pharo that would allow someone to create and control native windows, I would be more than happy to take the time to try and massage morphic into working cleanly/ elegantly with multiple windows. On Thu, Jun 11, 2009 at 10:44 AM, Damien Cassou damien.cas...@gmail.com wrote: On Thu, Jun 11, 2009 at 4:38 PM, Michael Ruegerm.rue...@acm.org wrote: Also the GTK bindings and Newspeak use native windows (I think?). Newspeak uses either native or morphic windows, depending on the wishes of the user. -- Damien Cassou http://damiencassou.seasidehosting.st Lambdas are relegated to relative obscurity until Java makes them popular by not having them. James Iry ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
In Newspeak, a dedicated icon enable to switch mode. Quite convenient. Cheers, Alexandre On 11 Jun 2009, at 12:02, Steve Wirts wrote: Would it be ok if this was configurable via a user preference, meaning pharo supported both? A VisualWorks multiple-native-window capability would open up the possibility of creating a different class of applications. Alot of my work revolves around integration with legacy systems. Having a smalltalk with multiple native windows would allow me to more seamlessly introduce it into the world of tools at my company. thanks sw On Thu, Jun 11, 2009 at 11:33 AM, Alexandre Bergel alexan...@bergel.eu wrote: I used Visualworks and Squeak, and frankly, I prefer to have embedded morphic windows in a unique native window, as it is now in Pharo. Application switching is easier in my opinion and I do not feel a need to have an email clients between two code browsers. As the discussion on save and quit testified, people have radically different habits when programming. Even for simple things. Interesting. Cheers, Alexandre On 11 Jun 2009, at 10:58, Steve Wirts wrote: If the primitives existed in pharo that would allow someone to create and control native windows, I would be more than happy to take the time to try and massage morphic into working cleanly/ elegantly with multiple windows. On Thu, Jun 11, 2009 at 10:44 AM, Damien Cassou damien.cas...@gmail.com wrote: On Thu, Jun 11, 2009 at 4:38 PM, Michael Ruegerm.rue...@acm.org wrote: Also the GTK bindings and Newspeak use native windows (I think?). Newspeak uses either native or morphic windows, depending on the wishes of the user. -- Damien Cassou http://damiencassou.seasidehosting.st Lambdas are relegated to relative obscurity until Java makes them popular by not having them. James Iry ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] a plea for save and quit
OK, here again the proposal of Lukas that I think is the best so far. - Save Save as... Save and quit Quit - The behavior of Save as... would be modified to automatically pick the next version number (but still lets you edit the file name). Like this, Save as next version is not needed anymore. Adrian +1 I use save and quit more than any of the others, it was just the wrong one to remove. -- Ramon Leon http://onsmalltalk.com ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
Would it be ok if this was configurable via a user preference, meaning pharo supported both? sure. A VisualWorks multiple-native-window capability would open up the possibility of creating a different class of applications. Alot of my work revolves around integration with legacy systems. Having a smalltalk with multiple native windows would allow me to more seamlessly introduce it into the world of tools at my company. I really think that if somebody would work on ffenestria we would integrate it. thanks sw On Thu, Jun 11, 2009 at 11:33 AM, Alexandre Bergel alexan...@bergel.eu wrote: I used Visualworks and Squeak, and frankly, I prefer to have embedded morphic windows in a unique native window, as it is now in Pharo. Application switching is easier in my opinion and I do not feel a need to have an email clients between two code browsers. As the discussion on save and quit testified, people have radically different habits when programming. Even for simple things. Interesting. Cheers, Alexandre On 11 Jun 2009, at 10:58, Steve Wirts wrote: If the primitives existed in pharo that would allow someone to create and control native windows, I would be more than happy to take the time to try and massage morphic into working cleanly/ elegantly with multiple windows. On Thu, Jun 11, 2009 at 10:44 AM, Damien Cassou damien.cas...@gmail.com wrote: On Thu, Jun 11, 2009 at 4:38 PM, Michael Ruegerm.rue...@acm.org wrote: Also the GTK bindings and Newspeak use native windows (I think?). Newspeak uses either native or morphic windows, depending on the wishes of the user. -- Damien Cassou http://damiencassou.seasidehosting.st Lambdas are relegated to relative obscurity until Java makes them popular by not having them. James Iry ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
what is ffenestria? links? On Thu, Jun 11, 2009 at 3:45 PM, Stéphane Ducasse stephane.duca...@inria.fr wrote: Would it be ok if this was configurable via a user preference, meaning pharo supported both? sure. A VisualWorks multiple-native-window capability would open up the possibility of creating a different class of applications. Alot of my work revolves around integration with legacy systems. Having a smalltalk with multiple native windows would allow me to more seamlessly introduce it into the world of tools at my company. I really think that if somebody would work on ffenestria we would integrate it. thanks sw On Thu, Jun 11, 2009 at 11:33 AM, Alexandre Bergel alexan...@bergel.eu wrote: I used Visualworks and Squeak, and frankly, I prefer to have embedded morphic windows in a unique native window, as it is now in Pharo. Application switching is easier in my opinion and I do not feel a need to have an email clients between two code browsers. As the discussion on save and quit testified, people have radically different habits when programming. Even for simple things. Interesting. Cheers, Alexandre On 11 Jun 2009, at 10:58, Steve Wirts wrote: If the primitives existed in pharo that would allow someone to create and control native windows, I would be more than happy to take the time to try and massage morphic into working cleanly/ elegantly with multiple windows. On Thu, Jun 11, 2009 at 10:44 AM, Damien Cassou damien.cas...@gmail.com wrote: On Thu, Jun 11, 2009 at 4:38 PM, Michael Ruegerm.rue...@acm.org wrote: Also the GTK bindings and Newspeak use native windows (I think?). Newspeak uses either native or morphic windows, depending on the wishes of the user. -- Damien Cassou http://damiencassou.seasidehosting.st Lambdas are relegated to relative obscurity until Java makes them popular by not having them. James Iry ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
I thought it was someone's name at first :) http://wiki.squeak.org/squeak/3862 This looks right to me, thanks for the heads up stef. I don't see where there is any code available however. A concrete starting point might be with vm primitives for creating and controlling native windows; once these are in place, it is a matter of creating a small pharo codebase to manage the OS resources(ffenestria), and drawing to them through primitives via the GraphicsContext (bitblitting of course). I would think that most everything in morphic would continue to work as is. does this make sense? If the primitives existed, I could help out, but not being a c/c++ programmer I am at a disadvantage here. 2009/6/11 Mariano Martinez Peck marianop...@gmail.com what is ffenestria? links? On Thu, Jun 11, 2009 at 3:45 PM, Stéphane Ducasse stephane.duca...@inria.fr wrote: Would it be ok if this was configurable via a user preference, meaning pharo supported both? sure. A VisualWorks multiple-native-window capability would open up the possibility of creating a different class of applications. Alot of my work revolves around integration with legacy systems. Having a smalltalk with multiple native windows would allow me to more seamlessly introduce it into the world of tools at my company. I really think that if somebody would work on ffenestria we would integrate it. thanks sw On Thu, Jun 11, 2009 at 11:33 AM, Alexandre Bergel alexan...@bergel.eu wrote: I used Visualworks and Squeak, and frankly, I prefer to have embedded morphic windows in a unique native window, as it is now in Pharo. Application switching is easier in my opinion and I do not feel a need to have an email clients between two code browsers. As the discussion on save and quit testified, people have radically different habits when programming. Even for simple things. Interesting. Cheers, Alexandre On 11 Jun 2009, at 10:58, Steve Wirts wrote: If the primitives existed in pharo that would allow someone to create and control native windows, I would be more than happy to take the time to try and massage morphic into working cleanly/ elegantly with multiple windows. On Thu, Jun 11, 2009 at 10:44 AM, Damien Cassou damien.cas...@gmail.com wrote: On Thu, Jun 11, 2009 at 4:38 PM, Michael Ruegerm.rue...@acm.org wrote: Also the GTK bindings and Newspeak use native windows (I think?). Newspeak uses either native or morphic windows, depending on the wishes of the user. -- Damien Cassou http://damiencassou.seasidehosting.st Lambdas are relegated to relative obscurity until Java makes them popular by not having them. James Iry ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
I'll note the Ffenestri.zip has both the Ffenestri and the HostMenu os- x logic in it. You'll need to be careful and only integrate the Ffenestri logic since the HostMenu logic already was integrated into Pharo and was updated for the new sensor logic so likely loading the HostMenus-Base.2.cs for example will break your image. On 11-Jun-09, at 11:35 AM, Stéphane Ducasse wrote: Ffenestri.zip -- = = = John M. McIntosh john...@smalltalkconsulting.com Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
thanks john stef On Jun 11, 2009, at 8:40 PM, John M McIntosh wrote: I'll note the Ffenestri.zip has both the Ffenestri and the HostMenu os- x logic in it. You'll need to be careful and only integrate the Ffenestri logic since the HostMenu logic already was integrated into Pharo and was updated for the new sensor logic so likely loading the HostMenus-Base.2.cs for example will break your image. On 11-Jun-09, at 11:35 AM, Stéphane Ducasse wrote: Ffenestri.zip -- = = = = = == John M. McIntosh john...@smalltalkconsulting.com Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http:// www.smalltalkconsulting.com = = = = = == ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Fixes for Numbers are ready (toward ANSI)
I cumulated the changes in this order: http://code.google.com/p/pharo/issues/list?id=874 PharoInbox/SLICE-Mantis6985-Issue874-Integer-bitAt-nice.1 add Integer #bitAt: http://code.google.com/p/pharo/issues/list?id=875 PharoIbox/SLICE-Mantis6601-Issue875-Float-hash-nice.1 fix Float hash http://code.google.com/p/pharo/issues/list?id=876 PharoInbox/SLICE-Mantis3374-Issue876-Arithmetic-Equality-transitive-Part1-nice.1 PharoInbox/SLICE-Mantis3374-Issue876-Arithmetic-Equality-transitive-Part2-nice.1 fix number equal transitivity (and further change Fraction hash) http://code.google.com/p/pharo/issues/detail?id=681 PharoInbox/SLICE-Mantis6982-Issue681-Number-readFrom-nice.1 connect SqNumberParser in Number readFrom: (with backward compatibility) http://code.google.com/p/pharo/issues/list?id=879 PharoInbox/SLICE-Issue879-ANSI-FloatCharacterization-nice.1 add ANSI Float Characterization Please review :) Nicolas ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] call for tester for
Hi guys would be nice if some of u could test: http://code.google.com/p/pharo/issues/detail?id=860colspec=ID%20Type%20Status%20Summary%20Milestonestart=200 Thanks ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Fwd: to go beta?
Marcus, Adrian, Mike how do we proceed to go beta? take the 1.0 fixes and integrate them. put a deadline and do it? Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Fixes for Numbers are ready (toward ANSI)
2009/6/11 Stéphane Ducasse stephane.duca...@inria.fr: thanks nicolas BTW did you got feedback about this one? http://code.google.com/p/pharo/issues/detail?id=860colspec=ID%20Type%20Status%20Summary%20Milestonestart=200 None yet. I only see 3 explanations: - everyone is busy, dead, in hollidays, in the garden, etc... - everyone disabled the preference for generating the error log - I'm the only one doing bugs, no one else ever seen a slow Notifier Maybe I should submit to squeak-dev, but the list seems rather quiet these times. Nicolas On Jun 11, 2009, at 9:24 PM, Nicolas Cellier wrote: I cumulated the changes in this order: http://code.google.com/p/pharo/issues/list?id=874 PharoInbox/SLICE-Mantis6985-Issue874-Integer-bitAt-nice.1 add Integer #bitAt: http://code.google.com/p/pharo/issues/list?id=875 PharoIbox/SLICE-Mantis6601-Issue875-Float-hash-nice.1 fix Float hash http://code.google.com/p/pharo/issues/list?id=876 PharoInbox/SLICE-Mantis3374-Issue876-Arithmetic-Equality-transitive- Part1-nice.1 PharoInbox/SLICE-Mantis3374-Issue876-Arithmetic-Equality-transitive- Part2-nice.1 fix number equal transitivity (and further change Fraction hash) http://code.google.com/p/pharo/issues/detail?id=681 PharoInbox/SLICE-Mantis6982-Issue681-Number-readFrom-nice.1 connect SqNumberParser in Number readFrom: (with backward compatibility) http://code.google.com/p/pharo/issues/list?id=879 PharoInbox/SLICE-Issue879-ANSI-FloatCharacterization-nice.1 add ANSI Float Characterization Please review :) Nicolas ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Fixes for Numbers are ready (toward ANSI)
On Jun 11, 2009, at 10:02 PM, Nicolas Cellier wrote: 2009/6/11 Stéphane Ducasse stephane.duca...@inria.fr: thanks nicolas BTW did you got feedback about this one? http://code.google.com/p/pharo/issues/detail?id=860colspec=ID%20Type%20Status%20Summary%20Milestonestart=200 None yet. I only see 3 explanations: - everyone is busy, dead, in hollidays, in the garden, etc... Dead busyz dead = stef - everyone disabled the preference for generating the error log - I'm the only one doing bugs, no one else ever seen a slow Notifier Maybe I should submit to squeak-dev, but the list seems rather quiet these times. Nicolas On Jun 11, 2009, at 9:24 PM, Nicolas Cellier wrote: I cumulated the changes in this order: http://code.google.com/p/pharo/issues/list?id=874 PharoInbox/SLICE-Mantis6985-Issue874-Integer-bitAt-nice.1 add Integer #bitAt: http://code.google.com/p/pharo/issues/list?id=875 PharoIbox/SLICE-Mantis6601-Issue875-Float-hash-nice.1 fix Float hash http://code.google.com/p/pharo/issues/list?id=876 PharoInbox/SLICE-Mantis3374-Issue876-Arithmetic-Equality-transitive- Part1-nice.1 PharoInbox/SLICE-Mantis3374-Issue876-Arithmetic-Equality-transitive- Part2-nice.1 fix number equal transitivity (and further change Fraction hash) http://code.google.com/p/pharo/issues/detail?id=681 PharoInbox/SLICE-Mantis6982-Issue681-Number-readFrom-nice.1 connect SqNumberParser in Number readFrom: (with backward compatibility) http://code.google.com/p/pharo/issues/list?id=879 PharoInbox/SLICE-Issue879-ANSI-FloatCharacterization-nice.1 add ANSI Float Characterization Please review :) Nicolas ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Fwd: to go beta?
That's a good question I was also thinking about today... I suggest the following steps: 1. Review all issues in the tracker and decide for each whether it is important for 1.0. 2. We concentrate on completing these 1.0-tagged items. New issues should only be tagged with 1.0 if they are critical bugs (i.e., no new improvements get integrated anymore!) 3. As soon as we have completed all items that change the behavior of the system (i.e., that are not bugfixes) we declare beta 4. As soon as all items are done, we declare gamma and after a while without newly reported problems we release 1.0 Adrian On Jun 11, 2009, at 21:59 , Stéphane Ducasse wrote: Marcus, Adrian, Mike how do we proceed to go beta? take the 1.0 fixes and integrate them. put a deadline and do it? Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Fixes for Numbers are ready (toward ANSI)
Nicolas Cellier a écrit : 2009/6/11 Stéphane Ducasse stephane.duca...@inria.fr: thanks nicolas BTW did you got feedback about this one? http://code.google.com/p/pharo/issues/detail?id=860colspec=ID%20Type%20Status%20Summary%20Milestonestart=200 None yet. I only see 3 explanations: - everyone is busy, dead, in hollidays, in the garden, etc... - everyone disabled the preference for generating the error log - I'm the only one doing bugs, no one else ever seen a slow Notifier :) Hi Nicolas, sorry for the stupid question but what are you asking testers to do ? I've loaded the 4 .cs, verified that the preference is on and evaluated 0/0. seen a notifier, click on proceed and get a SqueakDebug.log. and then what ? thanks Alain ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] [update] #10335
#10335 == Issue 645: Project exportSegmentWithChangeSet:fileName:directory: calls: writeStackText:in:registerIn: Issue 642: Project enterAsActiveSubprojectWithin: calls: okayToEnterProject Issue 644: Project displayZoom: calls: playProjectTransitionFrom:to:entering: Issue 641: Debugger abandon: calls: controller Issue 646: Parser parse:class: calls: parseError Issue 702: check Preferences overrides from closure changes Issue 746: missing package for Closure and friends Issue 878: fixes for newparser parsability -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Fwd: to go beta?
I will try to rewrite this week the last dirty method (according to my count)... so the 1.0 should be license clean... . After this maybe I could help with some bugs. On Thu, Jun 11, 2009 at 5:19 PM, Adrian Lienhard a...@netstyle.ch wrote: That's a good question I was also thinking about today... I suggest the following steps: 1. Review all issues in the tracker and decide for each whether it is important for 1.0. 2. We concentrate on completing these 1.0-tagged items. New issues should only be tagged with 1.0 if they are critical bugs (i.e., no new improvements get integrated anymore!) 3. As soon as we have completed all items that change the behavior of the system (i.e., that are not bugfixes) we declare beta 4. As soon as all items are done, we declare gamma and after a while without newly reported problems we release 1.0 Adrian On Jun 11, 2009, at 21:59 , Stéphane Ducasse wrote: Marcus, Adrian, Mike how do we proceed to go beta? take the 1.0 fixes and integrate them. put a deadline and do it? Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] multiple native windows
I tried wxsqueak. Demos ar really good, and populating a grid with miliions of rows is very fast, however you have to turn your mind to build so defensively... I crashed the wm 3 to 4 times in around 4 hours - effort,m then I gave up. -Mensaje original- De: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr]en nombre de Mariano Martinez Peck Enviado el: Jueves, 11 de Junio de 2009 12:25 p.m. Para: Pharo-project@lists.gforge.inria.fr Asunto: Re: [Pharo-project] multiple native windows Perhaps you can join forces with the rest of the present alternatives. For example, squeakgtk I think there is a lot of people that wants native windows so that being able to create desktop applications. Cheers, Mariano 2009/6/11 Steve Wirts stevewi...@gmail.com If the primitives existed in pharo that would allow someone to create and control native windows, I would be more than happy to take the time to try and massage morphic into working cleanly/elegantly with multiple windows. On Thu, Jun 11, 2009 at 10:44 AM, Damien Cassou damien.cas...@gmail.com wrote: On Thu, Jun 11, 2009 at 4:38 PM, Michael Ruegerm.rue...@acm.org wrote: Also the GTK bindings and Newspeak use native windows (I think?). Newspeak uses either native or morphic windows, depending on the wishes of the user. -- Damien Cassou http://damiencassou.seasidehosting.st Lambdas are relegated to relative obscurity until Java makes them popular by not having them. James Iry ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] a plea for save and quit
I like this one too.I don't like Save .. Save, Save as.. etc, to much cliks (or moves) just to save On Thu, Jun 11, 2009 at 9:17 AM, Alain Plantec alain.plan...@free.frwrote: Tudor Girba a écrit : Save Save as... Save and quit - Quit Hi all, I like this simple proposition. We still have 'recover lost changes' in the case of unwanted quit without saving. alain ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Fwd: to go beta?
On Fri, Jun 12, 2009 at 3:19 AM, Adrian Lienharda...@netstyle.ch wrote: That's a good question I was also thinking about today... I suggest the following steps: 1. Review all issues in the tracker and decide for each whether it is important for 1.0. 2. We concentrate on completing these 1.0-tagged items. New issues should only be tagged with 1.0 if they are critical bugs (i.e., no new improvements get integrated anymore!) 3. As soon as we have completed all items that change the behavior of the system (i.e., that are not bugfixes) we declare beta 4. As soon as all items are done, we declare gamma and after a while without newly reported problems we release 1.0 What could be great is a release during next ESUG conference in september. -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/ ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Fixes for Numbers are ready (toward ANSI)
2009/6/11 Alain Plantec alain.plan...@free.fr: Nicolas Cellier a écrit : 2009/6/11 Stéphane Ducasse stephane.duca...@inria.fr: thanks nicolas BTW did you got feedback about this one? http://code.google.com/p/pharo/issues/detail?id=860colspec=ID%20Type%20Status%20Summary%20Milestonestart=200 None yet. I only see 3 explanations: - everyone is busy, dead, in hollidays, in the garden, etc... - everyone disabled the preference for generating the error log - I'm the only one doing bugs, no one else ever seen a slow Notifier :) Hi Nicolas, sorry for the stupid question but what are you asking testers to do ? I've loaded the 4 .cs, verified that the preference is on and evaluated 0/0. seen a notifier, click on proceed and get a SqueakDebug.log. and then what ? thanks Alain The speed should increase, that's what the patch is all for. I don't know what test Stef wants exactly, I see two possibilities: -1) review the changes -2) install the changes and do normal activity, report if any trouble Nicolas ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
