[Pharo-dev] download from website: missing .sources file
Hi guys, Really nice job on the new website. Congrats! Though this one keeps popping up over and over again: the .sources file is _not_ available for download from the website. If you download the vm and the image, you still need to get the .sources from somewhere else. It would be really good to fix that. cheers Johan
Re: [Pharo-dev] Dev Art from Google
Indeed, I have a personal project exactly about that… I hope to concretize it this year… Alexandre On Mar 25, 2014, at 4:03 AM, S Krish wrote: > > > Moose art visualizations if not more from Phratch et als can make a mark > here. > > > https://devart.withgoogle.com/?utm_source=email&utm_medium=gsp&utm_campaign=gspb > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
Indeed, this would be very cool Alexandre On May 1, 2014, at 4:43 PM, GOUBIER Thierry wrote: > However, I would dream of merging Roassal(2) and Morphic. Use Roassal DSLs > and infrastructure to make Morphic simpler, and build fully integrated GUIs > (code exploration tools, or even a system browser) where some of the widgets > are Roassal(s). This was my dream when I started my browser: have a full > screen representation of the code inside my image, as an interactive > background to my Pharo, and editors floating there and there to edit the > code, run it, explore it, debug it, etc... -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
Oh Esteban… there is a lot of love in your heart man… This is so refreshing… And to share some more, here… there you have guys, this is our current dev theme at flowing https://github.com/sebastianconcept/Pharo3DawnTheme sebastian o/ On May 1, 2014, at 8:24 AM, Esteban Lorenzano wrote: > Dark Theme for Pharo 3 > == > > So, I finally took some time and hacked a Dark Theme for Pharo 3: > > > > How you install it? You need to execute this script: > > “1. You need this because otherwise Gofer merge becomes dumb :P" > MCRepositoryGroup default > addRepository: (MCSmalltalkhubRepository > owner: 'estebanlm' > project: 'Pharo3DarkTheme'). > “2. Now we can actually MERGE the project" > Gofer it > smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; > package: 'Pharo3DarkTheme'; > merge. > “3. And then install it" > Pharo3DarkTheme installFullTheme. > > WARNING 1: You need to do a merge (notice the script) > WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details. > WARNING 3: This changes something in the Pharo3Theme too... so you can go > back after installing, but not completely :) > > Considerations > --
Re: [Pharo-dev] Usage of should: in tests
On 01 May 2014, at 00:52, Nicolas Cellier wrote: > Hi, > I see many usage of #should: in SciSmalltalk tests that could simply be > turned into #assert: or eventually #assert:equals: > Why wanting to use a block? > Other than #should:raise: and #shouldnt:raise:, I don't really see the point > of #should: alone anyway... > IMO should: should be deprecated, less is more. > I'm possibly the author of several of these #should: sends, so don't take it > personnally ;) > > P.S. or is it easier to restart the block in the Debugger? > I cross post to pharo-dev because it's a generic question, and there are a > few #should: sends in Pharo-3.0 too. I also do not understand why you would want to use a block. So unless there is a good reason to use that, a simpler API is preferable. BTW, and this was discussed before, #shouldnt:raise: is useless as well ;-)
Re: [Pharo-dev] [Screencast] request for review
Hi Laurent, Very well done - this coding in the debugger is certainly a strong point of Pharo. It is even quite instructive for advanced users. And yes this has to be included in the website. Thanks ! Sven On 01 May 2014, at 23:21, Laurent Laffont wrote: > Hi, > > I've recorded a screencast for Pharo 3.0. Could some of you review the > english subtitles ? > > Project is here: https://github.com/lolgzs/pharo-picasa-screencast , > subtitles in picasa_pharo3.en.srt. It's a simple text format, but you can use > tools like KDE subtitle composer or Jubler to edit it. You can either send me > fix by mail or make merge requests on github (easier for me :). > > > Next the idea is to have subtitles translated into several languages, help > appreciated. > > And if you have courage and time :), it would be nice to have voice recorded > (my spoken english sounds, well, ... ). > > The screencast may be published on new Pharo website for people to get > started. > > Cheers, > > Laurent >
[Pharo-dev] [Screencast] request for review
Hi, I've recorded a screencast for Pharo 3.0. Could some of you review the english subtitles ? Project is here: https://github.com/lolgzs/pharo-picasa-screencast , subtitles in picasa_pharo3.en.srt. It's a simple text format, but you can use tools like KDE subtitle composer or Jubler to edit it. You can either send me fix by mail or make merge requests on github (easier for me :). Next the idea is to have subtitles translated into several languages, help appreciated. And if you have courage and time :), it would be nice to have voice recorded (my spoken english sounds, well, ... ). The screencast may be published on new Pharo website for people to get started. Cheers, Laurent
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
Well done! I really like it. Thanks On Thu, May 1, 2014 at 5:37 PM, Esteban Lorenzano wrote: > mmm… no, span the list :) > I will fix it. > > Esteban > > On 01 May 2014, at 22:35, p...@highoctane.be wrote: > > The critic browser shows a white on white pane. > > So, where can I report issues linked to this unofficial UI without > spamming the list ? > > Phil > > > > On Thu, May 1, 2014 at 10:28 PM, p...@highoctane.be wrote: > >> On Thu, May 1, 2014 at 1:24 PM, Esteban Lorenzano wrote: >> >>> Dark Theme for Pharo 3 >>> == >>> >>> So, I finally took some time and hacked a Dark Theme for Pharo 3: >>> >>> >>> >>> How you install it? You need to execute this script: >>> >>> “1. You need this because otherwise Gofer merge becomes dumb :P" >>> MCRepositoryGroup default >>> addRepository: (MCSmalltalkhubRepository >>> owner: 'estebanlm' >>> project: 'Pharo3DarkTheme'). >>> “2. Now we can actually MERGE the project" >>> Gofer it >>> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; >>> package: 'Pharo3DarkTheme'; >>> merge. >>> “3. And then install it" >>> Pharo3DarkTheme installFullTheme. >>> >>> >>> *WARNING 1:* You need to do a merge (notice the script) >>> *WARNING 2:* Yes, this is a HACK (also: an ugly hack). See below for >>> details. >>> *WARNING 3:* This changes something in the Pharo3Theme too... so you >>> can go back after installing, but not completely :) >>> >>> Considerations >>> -- >>> >>> It can look like an easy task, to make a theme over a non native GUI >>> like Pharo, but let me tell you: It is not. There are a lot of glitches and >>> errors of design you have to overcome to get a working version of a theme. >>> This is a pitty because we claim that our system is clean (or should be >>> clean) and easy to understand. >>> >>> But all the Morphic implementation is a hack over a hack, with >>> preconcepts and hardcodes everywhere, up to a point that to make the >>> smallest change is an incredibly annoying task. >>> >>> Then... I added ""yet another hack"" to this infinite list. I made it >>> because we need something like this, even if not a good solution. And I >>> also made it to start a debate into our community. I truly believe that >>> Morphic was a great idea, but I also believe that current implementation is >>> doomed. I would like to discuss a new implementation, with a good design >>> (for example I believe it should be a clear separation between a morph and >>> it's skin, making easy the actual-hard task of changing a colorset). >>> I also believe there will be a clear separation between what is a Morph >>> (a graphical unit) and a Widget (who at the time should use morphs, but >>> that's another story). >>> Etc., etc., etc. >>> >>> So, will we start the longtime postponed effort of effectively replace >>> current Morphic? >>> >>> In the mean time, enjoy the theme. Is so cool that I'm considering >>> making it my default theme :P >>> >>> Esteban >>> >>> >> I installed in on Windows and it works nicely. One needs to reopen >> existing windows as there is a kind of lighter border on them. >> I tried to go to the Pharo3 theme and back, well, yeah, don't try that :-) >> >> Now, I need a dark TWM (the menus are dark already but not the bar itself >> or the menu borders). >> >> Phil >> > > >
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
mmm… no, span the list :) I will fix it. Esteban On 01 May 2014, at 22:35, p...@highoctane.be wrote: > The critic browser shows a white on white pane. > > So, where can I report issues linked to this unofficial UI without spamming > the list ? > > Phil > > > > On Thu, May 1, 2014 at 10:28 PM, p...@highoctane.be > wrote: > On Thu, May 1, 2014 at 1:24 PM, Esteban Lorenzano wrote: > Dark Theme for Pharo 3 > == > > So, I finally took some time and hacked a Dark Theme for Pharo 3: > > > > How you install it? You need to execute this script: > > “1. You need this because otherwise Gofer merge becomes dumb :P" > MCRepositoryGroup default > addRepository: (MCSmalltalkhubRepository > owner: 'estebanlm' > project: 'Pharo3DarkTheme'). > “2. Now we can actually MERGE the project" > Gofer it > smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; > package: 'Pharo3DarkTheme'; > merge. > “3. And then install it" > Pharo3DarkTheme installFullTheme. > > WARNING 1: You need to do a merge (notice the script) > WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details. > WARNING 3: This changes something in the Pharo3Theme too... so you can go > back after installing, but not completely :) > > Considerations > -- > > It can look like an easy task, to make a theme over a non native GUI like > Pharo, but let me tell you: It is not. There are a lot of glitches and errors > of design you have to overcome to get a working version of a theme. This is a > pitty because we claim that our system is clean (or should be clean) and easy > to understand. > > But all the Morphic implementation is a hack over a hack, with preconcepts > and hardcodes everywhere, up to a point that to make the smallest change is > an incredibly annoying task. > > Then... I added ""yet another hack"" to this infinite list. I made it because > we need something like this, even if not a good solution. And I also made it > to start a debate into our community. I truly believe that Morphic was a > great idea, but I also believe that current implementation is doomed. I would > like to discuss a new implementation, with a good design (for example I > believe it should be a clear separation between a morph and it's skin, making > easy the actual-hard task of changing a colorset). > I also believe there will be a clear separation between what is a Morph (a > graphical unit) and a Widget (who at the time should use morphs, but that's > another story). > Etc., etc., etc. > > So, will we start the longtime postponed effort of effectively replace > current Morphic? > > In the mean time, enjoy the theme. Is so cool that I'm considering making it > my default theme :P > > Esteban > > > I installed in on Windows and it works nicely. One needs to reopen existing > windows as there is a kind of lighter border on them. > I tried to go to the Pharo3 theme and back, well, yeah, don't try that :-) > > Now, I need a dark TWM (the menus are dark already but not the bar itself or > the menu borders). > > Phil >
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
On 01 May 2014, at 21:32, GOUBIER Thierry wrote: > > De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Esteban > Lorenzano [esteba...@gmail.com] > > > >> By the way, I have added a PharoExtras UIThemes project to Smalltalkhub, >> right in time it seems ;) > > yeah, the problem is that currently there are a lot of changes happening to > make the dark theme possible (I removed hardcoded colors everywhere, > re-direct default colors to theme everywhere, modified without any > contemplation packages like Morphic*, Spec* and Nautilus*… along with > Polymorph* packages, of course. > > Yes, I had a look in the Pharo3DarkTheme package :) well… I said it was a hack :P > > This is the only thing which dissuades me from using it right now :( The time > for the merge to happen on my netbook is just too long... And I have to do > screenshots for PharoForTheEnterprise :) > > So… I need to work a lot more in polishing, ensure all continues working, > make appropriate SLICES, etc. > I see this as part of the “tool oriented” direction of Pharo 4. > I shared because I think the result is good enough and people can take > benefit of having it (also, then people can help on making the work, he). > But in any case, is not close at all of being integrable to core image, or to > a standard theme project :( > But it will be, it has to :) > You've given us something to dream about, and to start to use to boot :) > > >> >> About a morphic redesign, I just had a look at Cuis to see how was their >> Morphic. > > yeah, not sure that I want to follow that path, but we need to start > discussing it :) > I know Alain Plaintec started to work on a new morphic, and I suppose best > scenario is all community joining efforts to achieve the goal, but for that > we first need to discuss/agree on a design. > I've seen Alain's effort the last time I went to Brest, but I never took the > time to try it. I think it's probably a good base; as it is use-driven, it is > important to exercise it with the most complex Morphic / Spec GUIs we can > build, which means community support. > > What happens now is that every morph is a HUGE ball of mud, with mixed > responsibilities and many dependencies to other “layers”: is very famous the > dependency of HandMorph with the event dispatcher (now cleaned), but that was > just an example. Now it is mixed with Polymorph in a very dirty way, etc. etc. > As it's easy for me to see that, it's also frightening to see how many > protocols in Morphic are extensions for packages which do not exist anymore. > And the complexity of all the PluggableXXX is frightening, and it introduces > serious performance problems. > > In a ver corse grained way, I imagine a future morphic well split in his > different concerns: graphic “atoms”, skins and widgets. > And with a more understandable layout API, and with simpler widgets to > connect to models, and with working caching so that we don't busy lock Pharo > when exploring long collections, and that Moose doesn't have to use that ugly > paging tree/list morph, and ... > > While still keeping what made Morphic so great in the first place :) > > Thierry > > cheers, > Esteban > >> >> Thierry
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
On 01 May 2014, at 22:28, p...@highoctane.be wrote: > On Thu, May 1, 2014 at 1:24 PM, Esteban Lorenzano wrote: > Dark Theme for Pharo 3 > == > > So, I finally took some time and hacked a Dark Theme for Pharo 3: > > > > How you install it? You need to execute this script: > > “1. You need this because otherwise Gofer merge becomes dumb :P" > MCRepositoryGroup default > addRepository: (MCSmalltalkhubRepository > owner: 'estebanlm' > project: 'Pharo3DarkTheme'). > “2. Now we can actually MERGE the project" > Gofer it > smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; > package: 'Pharo3DarkTheme'; > merge. > “3. And then install it" > Pharo3DarkTheme installFullTheme. > > WARNING 1: You need to do a merge (notice the script) > WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details. > WARNING 3: This changes something in the Pharo3Theme too... so you can go > back after installing, but not completely :) > > Considerations > -- > > It can look like an easy task, to make a theme over a non native GUI like > Pharo, but let me tell you: It is not. There are a lot of glitches and errors > of design you have to overcome to get a working version of a theme. This is a > pitty because we claim that our system is clean (or should be clean) and easy > to understand. > > But all the Morphic implementation is a hack over a hack, with preconcepts > and hardcodes everywhere, up to a point that to make the smallest change is > an incredibly annoying task. > > Then... I added ""yet another hack"" to this infinite list. I made it because > we need something like this, even if not a good solution. And I also made it > to start a debate into our community. I truly believe that Morphic was a > great idea, but I also believe that current implementation is doomed. I would > like to discuss a new implementation, with a good design (for example I > believe it should be a clear separation between a morph and it's skin, making > easy the actual-hard task of changing a colorset). > I also believe there will be a clear separation between what is a Morph (a > graphical unit) and a Widget (who at the time should use morphs, but that's > another story). > Etc., etc., etc. > > So, will we start the longtime postponed effort of effectively replace > current Morphic? > > In the mean time, enjoy the theme. Is so cool that I'm considering making it > my default theme :P > > Esteban > > > I installed in on Windows and it works nicely. One needs to reopen existing > windows as there is a kind of lighter border on them. > I tried to go to the Pharo3 theme and back, well, yeah, don't try that :-) going back should be doable. But you need to close and open all windows. > > Now, I need a dark TWM (the menus are dark already but not the bar itself or > the menu borders). that’s a work for TWM maintainers, I’m already dealing with Glamour (quite easy, TBH) ;) > > Phil
Re: [Pharo-dev] a Pharo talk from a ruby conference
On May 1, 2014, at 3:37 PM, Sean P. DeNigris wrote: > kilon alios wrote >> "Smalltalk inspired" is reinforcing "Sorry for dead Smalltalk > > The more I think about it, the more I dislike Smalltalk-inspired. I think > the best plan would be to: > 1. Hold off for a brief moment mentioning Smalltalk at all - e.g. give a > sound bite, introduce the environment and libraries, and then when we're > ready to mention the language and legacy > 2. Something like "Smalltalk Unleashed" or "Smalltalk Reborn" Smalltalk reborn is the kind of bold statement that we should aim to say but I don’t feel we are quite ready to tell that just yet. If we force things and we do we’ll devaluate our speech because the expectations are very high out there. But.. if we raise the bar on innovation and become able to do things like Meteor, that’s a whole different story. If something of that caliber happens and we have things to battle test them and we do good, then things would get really exciting… super heroic kind of exciting… continuation of the legend kind of exiting... tl;dr: Many prolific and prosperous things could come from a Pharo Amber relationship In fact, hush hush, but at flowing we just approved doing a feature in airflowing that is not doable without Amber and Pharo. Wonder how our audience will respond to that... sebastian o/
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Sean P. DeNigris [s...@clipperadams.com] Envoyé : jeudi 1 mai 2014 20:31 À : pharo-dev@lists.pharo.org Objet : Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available EstebanLM wrote >> About a morphic redesign... > I suppose best scenario is all community joining efforts to achieve the > goal, but for that we first need to discuss/agree on a design. Yes!!! IMHO our Morphic implementation's ocmplexity is the biggest thing holding back our creative spirit. It seems that many other things have been cleared out of our way and now is the time to make this happen. I think you hit the nail right on the head: 1) all interested parties join forces - there have been too many experimental cleanups and re-implementations that are interesting but ultimately unused/unusable, and 2) start with a solid design. Morphic's power is incredible and it would be great to have that available when you need it, with all the more-business-friendly UI objects built on top. Some good places I've found ideas and insights are ARK, Self, Lively Kernel, KScript, and Cuis. Note on the design: I wouldn't hesitate to have some of the business-friendly objects slightly on the side of the overall design: we don't need the full complexity and power of Morphic for many business objects... Doru's work with Glamour may be a good benchmark of how simple business looking code may be. However, I would dream of merging Roassal(2) and Morphic. Use Roassal DSLs and infrastructure to make Morphic simpler, and build fully integrated GUIs (code exploration tools, or even a system browser) where some of the widgets are Roassal(s). This was my dream when I started my browser: have a full screen representation of the code inside my image, as an interactive background to my Pharo, and editors floating there and there to edit the code, run it, explore it, debug it, etc... I settled for less :) Thierry
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Esteban Lorenzano [esteba...@gmail.com] By the way, I have added a PharoExtras UIThemes project to Smalltalkhub, right in time it seems ;) yeah, the problem is that currently there are a lot of changes happening to make the dark theme possible (I removed hardcoded colors everywhere, re-direct default colors to theme everywhere, modified without any contemplation packages like Morphic*, Spec* and Nautilus*… along with Polymorph* packages, of course. Yes, I had a look in the Pharo3DarkTheme package :) This is the only thing which dissuades me from using it right now :( The time for the merge to happen on my netbook is just too long... And I have to do screenshots for PharoForTheEnterprise :) So… I need to work a lot more in polishing, ensure all continues working, make appropriate SLICES, etc. I see this as part of the “tool oriented” direction of Pharo 4. I shared because I think the result is good enough and people can take benefit of having it (also, then people can help on making the work, he). But in any case, is not close at all of being integrable to core image, or to a standard theme project :( But it will be, it has to :) You've given us something to dream about, and to start to use to boot :) About a morphic redesign, I just had a look at Cuis to see how was their Morphic. yeah, not sure that I want to follow that path, but we need to start discussing it :) I know Alain Plaintec started to work on a new morphic, and I suppose best scenario is all community joining efforts to achieve the goal, but for that we first need to discuss/agree on a design. I've seen Alain's effort the last time I went to Brest, but I never took the time to try it. I think it's probably a good base; as it is use-driven, it is important to exercise it with the most complex Morphic / Spec GUIs we can build, which means community support. What happens now is that every morph is a HUGE ball of mud, with mixed responsibilities and many dependencies to other “layers”: is very famous the dependency of HandMorph with the event dispatcher (now cleaned), but that was just an example. Now it is mixed with Polymorph in a very dirty way, etc. etc. As it's easy for me to see that, it's also frightening to see how many protocols in Morphic are extensions for packages which do not exist anymore. And the complexity of all the PluggableXXX is frightening, and it introduces serious performance problems. In a ver corse grained way, I imagine a future morphic well split in his different concerns: graphic “atoms”, skins and widgets. And with a more understandable layout API, and with simpler widgets to connect to models, and with working caching so that we don't busy lock Pharo when exploring long collections, and that Moose doesn't have to use that ugly paging tree/list morph, and ... While still keeping what made Morphic so great in the first place :) Thierry cheers, Esteban Thierry
Re: [Pharo-dev] New Proposal for new Pharo website - About page (with example website)
If I put the language last then I would mislead people into thinking its something like Emacs. In this case an IDE that also happens to have a programming language. It will only add to the confusion. I have recommended Pharo to several people their complaints were very similar a) the gui looks weird / ugly b) documentation does not look good/dated . As a matter of fact the language is one the things people liked, together with live code of course. I think the language is one of the very strong points of Pharo and it should be promoted. It also makes the goal of Pharo clear, the language comes first. But if others agree to put the language last, I have no issue its our website , the majority should decide. I don't want to go into the whole debate of whether Pharo is this kind of Smalltalk or the other kind of Smalltalk. Again if Pharo developers decide on what kinda of Smalltalk Pharo is I am more than happy to put that into the description. But to be frank with you I find the description of the old site too vague for my taste and very confusing. I want a description that is specific, clear and foremost practical. "Immersive" does not mean anything to me, "open" again not very clear (do you mean open source ?), "live" ? sorry I dont understand what is live ? These are the questions people will ask when they see the description. Please approach this from the side of a very sceptical yet curious coder that does not share the same excitement and love as you and me about Pharo. If he read a bunch of vague words its much more likely to be put off a lot more than seeing the very efficient and practical Smalltalk syntax. I also dont believe the ~20% of Ruby, how much stuff Ruby has that Pharo does not ? I rather not compete with other languages and make people see Pharo as elitist. On Thu, May 1, 2014 at 9:25 PM, Sean P. DeNigris wrote: > kilon alios wrote > > Class library section as third section sounds excellent idea, please if > > you > > can give me a paragraph or anyone with experience on this. I try to add > > anything I know about Pharo but unfortunately there is still much I don't > > know. > > I think it's important to introduce the concepts in a very specific order, > most importantly with the language last (the syntax was always the least > interesting thing about Smalltalk, and it addresses concerns about turning > people off right off the bat, without hiding anything) (see > http://forum.world.st/Pharo-is-Smalltalk-and-Not-tp4757342p4757348.html): > 1. a [pick 2 or 3 of: dynamic, open, immersive, live] computing environment > (like an IDE and OS rolled into one) > 2. [appropriate adjectives] core libraries > 3. a dialect of the Smalltalk programming language > > The immersive environment of live objects is the most compelling - from a > programming standpoint, sending someone a serialized debug session, > customizing the world menu, the simplicity of adding settings, all in a > live, dynamic way; that you have a whole computer (OS + IDE + libraries) > done with ~20% of the LOC of Ruby 1.9 (without *any* tools!) and ~0.5% of > the LOC of Windows Vista; this is the blue plane idea that Smalltalk took > on > > > > - > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/New-Proposal-for-new-Pharo-website-About-page-with-example-website-tp4757411p4757483.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >
Re: [Pharo-dev] a Pharo talk from a ruby conference
kilon alios wrote > "Smalltalk inspired" is reinforcing "Sorry for dead Smalltalk The more I think about it, the more I dislike Smalltalk-inspired. I think the best plan would be to: 1. Hold off for a brief moment mentioning Smalltalk at all - e.g. give a sound bite, introduce the environment and libraries, and then when we're ready to mention the language and legacy 2. Something like "Smalltalk Unleashed" or "Smalltalk Reborn" - Cheers, Sean -- View this message in context: http://forum.world.st/a-Pharo-talk-from-a-ruby-conference-tp4756805p4757488.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
EstebanLM wrote >> About a morphic redesign... > I suppose best scenario is all community joining efforts to achieve the > goal, but for that we first need to discuss/agree on a design. Yes!!! IMHO our Morphic implementation's ocmplexity is the biggest thing holding back our creative spirit. It seems that many other things have been cleared out of our way and now is the time to make this happen. I think you hit the nail right on the head: 1) all interested parties join forces - there have been too many experimental cleanups and re-implementations that are interesting but ultimately unused/unusable, and 2) start with a solid design. Morphic's power is incredible and it would be great to have that available when you need it, with all the more-business-friendly UI objects built on top. Some good places I've found ideas and insights are ARK, Self, Lively Kernel, KScript, and Cuis. - Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Pharo3-Dark-Theme-is-available-tp4757419p4757486.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] [ANN]: Little NeoJSON Helper
It is on my list ... On 01 May 2014, at 20:03, Sean P. DeNigris wrote: > I'd like for Sven to take a look and see if it's generally useful and > well-designed, but sure... > > > > - > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/ANN-Little-NeoJSON-Helper-tp4756763p4757481.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >
Re: [Pharo-dev] New Proposal for new Pharo website - About page (with example website)
kilon alios wrote > Class library section as third section sounds excellent idea, please if > you > can give me a paragraph or anyone with experience on this. I try to add > anything I know about Pharo but unfortunately there is still much I don't > know. I think it's important to introduce the concepts in a very specific order, most importantly with the language last (the syntax was always the least interesting thing about Smalltalk, and it addresses concerns about turning people off right off the bat, without hiding anything) (see http://forum.world.st/Pharo-is-Smalltalk-and-Not-tp4757342p4757348.html): 1. a [pick 2 or 3 of: dynamic, open, immersive, live] computing environment (like an IDE and OS rolled into one) 2. [appropriate adjectives] core libraries 3. a dialect of the Smalltalk programming language The immersive environment of live objects is the most compelling - from a programming standpoint, sending someone a serialized debug session, customizing the world menu, the simplicity of adding settings, all in a live, dynamic way; that you have a whole computer (OS + IDE + libraries) done with ~20% of the LOC of Ruby 1.9 (without *any* tools!) and ~0.5% of the LOC of Windows Vista; this is the blue plane idea that Smalltalk took on - Cheers, Sean -- View this message in context: http://forum.world.st/New-Proposal-for-new-Pharo-website-About-page-with-example-website-tp4757411p4757483.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] [ANN]: Little NeoJSON Helper
I'd like for Sven to take a look and see if it's generally useful and well-designed, but sure... - Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Little-NeoJSON-Helper-tp4756763p4757481.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
On 01 May 2014, at 18:43, GOUBIER Thierry wrote: > Bravo Esteban! merci :) > > By the way, I have added a PharoExtras UIThemes project to Smalltalkhub, > right in time it seems ;) yeah, the problem is that currently there are a lot of changes happening to make the dark theme possible (I removed hardcoded colors everywhere, re-direct default colors to theme everywhere, modified without any contemplation packages like Morphic*, Spec* and Nautilus*… along with Polymorph* packages, of course. So… I need to work a lot more in polishing, ensure all continues working, make appropriate SLICES, etc. I see this as part of the “tool oriented” direction of Pharo 4. I shared because I think the result is good enough and people can take benefit of having it (also, then people can help on making the work, he). But in any case, is not close at all of being integrable to core image, or to a standard theme project :( But it will be, it has to :) > > About a morphic redesign, I just had a look at Cuis to see how was their > Morphic. yeah, not sure that I want to follow that path, but we need to start discussing it :) I know Alain Plaintec started to work on a new morphic, and I suppose best scenario is all community joining efforts to achieve the goal, but for that we first need to discuss/agree on a design. What happens now is that every morph is a HUGE ball of mud, with mixed responsibilities and many dependencies to other “layers”: is very famous the dependency of HandMorph with the event dispatcher (now cleaned), but that was just an example. Now it is mixed with Polymorph in a very dirty way, etc. etc. In a ver corse grained way, I imagine a future morphic well split in his different concerns: graphic “atoms”, skins and widgets. cheers, Esteban > > Thierry
Re: [Pharo-dev] New Proposal for new Pharo website - About page (with example website)
Yes Eliot very good suggestions, I am not very familiar with the history or what Pharo adds to the Smalltalk syntax. I welcome any addition to my text , correction, modification. I am open to everything. Just post your text here and I will add it to the website. I am already in contact with esteban he likes my idea too and he said he can take the draft and integrate it inside the current new website for Pharo. Of course I would love it first if you the experienced Pharo developers improve my text so we have a very good quality website not only for begineers but also experienced coders. Class library section as third section sounds excellent idea, please if you can give me a paragraph or anyone with experience on this. I try to add anything I know about Pharo but unfortunately there is still much I don't know. Regarding other Pharo libraries they will go to the third page "The Enviroment" together with Live coding , the power of debugger and of course a basic description for the image format. Dont worry about the debugger, I decided to have a big section about it in "The Enviroment" page. Of course I can still mention it in the IDE page. On Thu, May 1, 2014 at 7:33 PM, Eliot Miranda wrote: > Hi Kilon, > > > On Thu, May 1, 2014 at 8:01 AM, kilon alios wrote: > >> I have further refined the About page but not I have also created >> additional pages for "language" and "ide" >> you can click on the main page on those words because they are links to >> send to you to the corresponding page or you can access these pages from >> here >> >> "The Language" >> >> http://thekilon.wix.com/pharo-about#!language/cee5 >> > > This is really good. My criticism is that "invented in 1969" implies it > hasn't changed that much since then. It has, and one of the biggest > changes was from Smalltalk-72 to Smalltalk-76. You might instead say > something like > "conceived in 1969, and stabilizing as Smalltalk-80 in the 1980's". > > One of the things I missed on first visit was the "fast moving forward" > section. I suggest you eliminate it and put the information in the first > section. > > But there are significant language developments since then: > > - traits > - namespaces > - closures > - ByteArray literals > - method pragmas/method tags > > and more to come: > - slots > > > I would replace the third section with something on the class library, > that it is large (numbers, collections, graphics, multi-media, etc, the > more the better) and mature. > > >> >> "The IDE" >> >> http://thekilon.wix.com/pharo-about#!ide/cfvg >> > > You don't say anything about the debugger. The debugger is of course > excellent and one of the few that allows programming in the debugger. That > deserves a sentence or two surely. > > >> >> >> >> Again these are drafts WIP , with many mistake and still with room for a >> lot of improvement. >> >> The good news is that I tried the website on my mobile phone and it seems >> it works well for mobile devices too >> >> >> On Thu, May 1, 2014 at 12:36 PM, kilon alios wrote: >> >>> I don't like the about page. Its still unclear what Pharo is and I have >>> to agree with the complains we are getting at reddit. >>> >>> So instead of starting a long conversation about how I would want it >>> done , I sat my ass down and made a draft of it so you can see it directly. >>> >>> Please bare in mind this is draft , I just wanted to show you my idea >>> for an About page. You can find the draft here >>> >>> http://thekilon.wix.com/pharo-about >>> >>> I think contributors should go to a seperate page called "Credit" >>> >>> I am open to comments and suggestions. >>> >> >> > > > -- > best, > Eliot >
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
Bravo Esteban! By the way, I have added a PharoExtras UIThemes project to Smalltalkhub, right in time it seems ;) About a morphic redesign, I just had a look at Cuis to see how was their Morphic. Thierry
Re: [Pharo-dev] Pharo 3.0 Released!
Hi eliot Thanks you all. I love this page http://www.pharo.org/about especially the contributors list :) Indeed. But "Pharo's goal is to deliver a clean, innovative, free open-source environment." is an environment for what? Not merely development, for deployment too, for a dynamic language? Why not "Pharo's goal is to deliver a clean, innovative, free open-source dynamic application development platform."? Indeed. I was on vacation when all the bus rmoders were pushing the web/release/ and my network was so slow that I could not even get the log button on the web-site :). Stef
Re: [Pharo-dev] Soon the LaserGame book for Pharo
Hi Steph, That is really great news. I _often_ direct people to the LaserGame tutorial even though its a bit awkward asking them to use an image seven years old (Squeak 3.9). A while ago I asked Steve for permission to update it for Pharo, but was discouraged to get no response at all. Perhaps my mail never made it through. I am interested in helping out, either directly with the conversion or as reviewer. Let me know. cheers -ben stepharo wrote: Hi guys Steve just told me that he is ok that we port his book to Pharo :) This is a great news. So I will start during my spare time. Stef Begin forwarded message: From: Stephan Wessels Subject: Re: [vwnc] Can this idea work Date: 24 Apr 2014 15:21:27 GMT+2 To: stephane ducasse Hi. Actually I got those requests and replied both times that you have my permission provided I'm credited or noted as the original author. Please go forward with it; it can only help the Smalltalk community. Sent from my iPhone On Apr 24, 2014, at 8:16 AM, stephane ducasse wrote: Hi steve I tried to contact you several times in the past but I got no answer. I would like to know if we can port the tutorial to Pharo and if we can turn it into a book to fit in the open-source book collection we are slowly building (SqueakbyExample, PharoByExample, Seaside, DeepintoPharo). Now since there is no license it is not clear that it is worth the effort. Stef On 22 Apr 2014, at 01:44, stevewessels wrote: As the author of the tutorial I'm not sure how I feel about my work being referred to as "old". The tutorial is remarkably still in use to this day. I still get emails from folks thanking me for it or reporting bugs. When the tutorial was written my intended audience was Smalltalk developers wanting to build Test Driven Development (TDD) skills. It was not intended for beginners. But as it turns out lots of beginners have slogged through it. The key concepts I tried to demonstrate were how to do TDD and building good models that were testable. I also wanted to show you could make stand-alone apps using Smalltalk/Squeak for the Mac. To convert the tutorial to VisualWorks might end up being a challenge, but alas, I haven't used VW since the late 90's and I know it's grown a whole lot since those days. So I cannot recommend how you go about doing it. You're welcome to send me questions about it and any design decisions that were made. I don't claim that it is a "proper OO design" or anything like that. Interestingly, I did port the design to Objective-C for the iPhone years ago and the basic design held up fine. The GUI was obviously done differently -- I ended up adopting OpenGL for the GUI. That was work. But it turned out well and has been in the App Store ever since. So if I can help you, drop me a note. -- View this message in context: http://forum.world.st/Can-this-idea-work-tp4753741p4755668.html Sent from the VisualWorks mailing list archive at Nabble.com. ___ vwnc mailing list v...@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Re: [Pharo-dev] Usage of should: in tests
Hi nicolas just because people do not know. I'm going over the tutorial of Steven Wessels and converting all the should: by assert: too. So I would just change everything and commit. Stef On 1/5/14 00:52, Nicolas Cellier wrote: Hi, I see many usage of #should: in SciSmalltalk tests that could simply be turned into #assert: or eventually #assert:equals: Why wanting to use a block? Other than #should:raise: and #shouldnt:raise:, I don't really see the point of #should: alone anyway... IMO should: should be deprecated, less is more. I'm possibly the author of several of these #should: sends, so don't take it personnally ;) P.S. or is it easier to restart the block in the Debugger? I cross post to pharo-dev because it's a generic question, and there are a few #should: sends in Pharo-3.0 too.
Re: [Pharo-dev] New Proposal for new Pharo website - About page (with example website)
Hi Kilon, On Thu, May 1, 2014 at 8:01 AM, kilon alios wrote: > I have further refined the About page but not I have also created > additional pages for "language" and "ide" > you can click on the main page on those words because they are links to > send to you to the corresponding page or you can access these pages from > here > > "The Language" > > http://thekilon.wix.com/pharo-about#!language/cee5 > This is really good. My criticism is that "invented in 1969" implies it hasn't changed that much since then. It has, and one of the biggest changes was from Smalltalk-72 to Smalltalk-76. You might instead say something like "conceived in 1969, and stabilizing as Smalltalk-80 in the 1980's". One of the things I missed on first visit was the "fast moving forward" section. I suggest you eliminate it and put the information in the first section. But there are significant language developments since then: - traits - namespaces - closures - ByteArray literals - method pragmas/method tags and more to come: - slots I would replace the third section with something on the class library, that it is large (numbers, collections, graphics, multi-media, etc, the more the better) and mature. > > "The IDE" > > http://thekilon.wix.com/pharo-about#!ide/cfvg > You don't say anything about the debugger. The debugger is of course excellent and one of the few that allows programming in the debugger. That deserves a sentence or two surely. > > > > Again these are drafts WIP , with many mistake and still with room for a > lot of improvement. > > The good news is that I tried the website on my mobile phone and it seems > it works well for mobile devices too > > > On Thu, May 1, 2014 at 12:36 PM, kilon alios wrote: > >> I don't like the about page. Its still unclear what Pharo is and I have >> to agree with the complains we are getting at reddit. >> >> So instead of starting a long conversation about how I would want it done >> , I sat my ass down and made a draft of it so you can see it directly. >> >> Please bare in mind this is draft , I just wanted to show you my idea for >> an About page. You can find the draft here >> >> http://thekilon.wix.com/pharo-about >> >> I think contributors should go to a seperate page called "Credit" >> >> I am open to comments and suggestions. >> > > -- best, Eliot
Re: [Pharo-dev] Pharo renamed to "MuchTalk"
Holy smoley! 117 emails since I checked a few hours ago? Maybe we should rename Pharo “Prolix”? :-) Hi oscar Would match well with axterix :) Stef on
Re: [Pharo-dev] Pharo 3.0 Released!
Thank you so much guys. I am already using it :) Loving it already. On Thu, May 1, 2014 at 1:03 PM, Eliot Miranda wrote: > Hi Stéph, > > > On Thu, May 1, 2014 at 1:35 AM, stepharo wrote: > >> Thanks you all. I love this page >> >> http://www.pharo.org/about >> especially the contributors list :) >> > > Indeed. But > "Pharo's goal is to deliver a clean, innovative, free open-source > environment." > is an environment for what? Not merely development, for deployment too, > for a dynamic language? > > Why not "Pharo's goal is to deliver a clean, innovative, free open-source > dynamic application development platform."? > > > -- > best, > Eliot > -- Mariano http://marianopeck.wordpress.com
Re: [Pharo-dev] Pharo 3.0 Released!
Hi Stéph, On Thu, May 1, 2014 at 1:35 AM, stepharo wrote: > Thanks you all. I love this page > > http://www.pharo.org/about > especially the contributors list :) > Indeed. But "Pharo's goal is to deliver a clean, innovative, free open-source environment." is an environment for what? Not merely development, for deployment too, for a dynamic language? Why not "Pharo's goal is to deliver a clean, innovative, free open-source dynamic application development platform."? -- best, Eliot
Re: [Pharo-dev] New Proposal for new Pharo website - About page (with example website)
I have further refined the About page but not I have also created additional pages for "language" and "ide" you can click on the main page on those words because they are links to send to you to the corresponding page or you can access these pages from here "The Language" http://thekilon.wix.com/pharo-about#!language/cee5 "The IDE" http://thekilon.wix.com/pharo-about#!ide/cfvg Again these are drafts WIP , with many mistake and still with room for a lot of improvement. The good news is that I tried the website on my mobile phone and it seems it works well for mobile devices too On Thu, May 1, 2014 at 12:36 PM, kilon alios wrote: > I don't like the about page. Its still unclear what Pharo is and I have to > agree with the complains we are getting at reddit. > > So instead of starting a long conversation about how I would want it done > , I sat my ass down and made a draft of it so you can see it directly. > > Please bare in mind this is draft , I just wanted to show you my idea for > an About page. You can find the draft here > > http://thekilon.wix.com/pharo-about > > I think contributors should go to a seperate page called "Credit" > > I am open to comments and suggestions. >
[Pharo-dev] Sound input does not work
Hello Pharoers, I am trying to play with sound in Pharo v3.0, and the sound input does not work. I tried: SpectrumAnalyzerMorph new openInWorld Cheers, -- ~~Jannik Laval~~ École des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://www.phratch.com http://car.mines-douai.fr/
Re: [Pharo-dev] Pharo crashes
And please don't take this as a criticism. It's more my anxiety. I appreciate it :)
Re: [Pharo-dev] [ANN]: Little NeoJSON Helper
sean May be we can add that to the JSOn chapter. Are you interested? Stef On 30/4/14 16:28, Sean P. DeNigris wrote: Okay, here is version 0.1 - the most basic useful functionality to aid in writing mappings. "Assuming Neo-JSON-Core is loaded" Gofer it smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; package: 'Neo-JSON-Utilities'; load. Now if you: reader := NeoJSONReader on: entity contents readStream. reader nextAs: MyClass "(that does not implement MyClass class>>#neoJsonMapping:)". You will get a debugger (which you probably want to close because the new mappings we create will not be activated as the helper hook is cached in the mappings) and a tree inspector on a NeoJSON model that you can customize, where: - a NeoJSONObject represents each JSON dictionary; for the enclosing object, the schema is already set to MyClass (i.e. the argument to #nextAs:) - a NeoJSONList represents each JSON list - a NeoJSONValue represents all other values e.g. bools, nil, strings, numbers Some useful things to do: - For each NeoJSONObject that you want to map to a class, select it in the explorer and: self schema: MyOtherClass. self generateInstVars. "self explanatory?" self mappingSourceCode inspect. "see the neoJsonMapping: source that would be generated" self generateMapping. "compile class-side neoJsonMapping:" - Select any field inside a NeoJSONObject that you want to map to an inst var with a different name and: self instVarName: #isSaved "(e.g. to map JSON fields_with_underscores to camelCase var names)" - Specify the element type of a list by selecting it and: self elementSchema: MyListReturnType. "This will automatically set the schema to #ArrayOfMyListReturnType, but you can change that manually if you want by sending #schema:) After customizing, sending #generateMapping to a NeoJSONObject should generate something like: neoJsonMapping: mapper mapper for: self do: [ :mapping | mapping mapInstVars: #(notes id). (mapping mapInstVar: #day) valueSchema: Date. (mapping mapInstVar: #events) valueSchema: #ArrayOfMyEvent. mapping mapInstVar: #isSaved to: #is_saved. (mapping mapInstVar: #timeSaved) valueSchema: DateAndTime ]. mapper for: Date customDo: [ :mapping | ]. "now you specify how to convert the string to a Date" mapper for: #ArrayOfMyEvent customDo: [ :mapping | mapping listOfElementSchema: MyEvent ]. mapper for: DateAndTime customDo: [ :mapping | ]. "same as Date above" This started as a tiny little personal experiment that got away from me, ha ha, so there is no UI, tests, or doc (except for this post). MIT of course. Enjoy!
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
On 01 May 2014, at 14:51, kilon alios wrote: > Esteban you are awesome, VIP of Pharo :) > > If there was one thing of Pharo that got in my nerves it was the white theme. > So tiring to my eyes it was the No 1 for me. > > What I can say about this dark theme, its amazing. The colors are right, I > love the syntax highlighting colors , I love it , love and love it. > > I have installed , I see no problems so far, I will keep using it from now on > a report back any problems. The thing I see is that class icons contain some > white in their edges which of course does not fit with the theme, but for a > hack its still awesome. > > Thank you , thank you and thank you. > > At last I can clearly see the scroll bars. > > Hm i found a problem, tried to open the help browser it asked for my name but > the input box is white and so i could not see what i was typing. thanks, I’m very glad you enjoy it :) yes. Pavel told me that… think is that I always set the author in preferences, so I never see that dialog (and therefore, I do not change it). I will fix it :) Esteban > > > On Thu, May 1, 2014 at 3:29 PM, Esteban Lorenzano wrote: > > On 01 May 2014, at 14:23, p...@highoctane.be wrote: > >> Yes!! >> >> Esteban, you really made my day on this one. >> > > you are welcome :) >> The good thing is also that with your changes we can spot where to look for >> changing all we want now. >> > > yes, the idea was to make a dark theme possible by removing hardcoded > colorisation and dumb things (I like current one, but the most important is > that now *it is* possible to play with themes for real). > > now, we need to think how we can actually integrate the changes to the image > (I suppose not in the way it is done now, as I said… it is mostly a hack). > > Esteban > >> Thanks again. >> >> Phil >> >> Le 1 mai 2014 14:08, "Sven Van Caekenberghe" a écrit : >> > >> > Wow! >> > >> > This will make a couple of people very happy, and it is quite impressive. >> > >> > Seriously, you found time to finish this while labouring during days on >> > the Pharo 3 release, are you sure you are not extra-terrestial ? >> > >> > Works like a charm : >> > >> > >> > Thanks. >> > >> > Sven >> > >> > PS: Yes, we should do the effort to make it possible to do this for real >> > (clean). >> > >> > On 01 May 2014, at 13:24, Esteban Lorenzano wrote: >> > >> >> Dark Theme for Pharo 3 >> >> == >> >> >> >> So, I finally took some time and hacked a Dark Theme for Pharo 3: >> >> >> >> >> >> >> >> How you install it? You need to execute this script: >> >> >> >> “1. You need this because otherwise Gofer merge becomes dumb :P" >> >> MCRepositoryGroup default >> >> addRepository: (MCSmalltalkhubRepository >> >> owner: 'estebanlm' >> >> project: 'Pharo3DarkTheme'). >> >> “2. Now we can actually MERGE the project" >> >> Gofer it >> >> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; >> >> package: 'Pharo3DarkTheme'; >> >> merge. >> >> “3. And then install it" >> >> Pharo3DarkTheme installFullTheme. >> >> >> >> WARNING 1: You need to do a merge (notice the script) >> >> WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for >> >> details. >> >> WARNING 3: This changes something in the Pharo3Theme too... so you can go >> >> back after installing, but not completely :) >> >> >> >> Considerations >> >> -- >> >> >> >> It can look like an easy task, to make a theme over a non native GUI like >> >> Pharo, but let me tell you: It is not. There are a lot of glitches and >> >> errors of design you have to overcome to get a working version of a >> >> theme. This is a pitty because we claim that our system is clean (or >> >> should be clean) and easy to understand. >> >> >> >> But all the Morphic implementation is a hack over a hack, with >> >> preconcepts and hardcodes everywhere, up to a point that to make the >> >> smallest change is an incredibly annoying task. >> >> >> >> Then... I added ""yet another hack"" to this infinite list. I made it >> >> because we need something like this, even if not a good solution. And I >> >> also made it to start a debate into our community. I truly believe that >> >> Morphic was a great idea, but I also believe that current implementation >> >> is doomed. I would like to discuss a new implementation, with a good >> >> design (for example I believe it should be a clear separation between a >> >> morph and it's skin, making easy the actual-hard task of changing a >> >> colorset). >> >> I also believe there will be a clear separation between what is a Morph >> >> (a graphical unit) and a Widget (who at the time should use morphs, but >> >> that's another story). >> >> Etc., etc., etc. >> >> >> >> So, will we start the longtime postponed effort of effectively replace >> >> current Morphic? >> >> >> >> In the mean time, enjoy the theme. Is so cool that I'm considering making
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
Esteban you are awesome, VIP of Pharo :) If there was one thing of Pharo that got in my nerves it was the white theme. So tiring to my eyes it was the No 1 for me. What I can say about this dark theme, its amazing. The colors are right, I love the syntax highlighting colors , I love it , love and love it. I have installed , I see no problems so far, I will keep using it from now on a report back any problems. The thing I see is that class icons contain some white in their edges which of course does not fit with the theme, but for a hack its still awesome. Thank you , thank you and thank you. At last I can clearly see the scroll bars. Hm i found a problem, tried to open the help browser it asked for my name but the input box is white and so i could not see what i was typing. On Thu, May 1, 2014 at 3:29 PM, Esteban Lorenzano wrote: > > On 01 May 2014, at 14:23, p...@highoctane.be wrote: > > Yes!! > > Esteban, you really made my day on this one. > > you are welcome :) > > The good thing is also that with your changes we can spot where to look > for changing all we want now. > > yes, the idea was to make a dark theme possible by removing hardcoded > colorisation and dumb things (I like current one, but the most important is > that now *it is* possible to play with themes for real). > > now, we need to think how we can actually integrate the changes to the > image (I suppose not in the way it is done now, as I said… it is mostly a > hack). > > Esteban > > Thanks again. > > Phil > > Le 1 mai 2014 14:08, "Sven Van Caekenberghe" a écrit : > > > > Wow! > > > > This will make a couple of people very happy, and it is quite impressive. > > > > Seriously, you found time to finish this while labouring during days on > the Pharo 3 release, are you sure you are not extra-terrestial ? > > > > Works like a charm : > > > > > > Thanks. > > > > Sven > > > > PS: Yes, we should do the effort to make it possible to do this for real > (clean). > > > > On 01 May 2014, at 13:24, Esteban Lorenzano wrote: > > > >> Dark Theme for Pharo 3 > >> == > >> > >> So, I finally took some time and hacked a Dark Theme for Pharo 3: > >> > >> > >> > >> How you install it? You need to execute this script: > >> > >> “1. You need this because otherwise Gofer merge becomes dumb :P" > >> MCRepositoryGroup default > >> addRepository: (MCSmalltalkhubRepository > >> owner: 'estebanlm' > >> project: 'Pharo3DarkTheme'). > >> “2. Now we can actually MERGE the project" > >> Gofer it > >> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; > >> package: 'Pharo3DarkTheme'; > >> merge. > >> “3. And then install it" > >> Pharo3DarkTheme installFullTheme. > >> > >> WARNING 1: You need to do a merge (notice the script) > >> WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for > details. > >> WARNING 3: This changes something in the Pharo3Theme too... so you can > go back after installing, but not completely :) > >> > >> Considerations > >> -- > >> > >> It can look like an easy task, to make a theme over a non native GUI > like Pharo, but let me tell you: It is not. There are a lot of glitches and > errors of design you have to overcome to get a working version of a theme. > This is a pitty because we claim that our system is clean (or should be > clean) and easy to understand. > >> > >> But all the Morphic implementation is a hack over a hack, with > preconcepts and hardcodes everywhere, up to a point that to make the > smallest change is an incredibly annoying task. > >> > >> Then... I added ""yet another hack"" to this infinite list. I made it > because we need something like this, even if not a good solution. And I > also made it to start a debate into our community. I truly believe > that Morphic was a great idea, but I also believe that current > implementation is doomed. I would like to discuss a new implementation, > with a good design (for example I believe it should be a clear > separation between a morph and it's skin, making easy the actual-hard task > of changing a colorset). > >> I also believe there will be a clear separation between what is a Morph > (a graphical unit) and a Widget (who at the time should use morphs, but > that's another story). > >> Etc., etc., etc. > >> > >> So, will we start the longtime postponed effort of effectively replace > current Morphic? > >> > >> In the mean time, enjoy the theme. Is so cool that I'm considering > making it my default theme :P > >> > >> Esteban > >> > > > > >
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
On 01 May 2014, at 14:23, p...@highoctane.be wrote: > Yes!! > > Esteban, you really made my day on this one. > you are welcome :) > The good thing is also that with your changes we can spot where to look for > changing all we want now. > yes, the idea was to make a dark theme possible by removing hardcoded colorisation and dumb things (I like current one, but the most important is that now *it is* possible to play with themes for real). now, we need to think how we can actually integrate the changes to the image (I suppose not in the way it is done now, as I said… it is mostly a hack). Esteban > Thanks again. > > Phil > > Le 1 mai 2014 14:08, "Sven Van Caekenberghe" a écrit : > > > > Wow! > > > > This will make a couple of people very happy, and it is quite impressive. > > > > Seriously, you found time to finish this while labouring during days on the > > Pharo 3 release, are you sure you are not extra-terrestial ? > > > > Works like a charm : > > > > > > Thanks. > > > > Sven > > > > PS: Yes, we should do the effort to make it possible to do this for real > > (clean). > > > > On 01 May 2014, at 13:24, Esteban Lorenzano wrote: > > > >> Dark Theme for Pharo 3 > >> == > >> > >> So, I finally took some time and hacked a Dark Theme for Pharo 3: > >> > >> > >> > >> How you install it? You need to execute this script: > >> > >> “1. You need this because otherwise Gofer merge becomes dumb :P" > >> MCRepositoryGroup default > >> addRepository: (MCSmalltalkhubRepository > >> owner: 'estebanlm' > >> project: 'Pharo3DarkTheme'). > >> “2. Now we can actually MERGE the project" > >> Gofer it > >> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; > >> package: 'Pharo3DarkTheme'; > >> merge. > >> “3. And then install it" > >> Pharo3DarkTheme installFullTheme. > >> > >> WARNING 1: You need to do a merge (notice the script) > >> WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for > >> details. > >> WARNING 3: This changes something in the Pharo3Theme too... so you can go > >> back after installing, but not completely :) > >> > >> Considerations > >> -- > >> > >> It can look like an easy task, to make a theme over a non native GUI like > >> Pharo, but let me tell you: It is not. There are a lot of glitches and > >> errors of design you have to overcome to get a working version of a theme. > >> This is a pitty because we claim that our system is clean (or should be > >> clean) and easy to understand. > >> > >> But all the Morphic implementation is a hack over a hack, with preconcepts > >> and hardcodes everywhere, up to a point that to make the smallest change > >> is an incredibly annoying task. > >> > >> Then... I added ""yet another hack"" to this infinite list. I made it > >> because we need something like this, even if not a good solution. And I > >> also made it to start a debate into our community. I truly believe that > >> Morphic was a great idea, but I also believe that current implementation > >> is doomed. I would like to discuss a new implementation, with a good > >> design (for example I believe it should be a clear separation between a > >> morph and it's skin, making easy the actual-hard task of changing a > >> colorset). > >> I also believe there will be a clear separation between what is a Morph (a > >> graphical unit) and a Widget (who at the time should use morphs, but > >> that's another story). > >> Etc., etc., etc. > >> > >> So, will we start the longtime postponed effort of effectively replace > >> current Morphic? > >> > >> In the mean time, enjoy the theme. Is so cool that I'm considering making > >> it my default theme :P > >> > >> Esteban > >> > >
Re: [Pharo-dev] [Pharo-users] [ANN] Pharo3 Dark Theme is available
On 01 May 2014, at 14:07, Sven Van Caekenberghe wrote: > Wow! > > This will make a couple of people very happy, and it is quite impressive. thanks! yes I made it for Phil and Yuriy :) > > Seriously, you found time to finish this while labouring during days on the > Pharo 3 release, are you sure you are not extra-terrestial ? well.. there were some dead moments while waiting for things to be ready (but I wasn’t able to work on more complicated things, I needed to keep my concentration on the release)… and then I have insomnia :P Esteban > > Works like a charm : > > > > Thanks. > > Sven > > PS: Yes, we should do the effort to make it possible to do this for real > (clean). > > On 01 May 2014, at 13:24, Esteban Lorenzano wrote: > >> Dark Theme for Pharo 3 >> == >> >> So, I finally took some time and hacked a Dark Theme for Pharo 3: >> >> >> >> How you install it? You need to execute this script: >> >> “1. You need this because otherwise Gofer merge becomes dumb :P" >> MCRepositoryGroup default >> addRepository: (MCSmalltalkhubRepository >> owner: 'estebanlm' >> project: 'Pharo3DarkTheme'). >> “2. Now we can actually MERGE the project" >> Gofer it >> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; >> package: 'Pharo3DarkTheme'; >> merge. >> “3. And then install it" >> Pharo3DarkTheme installFullTheme. >> >> WARNING 1: You need to do a merge (notice the script) >> WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details. >> WARNING 3: This changes something in the Pharo3Theme too... so you can go >> back after installing, but not completely :) >> >> Considerations >> -- >> >> It can look like an easy task, to make a theme over a non native GUI like >> Pharo, but let me tell you: It is not. There are a lot of glitches and >> errors of design you have to overcome to get a working version of a theme. >> This is a pitty because we claim that our system is clean (or should be >> clean) and easy to understand. >> >> But all the Morphic implementation is a hack over a hack, with preconcepts >> and hardcodes everywhere, up to a point that to make the smallest change is >> an incredibly annoying task. >> >> Then... I added ""yet another hack"" to this infinite list. I made it >> because we need something like this, even if not a good solution. And I also >> made it to start a debate into our community. I truly believe that Morphic >> was a great idea, but I also believe that current implementation is doomed. >> I would like to discuss a new implementation, with a good design (for >> example I believe it should be a clear separation between a morph and it's >> skin, making easy the actual-hard task of changing a colorset). >> I also believe there will be a clear separation between what is a Morph (a >> graphical unit) and a Widget (who at the time should use morphs, but that's >> another story). >> Etc., etc., etc. >> >> So, will we start the longtime postponed effort of effectively replace >> current Morphic? >> >> In the mean time, enjoy the theme. Is so cool that I'm considering making it >> my default theme :P >> >> Esteban >> >
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
Yes!! Esteban, you really made my day on this one. The good thing is also that with your changes we can spot where to look for changing all we want now. Thanks again. Phil Le 1 mai 2014 14:08, "Sven Van Caekenberghe" a écrit : > > Wow! > > This will make a couple of people very happy, and it is quite impressive. > > Seriously, you found time to finish this while labouring during days on the Pharo 3 release, are you sure you are not extra-terrestial ? > > Works like a charm : > > > Thanks. > > Sven > > PS: Yes, we should do the effort to make it possible to do this for real (clean). > > On 01 May 2014, at 13:24, Esteban Lorenzano wrote: > >> Dark Theme for Pharo 3 >> == >> >> So, I finally took some time and hacked a Dark Theme for Pharo 3: >> >> >> >> How you install it? You need to execute this script: >> >> “1. You need this because otherwise Gofer merge becomes dumb :P" >> MCRepositoryGroup default >> addRepository: (MCSmalltalkhubRepository >> owner: 'estebanlm' >> project: 'Pharo3DarkTheme'). >> “2. Now we can actually MERGE the project" >> Gofer it >> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; >> package: 'Pharo3DarkTheme'; >> merge. >> “3. And then install it" >> Pharo3DarkTheme installFullTheme. >> >> WARNING 1: You need to do a merge (notice the script) >> WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details. >> WARNING 3: This changes something in the Pharo3Theme too... so you can go back after installing, but not completely :) >> >> Considerations >> -- >> >> It can look like an easy task, to make a theme over a non native GUI like Pharo, but let me tell you: It is not. There are a lot of glitches and errors of design you have to overcome to get a working version of a theme. This is a pitty because we claim that our system is clean (or should be clean) and easy to understand. >> >> But all the Morphic implementation is a hack over a hack, with preconcepts and hardcodes everywhere, up to a point that to make the smallest change is an incredibly annoying task. >> >> Then... I added ""yet another hack"" to this infinite list. I made it because we need something like this, even if not a good solution. And I also made it to start a debate into our community. I truly believe that Morphic was a great idea, but I also believe that current implementation is doomed. I would like to discuss a new implementation, with a good design (for example I believe it should be a clear separation between a morph and it's skin, making easy the actual-hard task of changing a colorset). >> I also believe there will be a clear separation between what is a Morph (a graphical unit) and a Widget (who at the time should use morphs, but that's another story). >> Etc., etc., etc. >> >> So, will we start the longtime postponed effort of effectively replace current Morphic? >> >> In the mean time, enjoy the theme. Is so cool that I'm considering making it my default theme :P >> >> Esteban >> >
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
Very cool. Thank you, Esteban! Uko On 01 May 2014, at 13:24, Esteban Lorenzano wrote: > Dark Theme for Pharo 3 > == > > So, I finally took some time and hacked a Dark Theme for Pharo 3: > > > > How you install it? You need to execute this script: > > “1. You need this because otherwise Gofer merge becomes dumb :P" > MCRepositoryGroup default > addRepository: (MCSmalltalkhubRepository > owner: 'estebanlm' > project: 'Pharo3DarkTheme'). > “2. Now we can actually MERGE the project" > Gofer it > smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; > package: 'Pharo3DarkTheme'; > merge. > “3. And then install it" > Pharo3DarkTheme installFullTheme. > > WARNING 1: You need to do a merge (notice the script) > WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details. > WARNING 3: This changes something in the Pharo3Theme too... so you can go > back after installing, but not completely :) > > Considerations > -- > > It can look like an easy task, to make a theme over a non native GUI like > Pharo, but let me tell you: It is not. There are a lot of glitches and errors > of design you have to overcome to get a working version of a theme. This is a > pitty because we claim that our system is clean (or should be clean) and easy > to understand. > > But all the Morphic implementation is a hack over a hack, with preconcepts > and hardcodes everywhere, up to a point that to make the smallest change is > an incredibly annoying task. > > Then... I added ""yet another hack"" to this infinite list. I made it because > we need something like this, even if not a good solution. And I also made it > to start a debate into our community. I truly believe that Morphic was a > great idea, but I also believe that current implementation is doomed. I would > like to discuss a new implementation, with a good design (for example I > believe it should be a clear separation between a morph and it's skin, making > easy the actual-hard task of changing a colorset). > I also believe there will be a clear separation between what is a Morph (a > graphical unit) and a Widget (who at the time should use morphs, but that's > another story). > Etc., etc., etc. > > So, will we start the longtime postponed effort of effectively replace > current Morphic? > > In the mean time, enjoy the theme. Is so cool that I'm considering making it > my default theme :P > > Esteban >
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
Likey!! Now to find some time to actually install it and see if it works for me :) Cheers, Sergi 2014-05-01 12:47 GMT+01:00 Esteban Lorenzano : > ahhh… forget to say. There will be missing changes (my workflow is > covered, but that does not means all Pharo). > Please, report it and I will fix it as soon as I can. > > cheers, > Esteban > > On 01 May 2014, at 13:24, Esteban Lorenzano wrote: > > Dark Theme for Pharo 3 > == > > So, I finally took some time and hacked a Dark Theme for Pharo 3: > > > > How you install it? You need to execute this script: > > “1. You need this because otherwise Gofer merge becomes dumb :P" > MCRepositoryGroup default > addRepository: (MCSmalltalkhubRepository > owner: 'estebanlm' > project: 'Pharo3DarkTheme'). > “2. Now we can actually MERGE the project" > Gofer it > smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; > package: 'Pharo3DarkTheme'; > merge. > “3. And then install it" > Pharo3DarkTheme installFullTheme. > > > *WARNING 1:* You need to do a merge (notice the script) > *WARNING 2:* Yes, this is a HACK (also: an ugly hack). See below for > details. > *WARNING 3:* This changes something in the Pharo3Theme too... so you can > go back after installing, but not completely :) > > Considerations > -- > > It can look like an easy task, to make a theme over a non native GUI like > Pharo, but let me tell you: It is not. There are a lot of glitches and > errors of design you have to overcome to get a working version of a theme. > This is a pitty because we claim that our system is clean (or should be > clean) and easy to understand. > > But all the Morphic implementation is a hack over a hack, with preconcepts > and hardcodes everywhere, up to a point that to make the smallest change is > an incredibly annoying task. > > Then... I added ""yet another hack"" to this infinite list. I made it > because we need something like this, even if not a good solution. And I > also made it to start a debate into our community. I truly believe that > Morphic was a great idea, but I also believe that current implementation is > doomed. I would like to discuss a new implementation, with a good design > (for example I believe it should be a clear separation between a morph and > it's skin, making easy the actual-hard task of changing a colorset). > I also believe there will be a clear separation between what is a Morph (a > graphical unit) and a Widget (who at the time should use morphs, but that's > another story). > Etc., etc., etc. > > So, will we start the longtime postponed effort of effectively replace > current Morphic? > > In the mean time, enjoy the theme. Is so cool that I'm considering making > it my default theme :P > > Esteban > > >
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
ahhh… forget to say. There will be missing changes (my workflow is covered, but that does not means all Pharo). Please, report it and I will fix it as soon as I can. cheers, Esteban On 01 May 2014, at 13:24, Esteban Lorenzano wrote: > Dark Theme for Pharo 3 > == > > So, I finally took some time and hacked a Dark Theme for Pharo 3: > > > > How you install it? You need to execute this script: > > “1. You need this because otherwise Gofer merge becomes dumb :P" > MCRepositoryGroup default > addRepository: (MCSmalltalkhubRepository > owner: 'estebanlm' > project: 'Pharo3DarkTheme'). > “2. Now we can actually MERGE the project" > Gofer it > smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; > package: 'Pharo3DarkTheme'; > merge. > “3. And then install it" > Pharo3DarkTheme installFullTheme. > > WARNING 1: You need to do a merge (notice the script) > WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details. > WARNING 3: This changes something in the Pharo3Theme too... so you can go > back after installing, but not completely :) > > Considerations > -- > > It can look like an easy task, to make a theme over a non native GUI like > Pharo, but let me tell you: It is not. There are a lot of glitches and errors > of design you have to overcome to get a working version of a theme. This is a > pitty because we claim that our system is clean (or should be clean) and easy > to understand. > > But all the Morphic implementation is a hack over a hack, with preconcepts > and hardcodes everywhere, up to a point that to make the smallest change is > an incredibly annoying task. > > Then... I added ""yet another hack"" to this infinite list. I made it because > we need something like this, even if not a good solution. And I also made it > to start a debate into our community. I truly believe that Morphic was a > great idea, but I also believe that current implementation is doomed. I would > like to discuss a new implementation, with a good design (for example I > believe it should be a clear separation between a morph and it's skin, making > easy the actual-hard task of changing a colorset). > I also believe there will be a clear separation between what is a Morph (a > graphical unit) and a Widget (who at the time should use morphs, but that's > another story). > Etc., etc., etc. > > So, will we start the longtime postponed effort of effectively replace > current Morphic? > > In the mean time, enjoy the theme. Is so cool that I'm considering making it > my default theme :P > > Esteban >
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
Very well done! Nico Esteban Lorenzano writes: > Dark Theme for Pharo 3 > == > > So, I finally took some time and hacked a Dark Theme for Pharo 3: > > > > How you install it? You need to execute this script: > > “1. You need this because otherwise Gofer merge becomes dumb :P" > MCRepositoryGroup default > addRepository: (MCSmalltalkhubRepository > owner: 'estebanlm' > project: 'Pharo3DarkTheme'). > “2. Now we can actually MERGE the project" > Gofer it > smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; > package: 'Pharo3DarkTheme'; > merge. > “3. And then install it" > Pharo3DarkTheme installFullTheme. > > WARNING 1: You need to do a merge (notice the script) > WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details. > WARNING 3: This changes something in the Pharo3Theme too... so you can go > back after installing, but not completely :) > > Considerations > -- > > It can look like an easy task, to make a theme over a non native GUI like > Pharo, but let me tell you: It is not. There are a lot of glitches and errors > of design you have to overcome to get a working version of a theme. This is a > pitty because we claim that our system is clean (or should be clean) and easy > to understand. > > But all the Morphic implementation is a hack over a hack, with preconcepts > and hardcodes everywhere, up to a point that to make the smallest change is > an incredibly annoying task. > > Then... I added ""yet another hack"" to this infinite list. I made it because > we need something like this, even if not a good solution. And I also made it > to start a debate into our community. I truly believe that Morphic was a > great idea, but I also believe that current implementation is doomed. I would > like to discuss a new implementation, with a good design (for example I > believe it should be a clear separation between a morph and it's skin, making > easy the actual-hard task of changing a colorset). > I also believe there will be a clear separation between what is a Morph (a > graphical unit) and a Widget (who at the time should use morphs, but that's > another story). > Etc., etc., etc. > > So, will we start the longtime postponed effort of effectively replace > current Morphic? > > In the mean time, enjoy the theme. Is so cool that I'm considering making it > my default theme :P > > Esteban -- Nicolas Petton http://nicolas-petton.fr
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
… and I made a blog post with it :P http://smallworks.eu/web/blog/2014-05-01-dark-theme-for-pharo On 01 May 2014, at 13:24, Esteban Lorenzano wrote: > Dark Theme for Pharo 3 > == > > So, I finally took some time and hacked a Dark Theme for Pharo 3: > > > > How you install it? You need to execute this script: > > “1. You need this because otherwise Gofer merge becomes dumb :P" > MCRepositoryGroup default > addRepository: (MCSmalltalkhubRepository > owner: 'estebanlm' > project: 'Pharo3DarkTheme'). > “2. Now we can actually MERGE the project" > Gofer it > smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; > package: 'Pharo3DarkTheme'; > merge. > “3. And then install it" > Pharo3DarkTheme installFullTheme. > > WARNING 1: You need to do a merge (notice the script) > WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details. > WARNING 3: This changes something in the Pharo3Theme too... so you can go > back after installing, but not completely :) > > Considerations > -- > > It can look like an easy task, to make a theme over a non native GUI like > Pharo, but let me tell you: It is not. There are a lot of glitches and errors > of design you have to overcome to get a working version of a theme. This is a > pitty because we claim that our system is clean (or should be clean) and easy > to understand. > > But all the Morphic implementation is a hack over a hack, with preconcepts > and hardcodes everywhere, up to a point that to make the smallest change is > an incredibly annoying task. > > Then... I added ""yet another hack"" to this infinite list. I made it because > we need something like this, even if not a good solution. And I also made it > to start a debate into our community. I truly believe that Morphic was a > great idea, but I also believe that current implementation is doomed. I would > like to discuss a new implementation, with a good design (for example I > believe it should be a clear separation between a morph and it's skin, making > easy the actual-hard task of changing a colorset). > I also believe there will be a clear separation between what is a Morph (a > graphical unit) and a Widget (who at the time should use morphs, but that's > another story). > Etc., etc., etc. > > So, will we start the longtime postponed effort of effectively replace > current Morphic? > > In the mean time, enjoy the theme. Is so cool that I'm considering making it > my default theme :P > > Esteban >
Re: [Pharo-dev] Pharo 3.0 / Roassal2 / Ubuntu
> Yes yes yes ... it works. I quickly jumped through some examples. Roassal2 > looks so nice. Thank you. Let me know how it goes. Documentation is missing, but we have many many examples… The chapter in Deep into Pharo (www.deepintopharo.com) contains a documentation about Roassal1 and the Mondrian builder, written on top of the core of Roassal. Roassal2 is largely compatible with Roassal1. When it is not, then small changes have to be made. Alexandre > > > > Am 01.05.2014 03:31, schrieb Alexandre Bergel: >> Hi Volkert, >> >> You need to install the true type font. Unfortunately, Pharo3 does not do it >> for you. I guess this will be fixed in the next release of Pharo. >> >> I have made a very short video on how to install Roassal2 from scratch: >> https://dl.dropboxusercontent.com/u/31543901/TMP/InstallingTrueTypeFont.mov >> >> Let us know how it goes. >> >> Alexandre >> >> >> On Apr 30, 2014, at 2:53 PM, volk...@nivoba.de wrote: >> >>> Dear all, >>> >>> i just downloaded Pharo 3.0 and installed Roassal2 via Configuration >>> Manager (Stable Version). >>> When trying the "Roassal examples" (from Tool-Menu) i got an red screen. >>> >>> Platform Ubuntu 14.04LTS >>> Pharo3.0 Latest update: #30846 >>> >>> Need some help :-) >>> >>> BW, >>> Volkert >>> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Re: [Pharo-dev] Pharo 3.0 / Roassal2 / Ubuntu
Thanks Marcus, Alexandre On May 1, 2014, at 5:07 AM, Marcus Denker wrote: > > On 01 May 2014, at 09:36, Sven Van Caekenberghe wrote: > >> Nice, let's copy that to the Pharo YouTube channel… >> > Done: > > https://www.youtube.com/watch?v=8wQjFzy8tj0 > > >> On 01 May 2014, at 03:31, Alexandre Bergel wrote: >> >>> Hi Volkert, >>> >>> You need to install the true type font. Unfortunately, Pharo3 does not do >>> it for you. I guess this will be fixed in the next release of Pharo. >>> >>> I have made a very short video on how to install Roassal2 from scratch: >>> https://dl.dropboxusercontent.com/u/31543901/TMP/InstallingTrueTypeFont.mov >>> >>> Let us know how it goes. >>> >>> Alexandre >>> >>> >>> On Apr 30, 2014, at 2:53 PM, volk...@nivoba.de wrote: >>> Dear all, i just downloaded Pharo 3.0 and installed Roassal2 via Configuration Manager (Stable Version). When trying the "Roassal examples" (from Tool-Menu) i got an red screen. Platform Ubuntu 14.04LTS Pharo3.0 Latest update: #30846 Need some help :-) BW, Volkert >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Re: [Pharo-dev] Pharo is Smalltalk… and Not
+1 I understand the part about making Pharo appeal more to the wider audience in this decade and ahead Let me put in the effort in making that happen, before I say another word on this. Making a platform that I can be most productive in be the most accepted one across the industry is a big win for me... On Thu, May 1, 2014 at 2:20 AM, Sean P. DeNigris wrote: > Here's my musings about how we integrate the two motives - to acknowledge > our > heritage /and/ break out of our pigeon hole. My key point here is to > gradually introduce the Smalltalk part after people are deep enough to have > gotten excited about the ideas without dismissing them because of cultural > baggage... > > Drilling down: > 1. Sound bite: "Pharo - The immersive programming experience" > 2. Why Pharo: (about a paragraph, like the one on the site now, "Pharo > gives > you immediate and total control over your programming experience..." > 3. What is it. Here we can accurately paint the nuanced picture, > distinguishing Smalltalk as an idea based on design principles vs. > Smalltalk-80. If "Smalltalk" more exactly means an environment + libraries > + > a language (I think that order is important - the syntax was always the > least interesting thing about Smalltalk). What we might really say if we > had > the time to go beyond an initial sound bite is: > Pharo is: > - a [pick 2 or 3 of: dynamic, open, immersive, live] environment > (like an > IDE and OS rolled into one) > - beautifully designed core libraries including a web > client/server, FFI, > Y, Z... > - a dialect of the Smalltalk programming language > > For #1, the inspiration is most accurately the Dynabook > For #2, IMHO enough components have been rewritten to stand on it's own > For #3, this is where we are most obviously a Smalltalk, and should be > clear > about it > > And in an FAQ answer any common objections people might have: > Q: Is Pharo Smalltalk? > A: When most people hear "Smalltalk", they think of Smalltalk-80, which > Pharo is not. However, Smalltalk is really an idea... the lineage of which > Pharo is a proud member > Q: Can I talk to the world outside the environment? > A: Yes! While the original Smalltalk was quite insulated, now you can > [interact on the command line](link to unix command line examples e.g. the > very Ruby-like pharo [image filename] -e "self inform: 'hello world'"), > [talk to C libraries](link to native boost), etc. > yada yada yada > > > > - > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Pharo-is-Smalltalk-and-Not-tp4757342p4757348.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >
[Pharo-dev] New Proposal for new Pharo website - About page (with example website)
I don't like the about page. Its still unclear what Pharo is and I have to agree with the complains we are getting at reddit. So instead of starting a long conversation about how I would want it done , I sat my ass down and made a draft of it so you can see it directly. Please bare in mind this is draft , I just wanted to show you my idea for an About page. You can find the draft here http://thekilon.wix.com/pharo-about I think contributors should go to a seperate page called "Credit" I am open to comments and suggestions.
Re: [Pharo-dev] Pharo 3.0 Released!
Thanks you all. I love this page http://www.pharo.org/about especially the contributors list :)
Re: [Pharo-dev] Pharo 3.0 / Roassal2 / Ubuntu
On 01 May 2014, at 09:36, Sven Van Caekenberghe wrote: > Nice, let's copy that to the Pharo YouTube channel… > Done: https://www.youtube.com/watch?v=8wQjFzy8tj0 > On 01 May 2014, at 03:31, Alexandre Bergel wrote: > >> Hi Volkert, >> >> You need to install the true type font. Unfortunately, Pharo3 does not do it >> for you. I guess this will be fixed in the next release of Pharo. >> >> I have made a very short video on how to install Roassal2 from scratch: >> https://dl.dropboxusercontent.com/u/31543901/TMP/InstallingTrueTypeFont.mov >> >> Let us know how it goes. >> >> Alexandre >> >> >> On Apr 30, 2014, at 2:53 PM, volk...@nivoba.de wrote: >> >>> Dear all, >>> >>> i just downloaded Pharo 3.0 and installed Roassal2 via Configuration >>> Manager (Stable Version). >>> When trying the "Roassal examples" (from Tool-Menu) i got an red screen. >>> >>> Platform Ubuntu 14.04LTS >>> Pharo3.0 Latest update: #30846 >>> >>> Need some help :-) >>> >>> BW, >>> Volkert >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > >
Re: [Pharo-dev] 13204 Hard to see Morph halo label
OK I understand. Stef On 18/4/14 01:12, Sean P. DeNigris wrote: pharo4s...@free.fr wrote Why not just a StringMorph with correct background? That doesn't look possible with the current implementation. It just draws the string with no background: StringMorph>>#drawOn: aCanvas ... "super drawOn: aCanvas. <- This line doesn't exist" aCanvas drawString: contents in: bnd font: self fontToUse color: color. >From the "... color: color" above, it looks like StringMorph is hijacking the instVar it inherited from Morph, which usually means background color, to use for the text color. If you hack drawOn: to ... self color: Color white. super drawOn: aCanvas. aCanvas drawString: contents in: bnd font: self fontToUse color: Color black. you get the halo label you're looking for but of course break everything else. So I think that if we want StringMorphs to have backgrounds, we have to add a textColor instVar, initialize color to Color transparent, and rewrite all color assignments in StringMorph to set textColor. In short: not for 3.0. - Cheers, Sean -- View this message in context: http://forum.world.st/13204-Hard-to-see-Morph-halo-label-tp4755115p4755242.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
[Pharo-dev] About fonts
Hi pharoers I found the problems with the fonts and now I understand one of the possible way Roassal got broken. Imagine the following FT is on -> roassal works perfectly (using vectorial fonts) the standard fonts (default, code and others) are using vector graphics font. I deselect FT -> defaults and other are now in strike fonts like vera I reselect FT -> the defaults are still in strike fonts and this will then lead to errors in roassal. So I think that we should have a real object handling the restore and others. I will try to have a look in the end of the week. stef
Re: [Pharo-dev] Pharo 3.0 / Roassal2 / Ubuntu
Yes yes yes ... it works. I quickly jumped through some examples. Roassal2 looks so nice. Thank you. BW, Volkert Am 01.05.2014 03:31, schrieb Alexandre Bergel: Hi Volkert, You need to install the true type font. Unfortunately, Pharo3 does not do it for you. I guess this will be fixed in the next release of Pharo. I have made a very short video on how to install Roassal2 from scratch: https://dl.dropboxusercontent.com/u/31543901/TMP/InstallingTrueTypeFont.mov Let us know how it goes. Alexandre On Apr 30, 2014, at 2:53 PM, volk...@nivoba.de wrote: Dear all, i just downloaded Pharo 3.0 and installed Roassal2 via Configuration Manager (Stable Version). When trying the "Roassal examples" (from Tool-Menu) i got an red screen. Platform Ubuntu 14.04LTS Pharo3.0 Latest update: #30846 Need some help :-) BW, Volkert
Re: [Pharo-dev] Pharo 3.0 / Roassal2 / Ubuntu
Nice, let's copy that to the Pharo YouTube channel... On 01 May 2014, at 03:31, Alexandre Bergel wrote: > Hi Volkert, > > You need to install the true type font. Unfortunately, Pharo3 does not do it > for you. I guess this will be fixed in the next release of Pharo. > > I have made a very short video on how to install Roassal2 from scratch: > https://dl.dropboxusercontent.com/u/31543901/TMP/InstallingTrueTypeFont.mov > > Let us know how it goes. > > Alexandre > > > On Apr 30, 2014, at 2:53 PM, volk...@nivoba.de wrote: > >> Dear all, >> >> i just downloaded Pharo 3.0 and installed Roassal2 via Configuration Manager >> (Stable Version). >> When trying the "Roassal examples" (from Tool-Menu) i got an red screen. >> >> Platform Ubuntu 14.04LTS >> Pharo3.0 Latest update: #30846 >> >> Need some help :-) >> >> BW, >> Volkert >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >
Re: [Pharo-dev] [Pharo-users] Pharo 3 minor issue
thanks for reporting, I will look at it (super weird that it did not arise before :( ) Esteban On 30 Apr 2014, at 20:54, giorgio ferraris wrote: > Hi, > > started looking at Pharo after many years. > First of all, you all did an awesome works, thank you! > There is a small problems on System Browser > open image > open system browser > choose one class > select group > The class side checkbox is enabled, if you check it, you get a wall bak . > Giorgio > >
