- Pharo-dev - lists.pharo.org

[Pharo-project] How to redraw a PluggableTreeMorph when its contents change

by Rob Rothwell

Thanks to the TreeMorph Pharocast (thank you!) and some digging, I have added a context menu to a PluggableTreeMorph that lets me add a child to a selected node (I am just using the idea of nested "accounts"): addAccount | isExpanded | aTreeMorph selectedMorph complexContents item addAccount: (Account new accountName: (UIManager default request: 'Enter a new account name:')). isExpanded := aTreeMorph selectedMorph isExpanded. aTreeMorph toggleExpandedState: aTreeMorph selectedMorph. isExpanded ifTrue: [aTreeMorph toggleExpandedState: aTreeMorph selectedMorph.] But as you can see I can only figure out how to show new nodes by toggling the expanded state, which is really not helpful if you want to rename, delete, etc... Is there a way to somehow just inform the PluggableTreeMorph to redraw itself after changing its contents? Thank you, Rob

Aug. 21, 2010

Re: [Pharo-project] Something wrong with changes?

by Schwab,Wilhelm K

I was able to get a very recent image from the Windows box and it seems to work correctly after re-saving on Linux. I am not sure exactly what I would lose by stopping at this point, hence my next question. Not knowing whether the change log from the broken image is at fault, I hesitate to use it as the basis for future work. If I understand how to recover lost changes, that is exactly what I would do: use it as the change log for the working image and recover changes into it. Is there another, perhaps safer, way to do that? Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K [bschwab(a)anest.ufl.edu] Sent: Friday, August 20, 2010 3:24 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Something wrong with changes? I might have a corrupt change log. It is not particularly large, so I doubt it is size related. The problem is that I am not getting temporary names (lots of t1, t2, ... where there should be meaningful names). I recently copied the image from Linux to Windows and back; the timing is interesting. I also sometimes find that Ubuntu takes a LONG time to complete writes to flash sticks and wonder whether that might be an accident waiting to happen?? I have a backup from not quite a week ago and will check the image on the Windows box. Between the two of them and some recovery, I can probably be back in action quickly. It is also time for me to move from 1.1 RC2 to release anyway. Does any of this (possible changes woes and/or problems moving between Linux and Windows) sound familiar? Bill _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 20, 2010

Re: [Pharo-project] Trying to install Rio file handling package

by Schwab,Wilhelm K

Rio was a thorn in my side for several (sub)releases, but it was apparently because something was loading an old version of it?? You might try loading it in Linux, as there was a bug that would prevent it loading on Windows at one point, but it could load on Linux (and probably a mac too), after which it would have to fixed for the image to load on Windows. Good luck. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Lawson English [lenglish5(a)cox.net] Sent: Friday, August 20, 2010 5:36 PM To: The general-purpose Squeak developers list; Pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Trying to install Rio file handling package The Gallery addon for pier first requires that Rio be installed. http://www.squeaksource.com/@7zePIlRlfoA0dT1I/VwzOlsoy However, rio won't install due to errors: FileMacOSXExectuive class as yet unclassified getenv: getenv: varString " self getenv: 'HOME' " " self getenv: 'ZYZZYX' " <> expected ->cdecl: char* 'getenv' ( char* ) module: 'libc.dylib'> ^self externalCallFailed Happens in both the latest Pharo and the latest Squeak. Not sure how to fix this... thanks for any advice. Lawson _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 20, 2010

[Pharo-project] Trying to install Rio file handling package

by Lawson English

The Gallery addon for pier first requires that Rio be installed. http://www.squeaksource.com/@7zePIlRlfoA0dT1I/VwzOlsoy However, rio won't install due to errors: FileMacOSXExectuive class as yet unclassified getenv: getenv: varString " self getenv: 'HOME' " " self getenv: 'ZYZZYX' " <> expected ->cdecl: char* 'getenv' ( char* ) module: 'libc.dylib'> ^self externalCallFailed Happens in both the latest Pharo and the latest Squeak. Not sure how to fix this... thanks for any advice. Lawson

Aug. 20, 2010

Re: [Pharo-project] How can I load metacello without OB

by Mariano Martinez Peck

On Fri, Aug 20, 2010 at 4:19 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Indeed, now we could add this method in Gofer. > > I didn't understand. Which method ? why in Gofer? > Cheers, > Doru > > > > On 20 Aug 2010, at 16:01, Mariano Martinez Peck wrote: > > >> >> On Fri, Aug 20, 2010 at 3:54 PM, StÃ©phane Ducasse < >> stephane.ducasse(a)inria.fr> wrote: >> > >> > The problem is in ConfigurationOfRPackage as in #ensureMetacello is >> like this: >> > >> > ensureMetacello >> > Smalltalk at: #MetacelloProject ifAbsent: [ >> > Gofer new >> > disableRepositoryErrors; >> > url: 'http://seaside.gemstone.com/ss/metacello'; >> > package: 'ConfigurationOfMetacello'; >> > load. >> > (Smalltalk at: #ConfigurationOfMetacello) project latestVersion >> load: #('default' 'UI') ] >> >> I hate the fact that we should copy all the code around.... >> what a crap. >> >> This was discussed several, severaaaaal times. As I remember the problem >> was that otherwise you class depends on a base class that should be included >> in the image you are working on. >> But I guess we don't have problem to add such base class in PharoCore...if >> we have Gofer.. >> >> >> > >> > >> > If you see, it is loading #('default' 'UI') of metacello..... UI -> OB. >> > >> > change that to #('default') and wala >> > >> > BTW, I would use the latest recommended #ensureMetacello: >> > >> > http://code.google.com/p/metacello/wiki/EnsureMetacello >> > >> > cheers >> > >> > mariano >> > >> > >> > And stuck because OB does not load in 1.2 so I lost one hour...... >> boring. >> > >> > Stef >> > >> > >> > _______________________________________________ >> > 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 >> >> >> _______________________________________________ >> 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 >> > > -- > www.tudorgirba.com > > "Live like you mean it." > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 20, 2010

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

by StÃ©phane Ducasse

On Aug 20, 2010, at 9:57 PM, Adrian Lienhard wrote: > Hi Carla, > > Nice! Here a few random comments: > > - I really like that I can ship the diagrams with the code Thanks :) > - if I understand correctly, the method names are hardcoded in the spec. Hence, when I document my software with a diagram and then I change the code, my diagram gets out of date. If you already have the diagram with the code, I think you miss an opportunity here. For now we make it static but working. > - I don't understand why, when I drag a box, there are suddenly two arrows shown (I guess the second arrow should be its shadow, but it does not really work) > > - I suggest to simplify menu labels like "Add new class box" to "New class". "New" implies that it gets added, and you don't need to say "box" because its clear from the context that this will be a box. It also avoids confusion about classboxes (for those who know classboxes). > > - One feature of the class diagram that would be very nice to have is associations. > > - I couldn't figure out how to create relationships > > - I suggest, instead of adding new type of diagrams, to first make the class diagram really good. You have a much larger impact if you do just one small thing but really well. I told her :) > > > Cheers, > Adrian > > > On Aug 19, 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 20, 2010

Re: [Pharo-project] Updating Pharo kernel

by StÃ©phane Ducasse

This is expected since 1.2 is unstable and changed a lot of things so it means that external packages did not get yet migrated to 1.2. Normally migration happens in beta phase. Stef On Aug 20, 2010, at 9:02 PM, Andrei Stebakov wrote: > Got the 1.2 image. Failed to load > Gofer new > squeaksource: 'MetacelloRepository'; > package:'ConfigurationOfO2'; > load. > > ((Smalltalk at: #ConfigurationOfO2) project version: '1.2') load: 'Dev'. > > Also failed to load > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSeaside30'; > load. > > ((Smalltalk at: #ConfigurationOfSeaside30) project version: > '3.0.0-alpha5.15') load. > > Which loaded well with Pharo 1.1. Well, I guess it's a development > image so this is expected... > > On Fri, Aug 20, 2010 at 2:13 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Yes >> >> andrei I think that what miguel is telling you is key. Having a reproducable process to load your code >> is the best you can do to yourselves. >> >> Stef >> >> >> >>> El vie, 20-08-2010 a las 12:49 -0400, Andrei Stebakov escribiÃ³: >>>> But let's say I already have an image with a bunch of libraries >>>> installed and tweaked so they work. >>>> Is it possible to update only Pharo kernel so I can later use it with >>>> CogVM (which needs some latest updates)? >>> >>> The problem with this is that carries the old squeak way to work. That >>> is, a image is used and modified everywhere without a way to reliably >>> reproduce the steps to rebuild the image. That's even worse when you >>> accidentally destroy or render your image unusable. >>> The modern way or the pharo way is to have everything in monticello >>> packages. >>> From there you can reload your code in any new image by just loading >>> your monticello packages in the new image. >>> Now, you can automate this procedure either: >>> - writing a script to evaluate in a workspace that uses Gofer or >>> Installer to fetch and install the set of packages >>> - (recommended) write your Metacello ConfigurationOfMyPackage where you >>> put the packages that comprise your application, plus any other >>> dependency that is needed for it to work. Metacello then uses gofer to >>> load all your code and its dependencies from anywhere, either locally or >>> remotely and build your image from a given new image. >>> >>> This way, you can load your code in new images with just a do-it in a >>> workspace and to check if works correctly on newer images. >>> >>> Cheers. >>>> >>>> On Fri, Aug 20, 2010 at 12:19 PM, StÃ©phane Ducasse >>>> <stephane.ducasse(a)inria.fr> wrote: >>>>> yes :) >>>>> If you take an unstable image you can always select software update. >>>>> Now this is disable in dev images. >>>>> I suggest to use 1.2 if you want to fix the system >>>>> >>>>> Stef >>>>> >>>>> On Aug 20, 2010, at 5:46 PM, Andrei Stebakov wrote: >>>>> >>>>>> Is there a procedure similar to Squeak for updating to the latest kernel? >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> -- >>> Miguel CobÃ¡ >>> http://miguel.leugim.com.mx >>> >>> >>> _______________________________________________ >>> 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 >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 20, 2010

[Pharo-project] [update 1.2] #12102

by StÃ©phane Ducasse

12102 ----- - Issue 2810: Missing "Software update" menu in releases confusing new users. Thanks Sean De Nigris. - Issue 2812: Add ISO-8859-15 and CP-1252 encodings support. Thanks Philipp Marshall. Stef

Aug. 20, 2010

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

by Carla F. Griggio

Hi Adrian! Thanks!! Nice feedback :D I'll reply each of your comments: > - I really like that I can ship the diagrams with the code > > Great, I personally think it's the coolest feature this project can offer. > - if I understand correctly, the method names are hardcoded in the spec. > Hence, when I document my software with a diagram and then I change the > code, my diagram gets out of date. If you already have the diagram with the > code, I think you miss an opportunity here. Yes... that's true. This project was first planned for making "handmade" diagrams, I mean, YOU choose what to show and how to show it (i.e. I'd like to show that some objects share a type although they don't share a hierarchy, but I really want to document they have polimorfism). That kind of freedom makes me loose the opportunity to link the diagrams with actual code and get them to be always up to date. I'd like to think about how I can get closer to that, because it IS confortable, but the diagram would have to be more complex and remember all the time what parts are linked to actual code and what parts are customized by the person who built it. It could be interesting to design :P But in the [not very near] future. > - I don't understand why, when I drag a box, there are suddenly two arrows > shown (I guess the second arrow should be its shadow, but it does not really > work) Hmmm... I guess it is the shadow. It kind of bothers me too, I could try to make it look different (or take it off completely). Do you notice something similar with the boxes too? > - I suggest to simplify menu labels like "Add new class box" to "New > class". "New" implies that it gets added, and you don't need to say "box" > because its clear from the context that this will be a box. It also avoids > confusion about classboxes (for those who know classboxes). > > Great simple advice, thank you :) > - One feature of the class diagram that would be very nice to > have is associations. > - I couldn't figure out how to create relationships Yes! For now, you can describe how a class box associates with another in the little workspace of the Diagram Browser like this: - aClassBox *hasA*: anotherClassBox *labeledAs*: 'variableName' - aClassBox *hasLotsOf*: anotherClassBox *labeledAs*: 'variableName' - aClassBox *uses*: anotherClassBox - aClassBox *inheritsFrom*: anotherClassBox - aClassBox *isATypeOf*: anInterfaceBox - aClassBox *implements*: anInterfaceBox - aClassBox *usesTrait*: aTraitBox This is the kind of stuff I *urgently* have to document :P > - I suggest, instead of adding new type of diagrams, to first make the > class diagram really good. You have a much larger impact if you do just one > small thing but really well. > Thanks for that advice, and you're right, Stef says the same. I started doing some REALLY simple object diagrams because I needed them for the next week to use them at collage. But in the meantime I'm improving the project generally too (in the meantime means until next week XD then I'll start improving class diagrams upon all your feedback :D). Thanks a lot!!! I'll detail the list of features later, I'm pretty busy today :( Carla Cheers, Adrian > > On Aug 19, 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

Aug. 20, 2010

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

by Adrian Lienhard

Hi Carla, Nice! Here a few random comments: - I really like that I can ship the diagrams with the code - if I understand correctly, the method names are hardcoded in the spec. Hence, when I document my software with a diagram and then I change the code, my diagram gets out of date. If you already have the diagram with the code, I think you miss an opportunity here. - I don't understand why, when I drag a box, there are suddenly two arrows shown (I guess the second arrow should be its shadow, but it does not really work) - I suggest to simplify menu labels like "Add new class box" to "New class". "New" implies that it gets added, and you don't need to say "box" because its clear from the context that this will be a box. It also avoids confusion about classboxes (for those who know classboxes). - One feature of the class diagram that would be very nice to have is associations. - I couldn't figure out how to create relationships - I suggest, instead of adding new type of diagrams, to first make the class diagram really good. You have a much larger impact if you do just one small thing but really well. Cheers, Adrian On Aug 19, 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

Aug. 20, 2010