- Pharo-dev - lists.pharo.org

Re: [Pharo-project] NewTextMorph authoringPrototype

by Tudor Girba

Hi, Ok, but the problem appears also with a simple NewTextMorph: | t | t := NewTextMorph new. t openInWorld . Cheers, Doru On 11 Dec 2010, at 18:30, StÃ©phane Ducasse wrote: > doru authoringPrototype looks to me like deprecated. > and may be it was reintroduced when we loaded it back. > > Stef > > On Dec 11, 2010, at 6:26 PM, Tudor Girba wrote: > >> Hi, >> >> I was looking for examples of how to use NewTextMorph, and I tried: >> >> NewTextMorph authoringPrototype >> >> However, it raises errors which seem to be related to an initialization problem. Am I doing something wrong, or is it simply a bug? >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Not knowing how to do something is not an argument for how it cannot be done." >> >> > > -- www.tudorgirba.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

Dec. 12, 2010

Re: [Pharo-project] About using pragma for help like in setting

by Lukas Renggli

>> - For deployment I don't want to have unnecessary code loaded. >> > Couldn't you just add another loop to your script to "unload all help" just > like unload all tests Sure, but that means I have to package help text separately. This is the contrary to what Java, Ruby, Python, Javascript, ... are doing; keeping code and documention as close together as possible. >> - For portability I don't want to depend on "proprietary" code. >> > If you were installing on a non-HelpSystem platform, wouldn't you not even > load the help packages? Documenation is not going to be written (and read) if this is painful. I wouldn't bother to create a separate help package for each of the 30 Seaside model packages. I wouldn't even bother to load 30 packages to find some help, or find the right class to maintain them. Code should be as close with the documentation as possible, e.g. in method and class comments; but sometimes you want to present an overal picture or nicely aggreate method and class comments. This is not currently possible without pain. I think, the fact that there is no single external package with help system documentation proves this, no? Lukas -- Lukas Renggli www.lukas-renggli.ch

Dec. 11, 2010

Re: [Pharo-project] SmalltalkEditor new -> DNU

by Alain Plantec

Le 11/12/2010 21:21, StÃ©phane Ducasse a Ã©crit : > Hi > > When I tried to open a browser in SimpleMorphic I got an infinite DNU > Now the problem is not in SimpleMorphic but SmalltalkEditor new does not work. I will take a look. Alain > Stef > > > > > >

Dec. 11, 2010

Re: [Pharo-project] About using pragma for help like in setting

by Sean P. DeNigris

Lukas Renggli wrote: > > - For usability I want to have documentation accessible. > My intention is to learn something here. Are you saying that it would be beneficial to have your project's help pages included, even if the HelpSystem is not present, and have them degrade (e.g. to being browsed via implementorsOf like Steph mentioned). Because otherwise, it seems... Lukas Renggli wrote: > > - For deployment I don't want to have unnecessary code loaded. > Couldn't you just add another loop to your script to "unload all help" just like unload all tests Lukas Renggli wrote: > > - For portability I don't want to depend on "proprietary" code. > If you were installing on a non-HelpSystem platform, wouldn't you not even load the help packages? Sean -- View this message in context: http://forum.world.st/About-using-pragma-for-help-like-in-setting-tp3078978… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 11, 2010

Re: [Pharo-project] About using pragma for help like in setting

by Lukas Renggli

>> I cannot load any package that includes pages for the >> help system. >> > I guess that's what I don't understand. Â Why remove HelpSystem at all? - For deployment I don't want to have unnecessary code loaded. - For portability I don't want to depend on "proprietary" code. - For usability I want to have documentation accessible. Lukas -- Lukas Renggli www.lukas-renggli.ch

Dec. 11, 2010

Re: [Pharo-project] About using pragma for help like in setting

by Sean P. DeNigris

Lukas Renggli wrote: > > I cannot load any package that includes pages for the > help system. > I guess that's what I don't understand. Why remove HelpSystem at all? Lukas Renggli wrote: > > 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? > A hint that non-documentation habits are hard to break? ;-) -- View this message in context: http://forum.world.st/About-using-pragma-for-help-like-in-setting-tp3078978… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 11, 2010

Re: [Pharo-project] Issue 3177 in pharo: add sophie copyright

by Levente Uzonyi

You must add the license in 1.2, because there's already code in the image from Sophie. Levente On Sat, 11 Dec 2010, pharo(a)googlecode.com wrote: > Updates: > Labels: -Milestone-1.2 Milestone-1.3 > > Comment #2 on issue 3177 by stephane.ducasse: add sophie copyright > http://code.google.com/p/pharo/issues/detail?id=3177 > > (No comment was entered for this change.) > >

Dec. 11, 2010

[Pharo-project] Issue 3404 in pharo: Recent messages should be able to work on a limited subset of the recently changed methods

by pharo＠googlecode.com

Status: Accepted Owner: stephane.ducasse CC: Benjamin.VanRyseghem.Pharo Labels: Milestone-1.2 New issue 3404 by stephane.ducasse: Recent messages should be able to work on a limited subset of the recently changed methods http://code.google.com/p/pharo/issues/detail?id=3404 Benjamin RecentMessages is terribly slow and it should also take a lot of spaces when we have a lot of changes. Then when I selected version + by version I do not understand what it means and when I press browse I got an error.

Dec. 11, 2010

Re: [Pharo-project] Issue 3177 in pharo: add sophie copyright

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2 Milestone-1.3 Comment #2 on issue 3177 by stephane.ducasse: add sophie copyright http://code.google.com/p/pharo/issues/detail?id=3177 (No comment was entered for this change.)

Dec. 11, 2010

Re: [Pharo-project] Issue 2755 in pharo: Image Save loses Form's color [black becomes transparent]

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2 Milestone-1.3 Comment #12 on issue 2755 by stephane.ducasse: Image Save loses Form's color [black becomes transparent] http://code.google.com/p/pharo/issues/detail?id=2755 (No comment was entered for this change.)

Dec. 11, 2010