- Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN] SmalltalkHub Deprecation Notice

by Renaud de Villemeur

Hi Guille. It's a good news to see the community is moving forward. What would be the impact on Pharo catalog ? The instruction still advise to upload information to smalltalkhub: http://catalog.pharo.org/catalog/note-for-developers?_s=bHk4XDBcH9mb0muM&_k… Will it be deprecated as well ? Thanks Renaud Apr. 3, 2020, 05:55 by guillermopolito(a)gmail.com: > SmalltalkHub Deprecation Notice > SmalltalkHub is now getting old and it is time to deprecate it. We plan to replace it by a static file server during 2020. The public data will still be readable and consumable from monticello clients, but modifications will not be allowed in the near future. SmalltalkHub users should move their projects to git repositories or other monticello repository services. > What is changing? > If you currently host a project in SmalltalkHub, you should migrate your projects to another platform as soon as possible. If you depend on a project hosted on SmalltalkHub, you should contact the owner of that project to schedule a migration. > If you have documentation or tutorials using SmalltalkHub, we recommend to update those after a migration. > An archive of all public projects in SmalltalkHub will be made available in read-only mode. This archive will be readable through monticello clients for compatibility reasons. > Private projects, due to privacy reasons, will not be published in the public archive and will be removed to protect their owners. > Why are RMoD and Inria making this change? > SmalltalkHub has finished its cycle. The arrival of git integration in the past years caused the move of most users in the Pharo community to git hosting services. They now use exclusively other platforms. Furthermore, RMoD and Inria lack the manpower to properly maintain the SmalltalkHub service and keep it up to date. Smalltalkhub has no added value compared to other code source hosting platforms. > How much time do I have to adapt to this change? > > The SmalltalkHub deprecation will follow the next timetable: > Monday 04 of may 2020: SmalltalkHub will be read-only. Creation of new users and projects will be forbidden. New commits will be rejected. All existing users, projects (public and private) and their commits will remain available and visible, but their settings will become read-only. > Monday 02 of november 2020: SmalltalkHub will be migrated to a static file server archive. Private projects and their commits will not be available anymore. > > The RMoD team and Inria plan to keep the static file server alive for, at least, 5 years from the date of its creation. > What will happen if I do nothing? > Your public projects will become read-only and you will not be able to commit anymore. > Your private projects will become unavailable.> What alternatives do I have? > > Those wanting to keep using monticello can migrate their projects to other monticello hostings such as > http://squeaksource.com <http://squeaksource.com/>> or> http://ss3.gemstone.com > > Those wanting to migrate to git, Peter Uhnakâs git migration tool (> https://github.com/peteruhnak/git-migration> ) automates monticello to git migration in tonel format. > > Cheers, > Guille on behalf of the RMoD team >

April 3, 2020

Re: [Pharo-users] Latest PharoJS Success Story

by Noury Bouraqadi

Hi Shaping, > On 3 Apr 2020, at 06:09, Shaping <shaping(a)uurda.org> wrote: > > Hi Noury. > > Brain Treats got stuck during launch on my LG. > Which android version are you using ? > Is there a plan to move PharoJS to Wasm/WASI? > Dave and I talked about it a long time ago. This sounds like a good idea. Actually, Dave has a very ambition idea = turn PharoJS into Pharo* where * can be different targets. But, there's a lot to do before reaching this goal. So, don't expect it any time soon. Noury > > Shaping > > > -----Original Message----- > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of > N. Bouraqadi > Sent: Tuesday, 28 January, 2020 12:18 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] Latest PharoJS Success Story > > The latest PharoJS-powered smartphone app is now live. > Development has been made using Pharo. > Then, javascript code is generated using PharoJS. > Last, the app is built to target both iOS and Android thanks to Apache > Cordova. > > Learn more and Download at > https://nootrix.com/projects/brain-treats-app/ > > Noury > >

April 3, 2020

[ANN] SmalltalkHub Deprecation Notice

by Guillermo Polito

SmalltalkHub Deprecation Notice SmalltalkHub is now getting old and it is time to deprecate it. We plan to replace it by a static file server during 2020. The public data will still be readable and consumable from monticello clients, but modifications will not be allowed in the near future. SmalltalkHub users should move their projects to git repositories or other monticello repository services. What is changing? If you currently host a project in SmalltalkHub, you should migrate your projects to another platform as soon as possible. If you depend on a project hosted on SmalltalkHub, you should contact the owner of that project to schedule a migration. If you have documentation or tutorials using SmalltalkHub, we recommend to update those after a migration. An archive of all public projects in SmalltalkHub will be made available in read-only mode. This archive will be readable through monticello clients for compatibility reasons. Private projects, due to privacy reasons, will not be published in the public archive and will be removed to protect their owners. Why are RMoD and Inria making this change? SmalltalkHub has finished its cycle. The arrival of git integration in the past years caused the move of most users in the Pharo community to git hosting services. They now use exclusively other platforms. Furthermore, RMoD and Inria lack the manpower to properly maintain the SmalltalkHub service and keep it up to date. Smalltalkhub has no added value compared to other code source hosting platforms. How much time do I have to adapt to this change? The SmalltalkHub deprecation will follow the next timetable: Monday 04 of may 2020: SmalltalkHub will be read-only. Creation of new users and projects will be forbidden. New commits will be rejected. All existing users, projects (public and private) and their commits will remain available and visible, but their settings will become read-only. Monday 02 of november 2020: SmalltalkHub will be migrated to a static file server archive. Private projects and their commits will not be available anymore. The RMoD team and Inria plan to keep the static file server alive for, at least, 5 years from the date of its creation. What will happen if I do nothing? Your public projects will become read-only and you will not be able to commit anymore. Your private projects will become unavailable. What alternatives do I have? Those wanting to keep using monticello can migrate their projects to other monticello hostings such as http://squeaksource.com <http://squeaksource.com/> or http://ss3.gemstone.com <http://ss3.gemstone.com/> Those wanting to migrate to git, Peter Uhnakâs git migration tool (https://github.com/peteruhnak/git-migration <https://github.com/peteruhnak/git-migration>) automates monticello to git migration in tonel format. Cheers, Guille on behalf of the RMoD team

April 3, 2020

Re: [Pharo-users] Need help badly

by Ben Coman

Hi, You don't mention that the standard de-register process failed. Can you try this first? See the last button on this page... https://lists.pharo.org/mailman/listinfo/pharo-users_lists.pharo.org cheers -ben On Thu, 2 Apr 2020 at 12:47, Md Shahidul Hoque <shawon58(a)gmail.com> wrote: > Dear admin team > Can u please remove my email (shawon58(a)gmail.com) from user list. I got a > lot of email from other discussion. I don't want to get those. please help > me. > Thanks >

April 3, 2020

Re: [Pharo-users] Latest PharoJS Success Story

by Shaping

Hi Noury. Brain Treats got stuck during launch on my LG. Is there a plan to move PharoJS to Wasm/WASI? Shaping -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of N. Bouraqadi Sent: Tuesday, 28 January, 2020 12:18 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Latest PharoJS Success Story The latest PharoJS-powered smartphone app is now live. Development has been made using Pharo. Then, javascript code is generated using PharoJS. Last, the app is built to target both iOS and Android thanks to Apache Cordova. Learn more and Download at https://nootrix.com/projects/brain-treats-app/ Noury

April 3, 2020

Re: [Pharo-users] How should XMLHTMLParser handle strange HTML?

by PBKResearch

Hi Esteban Thanks for the suggestion. I have skimmed through the description of tidy. I think the things it puts right (mis-matched tags etc.) are exactly the things that XMLHTMLParser looks for and fixes. For example, in my distorted parses, the final </body> and </html> tags had been absorbed into the massive string node that contains most of the input text; the parser detected this and inserted them at the right point to close the parse correctly. Since my workaround, of editing out the specific features that cause the parse to go wrong, seems to fix the problem, I shall probably continue with it. Thanks for your help Peter Kenny -----Original Message----- From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Esteban Maringolo Sent: 02 April 2020 19:53 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] How should XMLHTMLParser handle strange HTML? Hi Peter, Just in case it helps you parsing the files... I had to parse HTML with a XMLParser (no XMLHTMLParser) so what I did was to pass it first through html tidy [1] converting it to xhtml which is compatible with XML parsers (it is XML, after all). Regards, [1] http://www.html-tidy.org/ Esteban A. Maringolo On Thu, Apr 2, 2020 at 2:17 PM PBKResearch <peter(a)pbkresearch.co.uk> wrote: > > Hello > > > > I have come across a strange problem in using XMLHTMLParser to parse some HTML files which use strange constructions. The input files have been generated by using MS Outlook to translate incoming messages, stored in .msg files, into HTML. The translated files display normally in Firefox, and the XMLHTMLParser appears to generate a normal parse, but examination of the parse output shows that the structure is distorted, and about half the input text has been put into one string node. > > > > Hunting around, I am convinced that the trouble lies in the presence in the HTML source of pairs of comment-like tags, with this form: > > <![if !supportLists]> > > <![endif]> > > since the distorted parse starts at the first occurrence of one of these tags. > > > > I donât know whether these are meant to be a structure in some programming language â there is no reference to supportLists anywhere in the source code. When it is displayed in Firefox, use of the âInspect Elementâ option shows that the browser has treated them as comments, displaying them with the necessary dashes as e.g. . I edited the source code by inserting the dashes, and XMLHTMLParser parsed everything correctly. > > > > I have a workaround, therefore; either edit in the dashes to make them into legitimate comments, or equivalently edit out these tags completely. The only question of general interest is whether XMLHTMLParser should be expected to handle these in some other way, rather than produce a distorted parse without comment. The Firefox approach, turning them into comments, seems sensible. It would also be interesting if anyone has any idea what is going on in the source code. > > > > Thanks for any help > > > > Peter Kenny

April 2, 2020

Re: [Pharo-users] How should XMLHTMLParser handle strange HTML?

by Esteban Maringolo

Hi Peter, Just in case it helps you parsing the files... I had to parse HTML with a XMLParser (no XMLHTMLParser) so what I did was to pass it first through html tidy [1] converting it to xhtml which is compatible with XML parsers (it is XML, after all). Regards, [1] http://www.html-tidy.org/ Esteban A. Maringolo On Thu, Apr 2, 2020 at 2:17 PM PBKResearch <peter(a)pbkresearch.co.uk> wrote: > > Hello > > > > I have come across a strange problem in using XMLHTMLParser to parse some HTML files which use strange constructions. The input files have been generated by using MS Outlook to translate incoming messages, stored in .msg files, into HTML. The translated files display normally in Firefox, and the XMLHTMLParser appears to generate a normal parse, but examination of the parse output shows that the structure is distorted, and about half the input text has been put into one string node. > > > > Hunting around, I am convinced that the trouble lies in the presence in the HTML source of pairs of comment-like tags, with this form: > > <![if !supportLists]> > > <![endif]> > > since the distorted parse starts at the first occurrence of one of these tags. > > > > I donât know whether these are meant to be a structure in some programming language â there is no reference to supportLists anywhere in the source code. When it is displayed in Firefox, use of the âInspect Elementâ option shows that the browser has treated them as comments, displaying them with the necessary dashes as e.g. . I edited the source code by inserting the dashes, and XMLHTMLParser parsed everything correctly. > > > > I have a workaround, therefore; either edit in the dashes to make them into legitimate comments, or equivalently edit out these tags completely. The only question of general interest is whether XMLHTMLParser should be expected to handle these in some other way, rather than produce a distorted parse without comment. The Firefox approach, turning them into comments, seems sensible. It would also be interesting if anyone has any idea what is going on in the source code. > > > > Thanks for any help > > > > Peter Kenny

April 2, 2020

How should XMLHTMLParser handle strange HTML?

by PBKResearch

Hello I have come across a strange problem in using XMLHTMLParser to parse some HTML files which use strange constructions. The input files have been generated by using MS Outlook to translate incoming messages, stored in .msg files, into HTML. The translated files display normally in Firefox, and the XMLHTMLParser appears to generate a normal parse, but examination of the parse output shows that the structure is distorted, and about half the input text has been put into one string node. Hunting around, I am convinced that the trouble lies in the presence in the HTML source of pairs of comment-like tags, with this form: <![if !supportLists]> <![endif]> since the distorted parse starts at the first occurrence of one of these tags. I don't know whether these are meant to be a structure in some programming language - there is no reference to supportLists anywhere in the source code. When it is displayed in Firefox, use of the 'Inspect Element' option shows that the browser has treated them as comments, displaying them with the necessary dashes as e.g. . I edited the source code by inserting the dashes, and XMLHTMLParser parsed everything correctly. I have a workaround, therefore; either edit in the dashes to make them into legitimate comments, or equivalently edit out these tags completely. The only question of general interest is whether XMLHTMLParser should be expected to handle these in some other way, rather than produce a distorted parse without comment. The Firefox approach, turning them into comments, seems sensible. It would also be interesting if anyone has any idea what is going on in the source code. Thanks for any help Peter Kenny

April 2, 2020

[ANN] Do you like the idea of Camp Smalltalk Supreme and do you support it?

by Richard Kenneth Eng

https://smalltalkrenaissance.wordpress.com/2020/04/02/do-you-like-the-idea-…

April 2, 2020

Re: [Pharo-users] Need help badly

by Russ Whaley

I think you can simply check the 'digest' box on the enrollment screen? This way, you would get 1 email instead of dozens. I set this back and forth depending on whether I have an open discussion. Hope it helps! On Thu, Apr 2, 2020 at 12:47 AM Md Shahidul Hoque <shawon58(a)gmail.com> wrote: > Dear admin team > Can u please remove my email (shawon58(a)gmail.com) from user list. I got a > lot of email from other discussion. I don't want to get those. please help > me. > Thanks > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_5805108441441545112_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > -- Russ Whaley whaley.russ(a)gmail.com

April 2, 2020