Re: [Pharo-dev] License agreement - are you kidding me?

The one thing I dont like about that agreement is that it forces to retreat from the personal copyright if I remember the document correctly. Even though personally I would not mind that for bug fixes and small enhancements where my copyright would not be so much of a big deal. For bigger tools

Re: [Pharo-dev] displayingProgress on demand

I would like to see this code injector too. Stef Le 7/12/15 18:43, Thierry Goubier a écrit : Hi Hernán, Le 07/12/2015 18:16, Hernán Morales Durand a écrit : Hi Sven 2015-12-06 17:34 GMT-03:00 Sven Van Caekenberghe >: There is still

Re: [Pharo-dev] displayingProgress on demand

Hi Denis, 2015-12-08 9:58 GMT+01:00 Denis Kudriashov : > Few years ago I try another approach which was work in my test. > > Instead of code rewriting to make loop iteration announcing steps you can > track periodically (in background) process which progress you want to >

[Pharo-dev] [pharo-project/pharo-core] ea78f0: 50489

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: ea78f0947d533da23c0281e0c38640bdc042bb3c https://github.com/pharo-project/pharo-core/commit/ea78f0947d533da23c0281e0c38640bdc042bb3c Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50489 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] displayingProgress on demand

2015-12-08 10:29 GMT+01:00 Denis Kudriashov : > > 2015-12-08 10:16 GMT+01:00 Thierry Goubier : > >> Wishfull thinking: >> >> you have a tradeoff when you do that, you interrupt running code and so >> changes timings and synchronisations, your scan

Re: [Pharo-dev] License agreement - are you kidding me?

On Tue, Dec 8, 2015 at 12:47 AM, webwarrior wrote: > Considering that there are a couple of responses and the fact that you > guys are so easily offended, I will not answer everyone but just state > couple of theses. > > > 0. I will not reveal my real name, because I value

Re: [Pharo-dev] [Pharo5] integration of FastTable needed

Le 08/12/2015 08:47, Marcus Denker a écrit : > Hi, > > FastTable recently has seen some important fixes. > > We are seeing people reporting the issues that are fixed again as they are > only fixed > in the repository, but these changes are not yet in Pharo5. > > Can the maintainer do a sync?

Re: [Pharo-dev] displayingProgress on demand

If this would work, that would make many people happy ! It would be basically make tracking progress a no-cost option. > On 08 Dec 2015, at 10:29, Denis Kudriashov wrote: > > > 2015-12-08 10:16 GMT+01:00 Thierry Goubier : > Wishfull thinking: >

Re: [Pharo-dev] displayingProgress on demand

Few years ago I try another approach which was work in my test. Instead of code rewriting to make loop iteration announcing steps you can track periodically (in background) process which progress you want to report. You can scan full call stack of it suspended context for loops and analyse it

Re: [Pharo-dev] [pharo-project/pharo-core] b01122: 50490

Le 08/12/2015 11:30, stepharo a écrit : > Thanks Cyril and others! > > Stef > > Le 8/12/15 11:16, Marcus Denker a écrit : >>> On 08 Dec 2015, at 11:10, GitHub wrote: >>> >>> >>> >>> Log Message: >>> --- >>> 50490 >>> 17211 FastTable update (see description) >>>

Re: [Pharo-dev] License agreement - are you kidding me?

I stand corrected , my memory fails me again. Agreed the document looks fine , I never talked about hidden agendas. I thinking I mixed up the "royalty-free" with the copyright part. My bad :) Absolutely no problem signing this. On Tue, Dec 8, 2015 at 12:13 PM Sven Van Caekenberghe

Re: [Pharo-dev] displayingProgress on demand

2015-12-08 13:53 GMT+01:00 Guillermo Polito : > Option 2: stack introspection > - this would not initially create a performance overhead if progress is > not used > - but there is the side effect of reifying the stack (that should be > measured) > Interesting how

Re: [Pharo-dev] CollectionValueHolder additions

Hi Peter, why don't you send the changed indexes as well? Just the value doesn't bring much imho. A single event could do all (ValueChangedFromToWith : hold all the information from a copyReplaceFrom:to:with: since I think this is a 'can do everything with it' kind of api: delete, replace, add).

Re: [Pharo-dev] License agreement - are you kidding me?

OK, no problem, just wanted to state the facts. > On 08 Dec 2015, at 13:36, Dimitris Chloupis wrote: > > I stand corrected , my memory fails me again. > > Agreed the document looks fine , I never talked about hidden agendas. I > thinking I mixed up the "royalty-free"

Re: [Pharo-dev] License agreement - are you kidding me?

I don't want to add to this discussion, but when plain errors are written, I have to. I thought you were a lawyer ? http://files.pharo.org/media/PharoSoftwareDistributionAgreement.pdf << The Parties agree that Supplier has contributed source code (the “Supplier’s Code”) for the open source

Re: [Pharo-dev] License agreement - are you kidding me?

On 08-12-15 00:47, webwarrior wrote: Considering that there are a couple of responses and the fact that you guys are so easily offended, I will not answer everyone but just state couple of theses. I'm happy that you care enough about pharo and our community that you take the time to explain

Re: [Pharo-dev] CollectionValueHolder additions

On 12/08, stepharo wrote: > Hi peter > > Do you mean instead of having ValueChanged? > What would be scenario for ValueRemoved? > In addition to ValueChanged. col := OrderedCollection new asValueHolder. col add: 1. "ValueAdded with 1 announced" col remove: 1. "ValueRemoved with 1 announced"

[Pharo-dev] [pharo-project/pharo-core] 0babd2: 50491

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 0babd210c7d0614f10059a70915c386fc3943810 https://github.com/pharo-project/pharo-core/commit/0babd210c7d0614f10059a70915c386fc3943810 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50491 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] displayingProgress on demand

Here is what I understand. Option 1: an aspect oriented solution where all usages of iterations get rewritten inside a scope to use progress - People showed examples using the RBTreeRewriter - I think that reflectivity should be also considered Option 2: stack introspection - this would

[Pharo-dev] [pharo-project/pharo-core] b01122: 50490

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: b01122f7148d3f9abdb0bb6ae4f2475650701927 https://github.com/pharo-project/pharo-core/commit/b01122f7148d3f9abdb0bb6ae4f2475650701927 Author: Jenkins Build Server Date:

Re: [Pharo-dev] [pharo-project/pharo-core] b01122: 50490

Thanks Cyril and others! Stef Le 8/12/15 11:16, Marcus Denker a écrit : On 08 Dec 2015, at 11:10, GitHub wrote: Log Message: --- 50490 17211 FastTable update (see description) https://pharo.fogbugz.com/f/cases/17211 This is: - Documentation -

Re: [Pharo-dev] License agreement - are you kidding me?

so, first of all, I find the way you communicate your arguments a bit… well, not very polite. second, even Ben’s affaire should show you why we value this license agreements. third, French laws are French laws and since the development of Pharo is in a big extent made here (through INRIA),

Re: [Pharo-dev] displayingProgress on demand

Could we have a synthesis of the discussion? It would be good to have a list of working solutions with pointers. Stef

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50490 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] [pharo-project/pharo-core] b01122: 50490

> On 08 Dec 2015, at 11:10, GitHub wrote: > > > > Log Message: > --- > 50490 > 17211 FastTable update (see description) > https://pharo.fogbugz.com/f/cases/17211 > This is: - Documentation - Improvement of the speed of examples - Removes indenting for

[Pharo-dev] Documentation epiphany

I just understood! Other languages might get better documentation because of all the extra slack time they get between compile cycles, that we don't get with Pharo's tight code-run-debug loop. I know... not a valid excuse for us**, but then I get to show this... https://xkcd.com/303/ ** of

Re: [Pharo-dev] displayingProgress on demand

2015-12-08 13:53 GMT+01:00 Guillermo Polito : > Here is what I understand. > > Option 1: an aspect oriented solution where all usages of iterations get > rewritten inside a scope to use progress > - People showed examples using the RBTreeRewriter > - I think that

Re: [Pharo-dev] displayingProgress on demand

I found code. It was work only in my test where I show progress of "(1 to: 1000) do: [:i | 1 seconds wait]". stack := executionProcess suspendedContext stack reversed. progressContext := stack detect: [:each | each receiver isKindOf: SequenceableCollection] ifNone: [nil]. progressContext

Re: [Pharo-dev] Documentation epiphany

Actually this joke I think is "stolen" by a previous joke about 3d artists , because our rendering times can be way longer than compiling the most complex C++ code. Easily can reach months of rendering time. Its a good joke, but it should be taken as it is , a joke and nothing more. Because I

Re: [Pharo-dev] doing stupid things (image will become unusable)

Hi, There used to be a mechanism for that (readonly variable bindings). It was there but not used: half the globals where readonly, all globals added after the experiment was done where “normal”. With the new “first class” variables we could easily add that back in a clean way. Marcus

Re: [Pharo-dev] displayingProgress on demand

On 12/7/2015 5:27 PM, Hernán Morales Durand wrote: but now I am failing to see how to replace #collect: with #collect:thenDo: using the rewriter: http://ws.stfx.eu/MOWS947F000O You don't need to first search using the RBParseTreeSearcher. The RBParseTreeRewriter works with search patterns.

Re: [Pharo-dev] Documentation epiphany

FWIW, the Blue Book is very good and is a free PDF now. Phil On Tue, Dec 8, 2015 at 4:36 PM, Dimitris Chloupis wrote: > "Actually this joke I think is "stolen" by a previous joke about 3d > artists" > > nope I think I am wrong once again, looks older. > > By the way

Re: [Pharo-dev] doing stupid things (image will become unusable)

I had this semester a lot of students having the same problem… I’m +1 to fix it. > On 8 dic 2015, at 5:19 p.m., Nicolai Hess wrote: > > Object := nil > > you can evaluate that piece of code, but afterwards > > Opal checks for assignments to read only variables

Re: [Pharo-dev] Documentation epiphany

"Actually this joke I think is "stolen" by a previous joke about 3d artists" nope I think I am wrong once again, looks older. By the way Pharo documentation is so good, I decided to start recommending it even to people new to coding. Much much better than it used to be 2 years ago, in another 2

Re: [Pharo-dev] doing stupid things (image will become unusable)

Yes, I wondered why it was not done in semantic analysis… would be much easier. The binding approach only takes care of reflective change (Smalltalk globals at: Object put: nil), a case that is not as important to fix. (reflection is dangerous, disallowing just this one operation does not

[Pharo-dev] doing stupid things (image will become unusable)

Object := nil you can evaluate that piece of code, but afterwards Opal checks for assignments to read only variables (method arguments for example) and signals an error if you try to modify those vars. But it does not check globals. Should all Globals (OCLiteralVariable with isGlobalVar ==

Re: [Pharo-dev] doing stupid things (image will become unusable)

I remember. But what I do not remember is if the compiler was aware of it. I remember you had these ReadOnlyVariable, subclass of association that redefined #value:. You were however still capable of doing: MyReadOnlyVar := 1. > On 8 dic 2015, at 5:29 p.m., Marcus Denker

[Pharo-dev] Unified Property API and persistent properties (Pharo 5)

In Pharo 5 the "properties" API is unified (means you can associate properties to classes, methods, packages, ...). Really cool and a good step toward a unified and more flexible system. Exampel: |pck| pck := #'Foo-Kernel' asPackage. pck propertyAt: #'lastModified' put: DateAndTime now

Re: [Pharo-dev] doing stupid things (image will become unusable)

i AM MORE INTERESTED IN WHAT STATE HER CONSCIOUSNESS IS INAFTER TRICKING HER? If there is true loss of perceptory connection with the mirage, real pratyahara, there may still be a seed of meditation, so called Sabija Samadhi. It is not clear to me whether there actually is - messages sent

Re: [Pharo-dev] License agreement - are you kidding me?

"What you lose is the right to take out your code (and to change the licensing of it retroactively…)." That is only true in one sense. 1) The author cannot demand that the code is removed from the codebase - as the original grant of licence was irrevocable. (Or at least, this is proven true in

Re: [Pharo-dev] Unicode Support

"No. a codepoint is the numerical value assigned to a character. An "encoded character" is the way a codepoint is represented in bytes using a given encoding." No. A codepoint may represent a component part of an abstract character, or may represent an abstract character, or it may do both (but

Re: [Pharo-dev] [Cuis] Sorting Unicode strings (Re: [Unicode] collation sequences (Re: [squeak-dev] Unicode Support))

Dale - is that you can't depend on the value of a codepoint *unless the string is either in fully-composed form (or has just been fully-decomposed from a fully-composed form) * OR are there circumstances where even those two cases cannot be relied upon? On 8 December 2015 at 19:20, Dale Henrichs

Re: [Pharo-dev] Documentation epiphany

The joke it's based on pre-dates use of computers to render complex 3D :-) Here's the world's first computer-generated 3D movie, from the Uni of Utah in 1972: https://vimeo.com/16292363 Compiled languages predate this. On 8 December 2015 at 15:24, Dimitris Chloupis

Re: [Pharo-dev] License agreement - are you kidding me?

"partially anonymous" The correct word is "pseudonimity". In UK law, as long as there is no intent to defraud, you can call yourself anything you like. In UK, you can provide signatures digitally, completely legally. UK law is has a long tradition of sorting out legal issues between two-third

Re: [Pharo-dev] Hook "WACurrentRequestContext" into debugger?

> On 07 Dec 2015, at 17:17, Mariano Martinez Peck wrote: > > OK Max. In the last version you can find the "likely" final version. It's > extremely simple, easy to use, and very very little code. Only one override. > All WADynamicVariables subclasses handled

Re: [Pharo-dev] displayingProgress on demand

Hi John, Thank you for your feedback and help! I started a ProgressBarInstaller using your corrections. Unfortunately SmalltalkHub is not working for me right now but will check tomorrow and share the link. Best regards, Hernán 2015-12-08 13:56 GMT-03:00 John Brant

Re: [Pharo-dev] Help needed: old issues issue tracker entries

Excellent. Can I suggest that in future they are simply closed, rather than re-assigned? On 3 December 2015 at 06:35, Nicolai Hess wrote: > > Am 03.12.2015 1:08 vorm. schrieb "EuanM" : >> >> I had an issue assigned against me, which I have not the time

Re: [Pharo-dev] displayingProgress on demand

http://www.smalltalkhub.com/#!/~hernan/ProgressBarInstaller Public write access Cheers, Hernán 2015-12-08 20:40 GMT-03:00 Hernán Morales Durand : > Hi John, > > Thank you for your feedback and help! > > I started a ProgressBarInstaller using your corrections.

Re: [Pharo-dev] [Cuis] Sorting Unicode strings (Re: [Unicode] collation sequences (Re: [squeak-dev] Unicode Support))

Euan, What I meant is that you can't _always_ use the code point for collation, i.e., sorting based on the value of code points is not always correct[1]. If I'm not mistaken the fully-composed and fully-decomposed forms can only be used for testing the equivalence of two strings[2] ...