- Pharo-dev - lists.pharo.org

Re: [Pharo-project] smallUML news: towards autogenerated diagrams

by Carla F. Griggio

Hi! Stef, I use a block because the idea is to get a diagram of a "scenario". This is a first approach, but my goal is to generate the diagrams from test runs. Of course this will be able to be used in different ways, but for now I'd like to get diagrams of delimited scenarios, for example, a diagram of a use case, instead of one big diagram of a whole project. I think it can help communicate better how the use cases of a project are implemented. The model behind the diagrams it's still the same I designed during GSoC 2010, I attach a class diagram showing the structure of a diagram. If you inspect this, you'll be able to see the objects representing class boxes and relationships: [|jack william blackPearl questMission| jack := Pirate new alcoholLevel: 0.7; items:#(#compass #islandMap #rum #moreRum #goldMedallion). questMission := TreasureQuest new. blackPearl := Ship new. blackPearl mission: questMission. blackPearl acceptIntoTripulation: jack. ] *asClassDiagram* Alex, try this new version: Gofer new squeaksource: 'smallUML'; package: 'ConfigurationOfSmallUML'; load. ((Smalltalk at: #ConfigurationOfSmallUML) project version:'1.1.7') load. I added a few more things. I'm experimenting with a new way of organizing diagrams. Now if you open a Diagram Browser, the diagrams will be listed by category, so we can organize diagrams by categories. DiagramsHolder *openDiagramBrowser* If you generate a diagram from a block and open a quick view like this: [|jack william blackPearl questMission| jack := Pirate new alcoholLevel: 0.7; items:#(#compass #islandMap #rum #moreRum #goldMedallion). questMission := TreasureQuest new. blackPearl := Ship new. blackPearl mission: questMission. blackPearl acceptIntoTripulation: jack. ] asClassDiagram *openQuickView* after you accomodate the diagram nodes you can save it into a category by doing right click on the diagram -> Save for category.... There you give a name to the diagram, and type the category it's related to, and your diagram will be saved as a method in an extension category inside the class DiagramsHolder. If you browse *DiagramsHolder*, you'll see all the diagrams as methods. I think that's cool because diagrams can be versioned as code :) Cheers! Carla On Fri, May 11, 2012 at 11:08 AM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > Hi Carla, > > I've just tried in Pharo 1.4 (Moose distribution), I get an error: > -=-=-=-=-=-=-=-=-=-=-=-= > This package depends on the following classes: > CategoryDiagramsHolder > You must resolve these dependencies before you will be able to load these > definitions: > ConnectableShapesDocumentation > connectableBounds > connectableShapes > inheritanceforConnection > inheritanceforDiagramNode > inheritanceforDiagramNodeMorph > DiagramDrawingDocumentation > connectableshapes > inheritanceforConnection > > > Select Proceed to continue, or close this window to cancel the operation. > -=-=-=-=-=-=-=-=-=-=-=-= > > I would be glad to try again. > > Cheers, > Alexandre > > > On 8 May 2012, at 05:37, Carla F. Griggio wrote: > > > Hi everyone! > > I've been doing some experiments to get Class Diagrams generated from > the evaluation of a block. There's still a lot of work to be done, but I've > just got this working and I wanted to show it to you :) > > > > Gofer new > > squeaksource: 'smallUML'; > > package: 'ConfigurationOfSmallUML'; > > load. > > ((Smalltalk at: #ConfigurationOfSmallUML) project version:'1.1.6') load. > > > > After downloading the project, try this example: > > > > [|jack william blackPearl questMission| > > jack := Pirate new alcoholLevel: 0.7; items:#(#compass #islandMap > #rum #moreRum #goldMedallion). > > questMission := TreasureQuest new. > > blackPearl := Ship new. > > blackPearl mission: questMission. > > blackPearl acceptIntoTripulation: jack. > > ] asClassDiagram openQuickView > > > > A messy and 'overlapped' diagram will come up, because there's still no > autimatic positioning of the diagram nodes :( but you can drag the class > boxes around to place them anywhere you want. > > > > You will notice that what I've got so far is: > > â¢ Drawing the classes involved in the evaluation of that block, > with the messages that were sent during that block > > â¢ Drawing the superclasses involved along with the inheritance > arrow. Superclasses are included only if there are inherited methods > excecuted. > > â¢ Drawing the association relationships between instances! That's > my favorite part, and the one that was not trivial to achieve. The code > still sucks, but it's working. You can see that the association > relationships between the Ship, the Pirate and the Mission are drawn, and > Collections are 'skipped' as in a regular class diagram using the > cardinality annotation * over the arrow. > > What's interesting about this last point, is resolving these (still > pending) issues: > > â¢ If an object form class A has a collection where the elements > are of different classes, or if it has an attribute that could point to > different polimorfic objects, there should be just one association arrow > from class A to: > > â¢ the superclass of those different classes, or > > â¢ the inferred type those different classes share: this > comes along with some questions, like 'what will the type name be?' > > â¢ What will be the scope of the diagram? Objects can have > attributes ponting to numbers, strings, blocks, booleans, etc. Are we > interested in showing those classes in a class diagram? I guess, it > depends. The diagram scope should not be hard coded (as it is now :P), > because if we want to document a core package, some core classes will have > to appear instead of being ignored like we would prefere in a 'domain > specific' diagram. > > â¢ Collections are 'skipped' in the diagrams. That means that if an > object A points to a collection, that points to several objects of class B, > in the diagram only the classes A and B are shown with the classical 'one > to many' arrow. This will mess up diagrams of the collection packages > themselves :P > > So, I invite you to think about how could these issues be resolved, and > also play a little bit with what I've got so far, executing [your block > code] asClassDiagram openQuickView. > > > > I hope that the GSoC project of Santiago will help with the type > inferences part :) > > > > Cheers! > > Carla. > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > >

May 13, 2012

Re: [Pharo-project] Nautilus oddities (Naudities?)

by Benjamin

Thank you :) I will try to do that soon ;) Ben On May 13, 2012, at 12:22 AM, blake wrote: > On Sat, May 12, 2012 at 3:18 PM, Benjamin > <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> Obviously some stuff I did wrong :) >> >> More often, it's just because of a lack of review, most probably because I shouldn't code after 4am :) > > Heh. > >> Thanks for your feedback, I will have a look at this asap :) >> Could you please open a bug entry to be sure I will not forget ? :) > > Done. > > Good work. > > ===Blake=== >

May 12, 2012

[Pharo-project] Pharo and the ST-80 classes

by blake

I went to use a "Line" today and found it wasn't in Pharo. Apparently this is part of the ST80-* (ST80-Paths) classes which aren't carried over to Pharo. So...how do I draw a line on a morph (without creating another morph)? ===Blake===

May 12, 2012

Re: [Pharo-project] Nautilus oddities (Naudities?)

by blake

On Sat, May 12, 2012 at 3:18 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Obviously some stuff I did wrong :) > > More often, it's just because of a lack of review, most probably because I shouldn't code after 4am :) Heh. > Thanks for your feedback, I will have a look at this asap :) > Could you please open a bug entry to be sure I will not forget ? :) Done. Good work. ===Blake===

May 12, 2012

Re: [Pharo-project] Nautilus oddities (Naudities?)

by Benjamin

Obviously some stuff I did wrong :) More often, it's just because of a lack of review, most probably because I shouldn't code after 4am :) Thanks for your feedback, I will have a look at this asap :) Could you please open a bug entry to be sure I will not forget ? :) Thanks again, Ben On May 12, 2012, at 11:48 PM, blake wrote: > Observation: > > The Nautilus browser seems to have a tendency to offer options that > have no effect. Or maybe it's just the refactoring elements, I'm not > sure how the integration works. > > When right clicking on the method pane one seems to get the full suite > of options even if no method is selected. > > One of the refactoring options is "move to class side" which one gets > even when one is already ON the class side. > > ===Blake=== >

May 12, 2012

Re: [Pharo-project] [Seaside] Zinc as static file server

by Sven Van Caekenberghe

On 12 May 2012, at 19:17, Paul DeBruicker wrote: >> BTW, we (or I) definitively need to add If-Modified-Since and 304 Not Modified behavior to ZnZincStaticServerAdaptor. >> > > OK. I added that to the version I just uploaded. I'll have a look later on (I have little time this weekend). We also need at least one simple test (another one of Marcus' quotes; if there is no actively run test, it does not exist). We just need an extra version of #testIfModifiedSinceNotModified directly on a local server, it will require some setup, be it should be doable. >> And I know that you know, but let me repeat that in production situations you definitively have to let apache or nginx serve the statis files, to take load of Seaside. >> > > Yes definitely. > >> Your hack in ZnSeasideStaticServerAdaptorDelegate>>#handleRequest: lets Seaside first try and make an error before you consider static file serving, this almost defeats the purpose of not doing it by Seaside itself. Just a hunch, I haven't tested or benchmarked this. > > Does Seaside have the ability to serve files from disk without loading them into a WAFileLibrary? I couldn't figure that out, or gave up before trying really. I edit all my CSS and JS in emacs and its a pain to reload after saving/committing. And for my use case the performance is fine. Yes, your use case is perfectly valid. Sven

May 12, 2012

[Pharo-project] Nautilus oddities (Naudities?)

by blake

Observation: The Nautilus browser seems to have a tendency to offer options that have no effect. Or maybe it's just the refactoring elements, I'm not sure how the integration works. When right clicking on the method pane one seems to get the full suite of options even if no method is selected. One of the refactoring options is "move to class side" which one gets even when one is already ON the class side. ===Blake===

May 12, 2012

Re: [Pharo-project] I cannot see the code in the latest Moose build

by Fabrizio Perin

Good! Thanks Benjamin. Fabrizio 2012/5/12 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > Cool :) > > Ben > > On May 12, 2012, at 10:11 PM, Tudor Girba wrote: > > > Thanks. It works now. > > > > Cheers, > > Doru > > > > > > On 12 May 2012, at 18:05, Benjamin wrote: > > > >> Thank you guys :) > >> > >> It was a stupid mistake when posting versions :) > >> So I fix it, and push the latest 2.0 fixes in the 1.4 version :) > >> > >> So now it seems to work properly :) > >> > >> Could you try and confirm please ? > >> > >> Thanks in advance, > >> > >> Ben > >> > >> On May 12, 2012, at 3:38 PM, Fabrizio Perin wrote: > >> > >>> Hi, > >>> just download the Moose build of May the 8th > >>> > >>> http://ci.moosetechnology.org/job/moose-latest-dev/972/artifact/moose/ > >>> > >>> and open Nautilus. You will notice that the browser is empty. > >>> > >>> I think that either in Moose is loaded the latest version of Nautilus, > so we can report bugs or suggest improvements (and we benefit from the on > going work), or it pointless to load Nautilus. > >>> If we have to rely on a fix version of a development environment than > I believe it is better to rely on an old version of a mature development > environment such as OB. This is why I suggested to use OB instead of > Nautilus. > >>> > >>> Cheers, > >>> Fabrizio > >>> > >>> > >>> 2012/5/12 Tudor Girba <tudor(a)tudorgirba.com> > >>> Hi, > >>> > >>> The problem is reproducible in the latest Pharo 1.4. > >>> > >>> Just download it, and then run: > >>> Gofer new > >>> url: 'http://ss3.gemstone.com/ss/Nautilus'; > >>> package: 'ConfigurationOfNautilus'; > >>> load. > >>> (ConfigurationOfNautilus project version: #stable) load. > >>> > >>> Cheers, > >>> Doru > >>> > >>> > >>> On 12 May 2012, at 14:20, Benjamin wrote: > >>> > >>>> Could you please point me where I can download the image and the > exact way to reproduce the issue ? > >>>> > >>>> Because it clearly sounds weird to me, and I am proud that Moose use > Nautilus :) > >>>> > >>>> > >>>> Thanks in advance, > >>>> Ben > >>>> > >>>> > >>>> On May 12, 2012, at 12:06 PM, Fabrizio Perin wrote: > >>>> > >>>>> If we don't use the latest version of Nautilus what about to load > the working version of Omnibrowser? > >>>>> > >>>>> Gofer new > >>>>> squeaksource: 'MetacelloRepository'; > >>>>> package: 'ConfigurationOfOmniBrowser'; > >>>>> load. > >>>>> > >>>>> (ConfigurationOfOmniBrowser > >>>>> project version: #stable) load: #( 'Dev' 'Dev Tests'). > >>>>> > >>>>> Cheers, > >>>>> Fabrizio > >>>>> > >>>>> 2012/5/11 Tudor Girba <tudor(a)tudorgirba.com> > >>>>> Now, I switched the build process to use as a seed, the fixed > Nautilus image built on May 4. > >>>>> > >>>>> This means that, at this point, in the Moose image Nautilus does not > get updated anymore. > >>>>> > >>>>> Cheers, > >>>>> Doru > >>>>> > >>>>> > >>>>> On 11 May 2012, at 08:52, Tudor Girba wrote: > >>>>> > >>>>>> I can reproduce the problem. > >>>>>> > >>>>>> Nautilus is loaded from its own repository like: > >>>>>> Gofer new > >>>>>> url: 'http://ss3.gemstone.com/ss/Nautilus'; > >>>>>> package: 'ConfigurationOfNautilus'; > >>>>>> load. > >>>>>> (ConfigurationOfNautilus project version: #stable) load. > >>>>>> > >>>>>> > >>>>>> It seems that when you load this in Pharo 1.4, there is a mismatch > with RPackage-Core: if I load the latest RPackage-Core version, it seems to > work. > >>>>>> > >>>>>> But, if you load the version (213) from the MetaRepoForPharo14, it > works. So, now I changed the loading code to be: > >>>>>> Gofer new > >>>>>> squeaksource:'MetaRepoForPharo14'; > >>>>>> package: 'ConfigurationOfNautilus'; > >>>>>> load. > >>>>>> (ConfigurationOfNautilus project version: #stable) load. > >>>>>> > >>>>>> > >>>>>> Nevertheless, it would be good if the ConfigurationOfNautilus would > continue to load properly in 1.4. > >>>>>> > >>>>>> Cheers, > >>>>>> Doru > >>>>>> > >>>>>> > >>>>>> > >>>>>> On 10 May 2012, at 15:01, Fabrizio Perin wrote: > >>>>>> > >>>>>>> Hi, > >>>>>>> I download the latest yellow build from the moose web site (8 > may). When I open Nautilus I cannot see the code. > >>>>>>> > >>>>>>> I don't have any clue if it is about Nautilus or about how > Nautilus is loaded in Moose or about something else. > >>>>>>> > >>>>>>> Any idea? > >>>>>>> > >>>>>>> Cheers, > >>>>>>> Fabrizio > >>>>>> > >>>>>> -- > >>>>>> www.tudorgirba.com > >>>>>> > >>>>>> "Sometimes the best solution is not the best solution." > >>>>>> > >>>>> > >>>>> -- > >>>>> www.tudorgirba.com > >>>>> > >>>>> "It's not how it is, it is how we see it." > >>>>> > >>>>> > >>>>> > >>>> > >>> > >>> -- > >>> www.tudorgirba.com > >>> > >>> "Not knowing how to do something is not an argument for how it cannot > be done." > >>> > >>> > >>> > >> > > > > -- > > www.tudorgirba.com > > > > "There are no old things, there are only old ways of looking at them." > > > > > > > > > > >

May 12, 2012

Re: [Pharo-project] I cannot see the code in the latest Moose build

by Benjamin

Cool :) Ben On May 12, 2012, at 10:11 PM, Tudor Girba wrote: > Thanks. It works now. > > Cheers, > Doru > > > On 12 May 2012, at 18:05, Benjamin wrote: > >> Thank you guys :) >> >> It was a stupid mistake when posting versions :) >> So I fix it, and push the latest 2.0 fixes in the 1.4 version :) >> >> So now it seems to work properly :) >> >> Could you try and confirm please ? >> >> Thanks in advance, >> >> Ben >> >> On May 12, 2012, at 3:38 PM, Fabrizio Perin wrote: >> >>> Hi, >>> just download the Moose build of May the 8th >>> >>> http://ci.moosetechnology.org/job/moose-latest-dev/972/artifact/moose/ >>> >>> and open Nautilus. You will notice that the browser is empty. >>> >>> I think that either in Moose is loaded the latest version of Nautilus, so we can report bugs or suggest improvements (and we benefit from the on going work), or it pointless to load Nautilus. >>> If we have to rely on a fix version of a development environment than I believe it is better to rely on an old version of a mature development environment such as OB. This is why I suggested to use OB instead of Nautilus. >>> >>> Cheers, >>> Fabrizio >>> >>> >>> 2012/5/12 Tudor Girba <tudor(a)tudorgirba.com> >>> Hi, >>> >>> The problem is reproducible in the latest Pharo 1.4. >>> >>> Just download it, and then run: >>> Gofer new >>> url: 'http://ss3.gemstone.com/ss/Nautilus'; >>> package: 'ConfigurationOfNautilus'; >>> load. >>> (ConfigurationOfNautilus project version: #stable) load. >>> >>> Cheers, >>> Doru >>> >>> >>> On 12 May 2012, at 14:20, Benjamin wrote: >>> >>>> Could you please point me where I can download the image and the exact way to reproduce the issue ? >>>> >>>> Because it clearly sounds weird to me, and I am proud that Moose use Nautilus :) >>>> >>>> >>>> Thanks in advance, >>>> Ben >>>> >>>> >>>> On May 12, 2012, at 12:06 PM, Fabrizio Perin wrote: >>>> >>>>> If we don't use the latest version of Nautilus what about to load the working version of Omnibrowser? >>>>> >>>>> Gofer new >>>>> squeaksource: 'MetacelloRepository'; >>>>> package: 'ConfigurationOfOmniBrowser'; >>>>> load. >>>>> >>>>> (ConfigurationOfOmniBrowser >>>>> project version: #stable) load: #( 'Dev' 'Dev Tests'). >>>>> >>>>> Cheers, >>>>> Fabrizio >>>>> >>>>> 2012/5/11 Tudor Girba <tudor(a)tudorgirba.com> >>>>> Now, I switched the build process to use as a seed, the fixed Nautilus image built on May 4. >>>>> >>>>> This means that, at this point, in the Moose image Nautilus does not get updated anymore. >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> On 11 May 2012, at 08:52, Tudor Girba wrote: >>>>> >>>>>> I can reproduce the problem. >>>>>> >>>>>> Nautilus is loaded from its own repository like: >>>>>> Gofer new >>>>>> url: 'http://ss3.gemstone.com/ss/Nautilus'; >>>>>> package: 'ConfigurationOfNautilus'; >>>>>> load. >>>>>> (ConfigurationOfNautilus project version: #stable) load. >>>>>> >>>>>> >>>>>> It seems that when you load this in Pharo 1.4, there is a mismatch with RPackage-Core: if I load the latest RPackage-Core version, it seems to work. >>>>>> >>>>>> But, if you load the version (213) from the MetaRepoForPharo14, it works. So, now I changed the loading code to be: >>>>>> Gofer new >>>>>> squeaksource:'MetaRepoForPharo14'; >>>>>> package: 'ConfigurationOfNautilus'; >>>>>> load. >>>>>> (ConfigurationOfNautilus project version: #stable) load. >>>>>> >>>>>> >>>>>> Nevertheless, it would be good if the ConfigurationOfNautilus would continue to load properly in 1.4. >>>>>> >>>>>> Cheers, >>>>>> Doru >>>>>> >>>>>> >>>>>> >>>>>> On 10 May 2012, at 15:01, Fabrizio Perin wrote: >>>>>> >>>>>>> Hi, >>>>>>> I download the latest yellow build from the moose web site (8 may). When I open Nautilus I cannot see the code. >>>>>>> >>>>>>> I don't have any clue if it is about Nautilus or about how Nautilus is loaded in Moose or about something else. >>>>>>> >>>>>>> Any idea? >>>>>>> >>>>>>> Cheers, >>>>>>> Fabrizio >>>>>> >>>>>> -- >>>>>> www.tudorgirba.com >>>>>> >>>>>> "Sometimes the best solution is not the best solution." >>>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "It's not how it is, it is how we see it." >>>>> >>>>> >>>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Not knowing how to do something is not an argument for how it cannot be done." >>> >>> >>> >> > > -- > www.tudorgirba.com > > "There are no old things, there are only old ways of looking at them." > > > >

May 12, 2012

Re: [Pharo-project] I cannot see the code in the latest Moose build

by Tudor Girba

Thanks. It works now. Cheers, Doru On 12 May 2012, at 18:05, Benjamin wrote: > Thank you guys :) > > It was a stupid mistake when posting versions :) > So I fix it, and push the latest 2.0 fixes in the 1.4 version :) > > So now it seems to work properly :) > > Could you try and confirm please ? > > Thanks in advance, > > Ben > > On May 12, 2012, at 3:38 PM, Fabrizio Perin wrote: > >> Hi, >> just download the Moose build of May the 8th >> >> http://ci.moosetechnology.org/job/moose-latest-dev/972/artifact/moose/ >> >> and open Nautilus. You will notice that the browser is empty. >> >> I think that either in Moose is loaded the latest version of Nautilus, so we can report bugs or suggest improvements (and we benefit from the on going work), or it pointless to load Nautilus. >> If we have to rely on a fix version of a development environment than I believe it is better to rely on an old version of a mature development environment such as OB. This is why I suggested to use OB instead of Nautilus. >> >> Cheers, >> Fabrizio >> >> >> 2012/5/12 Tudor Girba <tudor(a)tudorgirba.com> >> Hi, >> >> The problem is reproducible in the latest Pharo 1.4. >> >> Just download it, and then run: >> Gofer new >> url: 'http://ss3.gemstone.com/ss/Nautilus'; >> package: 'ConfigurationOfNautilus'; >> load. >> (ConfigurationOfNautilus project version: #stable) load. >> >> Cheers, >> Doru >> >> >> On 12 May 2012, at 14:20, Benjamin wrote: >> >> > Could you please point me where I can download the image and the exact way to reproduce the issue ? >> > >> > Because it clearly sounds weird to me, and I am proud that Moose use Nautilus :) >> > >> > >> > Thanks in advance, >> > Ben >> > >> > >> > On May 12, 2012, at 12:06 PM, Fabrizio Perin wrote: >> > >> >> If we don't use the latest version of Nautilus what about to load the working version of Omnibrowser? >> >> >> >> Gofer new >> >> squeaksource: 'MetacelloRepository'; >> >> package: 'ConfigurationOfOmniBrowser'; >> >> load. >> >> >> >> (ConfigurationOfOmniBrowser >> >> project version: #stable) load: #( 'Dev' 'Dev Tests'). >> >> >> >> Cheers, >> >> Fabrizio >> >> >> >> 2012/5/11 Tudor Girba <tudor(a)tudorgirba.com> >> >> Now, I switched the build process to use as a seed, the fixed Nautilus image built on May 4. >> >> >> >> This means that, at this point, in the Moose image Nautilus does not get updated anymore. >> >> >> >> Cheers, >> >> Doru >> >> >> >> >> >> On 11 May 2012, at 08:52, Tudor Girba wrote: >> >> >> >> > I can reproduce the problem. >> >> > >> >> > Nautilus is loaded from its own repository like: >> >> > Gofer new >> >> > url: 'http://ss3.gemstone.com/ss/Nautilus'; >> >> > package: 'ConfigurationOfNautilus'; >> >> > load. >> >> > (ConfigurationOfNautilus project version: #stable) load. >> >> > >> >> > >> >> > It seems that when you load this in Pharo 1.4, there is a mismatch with RPackage-Core: if I load the latest RPackage-Core version, it seems to work. >> >> > >> >> > But, if you load the version (213) from the MetaRepoForPharo14, it works. So, now I changed the loading code to be: >> >> > Gofer new >> >> > squeaksource:'MetaRepoForPharo14'; >> >> > package: 'ConfigurationOfNautilus'; >> >> > load. >> >> > (ConfigurationOfNautilus project version: #stable) load. >> >> > >> >> > >> >> > Nevertheless, it would be good if the ConfigurationOfNautilus would continue to load properly in 1.4. >> >> > >> >> > Cheers, >> >> > Doru >> >> > >> >> > >> >> > >> >> > On 10 May 2012, at 15:01, Fabrizio Perin wrote: >> >> > >> >> >> Hi, >> >> >> I download the latest yellow build from the moose web site (8 may). When I open Nautilus I cannot see the code. >> >> >> >> >> >> I don't have any clue if it is about Nautilus or about how Nautilus is loaded in Moose or about something else. >> >> >> >> >> >> Any idea? >> >> >> >> >> >> Cheers, >> >> >> Fabrizio >> >> > >> >> > -- >> >> > www.tudorgirba.com >> >> > >> >> > "Sometimes the best solution is not the best solution." >> >> > >> >> >> >> -- >> >> www.tudorgirba.com >> >> >> >> "It's not how it is, it is how we see it." >> >> >> >> >> >> >> > >> >> -- >> www.tudorgirba.com >> >> "Not knowing how to do something is not an argument for how it cannot be done." >> >> >> > -- www.tudorgirba.com "There are no old things, there are only old ways of looking at them."

May 12, 2012