- Pharo-dev - lists.pharo.org

new configuration of XMLParser

by StÃ©phane Ducasse

Hi guys I created a new configuration based on the work on monty for the XMLParser. Please test and let us know. In PharoExtras/XMLParser and available via the configurationBrowser. I merged its package and updated the configuration as well as added catalog meta data. Now it would be great if somebody would join maintaining this package. Thanks Monty Stef Name: ConfigurationOfXMLParser-StephaneDucasse.15 Author: StephaneDucasse Time: 24 November 2013, 6:44:05.130114 pm UUID: 4577e694-47fd-44b5-a301-78bf3a174987 Ancestors: ConfigurationOfXMLParser-DamienCassou.14 Enhancements made by Monty. 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. 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]]].

Nov. 24, 2013

New configuration for XMLWriter!

by StÃ©phane Ducasse

Hi guys I created a new configuration based on the work on monty for the XMLWriter. Please test and let us know. In PharoExtras/XMLWriter and available via the configurationBrowser. Thanks Monty Stef Working on the new configurationOfXMLParserâ¦.

Nov. 24, 2013

Re: [Pharo-dev] SLICE-Issue-12179-Nautilus-Add-package-filter-input-box

by StÃ©phane Ducasse

> Thank you StÃ©phane! :-) you are welcome :) Stef

Nov. 24, 2013

Re: [Pharo-dev] Graphic System Arquitecture Question

by StÃ©phane Ducasse

> It would be great to have this issue debated and fixed. I have the impression that using the Cairo backend suffers from the same problem. Money and time. This is not a question of debating this is about doing and having more people helping the core so that we can do something important. Stef

Nov. 24, 2013

Metacello Catalog job does not work anymore :(

by StÃ©phane Ducasse

Hi guys https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/ is red and I did not change anything. Now when we copy artefact does it mean that they are copied or used by references? Then can we get the latest green job keeping its generation? Because now - no catalog - no idea why it breaks This is fun that everybody complains about description of packages and nobody cares except me to add meta data to the packages. well I have an idea but no idea how to fix it. Stef

Nov. 24, 2013

Re: [Pharo-dev] Nautilus no longer guards against changed methods

by Stephan Eggermont

Sean wrote: >Stephan Eggermont wrote >We need to revert to the modal behavior >In general in UIs, he best approach is to do what the user requests without hesitation, and make everything undoable. But obviously modal is better than losing changesâ¦ It is not that I donât find the old behavior annoying... A better solution than the modal one should - make it unattractive to have lots of open edits - make it easy to find all open edits - make it easy to compare open edits to the same method - make it impossible to lose edits accidentally and preferably - show which edits are compilable - show what is probably just a typo (some random character inserted somewhere in a method) Stephan

Nov. 24, 2013

Re: [Pharo-dev] SLICE-Issue-12179-Nautilus-Add-package-filter-input-box

by Juraj Kubelka

Thank you StÃ©phane! :-) Jura El 24-11-2013, a las 13:56, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> escribiÃ³: > I will have a look at it :) > I want that too. > > Stef > > On Nov 24, 2013, at 3:16 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> Hi! >> >> I think the following should be part of Pharo: >> SLICE-Issue-12179-Nautilus-Add-package-filter-input-box-JurajKubelka.1 >> >> I have been using for some times already and it works pretty well. I have also reviewed the code. >> This slice makes me much much more productive. >> >> Cheers, >> Alexandre >> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >

Nov. 24, 2013

Re: [Pharo-dev] Graphic System Arquitecture Question

by Alexandre Bergel

It would be great to have this issue debated and fixed. I have the impression that using the Cairo backend suffers from the same problem. Alexandre > Le 22-11-2013 Ã 14:57, Ronie Salgado <roniesalg(a)gmail.com> a Ã©crit : > > Hello, > > I want to know about the Pharo graphic system architecture, I whould like to know if there's some documentation explaining his inner works. > > For NBOpenGL and Roassal 3D in particular, I'm having some flickering, which I think is related to the way that the OpenGL framebuffer is transferred into a pharo window. > > In NBOpenGL, rendering is done in a offscreen FBO, whose content is transferred into main memory y blitted into a pharo window. The pharo window of course must be blitted or renderer into the screen, which means anothere transfer into the GPU. In other words, we are a GPU->CPU->GPU memory roundtrip. > > The consequences of this are the lost of performance, the lost of double-buffering and which is more important, the lost v-sync. The lack of v-sync is seen in the way of tearing, which is more appreciated when moving on the X-axis in a 3d view, such as in the Roassal3D example in R3Example>>city. > > I have heard that in pharo 3, all of the graphics are being moving into Athens, a new graphics, for which I donr't know where's the documentation. I believe that athens is a vector graphics API, which several backends as cairo, which also has an opengl backend. I would like to share that OpenGL context to avoid that round-trip if possible, or use a native window for the OpenGL stuff, but to that I need to know how pharo graphics are done. > > Greetings, > Ronie Salgado

Nov. 24, 2013

Re: [Pharo-dev] SLICE-Issue-12179-Nautilus-Add-package-filter-input-box

by StÃ©phane Ducasse

I will have a look at it :) I want that too. Stef On Nov 24, 2013, at 3:16 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > I think the following should be part of Pharo: > SLICE-Issue-12179-Nautilus-Add-package-filter-input-box-JurajKubelka.1 > > I have been using for some times already and it works pretty well. I have also reviewed the code. > This slice makes me much much more productive. > > Cheers, > Alexandre > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >

Nov. 24, 2013

Re: [Pharo-dev] Nautilus no longer guards against changed methods

by Sean P. DeNigris

Stephan Eggermont wrote > We need to revert to the modal behavior In general in UIs, he best approach is to do what the user requests without hesitation, and make everything undoable. But obviously modal is better than losing changes... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Nautilus-no-longer-guards-against-changed-methods-tp4… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 24, 2013