August 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Introducing smallUML: a little project to help us document :)

by Carla F. Griggio

OK, although I tried to use what I separated in the Minimal Connectors package and there are still some things missing to be able to use it independently. So (although we're already talking about that here XD) we shouldn't announce that yet. And yes, I use some shout stuff, so I should add that dependency! Thanks. Although shout doesn't load in the latest Pharo Core image yet :( 2010/8/23 Fernando olivero <fernando.olivero(a)usi.ch> > Hi Carla, just a remark about the dependencies. > > > I tried to load it in a Core image and got some dependencies errors , > regarding shout and pluggable shout text morph. > Maybe you could add those to the configuration also. > > I'll give a try in a Pharo image now, Looking forward to try it! > > Ahh! we should announce the "minimal connectors" package, maybe we could > enhance the description in Squeaksource with the contents from the mails we > discussed with marcus. > I'll fetch them and try to add them to squeaksource. > > Saludos, > Fernando > On Aug 19, 2010, at 4:56 PM, Carla F. Griggio wrote: > > Hi everyone! > Well, here I am announcing the resulting project of my GSoC experience > during the [your] summer: smallUML, a project to help us building diagrams > and sharing them with any package of code. > My mentor was Stephane Ducasse and my co-mentor Geert Claes, so thanks to > them for the guidance up to now, and also to Fernando Olivero who helped me > a lot (hope to do some coding with you at ESUG! :P). > > You can gofer it: > > Gofer it >> squeaksource: 'smallUML'; >> package: 'ConfigurationOfSmallUML'; >> load. >> (Smalltalk at: #ConfigurationOfSmallUML) project latestVersion load. >> > > And then open the Diagram Browser of the current little examples > evaluating: > > DiagramDrawingDocumentation openDiagramBrowser . >> > > This is beta and I'm still working on it, my work will continue after > GSoC's deadline, so of course your welcome to give some feedback and think > about what features would you like it to have and if you're confortable with > the current features. It would be really nice if this helped to get all > Pharo projects more documented, with visual diagrams that help understanding > them at a glance. > > Talking about that... the current features are: > > - Open a *Diagram Browser* for an existing Category Diagrams Holder > (this is a class ment to hold the created diagrams and there should be one > per category, for now; you can browse DiagramDrawingDocumentation to see an > example) > - *Create and edit diagrams* programatically describing them with > "diagram code" (the diagram code it's just a protocol of methods meant to > describe diagrams, you can see some diagram code browsing > DiagramDrawingDocumentation methods or each Class Box in the Diagram > Browser) > - Every diagram you build through the Diagram Browser it's saved as > "diagram code", so you can *share it as code* that will reproduce your > diagram :) That means that diagrams can 'travel' along it's package when you > commit your changes with Monticello! And then they can be edited by anybody, > they're not just a pretty picture. > - You can *export* your diagram as a *PNG* picture or you can export > it's "diagram code" as a *workspace*. > - Only *Class Diagrams* can be built for now. > - Class Boxes of a class diagram can be *dragged* to be easily > positioned. > > Some details that are missing: > > - It's funny, but I can't center the class boxes title! :P > - I tried adding some scrollbars to the "whiteboard" where you can view > your diagrams in the Diagram Browser, but if I did that the drag & drop of > the class boxes worked funny :( I'll ask about that to you later. > > On the way: > > - Tests and documentation, and a screencast showing every feature. > - Lots of refactors: as I'm adding more kind of diagrams right now, so > I'm doing a lot of refactors to make everything more flexible and improving > all the messy code there. > - A version of Minimal Connectors for anybody to use if they feel like > connecting morphs for another project. > - Some usability improvements. > - Object diagrams > - Sequence diagrams > - Your feedback :D > > > So I'd really appreciate if you can give it a try and tell me how you feel > about it, I'd like it to be very usable. > > Cheers! > > Carla > > <ATT00001..txt> > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 23, 2010

Re: [Pharo-project] Introducing smallUML: a little project to help us document :)

by Fernando olivero

Hi Carla, just a remark about the dependencies. I tried to load it in a Core image and got some dependencies errors , regarding shout and pluggable shout text morph. Maybe you could add those to the configuration also. I'll give a try in a Pharo image now, Looking forward to try it! Ahh! we should announce the "minimal connectors" package, maybe we could enhance the description in Squeaksource with the contents from the mails we discussed with marcus. I'll fetch them and try to add them to squeaksource. Saludos, Fernando On Aug 19, 2010, at 4:56 PM, Carla F. Griggio wrote: > Hi everyone! > Well, here I am announcing the resulting project of my GSoC experience during the [your] summer: smallUML, a project to help us building diagrams and sharing them with any package of code. > My mentor was Stephane Ducasse and my co-mentor Geert Claes, so thanks to them for the guidance up to now, and also to Fernando Olivero who helped me a lot (hope to do some coding with you at ESUG! :P). > > You can gofer it: > > Gofer it > squeaksource: 'smallUML'; > package: 'ConfigurationOfSmallUML'; > load. > (Smalltalk at: #ConfigurationOfSmallUML) project latestVersion load. > > And then open the Diagram Browser of the current little examples evaluating: > > DiagramDrawingDocumentation openDiagramBrowser . > > This is beta and I'm still working on it, my work will continue after GSoC's deadline, so of course your welcome to give some feedback and think about what features would you like it to have and if you're confortable with the current features. It would be really nice if this helped to get all Pharo projects more documented, with visual diagrams that help understanding them at a glance. > > Talking about that... the current features are: > Open a Diagram Browser for an existing Category Diagrams Holder (this is a class ment to hold the created diagrams and there should be one per category, for now; you can browse DiagramDrawingDocumentation to see an example) > Create and edit diagrams programatically describing them with "diagram code" (the diagram code it's just a protocol of methods meant to describe diagrams, you can see some diagram code browsing DiagramDrawingDocumentation methods or each Class Box in the Diagram Browser) > Every diagram you build through the Diagram Browser it's saved as "diagram code", so you can share it as code that will reproduce your diagram :) That means that diagrams can 'travel' along it's package when you commit your changes with Monticello! And then they can be edited by anybody, they're not just a pretty picture. > You can export your diagram as a PNG picture or you can export it's "diagram code" as a workspace. > Only Class Diagrams can be built for now. > Class Boxes of a class diagram can be dragged to be easily positioned. > Some details that are missing: > It's funny, but I can't center the class boxes title! :P > I tried adding some scrollbars to the "whiteboard" where you can view your diagrams in the Diagram Browser, but if I did that the drag & drop of the class boxes worked funny :( I'll ask about that to you later. > On the way: > Tests and documentation, and a screencast showing every feature. > Lots of refactors: as I'm adding more kind of diagrams right now, so I'm doing a lot of refactors to make everything more flexible and improving all the messy code there. > A version of Minimal Connectors for anybody to use if they feel like connecting morphs for another project. > Some usability improvements. > Object diagrams > Sequence diagrams > Your feedback :D > > So I'd really appreciate if you can give it a try and tell me how you feel about it, I'd like it to be very usable. > > Cheers! > > Carla > > <ATT00001..txt>

Aug. 23, 2010

Re: [Pharo-project] Working on Pharo 1.2

by Marcus Denker

On Aug 22, 2010, at 9:54 PM, Adrian Lienhard wrote: > Yes, this is possible (its done with a code part in Cmsbox that triggers the redirect, so updating is similar to editing some other content). But we should then regularly update the links so they don't get outdated. Is it worth? > good question... right now people can't easily find the last pre-built unstable. I would update the link as soon as I put a new pre-built online. (of course this is just an intermediate step... the goal is to auto-build everything. Which we will have at some point... but if we learning anything the last 10 years is that because one could (and plans to) do it better, one should nevertheless do the dumb intermediate solution nevertheless) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Aug. 23, 2010

[Pharo-project] ExternalAddress and block copy?

by Schwab,Wilhelm K

Are there any well-worn ways to move data into and out of external memory? The best I have been able to uncover are recommendations to either do it one byte at a time (yuk!) or to (ab)use bitblt. There must be better ways, right? If not, what tools are present in the image that need to be brought to the surface? How/where should that be done so that it works on all three platforms? To what extent, if any, can String and ByteArray be used as buffers for external calls? Dolphin made that robust, but there were hints that the gc was slightly tamed to allow it. The little reading I have done in squeak-dev archives suggests that squeak/pharo is not so forgiving. Is that true? Bill

Aug. 23, 2010

Re: [Pharo-project] [squeak-dev] [ANN] SimpleLogger released

by GermÃ¡n Arduino

2010/8/19 GÃ¶ran Krampe <goran(a)krampe.se>: > Hi all! > > I wonder a few things: > > - Why was SimpleLog deemed "hard"? The class comment on SLLog etc is pretty > straight forward IMHO! > - Also SimpleLog has some quite nice features: > Â Â Â Â - A really nice Morph to keep an eye on the logging going on, and to > easily filter it etc, although it needs some love for Pharo to compile. > Â Â Â Â - A log to file class with rotation. > Â Â Â Â - Ability to use syslog like Ramon posted, in fact, I think SimpleLog > was first with that. > > I just... wonder why we need to reinvent so many things over and over? > Is so bad to develop a small utility and put it open to the community? What thing is bad with this? > Toothpick IMHO was a bit complex, I agree - that was the reason for creating > SimpleLog, but hey, SimpleLog is *not* complex. > This is your opinion, I respect but don't agree. Anyway I think that this is a topic really not relevant, I shared a small class that I developed by the reason that can be useful to others, nothing more. > regards, GÃ¶ran > Cheers.

Aug. 22, 2010

[Pharo-project] [update 1.2] #12107

by StÃ©phane Ducasse

12107 ----- - Issue 2846: remove empty DeprecatedPreferences Package. - Issue 2838: should remove multilingual package. Stef

Aug. 22, 2010

Re: [Pharo-project] Working on Pharo 1.2

by Adrian Lienhard

Yes, this is possible (its done with a code part in Cmsbox that triggers the redirect, so updating is similar to editing some other content). But we should then regularly update the links so they don't get outdated. Is it worth? On Aug 20, 2010, at 09:06 , Marcus Denker wrote: > > On Aug 19, 2010, at 9:47 PM, Adrian Lienhard wrote: > >> Ok, here are the two URLs with redirects to the current 1.1 release downloads. >> >> http://pharo-project.org/pharo-download/stable >> http://pharo-project.org/pharo-download/stable-core >> > > can we have the same for unstable in a way that we can update to where the link > points to? > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 22, 2010

[Pharo-project] [update 1.2] #12106

by StÃ©phane Ducasse

12106 ----- - Issue 2843: ColoredCodeStream not used. Thanks Marcus Denker. - Issue 2769: Fixes for broken SocketStream behavior. Thanks Andreas Raab Fix the loop in network tests. Stef

Aug. 22, 2010

[Pharo-project] [update 1.2] #12105

by StÃ©phane Ducasse

12105 ----- - Issue 2844: String>>#numArgs is broken - reformat String class>>#initialize so that the initializer gets executed (no other changes there) - fixed String>>#tokenish and String>>#numArgs - 4 new tests Thanks Lukas Renngli - Issue 2767: SocketStream>>upTo: and #upToAll: to fix an infinite loop. Thanks Andreas Raab. Apparently the fix does not solve the endless loop as in squeak. Stef

Aug. 22, 2010

Re: [Pharo-project] SocketStream enh

by StÃ©phane Ducasse

I will integrate another socket related fix because apparently the tests still break the image with these ones loaded. Stef On Aug 22, 2010, at 1:53 PM, Philippe Marschall wrote: > On 18.08.2010 12:56, StÃ©phane Ducasse wrote: >> >>>>>> I will integrate the following SocketStream tests and before I would love to see if this >>>>>> does not impact seaside >>>>>> >>>>>> http://code.google.com/p/pharo/issues/detail?id=2767 >> >> Does anybody have the time to give feedback on this important network changes? > > I did a short test with Seaside and everything still seems to work. And > if it fixes bugs, I'm all tits forward about it. > > The deprecation of SmalltalkImage >> #platformName is a PITA though. It > requires us to have different versions of Comanche and WebClient for > different versions of Pharo. > > Cheers > Philippe > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 22, 2010