Max, Thanks for taking care of that!
There is one thing we need to address with Webdoc: the system only documents packages, which is a pain with tags as it puts all classes together without any notion of the package tags. I use a ton of such tags and it makes the WebDoc very hard to use as ... a doc. Also, the tree for the inheritance graphic/popup is not working. I also saw some Yumlme code in the thing, if anyone knows how to use it, thanks in advance. I'll be working on my doc end of the month, that's why I asked about the Roassal UML Builder as well. If we could link the two together, we'd have a very cool toolkit for documenting things. Phil On Tue, Nov 11, 2014 at 9:59 PM, Max Leske <[email protected]> wrote: > > On 11.11.2014, at 21:53, [email protected] wrote: > > Well, the VM is on Github. > > I have switched my workflow to filetree:// (I commit using external tools > like git gui and git command line tools). > > With Thierry's merge driver, it is a joy to use. > > gitfiletree: works but I like the filetree:// way (especially since I have > lots of non Pharo files around). > > It's solid, it works well with Jenkins picking up new commits and > rebuilding. > > mczs are useful but as shipping units and safeguards. > > And Smalltalkhub is not that available/reliable, let's face it. > > I can live with it for standard packages that are at one point in my > general package-cache but full reloads are painful on bad days. > > > We’ll get there :) But for now at least WebDoc has been saved. Everything > else is just icing on the cake. > > > Phil > > On Tue, Nov 11, 2014 at 9:28 PM, Stephan Eggermont <[email protected]> > wrote: > >> Max wrote: >> >THIS IS MEANT ONLY AS A TEMPORARY SOLUTION! I only wanted to get the >> build back up. If anyone want’s to take care of >PetitMarkdown or WebDoc, >> move them back to github or whatever, please feel free. >> >> For the moment, our development infrastructure is smalltalkhub and >> ci.inria.fr. >> There is lots of experiments going on with travis and github. At the >> moment, >> I can not use that for my pharo development, it simply does not work on >> my >> machines. It is likely that has something to do with package management on >> mac (I have macports, homebrew, fink and stand-alone installs of software >> ). >> I do use git & github for other development, so I'm looking forward to >> being able to use the git(hub) infrastruture from inside my image. >> Till then, please don't move things to github that you hope others will >> use. >> It is fine to experiment, but not everyone can contribute there. >> >> >There is no project PharoExtras…? And if there were, I wouldn’t have >> write permission :) >> >> You are now in team PharoExtras >> >> Stephan >> > > >
