- Pharo-dev - lists.pharo.org

[Pharo-project] ToolSet

by Pavel Krivanek

Hi, we should decide how we will manipulate with tools. A lot of tools classes are referenced directly - that is wrong because you cannot then use different set of tools (for example a dummy toolset for no tools at all). In the KernelImage I added a registration mechanism for tools so they were called for example ToolSet default browser. There were no ToolSet subclasses and there was only a test if the default ToolSet is not nil. That was not optimal solution. The current philosophy of ToolSet class supposess that you will send messages directly to ToolSet class and you will not get real tools classes at all. However the set of this messages would be very long and Squeak wants sometimes directly the class (for comparison etc.) The default tools are: browser changeList changeSorter changedMessageSet classCommentVersionsBrowser classListBrowser debugger dualChangeSorter hierarchyBrowser instanceBrowser lexicon messageNames messageSet packagePaneBrowser pointerFinder protocolBrowser versionsBrowser Cheers, -- Pavel

Oct. 28, 2008

Re: [Pharo-project] Merging one-click and pharo-dev

by Marcus Denker

On 27.10.2008, at 20:29, StÃ©phane Ducasse wrote: > I do not know. > >> Looks ok, just one minor change, the bundle version in the >> info.plist reads 3.8.18b1U, but it should read 3.8.18b4U >> >> I note this app doesn't have the freetype plugins for any >> platforms, are they needed? Or is that a pending feature awaiting for >> font work in the pharo image? > I did put them into the first one-click (I just copied over from Sophie for the mac version). The win version is not up-to-date, there is a bug=tracker item about that. Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Oct. 28, 2008

[Pharo-project] Fwd: [squeak-dev] Re: Test Server

by StÃ©phane Ducasse

Begin forwarded message: > From: stephane ducasse <stephane.ducasse(a)free.fr> > Date: October 28, 2008 8:19:42 AM CEST > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > >, Noury Bouraqadi <bouraqadi(a)ensm-douai.fr> > Cc: Alexandre Bergel <Alexandre.Bergel(a)inria.fr>, An open mailing > list to discuss any topics related to an open-source Smalltalk <pharo-project(a)lists.gforge.inria.fr > > > Subject: Re: [squeak-dev] Re: Test Server > > Thanks for the update. > Now I cannot do everything. So other people should also have a look > at your code and give feedback > so that we integrate it or at least give you feedbakc. > The refactoring of installer that did matthew is great. > Now it would be good if you/he could take into account the remark of > lukas about the different instances lying around. > > Stef > > > On Oct 27, 2008, at 10:30 PM, Keith Hodges wrote: > >> Alexandre Bergel wrote: >>> Hi! >>> >>> I've been told that Keith and maybe few others are working on a test >>> server. >>> In a 10 minutes seaside coding session I did a small application >>> that >>> displays a result of a SUnit test. >>> Is there anything like this around? >>> >>> Cheers, >>> Alexandre >> >> Yes... 'SUnit improved' has a TestReporter, since Jan/Feb 2007. >> >> It is designed to be invoked from the command line on any image, >> and to >> work headless if desired. >> >> It generates results to files, the idea being that the progress can >> be >> observed remotely via ftp or http. >> >> Failures and Errors are generated in a file form that can be viewed >> remotely, but selected failures/errors can be run by doiting the >> line of >> the output file. >> >> There is one file which has a byte written per test so that you can >> see >> progress remotely just by looking at the file size in a web /dir/ftp >> browser. >> >> There are also custom icons for apache to show pass/fail/errors etc >> though I am not sure where I have put them. >> >> === >> >> Please please please, you pharo guys, actually look at SUnit >> improved, >> before doing other things with SUnit, I put a lot of effort in to it, >> over the past 2 years. >> >> The latest suite defining and building architecture is really cool. >> It >> uses less code than the old system and is better factored to achieve >> more. For those of us that are interested in developing packages that >> everyone can use, we need a coherant story accross the board so >> that we >> can write tests and flag which images we expect them to work in. >> 'SUnit >> improved' has this in TestCaseVersioned. >> >> ClassClonerTestResource is another case in point, I wrote it so >> that we >> can test the class side of DateAndTime, etc, but still the wheel gets >> reinvented again and again. >> >> A really useful addition which I have been planning for ages, but you >> would be welcome to have a go at, would be excellent if SSpec specs >> could be run in the same ui. >> >> cheers >> >> Keith >> >> p.s. Bob the Builder update to follow >> >> >

Oct. 28, 2008

Re: [Pharo-project] Bob

by StÃ©phane Ducasse

Ok we have to digest that. Jannik started to expand what I wrote on Installer and the next step is Sake than Bob I want to have all that three package well reviewed, documented, advertized. Now personally I should learn Sake. On Oct 27, 2008, at 10:50 PM, Keith Hodges wrote: > Dear All, > > Bob is slowly taking shape, I am perhaps a day away from alpha, but I > don't have much spare time this week, so I expect that this will not > be > available until next week. > > If you would like to contribute, I am hanging around in squeak irc > most > (uk) evenings. > > some docs follow, > > cheers > > Keith > > .... > > ======= > * > Bob the Builder* > > */Your Build is defined as a Class/* > > To add your own 'Build' process to Bob, create a subclass of BobBuild, > with your process defined as a SakeTask returned from the class method > #build. When Bob starts his work in BobBuild-c-#taskMain, he collects > all of these tasks, and sorts them according to their dependencies. > > /*Your build can depend upon other builds*/ > > So your build can specify which other builds it depends upon, for > example: > > BobBuildMyWebServer-#build > > ^ self define: [ :task | > task dependsOn: { BobBuildSeasideOneClick build }. > > .... ... ... ]. > > /*Repositories are watched and builds run when changes are spotted*/ > > Sake-Scheduler is used to run periodic tasks. These tasks can do many > useful things, as well as running #taskMain. Scheduled tasks are > used to: > > 1. Periodically collect data that either Bob/users may need in their > work (e.g. BobPeriodicallyReadMantis ) > 2. Periodically update the Bob server image with the latest code from > contributors (e.g. BobPeriodicallyWatchRepositories ) > > You can add your own periodic tasks by subclassing ScheduledTask, > however some tasks are designed to be extended, by adding (extension) > instance methods. > > e.g. BobPeriodicallyWatchRepositories-#taskWatchPackages (watches the > squeaksource Packages repository for updates) > if you wish to invoke bob following an update to your repository this > example shows how. > > BobPeriodicallyWatchRepositories >> #taskWatchTasks > > ^ SakeTask checkUrl: 'http://www.squeaksource.com/Tasks/feed.rss' > onChanged: [ Installer sake install: 'Tasks'. > BobBuild taskMain run. ]. > > /*Configuration*/ > > Your build process 'task' #build is defined on the class side of > your Build > class. If your task has a number of "const" parameters that configure > the task, these should also be defined on the class side. For example, > the location of a working directory would be returned from > #configWorkingDir > > /*Metadata - build numbers etc*/ > > The metadata for each Build task is specified on the instance side of > the class, e.g. #build0001, #build0002. > Your task definition in #build automatically uses the most recent > metadata method. > > example metadata: > > MyBuild>>#build0001 > > info name: 'Squeak3.11-basic'. > info moniker: '311'. > info codeName: 'Kipper'. > info by: 'kph'. > info image: 'bzr://bzr.warwick.st/squeak/3.10'. > info candidate: false. > info release: false. > info overwrite: true. > info comment: 'testing'. > > > /*Only build if necessary*/ > > It is very important that your build only runs when absolutely > necessary. If your build is manually invoked by an increment in build > number (i.e. info overwrite: false) then the existence of the output > directory with that build number is enough to determine that the build > has already been run. > > If your build is automatically invoked by updates to particular > repositories, then the versions of those packages need to be > recorded in > the metadata. The metadata is written to a file in the output > directory. > Subsequent builds should compare the current metadata with that in the > file to see whether the build needs to be re-run. > > If your build is a derivative of a released product, then you only > need > to build if the dependant has #info release = true. > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 28, 2008

Re: [Pharo-project] Issue 294: VM does not send script files to image

by StÃ©phane Ducasse

What do you mean? Installer-Laucnher really on project loading and Preferences eToyFriendly? I think that in the future we need a real script loader that is not bound with ProjectLauncher which to my eyes belong to Project. And we do not want to keep project in Pharo. Stef > Damien Cassou wrote: >> On Mon, Oct 27, 2008 at 9:51 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >> >>> Damien can you try >>> >> >> It works, thank you. >> > btw: this is bound to break Installer-Launcher > > > Keith > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 28, 2008

Re: [Pharo-project] Issue 294: VM does not send script files to image

by Keith Hodges

Damien Cassou wrote: > On Mon, Oct 27, 2008 at 9:51 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > >> Damien can you try >> > > It works, thank you. > btw: this is bound to break Installer-Launcher Keith

Oct. 28, 2008

Re: [Pharo-project] Issue 294: VM does not send script files to image

by Damien Cassou

On Mon, Oct 27, 2008 at 9:51 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Damien can you try It works, thank you. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

Oct. 28, 2008

[Pharo-project] iPhone 1.07

by John M McIntosh

I've push out an iPhone 1.07 VM. http://www.smalltalkconsulting.com/squeak.html This VM uses the latest core Pharo image. The VM has a number of changes to enable C data structure support and code examples for putting up a UITextEdit and UITextView for single and multiple line textual input, along with the ability to execute objective-c methods on the main thread versus the squeak thread. There is of course a new ObjectiveCPlugin for os-x users. For developers the key to getting a UITextEdit field to work is that you *must* create the UITextEdit thread on the main thread, otherwise if you create the object on the squeak thread, then attempt to use it for textual input on the main thread as per recommendations it deadlocks on a semaphore when it decides that the two process threads are different. Still to do is finishing the Keyboard entry logic, (oh I'm sure just a few minutes should do it...). Then I'll see if I can get a Menu control example working I've not included the VNC logic since I don't know if anyone uses it, or if it can be integrated into the Pharo image at this time, however I suspect someone will let me know. -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Oct. 28, 2008

Re: [Pharo-project] [ANN] 10116

by Damien Pollet

I don't have italics anymore (not even simulated). Also, a funny one: click to show the world menu, then mouse over the items in the middle section repeteadly. The menus get whiter each time they are displayed :) Maybe menus have to be ironed to fix the color to the pixels, like print-your-logo t-shirts ? I was thinking, if freetype is integrated and we want to use platform fonts as a default, then there should be code to switch all basic fonts to various settings depending on the conditions, like bitmap fallback, dejavu truetype, and maybe mac truetype (lucida or gill sans + monaco) and vista truetype (calibri + consolas). Demo mode would be just another font theme. On Mon, Oct 27, 2008 at 10:08 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> - Browsing seems to be much slower than before. I don't know exactly >>> why, but it could be related to the font changes? Scrolling lists (in >>> the Browser, in Monticello) is horribly slow. Italic letters are >>> strangely spaced. The issues disappear when I set all the fonts to >>> Accuny. >> >> Strange, I don't feel any slowdown. If there is a reason it likely is the >> font change. We can check on Wednesday. > > me neither. > > I learned a cool shortcut with noury ctl , to revert to a non edtied method > in the browser. > > stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Oct. 27, 2008

[Pharo-project] Bob

by Keith Hodges

Dear All, Bob is slowly taking shape, I am perhaps a day away from alpha, but I don't have much spare time this week, so I expect that this will not be available until next week. If you would like to contribute, I am hanging around in squeak irc most (uk) evenings. some docs follow, cheers Keith .... ======= * Bob the Builder* */Your Build is defined as a Class/* To add your own 'Build' process to Bob, create a subclass of BobBuild, with your process defined as a SakeTask returned from the class method #build. When Bob starts his work in BobBuild-c-#taskMain, he collects all of these tasks, and sorts them according to their dependencies. /*Your build can depend upon other builds*/ So your build can specify which other builds it depends upon, for example: BobBuildMyWebServer-#build ^ self define: [ :task | task dependsOn: { BobBuildSeasideOneClick build }. .... ... ... ]. /*Repositories are watched and builds run when changes are spotted*/ Sake-Scheduler is used to run periodic tasks. These tasks can do many useful things, as well as running #taskMain. Scheduled tasks are used to: 1. Periodically collect data that either Bob/users may need in their work (e.g. BobPeriodicallyReadMantis ) 2. Periodically update the Bob server image with the latest code from contributors (e.g. BobPeriodicallyWatchRepositories ) You can add your own periodic tasks by subclassing ScheduledTask, however some tasks are designed to be extended, by adding (extension) instance methods. e.g. BobPeriodicallyWatchRepositories-#taskWatchPackages (watches the squeaksource Packages repository for updates) if you wish to invoke bob following an update to your repository this example shows how. BobPeriodicallyWatchRepositories >> #taskWatchTasks ^ SakeTask checkUrl: 'http://www.squeaksource.com/Tasks/feed.rss' onChanged: [ Installer sake install: 'Tasks'. BobBuild taskMain run. ]. /*Configuration*/ Your build process 'task' #build is defined on the class side of your Build class. If your task has a number of "const" parameters that configure the task, these should also be defined on the class side. For example, the location of a working directory would be returned from #configWorkingDir /*Metadata - build numbers etc*/ The metadata for each Build task is specified on the instance side of the class, e.g. #build0001, #build0002. Your task definition in #build automatically uses the most recent metadata method. example metadata: MyBuild>>#build0001 info name: 'Squeak3.11-basic'. info moniker: '311'. info codeName: 'Kipper'. info by: 'kph'. info image: 'bzr://bzr.warwick.st/squeak/3.10'. info candidate: false. info release: false. info overwrite: true. info comment: 'testing'. /*Only build if necessary*/ It is very important that your build only runs when absolutely necessary. If your build is manually invoked by an increment in build number (i.e. info overwrite: false) then the existence of the output directory with that build number is enough to determine that the build has already been run. If your build is automatically invoked by updates to particular repositories, then the versions of those packages need to be recorded in the metadata. The metadata is written to a file in the output directory. Subsequent builds should compare the current metadata with that in the file to see whether the build needs to be re-run. If your build is a derivative of a released product, then you only need to build if the dependant has #info release = true.

Oct. 27, 2008