December 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] TextLint question

by Fabrizio Perin

Hi Alex, well the text index is calculated when you run the rules so of course if you touch the text than the indexes are not precise anymore. When you accept the text is saved and the rules are recalculated so also the positions of the errors are calculated again. Unfortunately i don't have a nice solution for this problem. One way could be: - when you save instead running the rules you just save the modified document. - than all the indexes of all the errors are update with the difference in size between the old and the new document. I don't know if this is going to be faster than simply re-run the rules. Anyway I will give it a try and i will let you know. Cheers, Fabrizio 2010/12/15 Alexandre Bergel <alexandre(a)bergel.eu> > hi! > > I am now using TextLint over my submissions. Each time I modify the text, > the rest of the errors have a wrong text index. It makes it difficult to > use. > I do an accept, to save my .tex and run the rules again, but it takes > time... > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > >

Dec. 15, 2010

Re: [Pharo-project] [Progress Report] Zinc HTTP Components

by Sven Van Caekenberghe

On 15 Dec 2010, at 17:11, Lukas Renggli wrote: > As usual, test results, code critics, and ready made images are available here: > > http://hudson.lukas-renggli.ch/job/Zinc/ I must say that I am quite addicted to your Hudson server, almost every time I check in I go look at the page to see how it rebuilds. It is really useful to have an integration server like that, and I can image it must be real fun for the (core) Pharo team as integration is one of their main issues. And it is instructive to so see all the Smalltalk scripting going on. Sven

Dec. 15, 2010

Re: [Pharo-project] Issue 2360 in pharo: nil out locals in a block if readBeforeWritten

by pharo＠googlecode.com

Comment #7 on issue 2360 by rydier: nil out locals in a block if readBeforeWritten http://code.google.com/p/pharo/issues/detail?id=2360 How about starting by writing a test where the problem this addresses is shown, before applying it blindly? Personally, I have a hard time figuring out what the code this is supposed to fix compilation of would look like just from glancing at the source...

Dec. 15, 2010

Re: [Pharo-project] Issue 2705 in pharo: Collection enh for Cog

by pharo＠googlecode.com

Comment #3 on issue 2705 by renggli: Collection enh for Cog http://code.google.com/p/pharo/issues/detail?id=2705 The version in Pharo is called #reduce: and slightly slower, but also more general. In Pharo not only two-argument blocks are supported, but also blocks with more arguments. Furthermore, for sequenceable collections there are variations for left- (#reduceLeft:) and right-fold (#reduceRight:). I suggest to keep the Pharo versions.

Dec. 15, 2010

Re: [Pharo-project] Issue 2705 in pharo: Collection enh for Cog

by pharo＠googlecode.com

Comment #2 on issue 2705 by marcus.denker: Collection enh for Cog http://code.google.com/p/pharo/issues/detail?id=2705 Next action: - take the code here and make a .cs or Slice out of it

Dec. 15, 2010

Re: [Pharo-project] Issue 2521 in pharo: ByteArray>>isLiteral more specific

by pharo＠googlecode.com

Comment #3 on issue 2521 by marcus.denker: ByteArray>>isLiteral more specific http://code.google.com/p/pharo/issues/detail?id=2521 Next action: - take the code here and make a .cs or Slice out of it

Dec. 15, 2010

Re: [Pharo-project] [Progress Report] Zinc HTTP Components

by Lukas Renggli

Cool, this is the way to go! As usual, test results, code critics, and ready made images are available here: http://hudson.lukas-renggli.ch/job/Zinc/ Lukas On 15 December 2010 17:04, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > I am pleased to report another milestone was reached in the Zn project. > > The default implementation for an HTTP Server is now a multi-threaded (forking) keep-alive implementation called ZnMultiThreadedServer. It passes my initial concurrent load tests. ZnServer is now a facade. This means that all features (test server, static file server, monticello server, seaside adaptor, as well as all unit tests) are now using the new code. > > In addition, several useful features were added to the servers, including logging and lastRequest/lastResponse debugging hooks. Extra handlers were added to ZnDefaultServerDelegate (favicon, benchmark, random) which double as examples. > > Next up will be some benchmarking and optimalization. As always, users/testers are most welcome. > > For more details: > > Â Â Â Â http://www.squeaksource.com/ZincHTTPComponents.html > > Â Â Â Â http://homepage.mac.com/svc/Zinc-HTTP-Components/index.html > > Â Â Â Â http://homepage.mac.com/svc/Zinc-HTTP-Components/getting-started.html > > Sven > > > -- Lukas Renggli www.lukas-renggli.ch

Dec. 15, 2010

Re: [Pharo-project] Issue 2454 in pharo: decompiler fix

by pharo＠googlecode.com

Comment #3 on issue 2454 by marcus.denker: decompiler fix http://code.google.com/p/pharo/issues/detail?id=2454 Next action: - take the code here and make a .cs or Slice out of it

Dec. 15, 2010

[Pharo-project] [Progress Report] Zinc HTTP Components

by Sven Van Caekenberghe

I am pleased to report another milestone was reached in the Zn project. The default implementation for an HTTP Server is now a multi-threaded (forking) keep-alive implementation called ZnMultiThreadedServer. It passes my initial concurrent load tests. ZnServer is now a facade. This means that all features (test server, static file server, monticello server, seaside adaptor, as well as all unit tests) are now using the new code. In addition, several useful features were added to the servers, including logging and lastRequest/lastResponse debugging hooks. Extra handlers were added to ZnDefaultServerDelegate (favicon, benchmark, random) which double as examples. Next up will be some benchmarking and optimalization. As always, users/testers are most welcome. For more details: http://www.squeaksource.com/ZincHTTPComponents.html http://homepage.mac.com/svc/Zinc-HTTP-Components/index.html http://homepage.mac.com/svc/Zinc-HTTP-Components/getting-started.html Sven

Dec. 15, 2010

Re: [Pharo-project] Issue 2445 in pharo: recent submission tools does not contain the recents message

by pharo＠googlecode.com

Comment #11 on issue 2445 by marcus.denker: recent submission tools does not contain the recents message http://code.google.com/p/pharo/issues/detail?id=2445 Next action: - Check if this is a problem in the current beta

Dec. 15, 2010