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

Re: [Pharo-project] code licenses...was HTML parser (again))

by Dale Henrichs

StÃ©phane Ducasse wrote: > Yes we should do something. > Now the question is how to do something that we can actually implement. > I think that we should > - start to identify package of interest (quality/topics////) > - check their license status > - check the author and get access > - create an inbox > > Stef > Stef, speaking of licenses...I was thinking that for mcz files, we should have a "directory" of each mcz file that contains the license statement for the code in that _version_ of the mcz file. Most tools would end up ignoring, but if we started including the license _in_ the mcz file, then license status would be _much clearer_. I also assume that a similar addition to mc2 files could/should be done.... Dale

Aug. 19, 2010

Re: [Pharo-project] CogVM binaries!!! {WAS} Re: [squeak-dev] Re: CogVM on the Mac

by laurent laffont

It seems that object as method support still not here Laurent On Thu, Aug 19, 2010 at 11:12 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > It also looks like: > - OSProcess works well on Mac > - the bug related to the window preview in the Watery theme works with the > latest VM (I am talking about the preview of the window when hovering over > the task bar from Pharo) > > This is really great! > > Cheers, > Doru > > > > On 19 Aug 2010, at 10:57, Lukas Renggli wrote: > > 2) Do these binaries include the fixes from henrik to avoid the crash tha >>> happens sometime? >>> >> >> Yes, looks like it. Seaside does not immediately crash the VM. >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > www.tudorgirba.com > > "Problem solving should be focused on describing > the problem in a way that makes the solution obvious." > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 19, 2010

Re: [Pharo-project] CogVM binaries!!! {WAS} Re: [squeak-dev] Re: CogVM on the Mac

by Mariano Martinez Peck

2010/8/19 Eliot Miranda <eliot.miranda(a)gmail.com> > > > 2010/8/19 Mariano Martinez Peck <marianopeck(a)gmail.com> > > >> >> On Thu, Aug 19, 2010 at 6:23 AM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: >> >>> >>> >>> On Wed, Aug 18, 2010 at 8:14 PM, Chris Cunnington < >>> smalltalktelevision(a)gmail.com> wrote: >>> >>>> Wow. Have I been looking in the wrong place. >>>> I've been downloading trunk build files from svn listed on the >>>> squeakvm.org/unix pages, but *sigh* I didn't see the trove of stuff you >>>> just pointed out. And there are specific instructions for Mac and Unix >>>> builds. This is what I should be looking at. Thank you for pointing there. >>>> >>> >>> For folks' convenience I've just put up some unofficial builds >>> (essentially the same builds I use for testing) under >>> http://www.mirandabanda.org/files/Cog/VM >>> >>> >>> HTH >>> >> >> >> Hi Eliot. This, this HELPS A LOT. This is awesome. Seriously. This is >> really cool. Now we could start to create a Pharo one click based on Cog. >> Having the binaries will increase people using it, reporting bugs, and >> submitting fixes. >> >> Two questions: >> >> 1) why "unofficial" builds? >> > > because these sources are not yet maintained by the Squeak VM builders, > Andreas, Ian & John, > I agreee with this :) now i got it > and because the cod is still green (e.g. object as method still crashes the > VMs). > > but this would mean unstable, or beta or something but not unofficial ;) that's why I was confused. > >> 2) Do these binaries include the fixes from henrik to avoid the crash tha >> happens sometime? >> > > Yes. They're built from the most up-to-date version of the Cog sources. > > Excellent!!! :) thanks a lot mariano > >> Thanks >> >> Mariano >> >> >>> Eliot >>> >>> >>>> Chris >>>> >>>> >>>> >>>> >>> >>> >>> >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 19, 2010

Re: [Pharo-project] CogVM binaries!!! {WAS} Re: [squeak-dev] Re: CogVM on the Mac

by Eliot Miranda

2010/8/19 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > On Thu, Aug 19, 2010 at 6:23 AM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > >> >> >> On Wed, Aug 18, 2010 at 8:14 PM, Chris Cunnington < >> smalltalktelevision(a)gmail.com> wrote: >> >>> Wow. Have I been looking in the wrong place. >>> I've been downloading trunk build files from svn listed on the >>> squeakvm.org/unix pages, but *sigh* I didn't see the trove of stuff you >>> just pointed out. And there are specific instructions for Mac and Unix >>> builds. This is what I should be looking at. Thank you for pointing there. >>> >> >> For folks' convenience I've just put up some unofficial builds >> (essentially the same builds I use for testing) under >> http://www.mirandabanda.org/files/Cog/VM >> >> >> HTH >> > > > Hi Eliot. This, this HELPS A LOT. This is awesome. Seriously. This is > really cool. Now we could start to create a Pharo one click based on Cog. > Having the binaries will increase people using it, reporting bugs, and > submitting fixes. > > Two questions: > > 1) why "unofficial" builds? > because these sources are not yet maintained by the Squeak VM builders, Andreas, Ian & John, and because the cod is still green (e.g. object as method still crashes the VMs). > > 2) Do these binaries include the fixes from henrik to avoid the crash tha > happens sometime? > Yes. They're built from the most up-to-date version of the Cog sources. > > Thanks > > Mariano > > >> Eliot >> >> >>> Chris >>> >>> >>> >>> >> >> >> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 19, 2010

Re: [Pharo-project] Can't file in *.st exports

by Robert Sirois

No problem, Pharo's driving me crazy today hehe. It says: "*** system error handling failed ***" (see attached image). Thanks,RS > From: oldmanlink(a)gmail.com > Date: Thu, 19 Aug 2010 17:33:03 +0200 > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Can't file in *.st exports > > Pardon me for being blunt, Robert, but we're going to need a bit more to go on than "some sort of weird system error". > > Could you please attach a file that you tried to file in, and maybe a screenshot of the error? It would certainly increase your chances of getting some help ;-) > > -- > Cheers, > Peter. > > On 19 aug 2010, at 17:11, Robert Sirois <watchlala(a)hotmail.com> wrote: > > > There's some sort of weird system error when I try to fileIn a *.st file (like a class method). It asks me to "CR" for a debugger or any key to restart. I ended up having to force quit. > > > > This is in the latest 1.1 one-click. > > > > Thanks, > > RS > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 19, 2010

Re: [Pharo-project] Wiki spam experience

by Mariano Martinez Peck

ehh? what are you talking about? which wiki? On Thu, Aug 19, 2010 at 5:32 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > Hello all, > > Are there any tricks to running a wiki and not ending up a directory of > Nigerian ecomomic scams and pornography? Is moderation the only way to do > it, or can it be more automatic? > > Bill > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 19, 2010

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

by Mariano Martinez Peck

Carla....I know you have a wishlist/future plans....why don't you list them here and avoid people re-telling you ideas? :) and of course, several people may be intrested in the future features or ideas ! 2010/8/19 Carla F. Griggio <carla.griggio(a)gmail.com> > > > On Thu, Aug 19, 2010 at 12:45 PM, Tudor Girba <tudor.girba(a)gmail.com>wrote: > >> And some more feedback: >> > > >> - It would be nice to be able to add comments >> > > Comments would be great indeed :) > > >> - When creating a new diagram, the new diagram should be selected by >> default (right now it is not predictable) >> > > Whoops, that's right! > > > Thanks! > > Carla > > >> Cheers, >> Doru >> >> >> >> On 19 Aug 2010, at 17:23, Tudor Girba wrote: >> >> I took a quick look, and it looks quite nice! >>> >>> Here is a bit of feedback: >>> - I would prefer to have the menus for manipulating entities directly on >>> the canvas, and not in the panes below >>> - It looks like the last character from the name of the class gets >>> trimmed >>> - sometimes the last character from the names of the methods appears on >>> the next row >>> - When trying to create a box from existing class, I get DNU when the >>> class does not exist. Here I would expect to have the option of selecting >>> this class from a list, not to know it upfront >>> - I would prefer another notation for interfaces vs. classes. Right now >>> you have two borders on top of each other: solid for those entities that can >>> hold code, and dotted for those that cannot be instantiated. I would prefer >>> to have only one border with different thicknesses or different shades of >>> gray to denote code, and italic text to denote abstractness (for traits and >>> interfaces). >>> >>> I am not sure if it matters, but I have to mention that I tested in on a >>> Pharo 1.1 on a CogVM. >>> >>> Cheers, >>> Doru >>> >>> On 19 Aug 2010, at 16:56, 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 >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "In a world where everything is moving ever faster, >>> one might have better chances to win by moving slower." >>> >>> >>> >>> >> -- >> www.tudorgirba.com >> >> "It's not what we do that matters most, it's how we do it." >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 19, 2010

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

by Carla F. Griggio

On Thu, Aug 19, 2010 at 12:45 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > And some more feedback: > > - It would be nice to be able to add comments > Comments would be great indeed :) > - When creating a new diagram, the new diagram should be selected by > default (right now it is not predictable) > Whoops, that's right! Thanks! Carla > Cheers, > Doru > > > > On 19 Aug 2010, at 17:23, Tudor Girba wrote: > > I took a quick look, and it looks quite nice! >> >> Here is a bit of feedback: >> - I would prefer to have the menus for manipulating entities directly on >> the canvas, and not in the panes below >> - It looks like the last character from the name of the class gets trimmed >> - sometimes the last character from the names of the methods appears on >> the next row >> - When trying to create a box from existing class, I get DNU when the >> class does not exist. Here I would expect to have the option of selecting >> this class from a list, not to know it upfront >> - I would prefer another notation for interfaces vs. classes. Right now >> you have two borders on top of each other: solid for those entities that can >> hold code, and dotted for those that cannot be instantiated. I would prefer >> to have only one border with different thicknesses or different shades of >> gray to denote code, and italic text to denote abstractness (for traits and >> interfaces). >> >> I am not sure if it matters, but I have to mention that I tested in on a >> Pharo 1.1 on a CogVM. >> >> Cheers, >> Doru >> >> On 19 Aug 2010, at 16:56, 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 >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> -- >> www.tudorgirba.com >> >> "In a world where everything is moving ever faster, >> one might have better chances to win by moving slower." >> >> >> >> > -- > www.tudorgirba.com > > "It's not what we do that matters most, it's how we do it." > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 19, 2010

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

by Carla F. Griggio

Thanks Doru :D Whoops, I forgot to mention: I developed this project mostly in a Pharo1.1 version but not the last one, and when I tested it in the last 1.1 version I noticed what you said: - It looks like the last character from the name of the class gets trimmed > - sometimes the last character from the names of the methods appears on the > next row > But this is because of NewTextMorph>>fitToParagraph and it's fixed in Pharo 1.2, so I left it as that until the new Pharo dev version is ready :$ About the other things: - I would prefer to have the menus for manipulating entities directly on the > canvas, and not in the panes below > Great, I'm planning to do that, and also make the boxes editable, so you can write and modify the text without using the little workspace below, and Mariano suggested me to be able to browse classes from the boxes too. What other features would you like to add specifically? - When trying to create a box from existing class, I get DNU when the class > does not exist. Here I would expect to have the option of selecting this > class from a list, not to know it upfront > Oops, thanks, I'll check that. You can choose an existing class from a list if that class is in the same package your documenting. I didn't do that for any existing class because they would be too many. Do you think of a better option? Maybe adding autocompletion of the class name? - I would prefer another notation for interfaces vs. classes. Right now you > have two borders on top of each other: solid for those entities that can > hold code, and dotted for those that cannot be instantiated. I would prefer > to have only one border with different thicknesses or different shades of > gray to denote code, and italic text to denote abstractness (for traits and > interfaces). > That's interesting and it's the kind of feedback I'm most looking for. I chose dashed lines for things you can't instantiate because that's the convention for interfaces in UML that I use at collage, and I thought of a variant of that for trait boxes. But I'm not 100% sure about the styling I chose. The same applies for arrows and the relationships lines. A little note upside the boxes like <<trait>> or <<interface>> would work also, although I'm afraid they could overlap with connections :/ I'll think about that, but I'd also like to have more opinions from the (hopefully) future users :) Different colors or shades of gray / black could work, I'd prefer not changing the border thickness between boxes. And I chose underlined italic style for Class Instance Variables, but I'm not sure about that either. The underline convention is for Class Variables, but what about Class Instance Variables? > I am not sure if it matters, but I have to mention that I tested in on a > Pharo 1.1 on a CogVM. > That matters! Haven't tested CogVM yet, so... great :D > > Cheers, > Doru > > > On 19 Aug 2010, at 16:56, 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 >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 19, 2010

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

by Tudor Girba

And some more feedback: - It would be nice to be able to add comments - When creating a new diagram, the new diagram should be selected by default (right now it is not predictable) Cheers, Doru On 19 Aug 2010, at 17:23, Tudor Girba wrote: > I took a quick look, and it looks quite nice! > > Here is a bit of feedback: > - I would prefer to have the menus for manipulating entities > directly on the canvas, and not in the panes below > - It looks like the last character from the name of the class gets > trimmed > - sometimes the last character from the names of the methods appears > on the next row > - When trying to create a box from existing class, I get DNU when > the class does not exist. Here I would expect to have the option of > selecting this class from a list, not to know it upfront > - I would prefer another notation for interfaces vs. classes. Right > now you have two borders on top of each other: solid for those > entities that can hold code, and dotted for those that cannot be > instantiated. I would prefer to have only one border with different > thicknesses or different shades of gray to denote code, and italic > text to denote abstractness (for traits and interfaces). > > I am not sure if it matters, but I have to mention that I tested in > on a Pharo 1.1 on a CogVM. > > Cheers, > Doru > > On 19 Aug 2010, at 16:56, 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 >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it."

Aug. 19, 2010