Fwd: Patches for Pharo packages you are maintaining
No time so fr to handle it. Stef Begin forwarded message:
From: "monty" <monty.os@engineer.com> Subject: Patches for Pharo packages you are maintaining Date: November 21, 2013 3:14:25 AM GMT+01:00 To: stephane.ducasse@inria.fr
Prof. Stef, I have produced updates to the XML-Parser, XML-Parser-Testing, and XML-Writer-Core packages you are maintaining.
These updates add validation against internal and external DTDs, proper replacement of general and parameter entites, customizable resolution of external parsed entities using Zinc and FileSystem, awareness of notations and unparsed entities, preservation of the internal DTD subset by the DOM parser (so printing a parsed doc with a DTD will produce approximately what was input), line numbers reporting in error messages, and better well-formed and validity constraints.
I had to largely rewrite the tokenizer to make everything work, but I followed the spec closely, and it is about the same speed as long as there is no DTD to validate against.
One problem is that while the tests I added and the existing tests all pass, for some reason helper messages in some test classes starting with "should" (in the style of should:raise:) are being interpreted as tests and run by TestRuner, even though they don't begin with "test" and take arguments! This is possibly a bug in TestRunner.
Another problem is that there are so many deprecated methods cluttering up classes, some of which have been deprecated for years! It is confusing and hard to see which methods to use just by browsing the protocols. I would really suggest using this code to get rid of the XML-Parser methods that have been deprecated for at least a year:
expiry := 1 year. (SystemNavigation default allClassesInPackageNamed: 'XML-Parser') do: [:class | class selectors do: [:selector | | compiledMethod timeStamp | compiledMethod := class compiledMethodAt: selector. timeStamp := compiledMethod timeStamp copyAfter: Character space. (compiledMethod isDeprecated and: [(DateAndTime now - (DateAndTime fromString: timeStamp)) > expiry]) ifTrue: [class removeSelector: selector]]].
I ran and checked it myself and it doesn't break anything. Running the above with XML-Writer-Core might not be a bad idea either.
I also updated BitmapCharacterSet to use less memory.
opened https://pharo.fogbugz.com/f/cases/12229/XML-Tools-improvement otherwise these changes are as good as lost. sending mcz via mail is from the last century. On 2013-11-23, at 09:00, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
No time so fr to handle it.
Stef
Begin forwarded message:
From: "monty" <monty.os@engineer.com> Subject: Patches for Pharo packages you are maintaining Date: November 21, 2013 3:14:25 AM GMT+01:00 To: stephane.ducasse@inria.fr
Prof. Stef, I have produced updates to the XML-Parser, XML-Parser-Testing, and XML-Writer-Core packages you are maintaining.
These updates add validation against internal and external DTDs, proper replacement of general and parameter entites, customizable resolution of external parsed entities using Zinc and FileSystem, awareness of notations and unparsed entities, preservation of the internal DTD subset by the DOM parser (so printing a parsed doc with a DTD will produce approximately what was input), line numbers reporting in error messages, and better well-formed and validity constraints.
I had to largely rewrite the tokenizer to make everything work, but I followed the spec closely, and it is about the same speed as long as there is no DTD to validate against.
One problem is that while the tests I added and the existing tests all pass, for some reason helper messages in some test classes starting with "should" (in the style of should:raise:) are being interpreted as tests and run by TestRuner, even though they don't begin with "test" and take arguments! This is possibly a bug in TestRunner.
Another problem is that there are so many deprecated methods cluttering up classes, some of which have been deprecated for years! It is confusing and hard to see which methods to use just by browsing the protocols. I would really suggest using this code to get rid of the XML-Parser methods that have been deprecated for at least a year:
expiry := 1 year. (SystemNavigation default allClassesInPackageNamed: 'XML-Parser') do: [:class | class selectors do: [:selector | | compiledMethod timeStamp | compiledMethod := class compiledMethodAt: selector. timeStamp := compiledMethod timeStamp copyAfter: Character space. (compiledMethod isDeprecated and: [(DateAndTime now - (DateAndTime fromString: timeStamp)) > expiry]) ifTrue: [class removeSelector: selector]]].
I ran and checked it myself and it doesn't break anything. Running the above with XML-Writer-Core might not be a bad idea either.
I also updated BitmapCharacterSet to use less memory. <XML-Writer-Core-monty.5.mcz> <XML-Tests-Parser-monty.27.mcz> <XML-Parser-monty.173.mcz> <Collections-BitmapCharacterSet-Anonymous.6.mcz> <Collections-BitmapCharacterSet-Anonymous.6.mcz>
On Nov 23, 2013, at 9:51 AM, Camillo Bruni <camillobruni@gmail.com> wrote:
opened https://pharo.fogbugz.com/f/cases/12229/XML-Tools-improvement otherwise these changes are as good as lost. sending mcz via mail is from the last century.
I did not say it like that but indeed I would prefer that people have account on Smalltalkhub :)
On 2013-11-23, at 09:00, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
No time so fr to handle it.
Stef
Begin forwarded message:
From: "monty" <monty.os@engineer.com> Subject: Patches for Pharo packages you are maintaining Date: November 21, 2013 3:14:25 AM GMT+01:00 To: stephane.ducasse@inria.fr
Prof. Stef, I have produced updates to the XML-Parser, XML-Parser-Testing, and XML-Writer-Core packages you are maintaining.
These updates add validation against internal and external DTDs, proper replacement of general and parameter entites, customizable resolution of external parsed entities using Zinc and FileSystem, awareness of notations and unparsed entities, preservation of the internal DTD subset by the DOM parser (so printing a parsed doc with a DTD will produce approximately what was input), line numbers reporting in error messages, and better well-formed and validity constraints.
I had to largely rewrite the tokenizer to make everything work, but I followed the spec closely, and it is about the same speed as long as there is no DTD to validate against.
One problem is that while the tests I added and the existing tests all pass, for some reason helper messages in some test classes starting with "should" (in the style of should:raise:) are being interpreted as tests and run by TestRuner, even though they don't begin with "test" and take arguments! This is possibly a bug in TestRunner.
Another problem is that there are so many deprecated methods cluttering up classes, some of which have been deprecated for years! It is confusing and hard to see which methods to use just by browsing the protocols. I would really suggest using this code to get rid of the XML-Parser methods that have been deprecated for at least a year:
expiry := 1 year. (SystemNavigation default allClassesInPackageNamed: 'XML-Parser') do: [:class | class selectors do: [:selector | | compiledMethod timeStamp | compiledMethod := class compiledMethodAt: selector. timeStamp := compiledMethod timeStamp copyAfter: Character space. (compiledMethod isDeprecated and: [(DateAndTime now - (DateAndTime fromString: timeStamp)) > expiry]) ifTrue: [class removeSelector: selector]]].
I ran and checked it myself and it doesn't break anything. Running the above with XML-Writer-Core might not be a bad idea either.
I also updated BitmapCharacterSet to use less memory. <XML-Writer-Core-monty.5.mcz> <XML-Tests-Parser-monty.27.mcz> <XML-Parser-monty.173.mcz> <Collections-BitmapCharacterSet-Anonymous.6.mcz> <Collections-BitmapCharacterSet-Anonymous.6.mcz>
Le 23/11/2013 09:51, Camillo Bruni a écrit :
opened https://pharo.fogbugz.com/f/cases/12229/XML-Tools-improvement otherwise these changes are as good as lost. sending mcz via mail is from the last century.
Hello In the welcome page of the bug tracker, add a page explaining how to create by yourself an account. Thanks Hilaire -- Dr. Geo http://drgeo.eu
hilaire wrote
Le 23/11/2013 09:51, Camillo Bruni a écrit : In the welcome page of the bug tracker, add a page explaining how to create by yourself an account.
Like the one there now (https://pharo.fogbugz.com/default.asp?W41) ? ;)
Welcome to the Pharo issue tracker. This is the official issue tracker for cases related to the different versions of Pharo.
You most probably see this page because you are not logged in, or you do not have an account on the issue tracker yet (*Register here*).
But seriously if this is not clear, how do we improve it? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Fwd-Patches-for-Pharo-packages-you-are-maintaining-tp4... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Le 23/11/2013 19:05, Sean P. DeNigris a écrit :
But seriously if this is not clear, how do we improve it?
Make it work. It never worked for me, I keep trying then give up, thinking about a temporary failure, then doing other business. I don't understand what the monkey really want but it is not nice with me. So I guess I miss something that should be documented. Hilaire -- Dr. Geo http://drgeo.eu
Le 23/11/2013 19:19, Hilaire Fernandes a écrit :
Le 23/11/2013 19:05, Sean P. DeNigris a écrit :
But seriously if this is not clear, how do we improve it?
Make it work. It never worked for me, I keep trying then give up, thinking about a temporary failure, then doing other business. I don't understand what the monkey really want but it is not nice with me. So I guess I miss something that should be documented.
Hilaire
So registering on Pharo tracker *never* worked for me, since I try, before the summer. Hilaire -- Dr. Geo http://drgeo.eu
On 23 Nov 2013, at 20:44, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
Le 23/11/2013 19:19, Hilaire Fernandes a écrit :
Le 23/11/2013 19:05, Sean P. DeNigris a écrit :
But seriously if this is not clear, how do we improve it?
Make it work. It never worked for me, I keep trying then give up, thinking about a temporary failure, then doing other business. I don't understand what the monkey really want but it is not nice with me. So I guess I miss something that should be documented.
Hilaire
So registering on Pharo tracker *never* worked for me, since I try, before the summer.
In the end I think is was a mistake to use fogbugz. For sure itâs nice for companies, but for open sourse projects it just does not work with a closed bug tracker. Now the question is what is the effort to move to yet another one? Marcus
On 2013-11-23, at 20:51, Marcus Denker <marcus.denker@inria.fr> wrote:
On 23 Nov 2013, at 20:44, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
Le 23/11/2013 19:19, Hilaire Fernandes a écrit :
Le 23/11/2013 19:05, Sean P. DeNigris a écrit :
But seriously if this is not clear, how do we improve it?
Make it work. It never worked for me, I keep trying then give up, thinking about a temporary failure, then doing other business. I don't understand what the monkey really want but it is not nice with me. So I guess I miss something that should be documented.
Hilaire
So registering on Pharo tracker *never* worked for me, since I try, before the summer.
In the end I think is was a mistake to use fogbugz. For sure itâs nice for companies, but for open sourse projects it just does not work with a closed bug tracker.
But I get the impression that everybody wants to submit fixes their way and assume that things are resolved in another way. There is quite a system behind everything which is documented and well described (of course nobody ever read it...): https://pharo.fogbugz.com/default.asp?W65 I currently see 4 big problems: 1. the password reset mail is not sent automatically (very confusing) 2. you need 2 accounts (once for fogbugz and once for smalltalkhub) 3. there are no public inboxes on smalltalkhub (requires another bothersome step to add people manually) 4. submitting a slice from the image requires the previous 3 steps to be completed upfront It is close to impossible to describe that accurately in text, that's why I opted for a video which takes some time, but should include all the above steps. I am pretty sure that if you follow the video step by step you will get access without problems. If not, I can update the instructions there.
Is it so hard to register on STH and Fogbugz + give access to a Pharo inbox ? Nah, come on. At least, Fogbugz looks like a decent issue tracker and is easy to use. (And we should push more Wiki pages in there). Phil
So registering on Pharo tracker *never* worked for me, since I try, before the summer.
In the end I think is was a mistake to use fogbugz. For sure itâs nice for companies, but for open sourse projects it just does not work with a closed bug tracker.
Now the question is what is the effort to move to yet another one?
I do not like fogbugz but I would not change now. Let us - make it easy for people to log - remove this ugly monkey pictures (I do not like it - do you think that people can understand anything with it. - get a newer version of smalltalkhub and continue. Stef
I do not like fogbugz but I would not change now. Let us - make it easy for people to log - remove this ugly monkey pictures (I do not like it - do you think that people can understand anything with it. - get a newer version of smalltalkhub and continue.
Stef
+ 1 Bye T.
>>> So registering on Pharo tracker *never* worked for me, since I try, >>> before the summer. >> In the end I think is was a mistake to use fogbugz. For sure itâs nice for companies, but >> for open sourse projects it just does not work with a closed bug tracker. >> >> Now the question is what is the effort to move to yet another one? > I do not like fogbugz but I would not change now. > Let us > - make it easy for people to log The Racket programming language (racket-lang.org) has in its IDE DrRacket a menu item - Submit bug report Details about the system and a description of the bug is gathered and sent of to a bugs mailing list as well as creating an issue in a bug tracker. This way you get the issue number, a possible discussion thread about the bug/enhancement and any user can take part. IMHO this is the _right_ way to do it. Is there something similar for pharo? Contributing changes this way might get more complicated though, but possible.
Truth is that we can do better than others because we can serialize the stack and rebuild it in another place, making the reproduction of the error a triviality. In my infinite TODO list I have: add a "submit bug" button to debugger window. Only think that has prevented me to implement it is lack of time... If someone wants to take this task (not so hard, all the parts needed are already there), it would be a cool contribution to community. Esteban On Sat, Nov 23, 2013 at 10:51 PM, Lorenz Köhl <lorenz@quub.de> wrote:
So registering on Pharo tracker *never* worked for me, since I try, before the summer. In the end I think is was a mistake to use fogbugz. For sure itâs nice for companies, but for open sourse projects it just does not work with a closed bug tracker.
Now the question is what is the effort to move to yet another one? I do not like fogbugz but I would not change now. Let us - make it easy for people to log
The Racket programming language (racket-lang.org) has in its IDE DrRacket a menu item - Submit bug report
Details about the system and a description of the bug is gathered and sent of to a bugs mailing list as well as creating an issue in a bug tracker. This way you get the issue number, a possible discussion thread about the bug/enhancement and any user can take part. IMHO this is the _right_ way to do it.
Is there something similar for pharo?
Contributing changes this way might get more complicated though, but possible.
On Nov 23, 2013, at 10:51 PM, Lorenz Köhl <lorenz@quub.de> wrote: >>>> So registering on Pharo tracker *never* worked for me, since I try, >>>> before the summer. >>> In the end I think is was a mistake to use fogbugz. For sure itâs nice for companies, but >>> for open sourse projects it just does not work with a closed bug tracker. >>> >>> Now the question is what is the effort to move to yet another one? >> I do not like fogbugz but I would not change now. >> Let us >> - make it easy for people to log > > The Racket programming language (racket-lang.org) has in its IDE DrRacket a menu item > - Submit bug report > > Details about the system and a description of the bug is gathered and sent of to a bugs mailing list as well as creating an issue in a bug tracker. This way you get the issue number, a possible discussion thread about the bug/enhancement and any user can take part. IMHO this is the _right_ way to do it. Long long time ago all the bugs could be submitted from Squeak itself (way before racket even started to exist) and we add a tool to crawl the emails and sort the bugs and it was a lot of work. So the Right way is something to evaluate and learn. > > Is there something similar for pharo? No but it was planned now if people can publish bug at a fast rate (and may be there are not bug) our question is: is it really reasonable to overwhelm with bugs :) > Contributing changes this way might get more complicated though, but possible.
On 24 November 2013 09:28, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
On Nov 23, 2013, at 10:51 PM, Lorenz Köhl <lorenz@quub.de> wrote:
So registering on Pharo tracker *never* worked for me, since I try, before the summer. In the end I think is was a mistake to use fogbugz. For sure itâs nice for companies, but for open sourse projects it just does not work with a closed bug tracker.
Now the question is what is the effort to move to yet another one? I do not like fogbugz but I would not change now. Let us - make it easy for people to log
The Racket programming language (racket-lang.org) has in its IDE DrRacket a menu item - Submit bug report
Details about the system and a description of the bug is gathered and sent of to a bugs mailing list as well as creating an issue in a bug tracker. This way you get the issue number, a possible discussion thread about the bug/enhancement and any user can take part. IMHO this is the _right_ way to do it.
Long long time ago all the bugs could be submitted from Squeak itself (way before racket even started to exist) and we add a tool to crawl the emails and sort the bugs and it was a lot of work.
Ah, good old BFAV (Bug Fix Archive Viewer). Helping maintain that was the first thing I actually did for the community (as opposed to lurking). frank
So the Right way is something to evaluate and learn.
Is there something similar for pharo?
No but it was planned now if people can publish bug at a fast rate (and may be there are not bug) our question is: is it really reasonable to overwhelm with bugs :)
Contributing changes this way might get more complicated though, but possible.
killing ugly monkey picture: +1000! (a reason why I don't go there BTW, it scares me). Phil On Sat, Nov 23, 2013 at 10:27 PM, Stéphane Ducasse < stephane.ducasse@inria.fr> wrote:
So registering on Pharo tracker *never* worked for me, since I try, before the summer.
In the end I think is was a mistake to use fogbugz. For sure itâs nice for companies, but for open sourse projects it just does not work with a closed bug tracker.
Now the question is what is the effort to move to yet another one?
I do not like fogbugz but I would not change now. Let us - make it easy for people to log - remove this ugly monkey pictures (I do not like it - do you think that people can understand anything with it. - get a newer version of smalltalkhub and continue.
Stef
I like the monkey... but I really don't care if is there or not. Now... I think there are some real bugs in the bug tracker (like not updating the list). I do not like fogbugz, I find it heavy, hard to use and a real pain in my ***, but I also think that "you do not change horses in the middle of the race" :) Esteban On Sun, Nov 24, 2013 at 12:38 AM, phil@highoctane.be <phil@highoctane.be>wrote:
killing ugly monkey picture: +1000! (a reason why I don't go there BTW, it scares me).
Phil
On Sat, Nov 23, 2013 at 10:27 PM, Stéphane Ducasse < stephane.ducasse@inria.fr> wrote:
So registering on Pharo tracker *never* worked for me, since I try, before the summer.
In the end I think is was a mistake to use fogbugz. For sure itâs nice for companies, but for open sourse projects it just does not work with a closed bug tracker.
Now the question is what is the effort to move to yet another one?
I do not like fogbugz but I would not change now. Let us - make it easy for people to log - remove this ugly monkey pictures (I do not like it - do you think that people can understand anything with it. - get a newer version of smalltalkhub and continue.
Stef
For the easiest thing in town, I'd say "Atlassian Jira" https://www.atlassian.com/opensource/overview I am using Fogbugz and JIRA on several client projects and JIRA definitely has more traction and engagement. But, migrating may be less painful than before: https://confluence.atlassian.com/display/JIRA/Importing+Data+from+FogBugz+fo... https://www.atlassian.com/software/jira/importer-migrations#!jira-fogbugz Phil
he, no, we are not going to re-migrate anytime soon :) last year we needed a solution and we find it with fogbugz. Now, probably it does not fits completely with our process or our openness our other stuff, but still we have a reality: changing it is a lot of effort and even if fogbugz is not perfect, it works. So... until we have time and a *proven* better solution, we will not change it. As Stef said, the right step (now) is to make what we have work better, not run away from it :) And of course, I'm not saying not to change ever... just not doing it impulsively and without reasoning... Esteban On Sun, Nov 24, 2013 at 10:15 AM, phil@highoctane.be <phil@highoctane.be>wrote:
For the easiest thing in town, I'd say "Atlassian Jira" https://www.atlassian.com/opensource/overview
I am using Fogbugz and JIRA on several client projects and JIRA definitely has more traction and engagement.
But, migrating may be less painful than before: https://confluence.atlassian.com/display/JIRA/Importing+Data+from+FogBugz+fo...
https://www.atlassian.com/software/jira/importer-migrations#!jira-fogbugz
Phil
Le 24/11/2013 10:23, Esteban Lorenzano a écrit :
he, no, we are not going to re-migrate anytime soon :)
As I am concerned, I was just complaining about an initial difficulty to register myself. No opinion on the bug tracker itself. Hilaire -- Dr. Geo http://drgeo.eu
I like the monkeyâ¦
we talk about the picture
but I really don't care if is there or not. Now... I think there are some real bugs in the bug tracker (like not updating the list).
I do not like fogbugz, I find it heavy, hard to use and a real pain in my ***, but I also think that "you do not change horses in the middle of the race" :)
Esteban
On Sun, Nov 24, 2013 at 12:38 AM, phil@highoctane.be <phil@highoctane.be> wrote: killing ugly monkey picture: +1000! (a reason why I don't go there BTW, it scares me).
Phil
On Sat, Nov 23, 2013 at 10:27 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
So registering on Pharo tracker *never* worked for me, since I try, before the summer.
In the end I think is was a mistake to use fogbugz. For sure itâs nice for companies, but for open sourse projects it just does not work with a closed bug tracker.
Now the question is what is the effort to move to yet another one?
I do not like fogbugz but I would not change now. Let us - make it easy for people to log - remove this ugly monkey pictures (I do not like it - do you think that people can understand anything with it. - get a newer version of smalltalkhub and continue.
Stef
On Sun, Nov 24, 2013 at 10:29 AM, Stéphane Ducasse < stephane.ducasse@inria.fr> wrote:
I like the monkeyâ¦
we talk about the picture
yeah, I know... me too, I like it :D (but as I say, I do not care about it :P)
but I really don't care if is there or not. Now... I think there are some real bugs in the bug tracker (like not updating the list).
I do not like fogbugz, I find it heavy, hard to use and a real pain in my ***, but I also think that "you do not change horses in the middle of the race" :)
Esteban
On Sun, Nov 24, 2013 at 12:38 AM, phil@highoctane.be <phil@highoctane.be>wrote:
killing ugly monkey picture: +1000! (a reason why I don't go there BTW, it scares me).
Phil
On Sat, Nov 23, 2013 at 10:27 PM, Stéphane Ducasse < stephane.ducasse@inria.fr> wrote:
So registering on Pharo tracker *never* worked for me, since I try, before the summer.
In the end I think is was a mistake to use fogbugz. For sure itâs nice for companies, but for open sourse projects it just does not work with a closed bug tracker.
Now the question is what is the effort to move to yet another one?
I do not like fogbugz but I would not change now. Let us - make it easy for people to log - remove this ugly monkey pictures (I do not like it - do you think that people can understand anything with it. - get a newer version of smalltalkhub and continue.
Stef
On 2013-11-24, at 10:44, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On Sun, Nov 24, 2013 at 10:29 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I like the monkeyâ¦
we talk about the picture
I removed it roughly 2 months ago but due to the seaside configuration hick-up the Jenkins job / public issue list configuration does no longer work.
On 2013-11-23, at 11:02, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
Le 23/11/2013 09:51, Camillo Bruni a écrit :
opened https://pharo.fogbugz.com/f/cases/12229/XML-Tools-improvement otherwise these changes are as good as lost. sending mcz via mail is from the last century.
Hello
In the welcome page of the bug tracker, add a page explaining how to create by yourself an account.
It is all there: https://pharo.fogbugz.com/default.asp?W41 I was even so lazy that I made a video ;) since there are so many nasty steps involved that I don't think text will do it.
On 23 Nov 2013, at 21:25, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2013-11-23, at 11:02, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
Le 23/11/2013 09:51, Camillo Bruni a écrit :
opened https://pharo.fogbugz.com/f/cases/12229/XML-Tools-improvement otherwise these changes are as good as lost. sending mcz via mail is from the last century.
Hello
In the welcome page of the bug tracker, add a page explaining how to create by yourself an account.
It is all there: https://pharo.fogbugz.com/default.asp?W41
I was even so lazy that I made a video ;) since there are so many nasty steps involved that I don't think text will do it.
and it should be noted that the scheme we use is not the way it is because we think itâs perfect. This is really strange that people always pre-suppose that whatever is done is done with indefinite resources and therefore by definition exactly what was wanted. To the contrary: we just make it up as we go along, with very limited resources, sometimes doing wrong decisions.. and we will slowly improve. And no, just stopping until the process is perfect is *not* they way to go. This will just lead to nothing happening, not to perfection. Marcus
On 23 November 2013 20:35, Marcus Denker <marcus.denker@inria.fr> wrote:
On 23 Nov 2013, at 21:25, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2013-11-23, at 11:02, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
Le 23/11/2013 09:51, Camillo Bruni a écrit :
opened https://pharo.fogbugz.com/f/cases/12229/XML-Tools-improvement otherwise these changes are as good as lost. sending mcz via mail is from the last century.
Hello
In the welcome page of the bug tracker, add a page explaining how to create by yourself an account.
It is all there: https://pharo.fogbugz.com/default.asp?W41
I was even so lazy that I made a video ;) since there are so many nasty steps involved that I don't think text will do it.
and it should be noted that the scheme we use is not the way it is because we think itâs perfect.
This is really strange that people always pre-suppose that whatever is done is done with indefinite resources and therefore by definition exactly what was wanted. To the contrary: we just make it up as we go along, with very limited resources, sometimes doing wrong decisions.. and we will slowly improve.
And no, just stopping until the process is perfect is *not* they way to go. This will just lead to nothing happening, not to perfection.
Or, the way to perfect the process is to use the existing process, and smooth off the rough edges, just like is happening. frank
Marcus
On 2013-11-23, at 21:35, Marcus Denker <marcus.denker@inria.fr> wrote:
On 23 Nov 2013, at 21:25, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2013-11-23, at 11:02, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
Le 23/11/2013 09:51, Camillo Bruni a écrit :
opened https://pharo.fogbugz.com/f/cases/12229/XML-Tools-improvement otherwise these changes are as good as lost. sending mcz via mail is from the last century.
Hello
In the welcome page of the bug tracker, add a page explaining how to create by yourself an account.
It is all there: https://pharo.fogbugz.com/default.asp?W41
I was even so lazy that I made a video ;) since there are so many nasty steps involved that I don't think text will do it.
and it should be noted that the scheme we use is not the way it is because we think itâs perfect.
This is really strange that people always pre-suppose that whatever is done is done with indefinite resources and therefore by definition exactly what was wanted. To the contrary: we just make it up as we go along, with very limited resources, sometimes doing wrong decisions.. and we will slowly improve.
And no, just stopping until the process is perfect is *not* they way to go. This will just lead to nothing happening, not to perfection.
... and we're one step closer: I removed some noise from the fogbugz entry page to guide people to the right direction.
Le 23/11/2013 21:24, Camillo Bruni a écrit :
It is all there: https://pharo.fogbugz.com/default.asp?W41
I was even so lazy that I made a video ;) since there are so many nasty steps involved that I don't think text will do it.
Already saw the menu of this video and did not fell related to my concern. Btw I can't watch video from VIMEO, maybe my ISP, I have to download it. Got it anyway. Well the 'Press the forgot password' link could be written somewhere, it will not hurt. Thanks Hilaire -- Dr. Geo http://drgeo.eu
On 2013-11-23, at 21:45, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
Le 23/11/2013 21:24, Camillo Bruni a écrit :
It is all there: https://pharo.fogbugz.com/default.asp?W41
I was even so lazy that I made a video ;) since there are so many nasty steps involved that I don't think text will do it.
Already saw the menu of this video and did not fell related to my concern. Btw I can't watch video from VIMEO, maybe my ISP, I have to download it.
weird... I could mirror it on youtube, but then again that just adds yet another point of confusion, does it?
Got it anyway. Well the 'Press the forgot password' link could be written somewhere, it will not hurt.
that solves one out of 20 little steps, so just writing down that part is not very useful I think. see https://pharo.fogbugz.com/f/cases/11550/
On 2013-11-23, at 21:49, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2013-11-23, at 21:45, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
Le 23/11/2013 21:24, Camillo Bruni a écrit :
It is all there: https://pharo.fogbugz.com/default.asp?W41
I was even so lazy that I made a video ;) since there are so many nasty steps involved that I don't think text will do it.
Already saw the menu of this video and did not fell related to my concern. Btw I can't watch video from VIMEO, maybe my ISP, I have to download it.
weird... I could mirror it on youtube, but then again that just adds yet another point of confusion, does it?
Got it anyway. Well the 'Press the forgot password' link could be written somewhere, it will not hurt.
that solves one out of 20 little steps, so just writing down that part is not very useful I think.
so yes, maybe show that link on the registration page under http://bugs.pharo.org ... but somebody has to do it ;)
*cough github cough* *** runs away *** On Sat, Nov 23, 2013 at 10:50 PM, Camillo Bruni <camillobruni@gmail.com>wrote:
On 2013-11-23, at 21:49, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2013-11-23, at 21:45, Hilaire Fernandes <hilaire.fernandes@gmail.com> wrote:
Le 23/11/2013 21:24, Camillo Bruni a écrit :
It is all there: https://pharo.fogbugz.com/default.asp?W41
I was even so lazy that I made a video ;) since there are so many nasty steps involved that I don't think text will do it.
Already saw the menu of this video and did not fell related to my concern. Btw I can't watch video from VIMEO, maybe my ISP, I have to download it.
weird... I could mirror it on youtube, but then again that just adds yet another point of confusion, does it?
Got it anyway. Well the 'Press the forgot password' link could be written somewhere, it will not hurt.
that solves one out of 20 little steps, so just writing down that part is not very useful I think.
so yes, maybe show that link on the registration page under http://bugs.pharo.org ... but somebody has to do it ;)
El 23/11/2013 5:51, Camillo Bruni escribió:
opened https://pharo.fogbugz.com/f/cases/12229/XML-Tools-improvement otherwise these changes are as good as lost. sending mcz via mail is from the last century.
Maybe, but some of us are attending 30 requirements not related with Pharo and do not have time to fill the bug cycle. Hernán
On 2013-11-23, at 09:00, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
No time so fr to handle it.
Stef
Begin forwarded message:
From: "monty" <monty.os@engineer.com> Subject: Patches for Pharo packages you are maintaining Date: November 21, 2013 3:14:25 AM GMT+01:00 To: stephane.ducasse@inria.fr
Prof. Stef, I have produced updates to the XML-Parser, XML-Parser-Testing, and XML-Writer-Core packages you are maintaining.
These updates add validation against internal and external DTDs, proper replacement of general and parameter entites, customizable resolution of external parsed entities using Zinc and FileSystem, awareness of notations and unparsed entities, preservation of the internal DTD subset by the DOM parser (so printing a parsed doc with a DTD will produce approximately what was input), line numbers reporting in error messages, and better well-formed and validity constraints.
I had to largely rewrite the tokenizer to make everything work, but I followed the spec closely, and it is about the same speed as long as there is no DTD to validate against.
One problem is that while the tests I added and the existing tests all pass, for some reason helper messages in some test classes starting with "should" (in the style of should:raise:) are being interpreted as tests and run by TestRuner, even though they don't begin with "test" and take arguments! This is possibly a bug in TestRunner.
Another problem is that there are so many deprecated methods cluttering up classes, some of which have been deprecated for years! It is confusing and hard to see which methods to use just by browsing the protocols. I would really suggest using this code to get rid of the XML-Parser methods that have been deprecated for at least a year:
expiry := 1 year. (SystemNavigation default allClassesInPackageNamed: 'XML-Parser') do: [:class | class selectors do: [:selector | | compiledMethod timeStamp | compiledMethod := class compiledMethodAt: selector. timeStamp := compiledMethod timeStamp copyAfter: Character space. (compiledMethod isDeprecated and: [(DateAndTime now - (DateAndTime fromString: timeStamp)) > expiry]) ifTrue: [class removeSelector: selector]]].
I ran and checked it myself and it doesn't break anything. Running the above with XML-Writer-Core might not be a bad idea either.
I also updated BitmapCharacterSet to use less memory. <XML-Writer-Core-monty.5.mcz> <XML-Tests-Parser-monty.27.mcz> <XML-Parser-monty.173.mcz> <Collections-BitmapCharacterSet-Anonymous.6.mcz> <Collections-BitmapCharacterSet-Anonymous.6.mcz>
participants (13)
-
btc＠openinworld.com -
Camillo Bruni -
Esteban Lorenzano -
Frank Shearar -
Hernán Morales Durand -
Hilaire Fernandes -
kilon alios -
Lorenz Köhl -
Marcus Denker -
phil＠highoctane.be -
Sean P. DeNigris -
Stéphane Ducasse -
Torsten Bergmann