+1 On Dec 11, 2010, at 8:45 PM, Lukas Renggli wrote:
>> On the chat, it seemed that the main objection was depending on an external >> class. Since HelpSystem is now part of core, what is the problem there? >> Isn't it just like Tests depending on TestCase? > > After running the tests, first thing I do in a Pharo 1.2 core image on > my build server: > > ====================================== > > "Unload all tests" > (MCWorkingCopy allManagers > inject: Gofer new > into: [ :gofer :each | > ((each packageName endsWith: 'Test') or: [ each packageName > endsWith: 'Tests' ]) > ifTrue: [ gofer package: each packageName ]. > gofer ]) > unload. > > "Unload other packages" > Gofer new > package: 'FixUnderscores'; > package: 'Glamour-Morphic-Theme'; > package: 'HelpSystem-Core'; > package: 'Announcements-Help'; > package: 'Regex-Help'; > unload. > > ====================================== > > That means that I cannot load any package that includes pages for the > help system. Furthermore, this means that none of my packages will > ever include help system text, even if I would love to include my blog > articles (for example for PetitParser) somehow more accessible than in > a class comment. > > In fact, I haven't seen a single non-core package providing help > pages. On contrary, there are many packages providing settings. This > does not introduce any dependencies. Maybe this is a hint? > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >
