Re: [Pharo-dev] PetitMarkdown
Thank you Jan, for your work in enhancing PetitParser for Markdown. I think I got what you did by loading PetitParser in Pharo 4.0. I found the examples PPMarkdownGrammarTest, category testing-documents. I also read http://scg.unibe.ch/research/indentParsing. Could you please elaborate a bit more about the changes you did to the grammar and give some more usage examples? Regards Hannes On 4/14/15, Jan Kurš k...@iam.unibe.ch wrote: Hey, I also created an indentation sensitive extension of PetitParser, I also included some examples including Markdown. If you load PetitParser, you get the Markdown example as well. There is a short introduction to the indentation: http://scg.unibe.ch/research/indentParsing Cheers Jan On Apr 13, 2015 5:24 PM, H. Hirzel hannes.hir...@gmail.com wrote: Are there any news on this? --Hannes On 12/28/14, Norbert Hartl norb...@hartl.name wrote: I found markdown parsers in smalltalkhub and in the configuration browser. http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ and the one in the configuration browser PPMarkdown If I understand it correctly both are rooted into work Camillo did. The one in PharoExtras looks newer to me. So I assume the best would be to copy the ConfigurationOfPetitMarkdown from PharoExtras to MetacelloRepo and remove the ConfigurationOfPPMarkdown. Right? Or are there any objections? Norbert
Re: [Pharo-dev] PetitMarkdown
Hi Hannes, I actually did not do any changes to the grammar, I wrote the grammar from scratch. The reason I did so was to have a proof of concept of my PetitParser extension for parsing indentation-sensitive grammars such as Markdown or Python. The most simplest example you can do is to evaluate following: PPMiniCommonMark new parse: ' # Heading - list item - second list item ' As a result, you will get HTML fragment, that corresponds to one heading and list of items. All the supported CommonMark syntax is covered in the tests, so what you don't see in the test, has to be implemented. CommonMark is kind of beast to parse, I had to do one big extension to parse it. It is to introduce the indentation stack (as described in http://scg.unibe.ch/research/indentParsing). You can see the indentation stack manipulation in PPMiniCommonMark rules such as: #prefix, #quoteBegin, #quoteEnd, #itemBullet and #itemEnd. Cheers, Jan On 3 May 2015 at 08:46, H. Hirzel hannes.hir...@gmail.com wrote: Thank you Jan, for your work in enhancing PetitParser for Markdown. I think I got what you did by loading PetitParser in Pharo 4.0. I found the examples PPMarkdownGrammarTest, category testing-documents. I also read http://scg.unibe.ch/research/indentParsing. Could you please elaborate a bit more about the changes you did to the grammar and give some more usage examples? Regards Hannes On 4/14/15, Jan Kurš k...@iam.unibe.ch wrote: Hey, I also created an indentation sensitive extension of PetitParser, I also included some examples including Markdown. If you load PetitParser, you get the Markdown example as well. There is a short introduction to the indentation: http://scg.unibe.ch/research/indentParsing Cheers Jan On Apr 13, 2015 5:24 PM, H. Hirzel hannes.hir...@gmail.com wrote: Are there any news on this? --Hannes On 12/28/14, Norbert Hartl norb...@hartl.name wrote: I found markdown parsers in smalltalkhub and in the configuration browser. http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ and the one in the configuration browser PPMarkdown If I understand it correctly both are rooted into work Camillo did. The one in PharoExtras looks newer to me. So I assume the best would be to copy the ConfigurationOfPetitMarkdown from PharoExtras to MetacelloRepo and remove the ConfigurationOfPPMarkdown. Right? Or are there any objections? Norbert
[Pharo-dev] [pharo-project/pharo-core] d31f21: 50028
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: d31f210a4de628dd26f5a20200ea1a332bb988d6 https://github.com/pharo-project/pharo-core/commit/d31f210a4de628dd26f5a20200ea1a332bb988d6 Author: Jenkins Build Server bo...@pharo-project.org Date: 2015-05-03 (Sun, 03 May 2015) Changed paths: M Collections-Abstract.package/SequenceableCollection.class/instance/private/combinationsAt_in_after_do_.st A GroupManager.package/DynamicGroup.class/instance/accessing/merge_.st R GroupManager.package/DynamicGroup.class/instance/accessing/or_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/accessing/groupsAreVisible.st M Network-Kernel.package/Socket.class/instance/initialization/initialize_.st M Network-Kernel.package/Socket.class/instance/initialize-destroy/acceptFrom_.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/accessing colors/backgroundColor.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script636.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script637.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50027.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50028.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-Base.package/AbstractTool.class/instance/group/mergeGroups_.st Log Message: --- 50028 15466 combinationsAt: jj in: aCollection after: nn do: aBlock bogus comment https://pharo.fogbugz.com/f/cases/15466 15464 Merging groups raised an DNU https://pharo.fogbugz.com/f/cases/15464 5465 Prevent accidental semaphore leaks when using Socket acceptFrom https://pharo.fogbugz.com/f/cases/5465 15467 better background color for Dark Theme https://pharo.fogbugz.com/f/cases/15467 http://files.pharo.org/image/50/50028.zip
[Pharo-dev] [pharo-project/pharo-core]
Branch: refs/tags/50028 Home: https://github.com/pharo-project/pharo-core
[Pharo-dev] New Versionner Tool and Authentication
It seems maybe the commit Xyz patch tool is creating new instances of repositories instead of using the existing ones? Even though I am logged into sthub/Pharo/TxText, when I try to commit a config and new package versions for packages, dialogs pop up to enter my username and password, and even if I fill them out the credentials don't seem to be accepted. After cancelling, I can copy them over from my cache in the MC browser, so I'm definitely logged in. Any ideas? - Cheers, Sean -- View this message in context: http://forum.world.st/New-Versionner-Tool-and-Authentication-tp4824032.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Improving the About Text of Versionner
Ok, I added the case, submited the Slice and Resolved the case. https://pharo.fogbugz.com/f/cases/15480/Improving-the-About-information-of-Versionner The final text is this: *Versionner is tool for creating configurations.* *A Configuration determines the dependencies between packages. More precisely, the dependency between a version of a package and a particular version of a required package.* *This tool is a GUI for Metacello that allows you to use a nice (but limited) tool instead of writing configurations by hand.* *Metacello is a package management system that declares dependencies between those packages in configuration classes.* *Monticello is our SCM system that groups code into packages.* *For a tutorial video on how to use Versionner:* * https://youtu.be/cFRJDuWL-Q0 https://youtu.be/cFRJDuWL-Q0* I hope I didn't make any mistakes. Cheers.
Re: [Pharo-dev] Improving the About Text of Versionner
Re: [Pharo-dev] Where to start contributing
Marcus opened a discussion last time and the result is that he'll maybe close all the bugs and ask to people to reopen only the one we really want. http://forum.world.st/Issue-tracker-what-about-old-issues-td4822552.html On 4 May 2015 at 02:27, Sergio Fedi sergio.f...@gmail.com wrote: @Cyril I tried to do what you suggested, but the amount of cases to resolve is huge, I'm quite lost on where to begin, and most of them I don't understand how to solve them @Ben How do I do that reviewing you suggest? Which ones do you suggest I should begin reviewing? If anyone else have more comments or suggestions on where and how I can contribute, please chime in. -- Cheers Cyril Ferlicot
Re: [Pharo-dev] TxText: More Cleaning and Questions
Sean P. DeNigris wrote a bit of cleaning... Issue 15475: TxText Cleanup for Pharo 5.0 #2 Finally passed validation! Okay to include? - Cheers, Sean -- View this message in context: http://forum.world.st/TxText-More-Cleaning-and-Questions-tp4823894p4824054.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] New Versionner Tool and Authentication
EstebanLM wrote I’m sorry for the mess. Don't be! This is a great feature. I'm happy to test it :) - Cheers, Sean -- View this message in context: http://forum.world.st/New-Versionner-Tool-and-Authentication-tp4824032p4824051.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] build pharo vm on windows (old mingw package)
[image: Inline image 1] Pharo.exe - 5 363 606 bytes Phil On Sun, May 3, 2015 at 1:17 PM, Nicolai Hess nicolaih...@web.de wrote: 2015-05-01 23:05 GMT+02:00 p...@highoctane.be p...@highoctane.be: Did you tried this ? https://github.com/pharo-project/pharo-vm/blob/master/README-Win32.md (I wrote that thing a while ago). http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/ was where I got the env from. I've got a PharoVM built with gcc 4.8.1 Can you check that this vm does not depend on the mingw runtime. (I managed to create a vm that opens, but if I start this without the mingw installation directory in my path, I get the following error: libgcc_s_dw2-1.dll is missing ) The vm from the build server works even without a local mingw installation. Uploading the thing in dropbox. Will send a link when done. Phil On Fri, May 1, 2015 at 9:04 PM, Nicolai Hess nicolaih...@web.de wrote: 2015-04-30 11:33 GMT+02:00 Esteban Lorenzano esteba...@gmail.com: aren’t you able to install an older version of gcc in your newer version of mingw? hm, downgrading the compiler was suprisingly easy. But I have still the same error. This is the gcc version information: Using built-in specs. COLLECT_GCC=c:\MinGW\bin\gcc.exe COLLECT_LTO_WRAPPER=c:/mingw/bin/../libexec/gcc/mingw32/4.6.2/lto-wrapper.exe Target: mingw32 Configured with: ../gcc-4.6.2/configure --enable-languages=c,c++,ada,fortran,objc,obj-c++ --disable-sjlj-exceptions --with-dwarf2 --enable-shared --enable-libgomp --disable-win32-registry --enable-libstdcxx-debug --enable-version-specific-runtime-libs --build=mingw32 --prefix=/mingw Thread model: win32 gcc version 4.6.2 (GCC) Anyone knows what could be the problem ? Stacktrace from the crash, this happens directly after the start: #0 0x772359dd in ntdll!RtlpNtMakeTemporaryKey () from C:\Windows\system32\ntdll.dll #1 0x77201d8f in ntdll!EtwSetMark () from C:\Windows\system32\ntdll.dll #2 0x77236a37 in ntdll!RtlpNtMakeTemporaryKey () from C:\Windows\system32\ntdll.dll #3 0x771fa3ef in ntdll!EtwSetMark () from C:\Windows\system32\ntdll.dll #4 0x771c6766 in wcsnicmp () from C:\Windows\system32\ntdll.dll #5 0x76cdc484 in KERNEL32!HeapFree () from C:\Windows\system32\kernel32.dll #6 0x6c24c4d7 in free () from C:\Windows\system32\crtdll.dll #7 0x0085 in ?? () #8 0x00542065 in glob_match () #9 0x00542604 in __mingw_glob () #10 0x00540f17 in _setargv () #11 0x004011ca in __mingw_CRTStartup () #12 0x004012d5 in WinMainCRTStartup () nicolai I do not have time right now to update the build into a new compiler, sorry (also, that is not always trivial/desired, he) Esteban On 30 Apr 2015, at 08:38, Nicolai Hess nicolaih...@web.de wrote: I managed to trash my mingw build environment - uninstalled /removed mingw/mingsys - reinstall from current mingw-installer - bad idea I can build a pharo windows vm but it immediately crashes on startup. I suspect some changes between gcc 4.6 (old environment) gcc 4.8 (new environment). (I think there are some changes related to file globbing (I managed to get the vm somehow working to not crash on startup but on shutdown instead - with _CRT_glob = 0. And gcc-4.8 uses dfferent (dwarf vs. sjlj ) exception handling, don't know if this is related). I tried to find a ming-installer for the old version but could not find anything and I tried to manually setup a ming installation from the old packages (dozen of packages for mingw / core-utils / bintutils /msys from different places (no fun)). 1) did anyone get a windows vm from mingws current version (with gcc 4.8) working? 2) can someone package/zip and upload an old mingw installation (maybe that one that is used on the build server? regards nicolai
[Pharo-dev] Beyond resolving a case
How do we state and/or document that further work is needed after a Case? For example, some things I had in mind after finishing this case: *While adding the About comment for the Versionner tool I've found that the About should be modeled (at least to encapsulate the about text and the about window title, but maybe also for other information such as the purpose of the tool, the author, external link, further reading, etc).* *Should we generate a test for this About behaviour ?* *Should we move the About functionality up in the hierarchy and integrate it more with the classes used to make Tools?* *I added a method that answers the tool name (as opposed to the tool class name, usually used in the About title)* *and I found out there was another implementor on another Tool, but which I didn't understand the relationship with the Versionner.* *Is there something that could be done? Maybe make an abstract method?* *Is there a place where to put all these comments and questions/comments/ramblings?* *If there is, where?*
Re: [Pharo-dev] Where to start contributing
I saw that discussion, but I didn't know how I could (if I could) contribute to that problem.
Re: [Pharo-dev] Improving the About Text of Versionner
There is ConfigurationOfVersionner in the image... - Cheers, Sean -- View this message in context: http://forum.world.st/Improving-the-About-Text-of-Versionner-tp4823759p4824122.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Improving the About Text of Versionner
There is ConfigurationOfVersionner in the image... Sorry, I don't understand. What does it mean? Is there something wrong I did?
[Pharo-dev] TxSpan#isAtEnd
Right now, there is: TxBasicSpan#isAtEnd ^ false and TxEndSpan#isAtEnd ^ true However, there are cases were a list of spans has no end marker e.g. the argument to #insert: I'm thinking of changing to: TxBasicSpan#isAtEnd ^ self next == self. This will allow changing e.g. the following slightly opaque loop condition: [ span next == span ] whileFalse: [ span := span next ]. to: [ span isAtEnd ] whileFalse: [ span := span next ]. All tests pass with this change, but I'm still very much beginning learning Tx, so I wanted to run it by everyone to see if I'm missing something... - Cheers, Sean -- View this message in context: http://forum.world.st/TxSpan-isAtEnd-tp4824134.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Improving the About Text of Versionner
Sergio Fedi wrote There is ConfigurationOfVersionner in the image... What does it mean? Is there something wrong I did? It was in response to Ben's question: is Versioneer Slice based or Configuration based?. We have two kinds of external projects in Pharo: - Traditional model: projects that, while technically external, have been adopted (cough... forked) by Pharo core so that we were free to evolve. This seemed to be the only way before we had really good tools because trying to keep everything in sync required massive effort. These can be considered core packages and are committed via the slice process. The projects are sometimes synced with the main project at irregular intervals. - Shiny new model: we have been starting to experiment with keeping projects (e.g. Rubric, TxText) in their own repos and loading improvements via Metacello configurations. While historically this was impractical, now fogbugz issues can specify configurations and their versions to be picked up by CI, and Esteban has just made a tool [1] to create those versions easily (i.e. almost automatically). Writing this, it seems a bit complicated, but actually it seems we are moving toward a very streamlined place. It's just that this moment is the transition. [1] http://forum.world.st/ANN-Screencast-on-Versionner-Part-2-td4823221.html - Cheers, Sean -- View this message in context: http://forum.world.st/Improving-the-About-Text-of-Versionner-tp4823759p4824127.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Improving the About Text of Versionner
Sean P. DeNigris wrote We have two kinds of external projects in Pharo: After reviewing your fix, your case is especially complicated - you have edited one of each type of project! Spec, which has been forked, and Versionner, which is externally maintained. You may have to open another issue for the Spec changes. In fact, I think we should have a discussion because you extended the extremely ugly SystemWindow logic (not blaming you, you didn't create it!) into Spec: (self model respondsTo: #aboutTitle) ifTrue: [^self model aboutTitle]. ^(self model respondsTo: #toolName) ifTrue: [self model toolName] ifFalse: [self model class name]. The Versionner about text proposal is more straightforward. I copied your package into the PharoExtras/Versionner repo (I actually made some edits to the text as I think that Metacello and Monticello should be described elsewhere in their own context). The next step would be to create a configuration to pick up these changes, but I guess the Spec question would have to be resolved first... Please don't be discouraged! By chance, you stepped into the absolute the worst-case scenario. Thankfully, many issues are much easier to integrate :) - Cheers, Sean -- View this message in context: http://forum.world.st/Improving-the-About-Text-of-Versionner-tp4823759p4824130.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] could the log message be placed on top of the files in the commit?
I think it is not possible (that’s github stuff, not ours)… at least it was not possible 1.5yr ago when we did it with Camilo. but I will take another look, in case things changed. Esteban On 03 May 2015, at 04:41, Sean P. DeNigris s...@clipperadams.com wrote: stepharo wrote could we put the log of the commit on top before the touched files? +1. But Nicolas wants to know if he can view the files in his favorite editor, `#(vim emacs) atRandom`ha ha - Cheers, Sean -- View this message in context: http://forum.world.st/could-the-log-message-be-placed-on-top-of-the-files-in-the-commit-tp4823824p4823888.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Pharo Inbox Link pointing to Pharo40 Inbox still
I corrected it. On 3 May 2015 at 13:55, Sergio Fedi sergio.f...@gmail.com wrote: Ah, that's why I commited my changes to version 4 On Sun, May 3, 2015 at 6:26 AM, Norbert Hartl norb...@hartl.name wrote: On http://pharo.org/contribute-propose-fix in Prerequisites the Pharo Inbox link points to the pharo40inbox instead of pharo50inbox. Norbert -- Cheers Cyril Ferlicot
Re: [Pharo-dev] could the log message be placed on top of the files in the commit?
I tried with this, but didn't know how to push it further... https://github.com/github/github-services/compare/master...bencoman:master cheers -ben On Sun, May 3, 2015 at 4:15 AM, stepharo steph...@free.fr wrote: Hi could we put the log of the commit on top before the touched files? Stef
[Pharo-dev] Pharo Inbox Link pointing to Pharo40 Inbox still
On http://pharo.org/contribute-propose-fix http://pharo.org/contribute-propose-fix in Prerequisites the Pharo Inbox link points to the pharo40inbox instead of pharo50inbox. Norbert
Re: [Pharo-dev] build pharo vm on windows (old mingw package)
2015-05-01 23:05 GMT+02:00 p...@highoctane.be p...@highoctane.be: Did you tried this ? https://github.com/pharo-project/pharo-vm/blob/master/README-Win32.md (I wrote that thing a while ago). http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/ was where I got the env from. I've got a PharoVM built with gcc 4.8.1 Can you check that this vm does not depend on the mingw runtime. (I managed to create a vm that opens, but if I start this without the mingw installation directory in my path, I get the following error: libgcc_s_dw2-1.dll is missing ) The vm from the build server works even without a local mingw installation. Uploading the thing in dropbox. Will send a link when done. Phil On Fri, May 1, 2015 at 9:04 PM, Nicolai Hess nicolaih...@web.de wrote: 2015-04-30 11:33 GMT+02:00 Esteban Lorenzano esteba...@gmail.com: aren’t you able to install an older version of gcc in your newer version of mingw? hm, downgrading the compiler was suprisingly easy. But I have still the same error. This is the gcc version information: Using built-in specs. COLLECT_GCC=c:\MinGW\bin\gcc.exe COLLECT_LTO_WRAPPER=c:/mingw/bin/../libexec/gcc/mingw32/4.6.2/lto-wrapper.exe Target: mingw32 Configured with: ../gcc-4.6.2/configure --enable-languages=c,c++,ada,fortran,objc,obj-c++ --disable-sjlj-exceptions --with-dwarf2 --enable-shared --enable-libgomp --disable-win32-registry --enable-libstdcxx-debug --enable-version-specific-runtime-libs --build=mingw32 --prefix=/mingw Thread model: win32 gcc version 4.6.2 (GCC) Anyone knows what could be the problem ? Stacktrace from the crash, this happens directly after the start: #0 0x772359dd in ntdll!RtlpNtMakeTemporaryKey () from C:\Windows\system32\ntdll.dll #1 0x77201d8f in ntdll!EtwSetMark () from C:\Windows\system32\ntdll.dll #2 0x77236a37 in ntdll!RtlpNtMakeTemporaryKey () from C:\Windows\system32\ntdll.dll #3 0x771fa3ef in ntdll!EtwSetMark () from C:\Windows\system32\ntdll.dll #4 0x771c6766 in wcsnicmp () from C:\Windows\system32\ntdll.dll #5 0x76cdc484 in KERNEL32!HeapFree () from C:\Windows\system32\kernel32.dll #6 0x6c24c4d7 in free () from C:\Windows\system32\crtdll.dll #7 0x0085 in ?? () #8 0x00542065 in glob_match () #9 0x00542604 in __mingw_glob () #10 0x00540f17 in _setargv () #11 0x004011ca in __mingw_CRTStartup () #12 0x004012d5 in WinMainCRTStartup () nicolai I do not have time right now to update the build into a new compiler, sorry (also, that is not always trivial/desired, he) Esteban On 30 Apr 2015, at 08:38, Nicolai Hess nicolaih...@web.de wrote: I managed to trash my mingw build environment - uninstalled /removed mingw/mingsys - reinstall from current mingw-installer - bad idea I can build a pharo windows vm but it immediately crashes on startup. I suspect some changes between gcc 4.6 (old environment) gcc 4.8 (new environment). (I think there are some changes related to file globbing (I managed to get the vm somehow working to not crash on startup but on shutdown instead - with _CRT_glob = 0. And gcc-4.8 uses dfferent (dwarf vs. sjlj ) exception handling, don't know if this is related). I tried to find a ming-installer for the old version but could not find anything and I tried to manually setup a ming installation from the old packages (dozen of packages for mingw / core-utils / bintutils /msys from different places (no fun)). 1) did anyone get a windows vm from mingws current version (with gcc 4.8) working? 2) can someone package/zip and upload an old mingw installation (maybe that one that is used on the build server? regards nicolai
Re: [Pharo-dev] Pharo Inbox Link pointing to Pharo40 Inbox still
Ah, that's why I commited my changes to version 4 On Sun, May 3, 2015 at 6:26 AM, Norbert Hartl norb...@hartl.name wrote: On http://pharo.org/contribute-propose-fix in Prerequisites the Pharo Inbox link points to the pharo40inbox instead of pharo50inbox. Norbert
Re: [Pharo-dev] could the log message be placed on top of the files in the commit?
On 03 May 2015, at 12:12, Esteban Lorenzano esteba...@gmail.com wrote: I think it is not possible (that’s github stuff, not ours)… at least it was not possible 1.5yr ago when we did it with Camilo. but I will take another look, in case things changed. I think there is a chance to do it with this magical thing: https://zapier.com https://zapier.com/ It seems to have an email parser that is very powerful… so github would send there and then zappier could send a modified mail onwards (and swallow the branch one). Marcus Esteban On 03 May 2015, at 04:41, Sean P. DeNigris s...@clipperadams.com wrote: stepharo wrote could we put the log of the commit on top before the touched files? +1. But Nicolas wants to know if he can view the files in his favorite editor, `#(vim emacs) atRandom`ha ha - Cheers, Sean -- View this message in context: http://forum.world.st/could-the-log-message-be-placed-on-top-of-the-files-in-the-commit-tp4823824p4823888.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] PetitMarkdown
Hi Jan, Thank you for your answer, in particular the PPMiniCommonMark example. For me this is an interesting work, I can see a lot lot of application areas in and out of the Pharo context. I'll have a closer look at your implementation, in particular the test cases. Have a good day Hannes On 5/3/15, Jan Kurš k...@iam.unibe.ch wrote: Hi Hannes, I actually did not do any changes to the grammar, I wrote the grammar from scratch. The reason I did so was to have a proof of concept of my PetitParser extension for parsing indentation-sensitive grammars such as Markdown or Python. The most simplest example you can do is to evaluate following: PPMiniCommonMark new parse: ' # Heading - list item - second list item ' As a result, you will get HTML fragment, that corresponds to one heading and list of items. All the supported CommonMark syntax is covered in the tests, so what you don't see in the test, has to be implemented. CommonMark is kind of beast to parse, I had to do one big extension to parse it. It is to introduce the indentation stack (as described in http://scg.unibe.ch/research/indentParsing). You can see the indentation stack manipulation in PPMiniCommonMark rules such as: #prefix, #quoteBegin, #quoteEnd, #itemBullet and #itemEnd. Cheers, Jan On 3 May 2015 at 08:46, H. Hirzel hannes.hir...@gmail.com wrote: Thank you Jan, for your work in enhancing PetitParser for Markdown. I think I got what you did by loading PetitParser in Pharo 4.0. I found the examples PPMarkdownGrammarTest, category testing-documents. I also read http://scg.unibe.ch/research/indentParsing. Could you please elaborate a bit more about the changes you did to the grammar and give some more usage examples? Regards Hannes On 4/14/15, Jan Kurš k...@iam.unibe.ch wrote: Hey, I also created an indentation sensitive extension of PetitParser, I also included some examples including Markdown. If you load PetitParser, you get the Markdown example as well. There is a short introduction to the indentation: http://scg.unibe.ch/research/indentParsing Cheers Jan On Apr 13, 2015 5:24 PM, H. Hirzel hannes.hir...@gmail.com wrote: Are there any news on this? --Hannes On 12/28/14, Norbert Hartl norb...@hartl.name wrote: I found markdown parsers in smalltalkhub and in the configuration browser. http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ and the one in the configuration browser PPMarkdown If I understand it correctly both are rooted into work Camillo did. The one in PharoExtras looks newer to me. So I assume the best would be to copy the ConfigurationOfPetitMarkdown from PharoExtras to MetacelloRepo and remove the ConfigurationOfPPMarkdown. Right? Or are there any objections? Norbert
Re: [Pharo-dev] could the log message be placed on top of the files in the commit?
2015-05-03 4:41 GMT+02:00 Sean P. DeNigris s...@clipperadams.com: stepharo wrote could we put the log of the commit on top before the touched files? +1. But Nicolas wants to know if he can view the files in his favorite editor, `#(vim emacs) atRandom`ha ha :) Sure, I can even use ed, it's only with punch cards that I feel not that confortable - lack of practice I guess. Seriously, i never read this litany of file names, that's essentially un-informative and could be removed. Code diffs would be more valuable, but adopting the tools of file lovers must come with a cost ;) Nicolas - Cheers, Sean -- View this message in context: http://forum.world.st/could-the-log-message-be-placed-on-top-of-the-files-in-the-commit-tp4823824p4823888.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
[Pharo-dev] Help required for understanding a project on smalltalk hub
Hello All ! I have just started with Pharo and still grasping it features. I have come across a project on Smalltalk Hub http://smalltalkhub.com/#!/~BenjA/FullTextSearch ; a search application for Pharo. I wish to explore this project and enhance/improvise it further. It would be great if the author of this project, any of its contributors or simply a Pharo enthusiast would guide me on how to go about understanding the project. I am keen on broadening it further. Thanks Jigyasa
Re: [Pharo-dev] could the log message be placed on top of the files in the commit?
in fact it was also not possible discriminate the mails they sent (it was all or nothing)… that’s why we receive two mails each commit, one complete unnecessary. On 03 May 2015, at 12:12, Esteban Lorenzano esteba...@gmail.com wrote: I think it is not possible (that’s github stuff, not ours)… at least it was not possible 1.5yr ago when we did it with Camilo. but I will take another look, in case things changed. Esteban On 03 May 2015, at 04:41, Sean P. DeNigris s...@clipperadams.com wrote: stepharo wrote could we put the log of the commit on top before the touched files? +1. But Nicolas wants to know if he can view the files in his favorite editor, `#(vim emacs) atRandom`ha ha - Cheers, Sean -- View this message in context: http://forum.world.st/could-the-log-message-be-placed-on-top-of-the-files-in-the-commit-tp4823824p4823888.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Idea how I could generate the update list automatically
I think is easier to make a program to extract those commits using the github api: https://api.github.com/repos/pharo-project/pharo-core/commits https://api.github.com/repos/pharo-project/pharo-core/commits that can be parametrised to take specific commits… Esteban On 02 May 2015, at 22:23, stepharo steph...@free.fr wrote: Hi I would like to get an idea how I could generate these lists automatically: https://pharoweekly.wordpress.com/2015/05/02/pharo-50-started-fast/ - so having an identification of the start and end sequence in the mail would help (especially the end) - then I'm wondering how I could get the mails to parse them Any suggestion is welcome. Stef
Re: [Pharo-dev] could the log message be placed on top of the files in the commit?
On Sun, May 3, 2015 at 4:15 AM, stepharo steph...@free.fr wrote: Hi could we put the log of the commit on top before the touched files? Stef On Sun, May 3, 2015 at 10:46 PM, Ben Coman b...@openinworld.com wrote: I tried with this, but didn't know how to push it further... https://github.com/github/github-services/compare/master...bencoman:master cheers -ben Whoops. Seems I missed actually submitting a pull request for the change. Now lets see how it goes. cheers -ben
Re: [Pharo-dev] PluggableTextMorph vs PluggableTextEditorMorph
2015-05-02 9:50 GMT+02:00 stepharo steph...@free.fr: No idea but if the difference is that small then this is clear that we should remove one. What is the difference between (or different use cases for) PluggableTextMorph and PluggableTextEditorMorph ? Do we need both? The only difference I see: You can not toggle enabled/disabled a PluggableTextMorph, whereas a PluggableTextEditorMorph can be disabled. nicolai Now I see, they use different editorclasses too (TextEditor vs. SmalltalkEditor).
Re: [Pharo-dev] New Versionner Tool and Authentication
yes… is a bug who should be fixed if you install bleedingEdge… I’m sorry for the mess. Esteban On 03 May 2015, at 19:29, Sean P. DeNigris s...@clipperadams.com wrote: It seems maybe the commit Xyz patch tool is creating new instances of repositories instead of using the existing ones? Even though I am logged into sthub/Pharo/TxText, when I try to commit a config and new package versions for packages, dialogs pop up to enter my username and password, and even if I fill them out the credentials don't seem to be accepted. After cancelling, I can copy them over from my cache in the MC browser, so I'm definitely logged in. Any ideas? - Cheers, Sean -- View this message in context: http://forum.world.st/New-Versionner-Tool-and-Authentication-tp4824032.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] could the log message be placed on top of the files in the commit?
do you guys know that if you press in the link provided, for example: https://github.com/pharo-project/pharo-core/commit/cf09b156e5bc943d6b99a34016d64ac0e6e972b5 https://github.com/pharo-project/pharo-core/commit/cf09b156e5bc943d6b99a34016d64ac0e6e972b5 you will have all the diffs well organised and for free? Esteban ps: in fact, if possible, I wouldn’t publish even the list of files changed… just the commit message and the link On 03 May 2015, at 18:23, stepharo steph...@free.fr wrote: Code diffs would be more valuable, but adopting the tools of file lovers must come with a cost ;) Yes I would love that too. I just want to compile a list of changes automatically. May I can do in the scriptLoader instead of reparsing git.
[Pharo-dev] [pharo-project/pharo-core] cf09b1: 50029
Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: cf09b156e5bc943d6b99a34016d64ac0e6e972b5 https://github.com/pharo-project/pharo-core/commit/cf09b156e5bc943d6b99a34016d64ac0e6e972b5 Author: Jenkins Build Server bo...@pharo-project.org Date: 2015-05-03 (Sun, 03 May 2015) Changed paths: M Morphic-Widgets-Tabs.package/TabManager.class/instance/private-actions/deleteSelectedTabs.st M NativeBoost-Core.package/NBExternalAddressType.class/instance/emitting code/pushAsPointer_.st M NativeBoost-Core.package/NBExternalAddressType.class/instance/emitting code/pushAsValue_.st M NativeBoost-Core.package/NBExternalObjectType.class/instance/emitting code/pushAsPointer_.st M NativeBoost-Core.package/NBExternalObjectType.class/instance/emitting code/pushAsValue_.st M NativeBoost-Core.package/NBExternalStructureType.class/instance/emitting code/pushAsPointer_.st A NativeBoost-Core.package/NBExternalType.class/instance/emitting code/coerceNilToNull_oop_doneLabel_.st M NativeBoost-Core.package/NBExternalType.class/instance/emitting code/pushAsPointer_.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testLinkConditionReflectiveDisable.st M Reflectivity-Tests.package/ReflectivityExamples.class/instance/examples/exampleMethod.st M Reflectivity.package/MetaLink.class/instance/ast/hook.st A Reflectivity.package/MetaLink.class/instance/ast/valueInContext_.st A Reflectivity.package/MetaLink.class/instance/ast/wrapCondition_.st R Reflectivity.package/MetaLink.class/instance/meta eval/valueInContext_.st A Reflectivity.package/MetaLink.class/instance/reflecive api/disable.st A Reflectivity.package/MetaLink.class/instance/reflecive api/enable.st A Reflectivity.package/MetaLink.class/instance/testing/hasMetaLevel.st A Reflectivity.package/MetaLink.class/instance/testing/hasReifiedCondition.st A Reflectivity.package/RFCondition.class/README.md A Reflectivity.package/RFCondition.class/class/as yet unclassified/for_.st A Reflectivity.package/RFCondition.class/definition.st A Reflectivity.package/RFCondition.class/instance/accessing/condition_.st A Reflectivity.package/RFCondition.class/instance/accessing/linkCondition_.st A Reflectivity.package/RFCondition.class/instance/enable%2Fdisable/disable.st A Reflectivity.package/RFCondition.class/instance/enable%2Fdisable/enable.st A Reflectivity.package/RFCondition.class/instance/evaluating/value.st A Reflectivity.package/RFCondition.class/instance/initialization/intitialize.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script637.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script638.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50028.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50029.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: --- 50029 15334 Closing tabs with ctrl+w shortcut sometimes throws error https://pharo.fogbugz.com/f/cases/15334 15479 Condition Reification https://pharo.fogbugz.com/f/cases/15479 14479 Enable nil to NULL coercion for NBExternalObjectType https://pharo.fogbugz.com/f/cases/14479 http://files.pharo.org/image/50/50029.zip
Re: [Pharo-dev] could the log message be placed on top of the files in the commit?
Code diffs would be more valuable, but adopting the tools of file lovers must come with a cost ;) Yes I would love that too. I just want to compile a list of changes automatically. May I can do in the scriptLoader instead of reparsing git.