February 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] HelpSystem & Class comments
by Torsten Bergmann Feb. 24, 2010

Feb. 24, 2010

Crosspost squeak-dev/pharo-dev Andreas Raab wrote: >a) Currently a book depends on the presence of HelpSystem (i.e., via >subclassing). No, you are not forced to be in the "CustomHelp" hierarchy. You can define an own hierarchy, directly as subclass of Object, whatever (athough I would recommond CustomHelp as common superclass similar to TestCase in SUnit) The standard builder ("HelpBuilder") is able to use a different root. See HelpBuilder class>>buildFromRoot: and HelpBuilder>>defaultRoot. With HelpSystem-Core-tbn.16 I even allow to provide own builders. To get the latest you can just load the baseline: (ConfigurationOfHelpSystem project version: '1.0-baseline') load b) Typing in '' quotes is pretty insane when you quote text. I know, but this is annoying since you currently write it manually using the browser and by adding methods yourself. Storing the contents in method is just the vehicle - additional authoring capabilities would help here in the future (an additional HelpEditor beside the HelpViewer). Again you judged too early. I would also like to see some reactivation of Scamper code for a more capable viewer/editor - since with a basic support for simple markup we could catch two flies by providing in-image and web-help with the same contents/source. >I'm not saying that comments are the only way by which HelpBooks should >be created but I think that this should be one of the ways that >HelpSystem directly supports. That's already there - Danny already added this for the help classes. Just open the book "Help on Help" -> "HelpSystem API Documentation" and subnodes after loading the latest baseline. If you click on a class node you will see the class comment displayed in the help (currently as ASCII). We may add a book "Reference" where you open two subbooks: "By categories" and "By hierarchy" - displaying the classes using categories or in their usual class hierarchy for browsing. However: the main question to me is the kind of format we should use: a) Wiki Style or similar + easy to write + easy to transform - mostly non-standard With Maven the APT format is often used [1], Eclipse for instance provides even editors, see [2] for screenshots) But we also have Tiny wiki syntax somewhere on SqueakSource which may be similar. b) real markup like HTML + easy to put onto the web without tranformation - we need to have more markup support -/+ embedding of Smalltalk has to be done the W3C way, similar to javascript <a href="smalltalk:..." c) specific format like Squeaks Text representation with textDoits, ... - very Squeak specific and may not work in Pharo - hard to put on the web I would like to see b) with a cleaned up Scamper code since a general markup editor/viewer would be helpfull anyway and it would be easy to publish stuff on the web. But looks like more work. There is also another HTML browser with markup and CSS now available open source as MIT (WithStyle), see [3] and [4] for more info. Maybe someone has a minute ;) Bye T. [1] http://maven.apache.org/doxia/references/apt-format.html [2] http://sourceforge.net/project/screenshots.php?group_id=193560 [3] http://n4.nabble.com/ANN-HelpSystem-was-ProfStef-td1554685.html [4] http://www.cincomsmalltalk.com/userblogs/rowanb/blogView?showComments=true&… -- Sicherer, schneller und einfacher. Die aktuellen Internet-Browser - jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/chbrowser

2 1

[Pharo-project] Issue 1972 clean ResourceCollector, ResourceManager and ResouceLocator reopened
by Pavel Krivanek Feb. 24, 2010

Feb. 24, 2010

Hi, I reopened the issue 1972 because it caused an obsolete class instance in Project current instVarNamed: #resourceManager Cheers, -- Pavel

2 1

[Pharo-project] Issue 1797 Object>>initialExtent reopened
by Pavel Krivanek Feb. 24, 2010

Feb. 24, 2010

Hi, I reopened the issue 1797 because it caused the deprecation warning while opening the FileBrowser. see: http://code.google.com/p/pharo/issues/detail?id=1797 -- Pavel

1 0

Re: [Pharo-project] [ANN] Magma 1.0 release 44
by Chris Muller Feb. 24, 2010

Feb. 24, 2010

Hi Ramiro, something happened between Pharo1.0-10502-rc1dev09.12.2. and 10508 related to Networking. Please see: http://lists.gforge.inria.fr/pipermail/pharo-project/2010-February/021912.h… I am not sure what happened. Perhaps someone on the Pharo team would elaborate? - Chris On Tue, Feb 23, 2010 at 6:54 PM, Ramiro Diaz Trepat <ramiro(a)diaztrepat.name> wrote: > Hi Chris, > Once again, thanks for your work. > One question though, is this version running fine on the latest Pharo 1.0 ? > I haven't been able to start a server successfuly, I get a primitive has > failed. > It doesn't run on Pharo 1.1 or Squeak trunk but you didn't mention those :) > I loaded it in a fresh Pharo 1.0 image using: > ScriptLoader new installer. > Installer ss project: 'Magma'; > install: '1.0r44 (server)'. > > Cheers > > r > > On Wed, Feb 17, 2010 at 8:46 PM, Chris Muller <asqueaker(a)gmail.com> wrote: >> >> I am pleased to announce the immediate availability of Magma 1.0 >> release "44" for both Squeak, 3.9, 3.10 and Pharo. Â Although I am >> looking into alternatives for future releases, for now I am still >> distributing Magma in my traditional ways: >> >> Â - On SqueakMap - three one-click installable packages. >> >> Â - In the "1.0r44" Monticello Configuration in the "Magma" project of >> squeaksource, there are three one-click installable configurations >> (client, server, tester). >> >> Â - The "r44Final" Monticello Configuration in the "MagmaTester" >> project of squeaksource is the one-click installable MagmaTester >> package. >> >> As has always been the case, ONLY ONE of the three packages needs to >> be installed, the full and proper configuration is loaded with >> one-click. >> >> Compared to r43, this is mostly a maintenance release without any >> major new functionality, but with improved robustness in the HA and >> luxury querying as well as several other fixes. Â Here are the specific >> improvements over 43: >> >> Â Â Â Â - Made several HA fixes and improvements, many identified by Bart >> Gaquie by testing with more than a two-server Magma Node. Â Many thanks >> Bart. >> Â Â Â Â - Updated MaQueryExecutor>>#fractionComplete to answer an unreduced >> Fraction instead of a reduced one. Â This convey's more information; >> since the denominator represents the total number of elements in the >> final result. Â Thanks again to Bart Gauqie. >> Â Â Â Â - Upgraded MagmaCollectionReader>>#release to allow give a >> well-behaved application much freer access to the "luxury" query >> features of MagmaCollections. Â It is essential for applications >> employing luxury query features of Magma for ad-hoc querying, to >> #release the Reader returned from the query so that resources on the >> server can be freed. >> Â Â Â Â - Now properly truncating the applied.images file, so it doesn't >> grow >> and grow.. >> Â Â Â Â - Now, when a repository is opened locally, if it's location has >> never been set (new repository) or was a different *local* location, >> then update it to the new aMagmaLocalLocation. Â If it was formerly a >> network-hosted server, do not update since we could be here simply >> just for re-opening that repository. Â So, to go from a remote >> repository to a local one, you have to manually update the node's >> primaryLocation. >> Â Â Â Â - Server no longer allows any clients to log in with the system >> name, >> since it is sometimes checked for special-purpose server housekeeping. >> Â Â Â Â - Updated MagmaSession's standard printing method, again! >> Â Â Â Â - Added MagmaCollectionReader>>#sortBy:makeDistinct:descending: and >> #sortBy:makeDistinct:descending:. >> Â Â Â Â - Made MaRepositoryDisconnectRequest asynchronous, it now returns >> considerably faster! >> Â Â Â Â - Fix for a recent MagmaCollection optimization. >> Â Â Â Â - Removed hard-reference to OSProcess. >> Â Â Â Â - Patch for #removeListener to avoid DependentsArray problem. >> Â Â Â Â - Fixed a ReadStrategy regression. >> _______________________________________________ >> Magma mailing list >> Magma(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/mailman/listinfo/magma > > > _______________________________________________ > Magma mailing list > Magma(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/magma > >

3 2

[Pharo-project] Why a package management system
by Torsten Bergmann Feb. 24, 2010

Feb. 24, 2010

>Janko, I don't know what it "decent" for you, but did you try Metacello-OB >and Metaceller ? I think what is still missing is a common tutorial showing all the details and pieces that are already here today. Not everybody reads the blog posts from Dale or follows the mailinglists. Is there a preview/early draft for the book chapter on Metacello available? Could it be posted/discussed here? Thx T. -- NEU: Mit GMX DSL Ã¼ber 1000,- Â¿ sparen! http://portal.gmx.net/de/go/dsl02

2 1

[Pharo-project] Shout
by StÃ©phane Ducasse Feb. 24, 2010

Feb. 24, 2010

Hi guys I would like to know which version of shout we are using and relying on. Apparently one version was integrated on squeak and I would like to make sure that the one we use continue to get improved. One of these days we will have to think about the status of important packages that are external to pharo: shout, XMLSupport.... Stef

2 1

[Pharo-project] 16rff broke 16r8e7
by Nicolas Cellier Feb. 24, 2010

Feb. 24, 2010

As you may know, with 16rff change, we cannot anymore use a radix notation combined with an exponent notation. At least for base > 14, the exponent letter is taken as an ordinary digit. The options are: 1) revert the change 2) abandon combined radix+exponent notation all the code for printing Float with different radix, and also for scanning can be removed Or I can provide a subclass of SqNumberParser for backward compatibility. 3) find a new syntax for radix+exponent For example, 16r7f_e6 16r7f^6 16r7f#6 None of these is ambiguous with existing code. Or maybe use an uppercase R for uppercase only digits... 4) use q exponent to at least enable base 16 This is hackish and not universal, but I guess hardly anybody ever used a base > 16. ------------------------------------- What would squeak/pharo folks choose ? ------------------------------------- Personnally, I'm OK with 1) and 2). But 2) deserves a bit more discussion After all this is a change of Squeak syntax. I find Dan's notation educative and fun, especially for writing tests. But it is a non portable Squeakish thing, rarely used, and it does not really has much value for industrial usage, On the other hand, is it really necessary to parse 16rff ? I dislike 3) because I find my own propositions bad. Also, if we remove Squeak-specific syntax for compatibility reasons, why the hell adding a new uncompatible syntax? Previous usage of e notation was far better because just extending an existing syntax, not creating a new one. Maybe you'll have other ideas... Nicolas -------------------------------------

3 6

[Pharo-project] Metacello --- How to make sure that we will be able to load... in 3 years from now
by stephane ducasse Feb. 24, 2010

Feb. 24, 2010

Hi all I would like that we have a discussion about how do we put in place an infrastructure to make sure that we can get metacello configuration working in 3/5 years from now. I think that there are two scenarios: MyProject ====== in my project I used metacello and I publish a config and if it breaks in the future this is my responsibility PublishedMyProjectIn ============= When I publish my project (for now I copy the configuration file from my repository to the one of metacello) in the metacelloPharo1.0 project, we could automatically pulled up all the necessary files and copy them in the 1.0 repository. This way we can shield and make sure that a project can be loaded. I would like to have MetacelloMetaRepository1.0 MetacelloMetaRepository1.1 MetacelloMetaRepository1.2 ... what do you think? Stef

9 12

Feb. 23, 2010

Hi guys if you want to follow the changes that are done during an update you can open the Tools > Code recovering > recent submission There is a slight bug with the scrolling list but this tool is useful. Stef

1 0

Feb. 23, 2010

11230 ----- - Issue 2048: delete class ChangeListForProjects - Issue 2041: remove #isSketchMorph - Issue 1519: remove #asKnownNameMenu - Issue 2031: Should add empty TheWorldMenu class - Issue 2046: Remove Network-in-Browser support (not used) - Issue 2028: remove Morph methods (#adaptedToWorld: and some more) - Issue 2033: remove Modell>>addItem: - Issue 2051: Clean users of Utilities - Issue 2052: PluggableDialogWindow should Inherit from ModelDependentDialogWindow - Issue 1950: Polymorph usage are broken - Clean some undeclared variables Stef

1 0