April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Improving the documentation model

by Hilaire

Le 21/04/2015 15:11, stephan a Ã©crit : > TL;DR: Some roadmap ideas. Looks like a lot of work. > Comments and improvements welcome: > We should replace the Pillar document format > by a better one, suitable for WYSIWYG editing and > creating long documents. People mentioned Lyx[1] and there is TeXmacs[2] as well. [1] https://en.wikipedia.org/wiki/LyX [2] https://en.wikipedia.org/wiki/GNU_TeXmacs -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

April 22, 2015

Re: [Pharo-dev] Integration process in presence of "external" project

by Thierry Goubier

Le 22/04/2015 09:02, Esteban Lorenzano a Ã©crit : > in fact I just checked and Versioner already does that: right button > on monticello over a configuration gives you a: âcreate > development/release versionâ. So only thing we need is to use the > tools we already created :) My position would be that, as in large projects with external upstream, the version of the external project you integrate is not exactly the same as the external one. You have a process of pushing fixes upstream, and merging the versions from the external project into yours. If you have good merge support, this is an easy process. Also remember that we have to deal with long-lived integration processes with a significant memory; large configurations with lots of versions may become a concern after a while (and for the current image, it doesn't mean much to have access to all that history). We saw that with package history; it may be nice to plan for that now. Another idea/possibility is to consider Baselines; given that a possible evolution for Pharo is towards versionning systems which handles branches and tags properly, baselines make that process significantly simpler than configurations by letting one only describe the dependencies between packages and sub-projects, and not their specific version numbers. A key evaluation to see if that works is: can a Minimal image can be rebuilt easily up to a full image, at any point (i.e. at least is all the information related to external projects easily available). A second one would be: if we had a git based process, how would that be? Could considering that (planning for branches, basically) make our current process simpler? Thierry > > >> On 22 Apr 2015, at 08:50, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >> and btwâ¦ of course I agree repositories need to be added, and >> configurations kept in image. >> >> cheers, Esteban >> >>> On 22 Apr 2015, at 08:34, Esteban Lorenzano <estebanlm(a)gmail.com> >>> wrote: >>> >>> I disagree with your proposal. It will be a mess, nobody will >>> merge (because there will be no point on doing it) and we will >>> not move out from a monolithic system. What I propose is not an >>> invention, is how big projects workâ¦ what you have to take into >>> account is that any project under the Pharo umbrella does not >>> have an owner, but a maintainer. That means if Alan is on >>> vacation or he does not has the time to do the new configuration, >>> anyone can doit. >>> >>> Yes, it can look slow, but that is because you are too used to >>> the old workflow, and because right now system is not modular. >>> The method I propose will enhance modularity (while the older >>> will, at least, not help), which means with time, changes will be >>> applied just in one module and not along the full system like >>> now. >>> >>> Of course with proper tools this will be faster, but I very much >>> prefer people telling me âI need thisâ (thatâs why I did the >>> integrator app, and modified the monkey to take and validate >>> configurations), and we do it, that we abandon our pursuit of >>> modularity because is uncomfortable at the beginning. >>> >>> We can modify also monticello or versioner (better monticello >>> because everything will be closer, but using versioner API) to >>> do a âsave new versionâ which would be more or less the same as a >>> slice, but for a configuration, and it will: >>> >>> - save the packages associated to the configuration - create a >>> new version - save the new configuration >>> >>> this will not be to much work (I think I can have it in a couple >>> of days), it will help the process (because eventually everything >>> should be managed through configurations (or PPM configurations), >>> and it will allow us to keep a process that is better and >>> validated.. >>> >>> TL;DR: Better enhance the tools than drop the process. >>> >>> Esteban >>> >>>> On 22 Apr 2015, at 07:47, stepharo <stepharo(a)free.fr> wrote: >>>> >>>> Esteban I was thinking about the following this night. >>>> >>>> While I understand that we want configuration only it will slow >>>> us down like hell. >>>> >>>> Example with guille we wanted to fix a problem (I do not >>>> remember which one) we need a change to be done in rubric so we >>>> will have to publish the change in rubric repo - (find it and >>>> add it) so the rubric repo should be there before - then one >>>> guy of rubric should have a look - then merge - then publish an >>>> issue with a configuration - then only then we can work => >>>> result why do we need sync for me and guille to continue to >>>> work??? => what if Alain in on vacation? we stop working? => >>>> Remember: We did Pharo especially because people in squeak did >>>> not want that we change packages. >>>> >>>> Alternate process - we do a fix we publish it in Pharo and yes >>>> this touches Rubric and - we integrate it in Pharo head - then >>>> the guy from rubric merge in their trunk when they want. it >>>> should be part of the their process to merge always with pharo >>>> trunk - At that point they can report a problem - then they >>>> produce at their speed a new configuration - then we integrate >>>> when ready their change >>>> >>>> >>>> Stef >>>> >>>> >>> >> > > > >

April 22, 2015

Re: [Pharo-dev] Integration process in presence of "external" project

by Esteban Lorenzano

in fact I just checked and Versioner already does that: right button on monticello over a configuration gives you a: âcreate development/release versionâ. So only thing we need is to use the tools we already created :) > On 22 Apr 2015, at 08:50, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > and btwâ¦ of course I agree repositories need to be added, and configurations kept in image. > > cheers, > Esteban > >> On 22 Apr 2015, at 08:34, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> I disagree with your proposal. >> It will be a mess, nobody will merge (because there will be no point on doing it) and we will not move out from a monolithic system. >> What I propose is not an invention, is how big projects workâ¦ what you have to take into account is that any project under the Pharo umbrella does not have an owner, but a maintainer. That means if Alan is on vacation or he does not has the time to do the new configuration, anyone can doit. >> >> Yes, it can look slow, but that is because you are too used to the old workflow, and because right now system is not modular. >> The method I propose will enhance modularity (while the older will, at least, not help), which means with time, changes will be applied just in one module and not along the full system like now. >> >> Of course with proper tools this will be faster, but I very much prefer people telling me âI need thisâ (thatâs why I did the integrator app, and modified the monkey to take and validate configurations), and we do it, that we abandon our pursuit of modularity because is uncomfortable at the beginning. >> >> We can modify also monticello or versioner (better monticello because everything will be closer, but using versioner API) to do a âsave new versionâ which would be more or less the same as a slice, but for a configuration, and it will: >> >> - save the packages associated to the configuration >> - create a new version >> - save the new configuration >> >> this will not be to much work (I think I can have it in a couple of days), it will help the process (because eventually everything should be managed through configurations (or PPM configurations), and it will allow us to keep a process that is better and validated.. >> >> TL;DR: Better enhance the tools than drop the process. >> >> Esteban >> >>> On 22 Apr 2015, at 07:47, stepharo <stepharo(a)free.fr> wrote: >>> >>> Esteban >>> I was thinking about the following this night. >>> >>> While I understand that we want configuration only it will slow us down like hell. >>> >>> Example >>> with guille we wanted to fix a problem (I do not remember which one) >>> we need a change to be done in rubric so we will have to publish the change in rubric repo >>> - (find it and add it) so the rubric repo should be there before >>> - then one guy of rubric should have a look >>> - then merge >>> - then publish an issue with a configuration >>> - then only then we can work >>> => result why do we need sync for me and guille to continue to work??? >>> => what if Alain in on vacation? >>> we stop working? >>> => Remember: We did Pharo especially because people in squeak did not want that we change >>> packages. >>> >>> Alternate process >>> - we do a fix we publish it in Pharo and yes this touches Rubric and >>> - we integrate it in Pharo head >>> - then the guy from rubric merge in their trunk when they want. >>> it should be part of the their process to merge always with pharo trunk >>> - At that point they can report a problem >>> - then they produce at their speed a new configuration >>> - then we integrate when ready their change >>> >>> >>> Stef >>> >>> >> >

April 22, 2015

QualityAssistant v0.4

by Yuriy Tymchuk

Hi everyone! Probably most of you know, that I am developing a tool called QualityAssistant, which displays current critics about your code in SystemBrowser, Inspector and Spotter. Iâm happy to tell you that there is a new release v0.4 which does not require you to do any previous setup! Just load it from configuration browser (pharo 4 & 5) and it will start giving you feedback. More details can be found here: https://github.com/Uko/QualityAssistant#quality-assistant-beta- <https://github.com/Uko/QualityAssistant#quality-assistant-beta->. If you are upgrading from older version, it is recommended to load QualityAssistant into a fresh image, because multiple announcement and process changes may cause exceptions in old objects. Even if you are an experienced programmer you can find QualityAssistant useful for instantly spotting typos or making sure that you didnât forget some details about your code. Please give me a feedback about your experience, as I want to make it even more useful. Either write me an email, or open an entry at: https://github.com/Uko/QualityAssistant/issues Have a nice week! Uko

April 22, 2015

Re: [Pharo-dev] Integration process in presence of "external" project

by Esteban Lorenzano

and btwâ¦ of course I agree repositories need to be added, and configurations kept in image. cheers, Esteban > On 22 Apr 2015, at 08:34, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > I disagree with your proposal. > It will be a mess, nobody will merge (because there will be no point on doing it) and we will not move out from a monolithic system. > What I propose is not an invention, is how big projects workâ¦ what you have to take into account is that any project under the Pharo umbrella does not have an owner, but a maintainer. That means if Alan is on vacation or he does not has the time to do the new configuration, anyone can doit. > > Yes, it can look slow, but that is because you are too used to the old workflow, and because right now system is not modular. > The method I propose will enhance modularity (while the older will, at least, not help), which means with time, changes will be applied just in one module and not along the full system like now. > > Of course with proper tools this will be faster, but I very much prefer people telling me âI need thisâ (thatâs why I did the integrator app, and modified the monkey to take and validate configurations), and we do it, that we abandon our pursuit of modularity because is uncomfortable at the beginning. > > We can modify also monticello or versioner (better monticello because everything will be closer, but using versioner API) to do a âsave new versionâ which would be more or less the same as a slice, but for a configuration, and it will: > > - save the packages associated to the configuration > - create a new version > - save the new configuration > > this will not be to much work (I think I can have it in a couple of days), it will help the process (because eventually everything should be managed through configurations (or PPM configurations), and it will allow us to keep a process that is better and validated.. > > TL;DR: Better enhance the tools than drop the process. > > Esteban > >> On 22 Apr 2015, at 07:47, stepharo <stepharo(a)free.fr> wrote: >> >> Esteban >> I was thinking about the following this night. >> >> While I understand that we want configuration only it will slow us down like hell. >> >> Example >> with guille we wanted to fix a problem (I do not remember which one) >> we need a change to be done in rubric so we will have to publish the change in rubric repo >> - (find it and add it) so the rubric repo should be there before >> - then one guy of rubric should have a look >> - then merge >> - then publish an issue with a configuration >> - then only then we can work >> => result why do we need sync for me and guille to continue to work??? >> => what if Alain in on vacation? >> we stop working? >> => Remember: We did Pharo especially because people in squeak did not want that we change >> packages. >> >> Alternate process >> - we do a fix we publish it in Pharo and yes this touches Rubric and >> - we integrate it in Pharo head >> - then the guy from rubric merge in their trunk when they want. >> it should be part of the their process to merge always with pharo trunk >> - At that point they can report a problem >> - then they produce at their speed a new configuration >> - then we integrate when ready their change >> >> >> Stef >> >> >

April 22, 2015

Re: [Pharo-dev] WhatsUp from: 2015-04-20 until: 2015-04-30

by kilon alios

I have been working on MorphicDoc , which is documentation about Morphic inside the image. Still studying Morphic and trying to figure things out. More to come :) On Wed, Apr 22, 2015 at 8:32 AM Tudor Girba <tudor(a)tudorgirba.com> wrote: > Could JB describe the problem with Metacello? Perhaps there is a > workaround. > > Doru > > On Tue, Apr 21, 2015 at 3:27 PM, stepharo <stepharo(a)free.fr> wrote: > >> >> Hi phil >>>> >>>> just that you know what we are doing >>>> >>>> - Mathieu Lacatou an intern from Thales should be visiting the >>>> team for >>>> 10 days to pair program with esteban >>>> about the OSWindow multi-windowing support >>>> >>>> - JB and Merwan are extending the OSWindow touch support, like >>>> generating scroll events >>>> >>>> - JB is working on Woden and adding some shadders for 3D demoes. >>>> >>> I will have a new guy from Senegal starting to work tomorrow in my lab >>> on using GPU and Wooden for doing SPH&epidemiological modeling. >>> How to coordinate all these activities ? >>> >> >> Cool :) >> I do not know >> For now he should have a look at Woden, JB planned to make a CI. >> But he was blocked because of a bug in the old version of Metacello that >> we use. >> So as soon as Metacello is updated, JB can continue his build. >> >> Stef >> >>> >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

April 22, 2015

Re: [Pharo-dev] Integration process in presence of "external" project

by Esteban Lorenzano

I disagree with your proposal. It will be a mess, nobody will merge (because there will be no point on doing it) and we will not move out from a monolithic system. What I propose is not an invention, is how big projects workâ¦ what you have to take into account is that any project under the Pharo umbrella does not have an owner, but a maintainer. That means if Alan is on vacation or he does not has the time to do the new configuration, anyone can doit. Yes, it can look slow, but that is because you are too used to the old workflow, and because right now system is not modular. The method I propose will enhance modularity (while the older will, at least, not help), which means with time, changes will be applied just in one module and not along the full system like now. Of course with proper tools this will be faster, but I very much prefer people telling me âI need thisâ (thatâs why I did the integrator app, and modified the monkey to take and validate configurations), and we do it, that we abandon our pursuit of modularity because is uncomfortable at the beginning. We can modify also monticello or versioner (better monticello because everything will be closer, but using versioner API) to do a âsave new versionâ which would be more or less the same as a slice, but for a configuration, and it will: - save the packages associated to the configuration - create a new version - save the new configuration this will not be to much work (I think I can have it in a couple of days), it will help the process (because eventually everything should be managed through configurations (or PPM configurations), and it will allow us to keep a process that is better and validated.. TL;DR: Better enhance the tools than drop the process. Esteban > On 22 Apr 2015, at 07:47, stepharo <stepharo(a)free.fr> wrote: > > Esteban > I was thinking about the following this night. > > While I understand that we want configuration only it will slow us down like hell. > > Example > with guille we wanted to fix a problem (I do not remember which one) > we need a change to be done in rubric so we will have to publish the change in rubric repo > - (find it and add it) so the rubric repo should be there before > - then one guy of rubric should have a look > - then merge > - then publish an issue with a configuration > - then only then we can work > => result why do we need sync for me and guille to continue to work??? > => what if Alain in on vacation? > we stop working? > => Remember: We did Pharo especially because people in squeak did not want that we change > packages. > > Alternate process > - we do a fix we publish it in Pharo and yes this touches Rubric and > - we integrate it in Pharo head > - then the guy from rubric merge in their trunk when they want. > it should be part of the their process to merge always with pharo trunk > - At that point they can report a problem > - then they produce at their speed a new configuration > - then we integrate when ready their change > > > Stef > >

April 22, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] de6e0a: 50003

by Yuriy Tymchuk

Yes, I know. But while I was trying to understand the problem, Iâve found places in StartupPreferencesLoader where code is generated with StartupLoader. Itâs a minor thing, but do we really need a place with potential problems in our system? Uko > On 22 Apr 2015, at 08:13, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 21 Apr 2015, at 19:27, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> Oh, it should be replaced by StartupPreferencesLoader. Iâll submit a slice > > a slice for what? > the changes you need to do are in your preferences file, not inside the image. > > Esteban > >> >> >>> On 21 Apr 2015, at 19:20, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>> >>> So now startup actions are not working because StartupLoader was removed. What are the plans about this? >>> >>>> On 21 Apr 2015, at 17:40, GitHub <noreply(a)github.com> wrote: >>>> >>>> Branch: refs/heads/5.0 >>>> Home: https://github.com/pharo-project/pharo-core >>>> Commit: de6e0a2db24ff07aaa850ca0fbea53e8860cbb0e >>>> https://github.com/pharo-project/pharo-core/commit/de6e0a2db24ff07aaa850ca0… >>>> Author: Jenkins Build Server <board(a)pharo-project.org> >>>> Date: 2015-04-21 (Tue, 21 Apr 2015) >>>> >>>> Changed paths: >>>> A AST-Core.package/NumberParser.class/class/testing/isNumber_.st >>>> A AST-Tests-Core.package/NumberParserTest.class/instance/tests - Float/testIsNumber.st >>>> R Deprecated40.package/NBWin32Caret.class/README.md >>>> R Deprecated40.package/NBWin32Caret.class/class/accessing/getBlinkTime.st >>>> R Deprecated40.package/NBWin32Caret.class/definition.st >>>> R Deprecated40.package/NBWin32Menu.class/README.md >>>> R Deprecated40.package/NBWin32Menu.class/definition.st >>>> R Deprecated40.package/NBWin32MessageBox.class/README.md >>>> R Deprecated40.package/NBWin32MessageBox.class/class/instance creation/messageBox_text_title_flags_.st >>>> R Deprecated40.package/NBWin32MessageBox.class/class/instance creation/test.st >>>> R Deprecated40.package/NBWin32MessageBox.class/definition.st >>>> R Deprecated40.package/NBWin32Process.class/README.md >>>> R Deprecated40.package/NBWin32Process.class/class/accessing/getCurrentProcess.st >>>> R Deprecated40.package/NBWin32Process.class/class/accessing/getCurrentProcessId.st >>>> R Deprecated40.package/NBWin32Process.class/definition.st >>>> R Deprecated40.package/NBWin32Process.class/instance/accessing/getPriorityClass.st >>>> R Deprecated40.package/NBWin32Process.class/instance/testing/isHighPriorityClass.st >>>> R Deprecated40.package/NBWin32Process.class/instance/testing/isIdlePriorityClass.st >>>> R Deprecated40.package/NBWin32Process.class/instance/testing/isNormalPriorityClass.st >>>> R Deprecated40.package/NBWin32Process.class/instance/testing/isRealtimePriorityClass.st >>>> R Deprecated40.package/NBWin32ShellTest.class/README.md >>>> R Deprecated40.package/NBWin32ShellTest.class/definition.st >>>> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testGetCommandLine.st >>>> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testGetComputerName.st >>>> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testGetDriveType.st >>>> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testNoDebuggerPresentByDefault.st >>>> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testNumberOfProcessors.st >>>> R Deprecated40.package/NBWin32Thread.class/README.md >>>> R Deprecated40.package/NBWin32Thread.class/class/accessing/getCurrentThread.st >>>> R Deprecated40.package/NBWin32Thread.class/class/accessing/getCurrentThreadId.st >>>> R Deprecated40.package/NBWin32Thread.class/definition.st >>>> R Deprecated40.package/NBWin32Thread.class/instance/testing/isThreadAllAccess.st >>>> R Deprecated40.package/Password.class/README.md >>>> R Deprecated40.package/Password.class/definition.st >>>> R Deprecated40.package/ShadowLabelMorph.class/README.md >>>> R Deprecated40.package/ShadowLabelMorph.class/definition.st >>>> R Deprecated40.package/ShadowLabelMorph.class/instance/drawing/drawOn_.st >>>> R Deprecated40.package/StartupLoader.class/README.md >>>> R Deprecated40.package/StartupLoader.class/class/accessing/default.st >>>> R Deprecated40.package/StartupLoader.class/definition.st >>>> R Deprecated40.package/TimeStamp.class/README.md >>>> R Deprecated40.package/TimeStamp.class/class/instance creation/now.st >>>> R Deprecated40.package/TimeStamp.class/class/instance creation/readFrom_.st >>>> R Deprecated40.package/TimeStamp.class/definition.st >>>> R Deprecated40.package/TimeStamp.class/instance/printing/printOn_.st >>>> R Deprecated40.package/TimeStamp.class/instance/squeak protocol/asTimeStamp.st >>>> R Deprecated40.package/TimeStamp.class/instance/squeak protocol/species.st >>>> R Deprecated40.package/TimeStamp.class/instance/squeak protocol/storeOn_.st >>>> R Deprecated40.package/extension/CheckBoxModel/instance/whenLabelChanged_.st >>>> R Deprecated40.package/extension/Class/instance/name_.st >>>> R Deprecated40.package/extension/CompiledMethod/instance/messagesDo_.st >>>> R Deprecated40.package/extension/Date/instance/leap.st >>>> R Deprecated40.package/extension/DateAndTime/instance/asTimeStamp.st >>>> R Deprecated40.package/extension/ImageModel/instance/whenActionChanged_.st >>>> R Deprecated40.package/extension/ImageModel/instance/whenImageChanged_.st >>>> R Deprecated40.package/extension/LabelModel/instance/text.st >>>> R Deprecated40.package/extension/LabelModel/instance/text_.st >>>> R Deprecated40.package/extension/LabelModel/instance/whenLabelChanged_.st >>>> R Deprecated40.package/extension/LabelModel/instance/whenTextChanged_.st >>>> R Deprecated40.package/extension/Locale/class/addLocalChangedListener_.st >>>> R Deprecated40.package/extension/Locale/class/isoLocale_.st >>>> R Deprecated40.package/extension/Locale/class/localeChanged.st >>>> R Deprecated40.package/extension/Locale/class/localeChangedListeners.st >>>> R Deprecated40.package/extension/LocaleID/class/previous.st >>>> R Deprecated40.package/extension/Matrix/class/column_.st >>>> R Deprecated40.package/extension/Matrix/class/row_.st >>>> R Deprecated40.package/extension/MenuMorph/class/fromArray_.st >>>> R Deprecated40.package/extension/MenuMorph/instance/addTranslatedList_.st >>>> R Deprecated40.package/extension/MenuMorph/instance/addUpdating_action_.st >>>> R Deprecated40.package/extension/MenuMorph/instance/addUpdating_target_action_.st >>>> R Deprecated40.package/extension/MenuMorph/instance/add_action_.st >>>> R Deprecated40.package/extension/MenuMorph/instance/add_target_action_.st >>>> R Deprecated40.package/extension/MenuMorph/instance/title_.st >>>> R Deprecated40.package/extension/MorphicUIManager/instance/request_initialAnswer_centerAt_.st >>>> R Deprecated40.package/extension/NonInteractiveUIManager/instance/request_initialAnswer_centerAt_.st >>>> R Deprecated40.package/extension/Object/instance/asReactiveVariable.st >>>> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/anonymousSubclassOf_.st >>>> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/becomeCompact_.st >>>> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/becomeCompact_simplyAt_.st >>>> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/becomeUncompact_.st >>>> R Deprecated40.package/extension/PluggableTextMorphWithLimits/instance/ifLocked_.st >>>> R Deprecated40.package/extension/PluggableTextMorphWithLimits/instance/ifLocked_ifUnlocked_.st >>>> R Deprecated40.package/extension/RGClassDefinition/instance/classSymbol.st >>>> R Deprecated40.package/extension/RGMethodDefinition/instance/classSymbol.st >>>> R Deprecated40.package/extension/RPackage/instance/correspondingMcPackage.st >>>> R Deprecated40.package/extension/RPackageOrganizer/instance/renamePackage_in_.st >>>> R Deprecated40.package/extension/RadioButtonModel/instance/whenLabelChanged_.st >>>> R Deprecated40.package/extension/Stream/instance/isMessageStream.st >>>> R Deprecated40.package/extension/String/instance/asTimeStamp.st >>>> R Deprecated40.package/extension/String/instance/do_toFieldNumber_.st >>>> R Deprecated40.package/extension/String/instance/padded_to_with_.st >>>> R Deprecated40.package/extension/String/instance/splitInteger.st >>>> R Deprecated40.package/extension/String/instance/tabDelimitedFieldsDo_.st >>>> R Deprecated40.package/extension/String/instance/withFirstCharacterDownshifted.st >>>> R Deprecated40.package/extension/SystemAnnouncement/class/fromInternal_.st >>>> R Deprecated40.package/extension/TClass/instance/classPoolFrom_.st >>>> R Deprecated40.package/extension/TClass/instance/ensureClassPool.st >>>> R Deprecated40.package/extension/ToolRegistry/instance/shortcuts.st >>>> R Deprecated40.package/extension/ToolRegistry/instance/userManager.st >>>> R Deprecated40.package/extension/UIManager/instance/displayProgress_at_from_to_during_.st >>>> R Deprecated40.package/extension/UIManager/instance/request_initialAnswer_centerAt_.st >>>> R Fuel.package/extension/TimeStamp/instance/fuelAccept_.st >>>> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script611.st >>>> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script612.st >>>> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50002.st >>>> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50003.st >>>> M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st >>>> >>>> Log Message: >>>> ----------- >>>> 50003 >>>> 15330 NumberParser>>#isNumber: >>>> https://pharo.fogbugz.com/f/cases/15330 >>>> >>>> 15368 unload Deprecate40 in Pharo5 >>>> https://pharo.fogbugz.com/f/cases/15368 >>>> >>>> http://files.pharo.org/image/50/50003.zip >>>> >>>> >>> >>> >> >> > >

April 22, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] de6e0a: 50003

by Esteban Lorenzano

> On 21 Apr 2015, at 19:27, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Oh, it should be replaced by StartupPreferencesLoader. Iâll submit a slice a slice for what? the changes you need to do are in your preferences file, not inside the image. Esteban > > >> On 21 Apr 2015, at 19:20, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> So now startup actions are not working because StartupLoader was removed. What are the plans about this? >> >>> On 21 Apr 2015, at 17:40, GitHub <noreply(a)github.com> wrote: >>> >>> Branch: refs/heads/5.0 >>> Home: https://github.com/pharo-project/pharo-core >>> Commit: de6e0a2db24ff07aaa850ca0fbea53e8860cbb0e >>> https://github.com/pharo-project/pharo-core/commit/de6e0a2db24ff07aaa850ca0… >>> Author: Jenkins Build Server <board(a)pharo-project.org> >>> Date: 2015-04-21 (Tue, 21 Apr 2015) >>> >>> Changed paths: >>> A AST-Core.package/NumberParser.class/class/testing/isNumber_.st >>> A AST-Tests-Core.package/NumberParserTest.class/instance/tests - Float/testIsNumber.st >>> R Deprecated40.package/NBWin32Caret.class/README.md >>> R Deprecated40.package/NBWin32Caret.class/class/accessing/getBlinkTime.st >>> R Deprecated40.package/NBWin32Caret.class/definition.st >>> R Deprecated40.package/NBWin32Menu.class/README.md >>> R Deprecated40.package/NBWin32Menu.class/definition.st >>> R Deprecated40.package/NBWin32MessageBox.class/README.md >>> R Deprecated40.package/NBWin32MessageBox.class/class/instance creation/messageBox_text_title_flags_.st >>> R Deprecated40.package/NBWin32MessageBox.class/class/instance creation/test.st >>> R Deprecated40.package/NBWin32MessageBox.class/definition.st >>> R Deprecated40.package/NBWin32Process.class/README.md >>> R Deprecated40.package/NBWin32Process.class/class/accessing/getCurrentProcess.st >>> R Deprecated40.package/NBWin32Process.class/class/accessing/getCurrentProcessId.st >>> R Deprecated40.package/NBWin32Process.class/definition.st >>> R Deprecated40.package/NBWin32Process.class/instance/accessing/getPriorityClass.st >>> R Deprecated40.package/NBWin32Process.class/instance/testing/isHighPriorityClass.st >>> R Deprecated40.package/NBWin32Process.class/instance/testing/isIdlePriorityClass.st >>> R Deprecated40.package/NBWin32Process.class/instance/testing/isNormalPriorityClass.st >>> R Deprecated40.package/NBWin32Process.class/instance/testing/isRealtimePriorityClass.st >>> R Deprecated40.package/NBWin32ShellTest.class/README.md >>> R Deprecated40.package/NBWin32ShellTest.class/definition.st >>> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testGetCommandLine.st >>> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testGetComputerName.st >>> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testGetDriveType.st >>> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testNoDebuggerPresentByDefault.st >>> R Deprecated40.package/NBWin32ShellTest.class/instance/tests/testNumberOfProcessors.st >>> R Deprecated40.package/NBWin32Thread.class/README.md >>> R Deprecated40.package/NBWin32Thread.class/class/accessing/getCurrentThread.st >>> R Deprecated40.package/NBWin32Thread.class/class/accessing/getCurrentThreadId.st >>> R Deprecated40.package/NBWin32Thread.class/definition.st >>> R Deprecated40.package/NBWin32Thread.class/instance/testing/isThreadAllAccess.st >>> R Deprecated40.package/Password.class/README.md >>> R Deprecated40.package/Password.class/definition.st >>> R Deprecated40.package/ShadowLabelMorph.class/README.md >>> R Deprecated40.package/ShadowLabelMorph.class/definition.st >>> R Deprecated40.package/ShadowLabelMorph.class/instance/drawing/drawOn_.st >>> R Deprecated40.package/StartupLoader.class/README.md >>> R Deprecated40.package/StartupLoader.class/class/accessing/default.st >>> R Deprecated40.package/StartupLoader.class/definition.st >>> R Deprecated40.package/TimeStamp.class/README.md >>> R Deprecated40.package/TimeStamp.class/class/instance creation/now.st >>> R Deprecated40.package/TimeStamp.class/class/instance creation/readFrom_.st >>> R Deprecated40.package/TimeStamp.class/definition.st >>> R Deprecated40.package/TimeStamp.class/instance/printing/printOn_.st >>> R Deprecated40.package/TimeStamp.class/instance/squeak protocol/asTimeStamp.st >>> R Deprecated40.package/TimeStamp.class/instance/squeak protocol/species.st >>> R Deprecated40.package/TimeStamp.class/instance/squeak protocol/storeOn_.st >>> R Deprecated40.package/extension/CheckBoxModel/instance/whenLabelChanged_.st >>> R Deprecated40.package/extension/Class/instance/name_.st >>> R Deprecated40.package/extension/CompiledMethod/instance/messagesDo_.st >>> R Deprecated40.package/extension/Date/instance/leap.st >>> R Deprecated40.package/extension/DateAndTime/instance/asTimeStamp.st >>> R Deprecated40.package/extension/ImageModel/instance/whenActionChanged_.st >>> R Deprecated40.package/extension/ImageModel/instance/whenImageChanged_.st >>> R Deprecated40.package/extension/LabelModel/instance/text.st >>> R Deprecated40.package/extension/LabelModel/instance/text_.st >>> R Deprecated40.package/extension/LabelModel/instance/whenLabelChanged_.st >>> R Deprecated40.package/extension/LabelModel/instance/whenTextChanged_.st >>> R Deprecated40.package/extension/Locale/class/addLocalChangedListener_.st >>> R Deprecated40.package/extension/Locale/class/isoLocale_.st >>> R Deprecated40.package/extension/Locale/class/localeChanged.st >>> R Deprecated40.package/extension/Locale/class/localeChangedListeners.st >>> R Deprecated40.package/extension/LocaleID/class/previous.st >>> R Deprecated40.package/extension/Matrix/class/column_.st >>> R Deprecated40.package/extension/Matrix/class/row_.st >>> R Deprecated40.package/extension/MenuMorph/class/fromArray_.st >>> R Deprecated40.package/extension/MenuMorph/instance/addTranslatedList_.st >>> R Deprecated40.package/extension/MenuMorph/instance/addUpdating_action_.st >>> R Deprecated40.package/extension/MenuMorph/instance/addUpdating_target_action_.st >>> R Deprecated40.package/extension/MenuMorph/instance/add_action_.st >>> R Deprecated40.package/extension/MenuMorph/instance/add_target_action_.st >>> R Deprecated40.package/extension/MenuMorph/instance/title_.st >>> R Deprecated40.package/extension/MorphicUIManager/instance/request_initialAnswer_centerAt_.st >>> R Deprecated40.package/extension/NonInteractiveUIManager/instance/request_initialAnswer_centerAt_.st >>> R Deprecated40.package/extension/Object/instance/asReactiveVariable.st >>> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/anonymousSubclassOf_.st >>> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/becomeCompact_.st >>> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/becomeCompact_simplyAt_.st >>> R Deprecated40.package/extension/OldClassBuilderAdapter/instance/becomeUncompact_.st >>> R Deprecated40.package/extension/PluggableTextMorphWithLimits/instance/ifLocked_.st >>> R Deprecated40.package/extension/PluggableTextMorphWithLimits/instance/ifLocked_ifUnlocked_.st >>> R Deprecated40.package/extension/RGClassDefinition/instance/classSymbol.st >>> R Deprecated40.package/extension/RGMethodDefinition/instance/classSymbol.st >>> R Deprecated40.package/extension/RPackage/instance/correspondingMcPackage.st >>> R Deprecated40.package/extension/RPackageOrganizer/instance/renamePackage_in_.st >>> R Deprecated40.package/extension/RadioButtonModel/instance/whenLabelChanged_.st >>> R Deprecated40.package/extension/Stream/instance/isMessageStream.st >>> R Deprecated40.package/extension/String/instance/asTimeStamp.st >>> R Deprecated40.package/extension/String/instance/do_toFieldNumber_.st >>> R Deprecated40.package/extension/String/instance/padded_to_with_.st >>> R Deprecated40.package/extension/String/instance/splitInteger.st >>> R Deprecated40.package/extension/String/instance/tabDelimitedFieldsDo_.st >>> R Deprecated40.package/extension/String/instance/withFirstCharacterDownshifted.st >>> R Deprecated40.package/extension/SystemAnnouncement/class/fromInternal_.st >>> R Deprecated40.package/extension/TClass/instance/classPoolFrom_.st >>> R Deprecated40.package/extension/TClass/instance/ensureClassPool.st >>> R Deprecated40.package/extension/ToolRegistry/instance/shortcuts.st >>> R Deprecated40.package/extension/ToolRegistry/instance/userManager.st >>> R Deprecated40.package/extension/UIManager/instance/displayProgress_at_from_to_during_.st >>> R Deprecated40.package/extension/UIManager/instance/request_initialAnswer_centerAt_.st >>> R Fuel.package/extension/TimeStamp/instance/fuelAccept_.st >>> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script611.st >>> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script612.st >>> R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50002.st >>> A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50003.st >>> M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st >>> >>> Log Message: >>> ----------- >>> 50003 >>> 15330 NumberParser>>#isNumber: >>> https://pharo.fogbugz.com/f/cases/15330 >>> >>> 15368 unload Deprecate40 in Pharo5 >>> https://pharo.fogbugz.com/f/cases/15368 >>> >>> http://files.pharo.org/image/50/50003.zip >>> >>> >> >> > >

April 22, 2015

Re: [Pharo-dev] [Pharo5] All systems on go!

by Marcus Denker

> On 22 Apr 2015, at 07:07, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 21 Apr 2015, at 22:58, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >> >> >> >> 2015-04-21 22:47 GMT+02:00 kilon alios <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>>: >> I cant see pharo classes in Nautiluse apart from a few, unless i open them with GTSpotter , then they get added to Nautilus. Is this normal ? Is it because I miss the sources file ? and if yes where I find it ? >> >> No, there is an active package pane filter. I thnk this happend by accident, the field should be empty. >> >> > > yes, saw it alreadyâ¦ we should add that #cleanUp resets it. > > I added an issue tracker entry: https://pharo.fogbugz.com/f/cases/15378/Pharo5-0003-Nautilus-start-with-pre… <https://pharo.fogbugz.com/f/cases/15378/Pharo5-0003-Nautilus-start-with-pre…> Marcus

April 22, 2015