Pharo-dev
By thread
pharo-dev@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- 1 participants
- 144619 messages
Re: [Pharo-dev] How to manage GitFileTree and being integrated in-image (QualityAssistant example?)
by Thierry Goubier
Hi Mariano,
this is a common question for external projects integrated inside the Pharo
image. And we have an issue with version numbers, but let's try to keep
that separate.
Fixes to the code of external projects integrated inside Pharo should be
done upstream (on the external project itself), not in the Pharo image.
This is what is currently happening with the GT tools, NeoJSON, Zinc, and
probably a few more. So, as a maintainer of such a projects in github, say,
you can ask people to create issues on your project, pull requests and the
like, and this is the only way bugs found in Pharo in your release project
should be corrected. Then, everytime a new version of the Pharo image is
built, a version of your project is integrated; and you can add an issue to
update your project to a newer version inside Pharo.
(Was I clear with that description? Feel free to ask or correct me :))
Now, about the package versions. There is an issue with metadata-less mode
and a few quirks about the way Metacello check versions to upgrade
packages, and the issue is open. Two ways forward are possible: David
Allouche pointed one by saying ordering between versions (without checking
the numbers) can be resolved by checking if one is an ancestor of the
other... and the other is that, with Skip work on the github api, it
becomes possible(*) to retrieve the version info from github without git
and avoid those -Cypress.1.
Thierry
* There is a bit of code to write, of course, but most of it is reusing
what already exists inside Skip github and GitFileTree.
2016-01-22 14:33 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com>:
> Hi guys,
>
> Let's say there is a project which is being build with metadata-less
> GitFileTree. There is a BaselineOf and a ConfigurationOf which work
> correctly. And ConfigurationOf can perfectly have fixed "versions" that
> could be, at some point, integrated in Pharo.
>
> Let's say I release version 1.0 which is INTEGRATED inside Pharo. When
> Pharo image is build, it uses ConfigurationOfMyApp to load the code and so
> there will be NO history of versions (cypress.1).
>
> Now, as Pharo goes on, there may be changes to that project as part of
> refactors or whatever that happens in-image. So in one months from now,
> Pharo may have a "newer" code than the originally released 1.0. Let's say
> that for the package MyAppPackage were only 3 commits in those 2 months.
>
> At the same time, I have continue working with my project, and I am ready
> to publish 1.1.
>
> Question is.... how do I bring Pharo changes to my own place?
>
> 1) Fetching (from Pharo repo) and pushing to my GitFileTree only the
> versions during those 2 months? I doubt this will work as crappy
> Monticello numbers could have collisions, right?
>
> 2) Doing a poor man diff and cherry picking changes from Pharo repo and
> manually apply them to my own repo? In this case, the "3 commits" of those
> 2 months will be lost as from git history version.
>
> Is there a project doing this?? I know QualityAssistant is close, but he
> does not use metadata-less GitFileTree I think...so I am not sure.
>
> Thoughts?
>
> Thanks!
>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
Jan. 22, 2016
Re: [Pharo-dev] [ANN] GitHub API Bindings: new version
by Skip Lentz
Hi, thanks a lot for your feedback.
> On Jan 22, 2016, at 2:25 PM, Hernán Morales Durand <hernan.morales(a)gmail.com> wrote:
>
> Yes, now it works. Thank you.
>
> May I suggest a couple of UI tips?
>
> - Please don't use input boxes without label.
Yes I chose to use a ghost text inside the input boxes instead of labels. I thought labels would take too much space..
> - In the same row it would be better a Login button.
> - A button to logout?
Sure, the login button could turn into a logout button after logging in :P.
Or it can be an option when you click on your username in the top right.. I think that is better actually.
> - A progress bar or clock while logging and/or switching repositories/branches?
Yes I was thinking about the same.
What I would like most is a spinner of some sort, however I donât know if any of this is supported by Pharoâs UI framework
> - I clicked "Checkout" button but what happened? After a wait clock, I don't know, there is no feedback at all. A pane at bottom would be awesome :)
A progress/status pane at the bottom is not a bad idea at all!
> Cheers,
>
> Hernán
>
>
> 2016-01-22 9:11 GMT-03:00 Skip Lentz <skip.lentz(a)inria.fr <mailto:skip.lentz@inria.fr>>:
> That sounds like the most probable source of the problem.
>
> Thanks Sven for the new version, I will update my configuration (or âBaselineOfâ).
> Hernán, maybe you can try loading it in a new image to see if you get the same problem?
>
>> On Jan 22, 2016, at 12:42 PM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote:
>>
>> Hi,
>> If there is already a version of NeoJSON in the image the new version can be skip (ahah!) during the loading. I had this problem before, I had to load the bleeding edge in a new image.
>>
>>
>>
>> On Friday, January 22, 2016, Skip Lentz <skip.lentz(a)inria.fr <mailto:skip.lentz@inria.fr>> wrote:
>> Thanks Hernán for your report.
>> As Sven said, it is not yet present in the stable version of NeoJSON.
>> But it should not matter as I load the bleeding-edge version.
>>
>> I will look into this.
>> Can you tell me which script you used to load the tool? Is it the one in the first e-mail?
>>
>>
>> --
>> Cheers
>> Cyril Ferlicot
>>
>
>
Jan. 22, 2016
Re: [Pharo-dev] Pharo bootstrap
by Christophe Demarey
Hi Brad,
Envy is a package manager. It does not define the minimal kernel you need to install packages needed for your application.
The goal of a bootstrap is to set up an environment from a know state. In the same time, this exercise forces us to define the minimal kernel needed to run Pharo (because you do not want to bootstrap the full system).
Currently, we miss both the minimal kernel and a bootstrapped image of Pharo.
Le 20 janv. 2016 à 20:17, Brad Selfridge a écrit :
> Has anyone looked at the VASmalltalk Envy Packager. It let's one decide
> whether you want to package a headless or UI image. It then allows one to
> define packaging instructions, that are saved with the new application),
> that get fed into the packager. The instructions define prerequisite apps,
> un-referenced methods, etc. When one defines a new application (package),
> one can define prerequisite applications that have to be installed before
> the current application is installed. This prerequisite chain is used in
> loading the application from Envy and in packaging. Seems to work fairly
> well. Doesn't take too long to package an app and give the developer pretty
> fine control over the packaging and loading process.
>
>
>
> -----
> Brad Selfridge
> --
> View this message in context: http://forum.world.st/ANN-Pharo-bootstrap-tp4872633p4872989.html
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
>
Jan. 22, 2016
How to manage GitFileTree and being integrated in-image (QualityAssistant example?)
by Mariano Martinez Peck
Hi guys,
Let's say there is a project which is being build with metadata-less
GitFileTree. There is a BaselineOf and a ConfigurationOf which work
correctly. And ConfigurationOf can perfectly have fixed "versions" that
could be, at some point, integrated in Pharo.
Let's say I release version 1.0 which is INTEGRATED inside Pharo. When
Pharo image is build, it uses ConfigurationOfMyApp to load the code and so
there will be NO history of versions (cypress.1).
Now, as Pharo goes on, there may be changes to that project as part of
refactors or whatever that happens in-image. So in one months from now,
Pharo may have a "newer" code than the originally released 1.0. Let's say
that for the package MyAppPackage were only 3 commits in those 2 months.
At the same time, I have continue working with my project, and I am ready
to publish 1.1.
Question is.... how do I bring Pharo changes to my own place?
1) Fetching (from Pharo repo) and pushing to my GitFileTree only the
versions during those 2 months? I doubt this will work as crappy
Monticello numbers could have collisions, right?
2) Doing a poor man diff and cherry picking changes from Pharo repo and
manually apply them to my own repo? In this case, the "3 commits" of those
2 months will be lost as from git history version.
Is there a project doing this?? I know QualityAssistant is close, but he
does not use metadata-less GitFileTree I think...so I am not sure.
Thoughts?
Thanks!
--
Mariano
http://marianopeck.wordpress.com
Jan. 22, 2016
Re: [Pharo-dev] [ANN] GitHub API Bindings: new version
by Hernán Morales Durand
Yes, now it works. Thank you.
May I suggest a couple of UI tips?
- Please don't use input boxes without label.
- In the same row it would be better a Login button.
- A button to logout?
- A progress bar or clock while logging and/or switching
repositories/branches?
- I clicked "Checkout" button but what happened? After a wait clock, I
don't know, there is no feedback at all. A pane at bottom would be awesome
:)
Cheers,
Hernán
2016-01-22 9:11 GMT-03:00 Skip Lentz <skip.lentz(a)inria.fr>:
> That sounds like the most probable source of the problem.
>
> Thanks Sven for the new version, I will update my configuration (or
> âBaselineOfâ).
> Hernán, maybe you can try loading it in a new image to see if you get the
> same problem?
>
> On Jan 22, 2016, at 12:42 PM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com>
> wrote:
>
> Hi,
> If there is already a version of NeoJSON in the image the new version can
> be skip (ahah!) during the loading. I had this problem before, I had to
> load the bleeding edge in a new image.
>
>
>
> On Friday, January 22, 2016, Skip Lentz <skip.lentz(a)inria.fr> wrote:
>
>> Thanks Hernán for your report.
>> As Sven said, it is not yet present in the stable version of NeoJSON.
>> But it should not matter as I load the bleeding-edge version.
>>
>> I will look into this.
>> Can you tell me which script you used to load the tool? Is it the one in
>> the first e-mail?
>>
>
>
> --
> Cheers
> Cyril Ferlicot
>
>
>
Jan. 22, 2016
Re: [Pharo-dev] Pharo bootstrap
by Craig Latta
> From my perspective, I am very frustrated to not be able to use:
>
> - Context in Pharo
> - Your remote running of tiny images in my Pharo browser (including
> the sonar ping sound when messages are landing remotely)
> - Using WebDav for looking into my images using your WebDav component
Cool, that's all planned for this year (in reverse order).
thanks,
-C
--
Craig Latta
netjam.org
+31 6 2757 7177 (SMS ok)
+ 1 415 287 3547 (no SMS)
Jan. 22, 2016
[pharo-project/pharo-core] 082dae: 50539
by GitHub
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 082dae8a9b6bf05b6a37ad4587f5b699d9fc3f05
https://github.com/pharo-project/pharo-core/commit/082dae8a9b6bf05b6a37ad45…
Author: Jenkins Build Server <board(a)pharo-project.org>
Date: 2016-01-22 (Fri, 22 Jan 2016)
Changed paths:
M BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/api projectSpec/baseline_.st
R BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/data/removedExtendedCLasses.st
M BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/pre-post-load-do-its/preLoadDoIt.st
A BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/pre-post-load-do-its/removeExtensionMethods.st
R BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/pre-post-load-do-its/removeRenrakuCrap.st
M ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/symbolic versions/development_.st
M ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/symbolic versions/stable_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/pre2%5F3%5F0_.st
A ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/pre2%5F4%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F2%5F2_.st
A ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F3%5F0_.st
A ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F3%5F1_.st
M ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/symbolic versions/development_.st
M ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/symbolic versions/stable_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/pre0%5F10%5F0_.st
A ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/pre0%5F12%5F0_.st
A ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F10%5F0_.st
A ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F11%5F0_.st
A ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F11%5F1_.st
M QualityAssistant.package/QANautilusPlugin.class/class/installing/install.st
A QualityAssistant.package/QANautilusPlugin.class/class/installing/isInstalled.st
A QualityAssistant.package/QANautilusPlugin.class/instance/announcement handling/packageSelected_.st
M QualityAssistant.package/QANautilusPlugin.class/instance/interaction delegation/criticSelected_.st
M QualityAssistant.package/QANautilusPlugin.class/instance/registration/registerTo_.st
R QualityAssistant.package/QANautilusPluginMorph.class/instance/actions/fixAutomatically_.st
M QualityAssistant.package/QANautilusPluginMorph.class/instance/initialization/initializeUpdateTask.st
A QualityAssistant.package/QANautilusPluginMorph.class/instance/list-morph/displayCritic_.st
R QualityAssistant.package/QANautilusPluginMorph.class/instance/listLine-morph/autofixButtonFor_.st
R QualityAssistant.package/QANautilusPluginMorph.class/instance/listLine-morph/displayCritic_.st
R QualityAssistant.package/QANautilusPluginMorph.class/instance/listLine-morph/infoButtonFor_.st
R QualityAssistant.package/QANautilusPluginMorph.class/instance/listLine-morph/skipButtonFor_.st
M QualityAssistant.package/QANautilusPluginMorph.class/instance/task handling/setTaskAction.st
A QualityAssistant.package/QASettings.class/class/settings-accessing/nautilusPlugin.st
A QualityAssistant.package/QASettings.class/class/settings-accessing/nautilusPlugin_.st
M QualityAssistant.package/QASettings.class/class/settings-definition/inspectorPlugginSettingsOn_.st
M QualityAssistant.package/QASettings.class/class/settings-definition/qaGroupSettingsOn_.st
A QualityAssistant.package/QASettings.class/class/settings-definition/qaNautilusPlugginSettingOn_.st
M QualityAssistant.package/QASettings.class/class/settings-definition/spotterPluginSettingsOn_.st
M QualityAssistant.package/extension/CompiledMethod/instance/gtInspectorCriticsIn_.st
R QualityAssistant.package/extension/CompiledMethod/instance/guidedBan_.st
M QualityAssistant.package/extension/CompiledMethod/instance/spotterQACriticsFor_.st
R QualityAssistant.package/extension/ReAbstractCritic/instance/gtInspectorDescriptionIn_.st
R QualityAssistant.package/extension/ReAbstractCritic/instance/gtInspectorSourceCodeIn_.st
R QualityAssistant.package/extension/ReAbstractCritic/instance/guidedSkip.st
R QualityAssistant.package/extension/ReAbstractCritic/instance/icon.st
R QualityAssistant.package/extension/ReAbstractCritic/instance/popDescriptionUp.st
R QualityAssistant.package/extension/ReAbstractCritic/instance/spotterPreviewCodeIn_.st
R QualityAssistant.package/extension/ReAbstractCritic/instance/spotterPreviewRationaleIn_.st
M QualityAssistant.package/extension/TBehavior/instance/gtInspectorCriticsIn_.st
R QualityAssistant.package/extension/TBehavior/instance/guidedBan_.st
R QualityAssistant.package/extension/TBehavior/instance/guidedSkip_.st
M QualityAssistant.package/extension/TBehavior/instance/spotterQACriticsFor_.st
M QualityAssistantRecording.package/QARCriticEvent.class/instance/initialization/fromAnnouncement_.st
A QualityAssistantRecording.package/extension/CompiledMethod/instance/asCollectedEntity.st
A QualityAssistantRecording.package/extension/Object/instance/asCollectedEntity.st
A QualityAssistantRecording.package/extension/RBMethodNode/instance/asCollectedEntity.st
A QualityAssistantRecording.package/extension/RPackage/instance/asCollectedEntity.st
A QualityAssistantRecording.package/extension/TClassDescription/instance/asCollectedEntity.st
M Renraku-Test.package/ReCriticTest.class/instance/tests/testTarget.st
A Renraku.package/ReAbstractCritic.class/class/instance creation/withAnchor_by_.st
M Renraku.package/ReAbstractCritic.class/definition.st
A Renraku.package/ReAbstractCritic.class/instance/accessing/icon.st
R Renraku.package/ReAbstractCritic.class/instance/accessing/selection.st
R Renraku.package/ReAbstractCritic.class/instance/accessing/target.st
A Renraku.package/ReAbstractCritic.class/instance/actions/actions.st
M Renraku.package/ReAbstractCritic.class/instance/actions/ban.st
A Renraku.package/ReAbstractCritic.class/instance/actions/guidedBan.st
A Renraku.package/ReAbstractCritic.class/instance/actions/popDescriptionUp.st
A Renraku.package/ReAbstractCritic.class/instance/gt-extension/gtInspectorDescriptionIn_.st
A Renraku.package/ReAbstractCritic.class/instance/gt-extension/gtInspectorSourceCodeIn_.st
A Renraku.package/ReAbstractCritic.class/instance/gt-extension/spotterPreviewRationaleIn_.st
A Renraku.package/ReAbstractCritic.class/instance/initialization/initializeRule_sourceAnchor_.st
M Renraku.package/ReAbstractCritic.class/instance/initialization/initializeRule_target_.st
A Renraku.package/ReAbstractCritic.class/instance/testing/isCritic.st
R Renraku.package/ReAbstractCritic.class/instance/testing/providesSelection.st
A Renraku.package/ReBasicMethodRule.class/README.md
A Renraku.package/ReBasicMethodRule.class/class/accessing/uniqueIdentifierName.st
A Renraku.package/ReBasicMethodRule.class/class/testing/checksMethod.st
A Renraku.package/ReBasicMethodRule.class/class/testing/isVisible.st
A Renraku.package/ReBasicMethodRule.class/definition.st
A Renraku.package/ReBasicMethodRule.class/instance/accessing/resultClass.st
A Renraku.package/ReBasicMethodRule.class/instance/running/checkMethod_.st
A Renraku.package/ReBasicTreeRule.class/README.md
A Renraku.package/ReBasicTreeRule.class/class/accessing/uniqueIdentifierName.st
A Renraku.package/ReBasicTreeRule.class/class/testing/checksAST.st
A Renraku.package/ReBasicTreeRule.class/class/testing/isVisible.st
A Renraku.package/ReBasicTreeRule.class/definition.st
A Renraku.package/ReBasicTreeRule.class/instance/accessing/resultClass.st
A Renraku.package/ReBasicTreeRule.class/instance/running/checkMethod_.st
M Renraku.package/ReFeedbacker.class/class/actions/feedback_positive_About_.st
M Renraku.package/ReFeedbacker.class/definition.st
A Renraku.package/ReInspectorPresentationsNonBlockSetup.class/README.md
A Renraku.package/ReInspectorPresentationsNonBlockSetup.class/definition.st
A Renraku.package/ReInspectorPresentationsNonBlockSetup.class/instance/accessing/group.st
A Renraku.package/ReInspectorPresentationsNonBlockSetup.class/instance/accessing/name.st
A Renraku.package/ReInspectorPresentationsNonBlockSetup.class/instance/private/presentationScriptingMathods.st
A Renraku.package/ReInspectorPresentationsNonBlockSetup.class/instance/running/basicCheck_.st
A Renraku.package/ReInspectorPresentationsNonBlockSetup.class/instance/running/check_forCriticsDo_ifNone_.st
A Renraku.package/ReInspectorPresentationsNonlazyCode.class/README.md
A Renraku.package/ReInspectorPresentationsNonlazyCode.class/definition.st
A Renraku.package/ReInspectorPresentationsNonlazyCode.class/instance/accessing/group.st
A Renraku.package/ReInspectorPresentationsNonlazyCode.class/instance/accessing/name.st
A Renraku.package/ReInspectorPresentationsNonlazyCode.class/instance/private/presentation_isTheLeftmostRecepientIn_.st
A Renraku.package/ReInspectorPresentationsNonlazyCode.class/instance/running/basicCheck_.st
A Renraku.package/ReInspectorPresentationsNonlazyCode.class/instance/running/check_forCriticsDo_ifNone_.st
A Renraku.package/ReIntervalSourceAnchor.class/README.md
A Renraku.package/ReIntervalSourceAnchor.class/class/instance creation/entity_interval_.st
A Renraku.package/ReIntervalSourceAnchor.class/definition.st
A Renraku.package/ReIntervalSourceAnchor.class/instance/accessing/interval.st
A Renraku.package/ReIntervalSourceAnchor.class/instance/gt-inspector-extension/gtInspectorSourceCodeIn_.st
A Renraku.package/ReIntervalSourceAnchor.class/instance/initialization/initializeEnitity_interval_.st
A Renraku.package/ReIntervalSourceAnchor.class/instance/testing/providesInterval.st
M Renraku.package/ReMissingMethodCritic.class/definition.st
M Renraku.package/ReMissingMethodCritic.class/instance/accessing/change.st
R Renraku.package/ReMissingMethodCritic.class/instance/accessing/selection.st
M Renraku.package/ReMissingMethodCritic.class/instance/accessing/title.st
A Renraku.package/ReMissingMethodCritic.class/instance/private/methodHeader.st
R Renraku.package/ReMissingMethodCritic.class/instance/testing/providesSelection.st
A Renraku.package/ReProperty.class/README.md
A Renraku.package/ReProperty.class/definition.st
A Renraku.package/ReProperty.class/instance/accessing/icon.st
A Renraku.package/ReProperty.class/instance/accessing/sourceAnchor.st
A Renraku.package/ReProperty.class/instance/accessing/title.st
A Renraku.package/ReProperty.class/instance/actions/actions.st
A Renraku.package/ReProperty.class/instance/initialization/initializeSourceAnchor_.st
A Renraku.package/ReProperty.class/instance/testing/isCritic.st
A Renraku.package/RePropertyAction.class/README.md
A Renraku.package/RePropertyAction.class/definition.st
A Renraku.package/RePropertyAction.class/instance/accessing/action.st
A Renraku.package/RePropertyAction.class/instance/accessing/action_.st
A Renraku.package/RePropertyAction.class/instance/accessing/description.st
A Renraku.package/RePropertyAction.class/instance/accessing/description_.st
A Renraku.package/RePropertyAction.class/instance/accessing/icon.st
A Renraku.package/RePropertyAction.class/instance/accessing/icon_.st
A Renraku.package/RePropertyAction.class/instance/evaluating/actOnCritic_ofEntity_.st
A Renraku.package/RePropertyAction.class/instance/initialization/initialize.st
A Renraku.package/ReReturnMethodRule.class/README.md
A Renraku.package/ReReturnMethodRule.class/definition.st
A Renraku.package/ReReturnMethodRule.class/instance/accessing/group.st
A Renraku.package/ReReturnMethodRule.class/instance/accessing/name.st
A Renraku.package/ReReturnMethodRule.class/instance/accessing/severity.st
A Renraku.package/ReReturnMethodRule.class/instance/running/basicCheck_.st
A Renraku.package/ReReuseBasickCkeck.class/README.md
A Renraku.package/ReReuseBasickCkeck.class/definition.st
A Renraku.package/ReReuseBasickCkeck.class/instance/accessing/group.st
A Renraku.package/ReReuseBasickCkeck.class/instance/accessing/name.st
A Renraku.package/ReReuseBasickCkeck.class/instance/accessing/severity.st
A Renraku.package/ReReuseBasickCkeck.class/instance/private/lintCheckSelectors.st
A Renraku.package/ReReuseBasickCkeck.class/instance/running/basicCheck_.st
M Renraku.package/ReRuleManager.class/definition.st
A Renraku.package/ReRuleManager.class/instance/accessing/astRules.st
A Renraku.package/ReRuleManager.class/instance/accessing/packageRules.st
M Renraku.package/ReRuleManager.class/instance/initialization/initializeRules.st
A Renraku.package/ReSearchStringSourceAnchor.class/README.md
A Renraku.package/ReSearchStringSourceAnchor.class/class/instance creation/entity_string_.st
A Renraku.package/ReSearchStringSourceAnchor.class/definition.st
A Renraku.package/ReSearchStringSourceAnchor.class/instance/accessing/interval.st
A Renraku.package/ReSearchStringSourceAnchor.class/instance/accessing/searchString.st
A Renraku.package/ReSearchStringSourceAnchor.class/instance/gt-inspector-extension/gtInspectorSourceCodeIn_.st
A Renraku.package/ReSearchStringSourceAnchor.class/instance/initialization/initializeEnitity_searchString_.st
A Renraku.package/ReSearchStringSourceAnchor.class/instance/testing/providesInterval.st
A Renraku.package/ReSourceAnchor.class/README.md
A Renraku.package/ReSourceAnchor.class/class/instance creation/entity_.st
A Renraku.package/ReSourceAnchor.class/definition.st
A Renraku.package/ReSourceAnchor.class/instance/accessing/entity.st
A Renraku.package/ReSourceAnchor.class/instance/accessing/interval.st
A Renraku.package/ReSourceAnchor.class/instance/accessing/sourceEntity.st
A Renraku.package/ReSourceAnchor.class/instance/gt-inspector-extension/gtInspectorSourceCodeIn_.st
A Renraku.package/ReSourceAnchor.class/instance/initialization/initializeEnitity_.st
A Renraku.package/ReSourceAnchor.class/instance/testing/providesInterval.st
A Renraku.package/ReStringBasedCritic.class/README.md
A Renraku.package/ReStringBasedCritic.class/class/as yet unclassified/for_by_badString_.st
A Renraku.package/ReStringBasedCritic.class/definition.st
A Renraku.package/ReStringBasedCritic.class/instance/accessing/change.st
A Renraku.package/ReStringBasedCritic.class/instance/accessing/title.st
A Renraku.package/ReStringBasedCritic.class/instance/initialization/initializeRule_target_badString_.st
A Renraku.package/ReStringBasedCritic.class/instance/testing/providesChange.st
R Renraku.package/ReStringSearchCritic.class/README.md
R Renraku.package/ReStringSearchCritic.class/class/as yet unclassified/for_by_badSubstring_.st
R Renraku.package/ReStringSearchCritic.class/definition.st
R Renraku.package/ReStringSearchCritic.class/instance/accessing/change.st
R Renraku.package/ReStringSearchCritic.class/instance/accessing/selection.st
R Renraku.package/ReStringSearchCritic.class/instance/accessing/title.st
R Renraku.package/ReStringSearchCritic.class/instance/initialization/initializeRule_target_badSubstring_.st
R Renraku.package/ReStringSearchCritic.class/instance/testing/providesChange.st
R Renraku.package/ReStringSearchCritic.class/instance/testing/providesSelection.st
R Renraku.package/ReSystemAnnouncer.class/instance/announce/notifyCritic_of_BannedOn_.st
A Renraku.package/ReSystemAnnouncer.class/instance/announce/notifyCritic_of_bannedOn_.st
R Renraku.package/ReSystemAnnouncer.class/instance/announce/notifyEntity_CriticizedWith_.st
A Renraku.package/ReSystemAnnouncer.class/instance/announce/notifyEntity_criticizedWith_.st
M Renraku.package/ReTransformationCritic.class/definition.st
M Renraku.package/ReTransformationCritic.class/instance/accessing/change.st
R Renraku.package/ReTransformationCritic.class/instance/accessing/selection.st
R Renraku.package/ReTransformationCritic.class/instance/testing/providesSelection.st
M Renraku.package/ReTrivialCritic.class/definition.st
M Renraku.package/ReTrivialCritic.class/instance/accessing/change.st
R Renraku.package/ReTrivialCritic.class/instance/accessing/selection.st
R Renraku.package/ReTrivialCritic.class/instance/testing/providesSelection.st
M Renraku.package/extension/CompiledMethod/instance/ban_.st
M Renraku.package/extension/CompiledMethod/instance/critics.st
A Renraku.package/extension/CompiledMethod/instance/guidedBan_.st
A Renraku.package/extension/CompiledMethod/instance/overriddenMethods.st
A Renraku.package/extension/Object/instance/externalProperties.st
A Renraku.package/extension/RBBadMessageRule/instance/check_forCriticsDo_ifNone_.st
A Renraku.package/extension/RBCascadeNode/instance/leftmostChainReceiver.st
A Renraku.package/extension/RBDefineBasickCheckRule/instance/check_forCriticsDo_ifNone_.st
A Renraku.package/extension/RBLintRule/class/checksAST.st
A Renraku.package/extension/RBMessageNode/instance/leftmostChainReceiver.st
A Renraku.package/extension/RBMethodNode/instance/ban_.st
A Renraku.package/extension/RBMethodNode/instance/critics.st
A Renraku.package/extension/RBMethodNode/instance/guidedBan_.st
M Renraku.package/extension/RBOnlyReadOrWrittenVariableRule/instance/check_forCriticsDo_ifNone_.st
M Renraku.package/extension/RBSentNotImplementedRule/instance/check_forCriticsDo_ifNone_.st
M Renraku.package/extension/RBUndeclaredReferenceRule/instance/check_forCriticsDo_ifNone_.st
M Renraku.package/extension/RBUnreferencedVariablesRule/instance/check_forCriticsDo_ifNone_.st
M Renraku.package/extension/RBVariableNotDefinedRule/instance/check_forCriticsDo_ifNone_.st
A Renraku.package/extension/RPackage/instance/ban_.st
A Renraku.package/extension/RPackage/instance/critics.st
A Renraku.package/extension/RPackage/instance/guidedBan_.st
A Renraku.package/extension/RPackage/instance/package.st
M Renraku.package/extension/TBehavior/instance/ban_.st
M Renraku.package/extension/TBehavior/instance/critics.st
A Renraku.package/extension/TBehavior/instance/guidedBan_.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50538.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50539.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50538.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50539.st
M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
Log Message:
-----------
50539
17429 QualityAssistant v2.3
https://pharo.fogbugz.com/f/cases/17429
http://files.pharo.org/image/50/50539.zip
Jan. 22, 2016
[pharo-project/pharo-core]
by GitHub
Branch: refs/tags/50539
Home: https://github.com/pharo-project/pharo-core
Jan. 22, 2016
Re: [Pharo-dev] another spotter question
by Yuriy Tymchuk
I think that it is really hard to figure out that the arrow is clickable if you do res shift and see it highlighted. I mean, it doesnât look like a button or anything specialâ¦
Cheers!
Uko
> On 22 Jan 2016, at 11:08, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote:
>
> I was talking about clickable arrow to open preview ;)
>
> On Jan 22, 2016 10:47 AM, "stepharo" <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote:
> Hi aliaksei
>
>> Hi Stef
>>
>> I saw an early version of Spotter with arrows near each item and it was IMHO awful. But still, pencils taste differently for each of us ;)
>>
>
> I do not know. May be the arrow should not be on every element but just on the group/category
> may be the colors should be deemed.
>
>> I can agree with you that people "do not get how to use spotter". However it depends on how we define "use spotter". From my prospective almost all do understand how to use main feature: searching.
>> I think the whole discussion is about more advanced features.
>>
> No it is about frustration.
> I get a list in front of my nose and I have no clue how to access it. I click on it and it does not work.
> I have to read blog to see something and I have no clue how to obtain the same result.
> This kind of thing.
>
>> Let's talk about how to open preview(pane to the right) in context of learnability which consists of multiple design principles. During our analysis we will try to determinate violated ones and see how they can be fixed.
>>
>> a) Familiarity. It consists of guessability which is surely violated - I can not imagine anyone who could guess that in order to open preview she should click on arrow to the right of the item (I talk about intentional click, not random one to see what will happen).
>>
> ok
>
>> Second part describes how prior knowledge applies to new system. If we would take Pharo as new system, then principle is finally busted because I never saw such behaviour anywhere else - it was invented in spotter. If new system would be spotter in context of Pharo, then still violated as clicking on arrow is not used anywhere else in Pharo.
>>
> If you put a little triangular icons on top of the arrow then people will certainly undertsand that they can click on it.
>
> My point is ask yourself why many people do not know how to open the pane.
> I could not find it. Once I got it I asked around and really few people know it.
>> Possible way to fix familiarity principle is to spread usage of arrow to the whole Pharo (or world) or to modify its design to improve guessability by adding preview icon/label/whatever on the arrow.
>>
>> b) Generalizability. Meaning that user can extend specific interaction knowledge to new situations. Clicking on arrow is only used in one place in spotter - so there is no chance for user to extend not existing knowledge. Violated.
>>
>> Fix is similar to familiarity - clicking on arrow to expand/open new pane should be used in more places.
>>
> I do not think.
>
>> c) Predictability. Consists of determinism and operation visibility. Determinism is not violated because effect of clicking on arrow can be immediately observed by user. However, operation visibility is violated - arrow does not change depending whether preview is available or not.
>>
>> To fix operation visibility we need to change arrow color/icon depending on availability of preview.
>>
>
> You do not reply to the point that to see that I can interact with a group of element I have to select the first one.
> Currently it only work because some people use arrows. I never because there are at the bottom of my keyboard.
>
>> d) Synthesisability. Not violated - user can easily observe effect of past operations. Preview has only two states: on and off.
>>
>> e) Consistency. We can not say anything, because there are no similar situations in the system.
>>
>> To conclude, an action to open preview should be improved. The most easiest fix would be to add something on top of arrow to make it obvious (improve guessability) what clicking does.
>>
> yes to improve the fact that we may click on something.
>> More preferred one IMHO is to expose arrow usecases and teach users so that generalizability would start playing a role.
>>
> I do not get it.
> You should understand that Pharo can be used with a mouse.
>> Sorry for long email
>> Alex
>>
>>
>>
>> Le 20/1/16 14:30, Aliaksei Syrel a écrit :
>>> On Wed, Jan 20, 2016 at 12:59 PM, Ben Coman < <mailto:btc@openinworld.com>btc(a)openinworld.com <mailto:btc@openinworld.com>> wrote:
>>> +1. Its annoying that it takes two clicks to dive into categories like "Implementors" (one to click an item under the category to make the arrow appear, and then another to click on it) when it would only take one if that arrow for each category was always visible.
>>>
>>> Doru is right, always visible arrows would pollute UI.
>> I do not see why.
>> A user interface is not something that we should click randomly at to learn how to use it.
>>
>>> A compromise solution would be to show them on mouse hover - one click + not overcrowded interface.
>>
>> may be
>> but you can ask yourselves why so many people do not get how to use Spotter.
>> I asked again today to people how to show the pane on the right and nobody knew obviously.
>>>
>>> Cheers,
>>> Alex
>>
>
> <IMG_20160122_110543.jpg>
Jan. 22, 2016
Re: [Pharo-dev] [ANN] GitHub API Bindings: new version
by Hernán Morales Durand
2016-01-22 8:13 GMT-03:00 Skip Lentz <skip.lentz(a)inria.fr>:
> Thanks Hernán for your report.
> As Sven said, it is not yet present in the stable version of NeoJSON.
> But it should not matter as I load the bleeding-edge version.
>
> I will look into this.
> Can you tell me which script you used to load the tool? Is it the one in
> the first e-mail?
>
Yes, I used the script in your first e-mail
Hernán
> On Jan 22, 2016, at 12:02 PM, Hernán Morales Durand <
> hernan.morales(a)gmail.com> wrote:
>
> Hi Skip,
>
> Trying your tool in Windows 8.1 and Pharo 5. I wrote my username and
> password and this is what I get:
>
> MessageNotUnderstood: NeoJSONObjectMapping>>allowNil
> (there is no implementor of #allowNil)
>
> Cheers,
>
> Hernán
>
>
> 2016-01-21 7:30 GMT-03:00 Skip Lentz <skip.lentz(a)inria.fr>:
>
>> Hi everyone,
>>
>> I am announcing a new version for the API bindings to GitHub in Pharo.
>> For documentation and information on how to load it, see the new project
>> homepage:
>>
>> https://balletie.github.io/GitHub/ (generated with Pillar. Plug for
>> Damien and Cyril)
>>
>> For a list of changes in this release, follow this link:
>> https://github.com/Balletie/GitHub/releases/tag/v0.5
>>
>> To load absolutely everything, including the tests and the tool, evaluate:
>>
>> Metacello new
>> baseline: 'GitHub';
>> repository: 'github://Balletie/GitHub:master';
>> load: #(tests tool)
>>
>> If you have loaded the tool, it can be opened via the world
>> menu, under âToolsâ.
>>
>> Feedback welcome :)
>>
>
>
>
Jan. 22, 2016