- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Most wanted programming language:

by Guido Stepken

This here is real fun: http://www.reactos.de/forum/viewtopic.php?p=82781 I really love PVS - Studio, cause it documents, that its - by principle - *impossible* to write reliable software in certain programming languages. :-) Have fun! Guido Stepken Am 10.01.2012 19:46 schrieb "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr>: > fun :) > > >> > >> yes, see http://astares.blogspot.com/2006/07/stupid-metrics.html > >> > > > > Exactly! I wrote a short blog post to vent: > > http://seandenigris.com/blog/?p=911 > > > > -- > > View this message in context: > http://forum.world.st/Most-wanted-programming-language-tp4282590p4282943.ht… > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > >

Jan. 10, 2012

Re: [Pharo-project] Drag and Drop - drag from hook

by Sean P. DeNigris

Hilaire Fernandes wrote > > Yes you have to use dispatching. > You mean call a custom method from justGrabbedFrom:? The problem is that the grabbed morph is not a part of my project, and I want the behavior for *any* morph grabbed out of this container. Hilaire Fernandes wrote > > I did no see message sent to the owner > morph by the system. > Yes, I will add a hook and submit to inbox. What should it be called? It's a weird passive-voice situation... #justGrabbedFromMe: aMorph? #justLost:? Ugly, but I can't think of anything better. -- View this message in context: http://forum.world.st/Drag-and-Drop-drag-from-hook-tp4282507p4282966.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 10, 2012

Re: [Pharo-project] Most wanted programming language:

by StÃ©phane Ducasse

fun :) >> >> yes, see http://astares.blogspot.com/2006/07/stupid-metrics.html >> > > Exactly! I wrote a short blog post to vent: > http://seandenigris.com/blog/?p=911 > > -- > View this message in context: http://forum.world.st/Most-wanted-programming-language-tp4282590p4282943.ht… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 10, 2012

Re: [Pharo-project] Most wanted programming language:

by Sean P. DeNigris

Torsten Bergmann wrote > > yes, see http://astares.blogspot.com/2006/07/stupid-metrics.html > Exactly! I wrote a short blog post to vent: http://seandenigris.com/blog/?p=911 -- View this message in context: http://forum.world.st/Most-wanted-programming-language-tp4282590p4282943.ht… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 10, 2012

Re: [Pharo-project] Drag and Drop - drag from hook

by Hilaire Fernandes

Yes you have to use dispatching. I did no see message sent to the owner morph by the system. Hilaire Le 10/01/2012 18:26, Sean P. DeNigris a Ã©crit : > > Hilaire Fernandes wrote >> >> You can achieve the effect with the message #justGrabbedFrom: sent to >> the grabbed morph >> > > Thanks Hilaire. I saw that one, but I'm wanting to notify the containing > morph (i.e. former owner) > > -- > View this message in context: http://forum.world.st/Drag-and-Drop-drag-from-hook-tp4282507p4282654.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Dr. Geo -- http://www.drgeo.eu

Jan. 10, 2012

Re: [Pharo-project] Drag and Drop - drag from hook

by StÃ©phane Ducasse

Ok my example was different. I wanted to know how I can control dropping. Stef On Jan 10, 2012, at 6:22 PM, Hilaire Fernandes wrote: > You can achieve the effect with the message #justGrabbedFrom: sent to > the grabbed morph > > Hilaire > > Le 10/01/2012 17:49, Sean P. DeNigris a Ã©crit : >> Is there a hook sent to the containing morph when one of its submorphs gets >> dragged out? I don't see one. >> >> Thanks. >> Sean >> >> -- >> View this message in context: http://forum.world.st/Drag-and-Drop-drag-from-hook-tp4282507p4282507.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> > > > -- > Dr. Geo -- http://www.drgeo.eu > >

Jan. 10, 2012

Re: [Pharo-project] Drag and Drop - drag from hook

by StÃ©phane Ducasse

long time ago I did a simple drag and drop example to understand how it works. On Jan 10, 2012, at 5:49 PM, Sean P. DeNigris wrote: > Is there a hook sent to the containing morph when one of its submorphs gets > dragged out? I don't see one. > > Thanks. > Sean > > -- > View this message in context: http://forum.world.st/Drag-and-Drop-drag-from-hook-tp4282507p4282507.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 10, 2012

Re: [Pharo-project] Drag and Drop - drag from hook

by Sean P. DeNigris

Hilaire Fernandes wrote > > You can achieve the effect with the message #justGrabbedFrom: sent to > the grabbed morph > Thanks Hilaire. I saw that one, but I'm wanting to notify the containing morph (i.e. former owner) -- View this message in context: http://forum.world.st/Drag-and-Drop-drag-from-hook-tp4282507p4282654.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 10, 2012

Re: [Pharo-project] SmallLint

by StÃ©phane Ducasse

Lukas Tx for the feedback. >> The correction of some rules can be automated (eg Rule Unnecessary "= true" or Variable not reference) -> add transformation to these rules. > > Yes, that would be nice. > >> Some rules such as Spelling rules (eg comments Method: Checks for spelling errors in method comments., 7088 problems) are not very interesting and could be removed (or treated differently?) > > I like them, but if you don't want the spelling rules you don't have > to load or run them. The question is how the package specifies what rules should be run. I think that packages should be able to state their false positive and the rules that they do not want to be run on them. > >> Adding an indice of difficulty to correct the rule: >> - Level of automation for the correction of the rule (automatic, semi-automatic, â¦). > > Actually this information is there: rules correct automatically if the > rule is a subclass of RBTransformationRule. Ok good to know. Are they linked to a refactoring? >> - Scope of the rule (block, method, class â¦). > > Not sure what you mean, but you can scope the rules to any > RBEnvironment (see > http://www.lukas-renggli.ch/blog/programmatically-run-lint) This is not in that direction but more. This rule may impact method, classesâ¦ One idea is can we propose a way to assess the cost of fixing a violated rules. Not easy since some of the rules are trivially fixed but may report a lot of violated places while a rule can be difficult to fix and only get to one place. Still we would like to give some hints to the maintainer. >> Other costs could be >> - cost of applying (may be the rule requires to compute something else, or if a rule has 50000 hits, it generates an extra cost to analyze the results) >> - cost of NOT applying the rule (if it could detect a bug and we don' t apply it ...) > > There is something like this in RBLintRule>>#severity. The severity is > shown as an icon in OB. Ok we should use that. >> Adding a manifest to manage/mark falses positive: >> - one manifest (a class) by package. >> - Manifest: exclusion of class/method of the package for rules or for all the rules. >> - Exclusion of rules for the package. > > See http://www.lukas-renggli.ch/blog/ignoring-lint-rules. > > Also many years ago I wrote some infrastructure to run critics rules > as part of the tests, what essentially served as a runnable manifest. what was it? How did you manage false positives. What we want is to add a package Manifesto to store false positives. Because we should not use pragma for that because we will have tons of pragmas everywhere. Then the package should also declared which rules not to run (or the inverse - any suggestion is welcome). Then also resolve the problem of ignoring completely classes for example. Now the manifesto could hold more information such as documentation, licenseâ¦. other metadata. We brainstormed For now we would like to add ManifestoofPackageXXX to each package add into it a data structure (may be under the form of methods). We could also easily strip out Manifesto for shrinking purpose. Now what is not good is if we want to store evolution of violation because the package should not get dirt each time a rule is run. Finally we are not sure if we want to have inside the package or on a separate package. I prefer inside to always ave synchronized metadata. and less packages to manage. > The code is in http://source.lukas-renggli.ch/essential.html, but it > likely needs some fixes to make it work in a recent version of Pharo. > >> One could also think on how to efficiently visualize the results of smallLint ... > > See for example the SmallLint results of Seaside 3.0 run by Jenkins: > http://jenkins.lukas-renggli.ch/job/Seaside%203.0/791/checkstyleResult/. How simon can help concretely? Right now we will prototype the idea on a couple of packages to see how it works. After we will report what we did and the result. I would like that we converge. And after that we would like to have an integration server running systematically the tests and the rules. Stef > > Cheers, > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

Jan. 10, 2012

Re: [Pharo-project] Drag and Drop - drag from hook

by Hilaire Fernandes

You can achieve the effect with the message #justGrabbedFrom: sent to the grabbed morph Hilaire Le 10/01/2012 17:49, Sean P. DeNigris a Ã©crit : > Is there a hook sent to the containing morph when one of its submorphs gets > dragged out? I don't see one. > > Thanks. > Sean > > -- > View this message in context: http://forum.world.st/Drag-and-Drop-drag-from-hook-tp4282507p4282507.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Dr. Geo -- http://www.drgeo.eu

Jan. 10, 2012