- Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo crashing under new Fedora 24 (64bits plus 32bits libraries)

by Ben Coman

On Fri, Jun 24, 2016 at 4:10 AM, Casimiro - GMAIL < casimiro.barreto(a)gmail.com> wrote: > Pharo 5 crashes. VM does a SIGSEGV 0x00000000 at start > > Running GDB I got: > > (gdb) run > Starting program: /home/CdAB63/Downloads/pharo5.0/bin/pharo > Missing separate debuginfos, use: dnf debuginfo-install > glibc-2.23.1-8.fc24.i686 > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib64/libthread_db.so.1". > > Program received signal SIGSEGV, Segmentation fault. > I'm not practised enough to be sure, but does that /lib64/ give any hints since Pharo is 32-bit? cheers -ben

June 24, 2016

Re: [Pharo-users] Styling a Pharo UI application

by Tommaso Dal Sasso

Personally I don't dislike the Spec approach, but the API still looks not expressive enough for doing things beyond the standard. I am deepening my knowledge of Morphic now, thanks for your answer! Tommaso On 22/06/16 17:11, Dimitris Chloupis wrote: > Documentation is always a problem. > > I dont use Spec because I dont like it , but I use Morphic for my > project ChronosManager. I do some "styling" for example use different > fonts for different labels , different sizes , I format strings to > time stamps and even offer easy ways for user to change them without > modifying the whole string. > > You can do a lot with Morphic, though I have not played with layout > stuff since this GUI is static and image (PNGs) based but yeah Morphic > can do that as well. My project is on Catalog browser and it has class > comments , dont know if this exactly what you want but it may be a > good start. > > Obviously there are a ton of things you can do with a web page that > Morphic will not offer you out of the box. > > You can use Html as the front end / GUI and keep Pharo as the backend, > thats how most web apps made with Pharo work. This you get the full > power of Html/JS and Pharo. Seaside has classes that map html to pharo > methods so you dont have to write html and js, and also I remember a > pharo library dealing with CSS. > > Another option is to use a GUI API like QT , I have tried this with my > python bridge and it works at least on a very basic level, again > similar recipe to the above solution. > > But yeah if you are not too demanding I think Morphic will serve you > well. Personally I only like Morphic , its the only GUI API that does > not kill my inner child. > > On Wed, Jun 22, 2016 at 5:44 PM Tommaso Dal Sasso > <tommaso.dalsasso(a)gmail.com <mailto:tommaso.dalsasso@gmail.com>> wrote: > > Hello everybody, > > I have a question about the UI toolkits available for Pharo. I already > asked something about this on Slack, but since I saw that there was a > recent discussion about UI in the mailing list, I think this is a > better > place to discuss the matter. > > I am writing an application for Pharo where I am displaying some > structured text. The structure is similar to the one of a web page: A > main title with a list of paragraphs, where each paragraph has a title > and a description. > > What I would like to do is to format the text to present the > contents in > a meaningful way: For example, I would like a bigger font for the > title, > and change the background of the text, to give a better separation > between the paragraphs. Basically I would like to manipulate and > display > my contents as I would do in a web page. > > To write UI widgets I usually use Spec, but I found that going beyond > easy formatting (e.g. bold text and emphasis) is harder than I > thought. > I saw there were discussion about the styling text and the role of the > theme class, using TextStyle but that part is not really documented. > > So far, the easiest way to solve my problem seems to be to use Morphic > to display the contents as I want it, and then include my widget in my > spec application. > > Do you have any suggestions about how to do that? I think that styling > the UI widgets is an important part of the application > development, but > it is really hard to find documentation about this. > > Thanks, have a nice day! > Tommaso > >

June 23, 2016

Re: [Pharo-users] Xtreams: Extending Bootstrap

by Sean P. DeNigris

Sean P. DeNigris wrote > I wanted to extend the Xtream grammar to handle "/d97" I also wonder: - is there any specific reason that rules can't contain dashes? This seems pretty common. - Why use <- instead of = to separate the rule name from the definition? The standards I want to parse use the latter. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Xtreams-Extending-Bootstrap-tp4902579p4902741.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 23, 2016

Re: [Pharo-users] Xtreams: Debugging Grammars

by Sean P. DeNigris

Tudor Girba-2 wrote > If you are looking for PEG parsers, you can also try using PetitParser as > it comes with several debugging and inspection tools. I used Xtreams because I wanted to copy/paste the grammar from the spec instead of rewriting it in Smalltalk. I don't think that is possible in PP, is it? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Xtreams-Debugging-Grammars-tp4902581p4902739.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 23, 2016

Re: [Pharo-users] Xtreams: Debugging Grammars

by Sean P. DeNigris

stepharo wrote > Xtreams? Just to be sure is PEGParser built using Xtreams? Yes, there's some kind of bootstrapping process but I'm not clear how it works and haven't found any documentation. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Xtreams-Debugging-Grammars-tp4902581p4902738.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 23, 2016

Re: [Pharo-users] SQLite on multiple images

by stepharo

If i understand it correctly, you reuse your connexion instead of always releasing and requesting new ones from the os Stef > What is it exactly? A pool of pre-open connections to a database, to > save the connection time and make an application more responsive when > doing data operations? > > Thanks for the update. > > Hilaire > > > Le 19/06/2016 10:24, stepharo a Ã©crit : >> Hi hilaire >> >> >> I do not know if this is the anwser. Now I wanted to let you know that >> Olivier developed a session pool for database connexion. >> >> >> Stef

June 23, 2016

Re: [Pharo-users] Pharo crashing under new Fedora 24 (64bits plus 32bits libraries)

by Esteban Lorenzano

Iâm sorry, but this is not enough informationâ¦ normally crash should let a crash.dmp fileâ¦ also a way to reproduce the problem would be coolâ¦ a description of what you are doing, etc. cheers, Esteban > On 23 Jun 2016, at 22:10, Casimiro - GMAIL <casimiro.barreto(a)gmail.com> wrote: > > Pharo 5 crashes. VM does a SIGSEGV 0x00000000 at start > > Running GDB I got: > > (gdb) run > Starting program: /home/CdAB63/Downloads/pharo5.0/bin/pharo > Missing separate debuginfos, use: dnf debuginfo-install glibc-2.23.1-8.fc24.i686 > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib64/libthread_db.so.1". > > Program received signal SIGSEGV, Segmentation fault. > 0x00000000 in ?? () > (gdb) backtrace full > #0 0x00000000 in ?? () > No symbol table info available. > #1 0xf7f3dd7e in __pthread_once_slow () from /lib/libpthread.so.0 > No symbol table info available. > #2 0xf7aa9c05 in ?? () from /lib/libGL.so.1 > No symbol table info available. > #3 0xf7a722ab in ?? () from /lib/libGL.so.1 > No symbol table info available. > #4 0xf7fe8da1 in call_init.part () from /lib/ld-linux.so.2 > No symbol table info available. > #5 0xf7fe8f00 in _dl_init () from /lib/ld-linux.so.2 > No symbol table info available. > #6 0xf7fed80f in dl_open_worker () from /lib/ld-linux.so.2 > No symbol table info available. > #7 0xf7fe8c91 in _dl_catch_error () from /lib/ld-linux.so.2 > No symbol table info available. > #8 0xf7fecd89 in _dl_open () from /lib/ld-linux.so.2 > No symbol table info available. > #9 0xf7f4dc05 in dlopen_doit () from /lib/libdl.so.2 > No symbol table info available. > #10 0xf7fe8c91 in _dl_catch_error () from /lib/ld-linux.so.2 > No symbol table info available. > #11 0xf7f4e35d in _dlerror_run () from /lib/libdl.so.2 > No symbol table info available. > #12 0xf7f4dcae in dlopen@@GLIBC_2.1 <mailto:dlopen@@GLIBC_2.1> () from /lib/libdl.so.2 > No symbol table info available. > #13 0x080bd60f in tryLoading () > No symbol table info available. > #14 0x080bd751 in ioLoadModule () > No symbol table info available. > #15 0x080bf18b in queryLoadModule () > No symbol table info available. > #16 0x080bf27f in queryModule () > No symbol table info available. > #17 0x080bf2c7 in loadImplicit () > No symbol table info available. > #18 0x0805ccd7 in main () > No symbol table info available. > (gdb) > > > -- > The information contained in this message is confidential and intended to the recipients specified in the headers. If you received this message by error, notify the sender immediately. The unauthorized use, disclosure, copy or alteration of this message are strictly forbidden and subjected to civil and criminal sanctions. > > == > > This email may be signed using PGP key ID: 0x4134A417

June 23, 2016

Re: [Pharo-users] Xtreams: Debugging Grammars

by Tudor Girba

Hi, If you are looking for PEG parsers, you can also try using PetitParser as it comes with several debugging and inspection tools. Cheers, Doru > On Jun 23, 2016, at 10:23 PM, stepharo <stepharo(a)free.fr> wrote: > > Hi sean > > Xtreams? Just to be sure is PEGParser built using Xtreams? > > > Stef > > Le 23/6/16 Ã 02:20, Sean P. DeNigris a Ã©crit : >> I converted parts of rfc 5322 to the following: >> grammarEmailAddress >> >> ^'addrspec <- localpart "@" domain >> localpart <- dotatom / quotedstring /* obs-local-part */ >> domain <- dotatom / domainliteral /* obs-domain */ >> domainliteral <- [CFWS] "[" *([FWS] dtext) [FWS] "]" [CFWS] >> dtext <- [\x000021-\x000050] / /* Printable US-ASCII */ >> [\x000054-\x00007E] /* characters not including */ >> /* / obs-dtext ; "[", "]", or "\" */ >> >> /* rfc5234 B.1 */ >> ALPHA <- [\x000041-\x00005A] / [\x000061-\x00007A] >> DIGIT <- [\x000030-\x000039] >> HTAB <- [\x000009] /* horizontal tab */ >> SP <- [\x000020] >> WSP <- SP / HTAB >> >> /* 3.2.2. Folding White Space and Comments */ >> FWS <- ([*WSP CRLF] 1*WSP) >> /* obs-FWS */ >> ctext <- [\x000021-\x000027] / >> [\x00002A-\x00005B] / >> [\x00005D-\x00007E] >> >> ccontent <- ctext / quotedpair / comment >> >> comment <- "(" *([FWS] ccontent) [FWS] ")" >> >> CFWS <- (1*([FWS] comment) [FWS]) / FWS >> /* 3.2.1. Quoted characters */ >> quotedpair <- ("\" (VCHAR / WSP)) /* / obs-qp */ >> /* 3.2.3. Atom */ >> atext <- ALPHA / DIGIT / >> "!" / "#" / >> "$" / "%" / >> "&" / "''" / >> "*" / "+" / >> "-" / "/" / >> "=" / "?" / >> "^" / "_" / >> "`" / "{" / >> "|" / "}" / >> "~" >> >> atom <- [CFWS] 1*atext [CFWS] >> >> dotatomtext <- 1*atext *("." 1*atext) >> >> dotatom <- [CFWS] dotatomtext [CFWS] >> >> /* 3.2.4. Quoted Strings */ >> qtext <- [\x000021] / /* Printable US-ASCII */ >> [\x000023-\x00005B] / /* characters not including */ >> [\x00005D-\x00007E] /* "\" or the quote character */ >> /* obs-qtext */ >> qcontent <- qtext / quotedpair >> quotedstring <- [CFWS] DQUOTE *([FWS] qcontent) [FWS] DQUOTE [CFWS]' >> >> When I evaluate: >> parser := PEGParser parserPEG parse: 'Grammar' stream: PEGParser >> grammarEmailAddress actor: PEGParserParser new. >> >> I get: KeyNotFound: key 'quotedstring' not found in Dictionary >> >> How am I supposed to debug that to find the typo in my giant string above?! >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Xtreams-Debugging-Grammars-tp4902581.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> > > -- www.tudorgirba.com www.feenk.com "Things happen when they happen, not when you talk about them happening."

June 23, 2016

Re: [Pharo-users] Styling a Pharo UI application

by stepharo

For your information Glenn has a complete CSS support for widgets. But this is not yet ready. Stef Le 22/6/16 Ã 16:43, Tommaso Dal Sasso a Ã©crit : > Hello everybody, > > I have a question about the UI toolkits available for Pharo. I already > asked something about this on Slack, but since I saw that there was a > recent discussion about UI in the mailing list, I think this is a > better place to discuss the matter. > > I am writing an application for Pharo where I am displaying some > structured text. The structure is similar to the one of a web page: A > main title with a list of paragraphs, where each paragraph has a title > and a description. > > What I would like to do is to format the text to present the contents > in a meaningful way: For example, I would like a bigger font for the > title, and change the background of the text, to give a better > separation between the paragraphs. Basically I would like to > manipulate and display my contents as I would do in a web page. > > To write UI widgets I usually use Spec, but I found that going beyond > easy formatting (e.g. bold text and emphasis) is harder than I > thought. I saw there were discussion about the styling text and the > role of the theme class, using TextStyle but that part is not really > documented. > > So far, the easiest way to solve my problem seems to be to use Morphic > to display the contents as I want it, and then include my widget in my > spec application. > > Do you have any suggestions about how to do that? I think that styling > the UI widgets is an important part of the application development, > but it is really hard to find documentation about this. > > Thanks, have a nice day! > Tommaso > > >

June 23, 2016

Re: [Pharo-users] Xtreams: Debugging Grammars

by stepharo

Hi sean Xtreams? Just to be sure is PEGParser built using Xtreams? Stef Le 23/6/16 Ã 02:20, Sean P. DeNigris a Ã©crit : > I converted parts of rfc 5322 to the following: > grammarEmailAddress > > ^'addrspec <- localpart "@" domain > localpart <- dotatom / quotedstring /* obs-local-part */ > domain <- dotatom / domainliteral /* obs-domain */ > domainliteral <- [CFWS] "[" *([FWS] dtext) [FWS] "]" [CFWS] > dtext <- [\x000021-\x000050] / /* Printable US-ASCII */ > [\x000054-\x00007E] /* characters not including */ > /* / obs-dtext ; "[", "]", or "\" */ > > /* rfc5234 B.1 */ > ALPHA <- [\x000041-\x00005A] / [\x000061-\x00007A] > DIGIT <- [\x000030-\x000039] > HTAB <- [\x000009] /* horizontal tab */ > SP <- [\x000020] > WSP <- SP / HTAB > > /* 3.2.2. Folding White Space and Comments */ > FWS <- ([*WSP CRLF] 1*WSP) > /* obs-FWS */ > ctext <- [\x000021-\x000027] / > [\x00002A-\x00005B] / > [\x00005D-\x00007E] > > ccontent <- ctext / quotedpair / comment > > comment <- "(" *([FWS] ccontent) [FWS] ")" > > CFWS <- (1*([FWS] comment) [FWS]) / FWS > /* 3.2.1. Quoted characters */ > quotedpair <- ("\" (VCHAR / WSP)) /* / obs-qp */ > /* 3.2.3. Atom */ > atext <- ALPHA / DIGIT / > "!" / "#" / > "$" / "%" / > "&" / "''" / > "*" / "+" / > "-" / "/" / > "=" / "?" / > "^" / "_" / > "`" / "{" / > "|" / "}" / > "~" > > atom <- [CFWS] 1*atext [CFWS] > > dotatomtext <- 1*atext *("." 1*atext) > > dotatom <- [CFWS] dotatomtext [CFWS] > > /* 3.2.4. Quoted Strings */ > qtext <- [\x000021] / /* Printable US-ASCII */ > [\x000023-\x00005B] / /* characters not including */ > [\x00005D-\x00007E] /* "\" or the quote character */ > /* obs-qtext */ > qcontent <- qtext / quotedpair > quotedstring <- [CFWS] DQUOTE *([FWS] qcontent) [FWS] DQUOTE [CFWS]' > > When I evaluate: > parser := PEGParser parserPEG parse: 'Grammar' stream: PEGParser > grammarEmailAddress actor: PEGParserParser new. > > I get: KeyNotFound: key 'quotedstring' not found in Dictionary > > How am I supposed to debug that to find the typo in my giant string above?! > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Xtreams-Debugging-Grammars-tp4902581.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

June 23, 2016