- Pharo-users - lists.pharo.org

nice CSS for the Pharo online HTML version?

by Stephane Ducasse

Hi Iâm looking for a nice CSS for the Pharo online HTML version. I found something like that https://www.smashingmagazine.com/2015/02/designers-start-coding-with-uilang/ Stef -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Nov. 5, 2017

Re: [Pharo-users] LiteratureResearcher - where graphs, PDFs, and BibTex happily live together

by Evan Donahue

This looks great. What would it take to get it running on Ubuntu? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 5, 2017

Re: [Pharo-users] Embedded PDF viewer?

by tesonep＠gmail.com

Hello Ben, UFFI does not allow you to call static libraries. Static libraries are not executable per se, they need to be linked in another program. As I know, the only way of using an static library from Pharo is to: - Build a plugin that wraps it. - Build a DLL exposing all the functions in the library and then they are used through UFFI. The second option is the easiest to me, but it depends how the library is built up. For example, if the library uses a lot of compile time code generation (like macros or templates) making a generic DLL is not so easy. I think it is better to see if not other project has already tackle this problem when using the desired static library. Cheers, Pablo On Sun, Nov 5, 2017 at 1:39 PM, Ben Coman <btc(a)openinworld.com> wrote: > I'm looking into calling PDFium from Pharo via FFI. > Currently I'm stalled a bit since it doesn't have a shared-library target. > > If you consider access to such a library would be useful to the community, > please take a few moments to star this issue... > https://bugs.chromium.org/p/pdfium/issues/detail?id=826 > > cheers -ben > > > P.S. Can anyone comment on calling into a static library via FFI? > > > > On Wed, Oct 11, 2017 at 2:05 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> >> >> On Wed, Oct 11, 2017 at 2:03 PM, Ben Coman <btc(a)openinworld.com> wrote: >> >>> >>> > On Tue, Oct 10, 2017 at 8:58 PM, Manuel Leuenberger >>> > <leuenberger(a)inf.unibe.ch> wrote: >>> > > Hi, >>> > > >>> > > I want to view a PDF within Pharo. I found that Athens has a PDF >>> canvas, but I have no idea how to use it. Is there a way to view a PDF >>> within Pharo, so that I can scroll, zoom, click links etc. in the PDF? >>> > > >>> > > Cheers, >>> > > Manuel >>> >>> >>> On Wed, Oct 11, 2017 at 3:04 AM, Stephane Ducasse < >>> stepharo.self(a)gmail.com> wrote: >>> > >>> > Hi manuel >>> > >>> > So far I do not know if we have this is Pharo. >>> > I imagine that we would have to build a renderer once we will have the >>> > PDF reader from Christian library. >>> > >>> > Stef >>> >>> >> [Edit: Update license link] >> >> >>> A renderer will have great synergy with PDFTalk, but I think a proof of >>> concept can be done independently. >>> I've been poking at this topic for a while looking for options. >>> Coincidentally a couple of days I discovered the PDFium library. >>> I haven't had time yet to give it a run, but it seems a good candidate >>> since... >>> * Its a successful commercial product by Foxit built into Chrome >>> converted to open source with Google's backing for use in Chromium >>> https://www.foxitsoftware.com/company/press.php?id=305 >>> * Its license is BSD style >>> *https://github.com/hfiguiere/pdfium/blob/master/LICENSE >>> <https://github.com/hfiguiere/pdfium/blob/master/LICENSE>* >>> * Although written in C++ it has a C interface >>> https://github.com/hfiguiere/pdfium/blob/master/public/fpdfview.h >>> * Search here on " Function: " to skim through >>> * Proof of concept seems to only need these key functions... >>> * void FPDF_RenderPageBitmap( FPDF_BITMAP bitmap,FPDF_PAGE >>> page, ... ) >>> * FPDF_BITMAP FPDFBitmap_Create( int width, int height, int >>> alpha); >>> * FPDF_PAGE FPDF_LoadPage ( FPDF_DOCUMENT document, int >>> page_index ) >>> * FPDF_DOCUMENT FPDF_LoadMemDocument ( const void* >>> data_buf ... ) >>> * void FPDF_InitLibrary () >>> * Has a concise getting started for POC... >>> https://github.com/hfiguiere/pdfium/blob/master/docs/getting >>> -started.md >>> * Maybe useful fork with V8 disabled by default >>> https://github.com/klokantech/pdfium >>> * Master repo here >>> https://pdfium.googlesource.com/pdfium/ >>> >>> So Pharo might load a PDF file into a ByteArray, pass that to >>> FPDF_LoadMemDocument() & FPDF_LoadPage(), >>> then get a bitmap back from FPDFBitmap_Create() & >>> FPDF_RenderPageBitmap() and display the result in a Pharo window. >>> >>> The rest of this week I'm working 12 hour days on a mine site. I could >>> try it out once I'm home, but in the meantime is anyone else keen to try >>> it? >>> >>> cheers -ben >>> >> >> > -- Pablo Tesone. tesonep(a)gmail.com

Nov. 5, 2017

Re: [Pharo-users] [squeak-dev] [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations

by henry

I was a latecomer to all the work the Cryptography Team put together, all functions and ciphers and hashes they put together. I helped add ASN.1, later on. They did the hard work I put some pieces together. I heard someone likes it. That makes me happy. Henry Sent from ProtonMail Mobile On Fri, Nov 3, 2017 at 00:04, Ben Coman <btc(a)openinworld.com> wrote: > On Fri, Nov 3, 2017 at 4:06 AM, henry <henry(a)callistohouse.club> wrote: > >> I have a question about my derivation of a MAC key. It is very complicated and I am considering ways to simplify for use by potential language implementations. Here is the current derivation in Squeak/Pharo. Should I just use the sharedKey as the SHA1HMAC key or some simplified hash of the sharedKey, without all the pad hashings I am doing? What do you think? I want to hear from you. > > Hi Henry, > > I'd guess not many people here are *really* competent enough in crypto to confidently advise you. I know I'm not. I only know enough to know crypto is *hard*. > * https://www.happybearsoftware.com/you-are-dangerously-bad-at-cryptography.h… > * https://www.schneier.com/blog/archives/2011/04/schneiers_law.html > * https://www.schneier.com/essays/archives/1997/01/why_cryptography_is.html > > I hope that doesn't discourage you, and I'm interested to hear a more useful reply from anyone else. > cheers -ben > > P.S. I just bumped into what looks like an interesting intellectual exercise... > http://cryptopals.com/ > >> makeHMAC >> >> | sharedKey hashPadder macKey | >> sharedKey := diffieHellman sharedKeyPadPositiveByteArray. >> hashPadder := self class. >> macKey := MD5 hashMessage: ( >> (hashPad der hash: sharedKey pad: 16rCC), >> (hashPad der hash: sharedKey pad: 16rBB), >> (hashPad der hash: sharedKey pad: 16rAA), >> (hashPad der hash: sharedKey pad: 16r99)). >> macKey := macKey, (MD5 hashMessage: ( >> (hashPadder hash: sharedKey pad: 16r88), >> (hashPad der hash: sharedKey pad: 16r77), >> (hashPad der hash: sharedKey pad: 16r66), >> (hashPad der hash: sharedKey pad: 16r55))). >> macKey := macKey, (MD5 hashMessage: ( >> (hashPad der hash: sharedKey pad: 16r44), >> (hashPad der hash: sharedKey pad: 16r33), >> (hashPad der hash: sharedKey pad: 16r22), >> (hashPad der hash: sharedKey pad: 16r11))). >> ^ SHA1 new hmac key: macKey. >> >> Would a better way forwards is simply this? >> >> makeHMAC >> >> macKey := diffieHellman sharedKeyPadPositiveByteArray. >> ^ SHA1 new hmac key: macKey. >> >> Thank you. >> >> - HH >> >>> -------- Original Message -------- >>> Subject: Re: [Pharo-users] [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerationsLocal Time: November 2, 2017 3:50 PM >>> UTC Time: November 2, 2017 7:50 PM >>> From: henry(a)callistohouse.club >>> To: henry <henry(a)callistohouse.club> >>> Squeak-dev <squeak-dev(a)lists.squeakfoundation.org>, Pharo-users list <pharo-users(a)lists.pharo.org>, Pharo Development List <pharo-dev(a)lists.pharo.org> >>> >>> I have developed the ParrotTalk Protocol, documented in part here[1], while I have two implementations: 1 in Squeak/Pharo [2 a/b] and the other in Java [3 a/b]. Particulars of some decisions are absent from the specification: namely the MAC key and ivSequence derivations, as well as constrained traffic signing; they are in the implementations. I will update the 3.6 slideshow to specify these items. >>> >>> Thank you. >>> >>> - HH >>> >>> [1] - ParrotTalk Protocol : http://jmp.sh/OqlYpyg >>> >>> Squeak/Pharo implementation >>> [2 a] - http://www.squeaksource.com/Cryptography/Cryptography-HenryHouse.113.mcz >>> >>> [2 b] - http://www.squeaksource.com/Cryptography/ParrotTalk-HenryHouse.9.mcz >>> >>> Java implementation >>> [3 a] - https://github.com/ZiroZimbarra/ASN1 >>> [3 b] - https://github.com/ZiroZimbarra/ParrotTalk >>> >>> - HH >>> >>>> -------- Original Message -------- >>>> Subject: Re: [Pharo-users] [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations >>>> Local Time: November 2, 2017 3:43 PM >>>> UTC Time: November 2, 2017 7:43 PM >>>> From: henry(a)callistohouse.club >>>> To: Squeak-dev <squeak-dev(a)lists.squeakfoundation.org> >>>> Pharo-users list <pharo-users(a)lists.pharo.org>, Pharo Development List <pharo-dev(a)lists.pharo.org> >>>> >>>> More celebration requested. I got encrypted data passing between Squeak/Pharo and Java: AES with CBC and IVs and SHA1 HMAC. It works! NSA-proof crypto rocking Squeak, Pharo & Java! >>>> >>>> *Celebrates again, drinks for everyone* >>>> >>>> - HH >>>> >>>>> -------- Original Message -------- >>>>> Subject: Re: [Pharo-users] [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations >>>>> Local Time: October 31, 2017 1:54 PM >>>>> UTC Time: October 31, 2017 5:54 PM >>>>> From: henry(a)callistohouse.club >>>>> To: henry <henry(a)callistohouse.club> >>>>> Ben Coman <btc(a)openinworld.com>, Squeak-dev <squeak-dev(a)lists.squeakfoundation.org>, Pharo-users list <pharo-users(a)lists.pharo.org>, Pharo Development List <pharo-dev(a)lists.pharo.org> >>>>> >>>>> I wanted to share my good news, though I have not yet gotten Pharo, Squeak and Java talking. What I was able to accomplish, after finishing the port of Cryptography's ASN1Types, Module and Streams is to get Java's rendezvous and key exchange working. After I got that connecting, I looked at the ciphers, ivSequences and MAC and got that working. In Java, I am now able to encrypt and decrypt "hello world". >>>>> >>>>> *Celebrates* >>>>> >>>>> - HH >>>>> >>>>>> -------- Original Message -------- >>>>>> Subject: Re: [Pharo-users] [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations >>>>>> Local Time: October 25, 2017 12:00 PM >>>>>> UTC Time: October 25, 2017 4:00 PM >>>>>> From: henry(a)callistohouse.club >>>>>> To: Ben Coman <btc(a)openinworld.com>, Squeak-dev <squeak-dev(a)lists.squeakfoundation.org>, Pharo-users list <pharo-users(a)lists.pharo.org> >>>>>> Pharo Development List <pharo-dev(a)lists.pharo.org> >>>>>> >>>>>> I disabled vatId authorization in version 3, located in SessionOperations>>processIWan t | SessionOperations>>processIAm: . >>>>>> >>>>>> I was asked to disseminate my news to Pharo Users, hello there. I was asked to describe ParrotTalk well, provide use cases and adopters of its use. Alright, I will give an attempt. >>>>>> >>>>>> ParrotTalk is an encrypted connection framework. Currently allowing anonymous 2048-bit key negotiation to establish user-provided encryption cipher and user-provided encoding and decoding, both through a provided SessionAgentMap to a starting SessionAgent server. Please look in the test case ThunkHelloWorldTest for building these maps and running a connection iwth data passing after encryption is established. There is a 4-way negotiation, from ProtocolOffered/Accepted to Go/GoToo. In using RSA 2048 signature validation and DH 2048 primes to establish the key used within the selected Cipher. The Cipher and Encoder are selected by name through the negotiation protocol. Currently three Ciphers are selectable, AESede, DESede, and DES. There are two encoders tested, asn1der, and Bytes. This protocol is described here, in this document. >>>>>> >>>>>> https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFr… >>>>>> >>>>>> For as to use cases, this encrypted connection has no third party, man-in-the-middle situation by not using Certificates. As such, this is a tight implementation of NSA-proof encryption without explicit authorization beyond knowledge of a host:port. The use cases involve any communication desired to be encrypted with such high encryption. The support will last my lifetime, so we have a settled solution, here in the third version, provided here. It requires version 111 of Cryptography, as a prerequisite. Both run on Squeak and Pharo. >>>>>> >>>>>> http://www.squeaksource.com/Cryptography/Cryptography-zzz.111.mcz >>>>>> http://www.squeaksource.com/Cryptography/ParrotTalk-HenryHouse.3.mcz >>>>>> >>>>>> The current use is with my hubbub system, a promise-based distributed object implementation. I am working to bring ParrotTalk to Java and allow hubbub to operate interdependently between Squeak, Pharo, Java and any other languages which can support ParrotTalk and STON. My latest efforts with hubbub are to bring STON as the Layer 6 encoding. Hubbub depends on eLinda. >>>>>> >>>>>> http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz >>>>>> http://www.squeaksource.com/Oceanside/hubbub-HenryHouse.38.mcz >>>>>> >>>>>> Hubbub currently fails to load correctly in Pharo. In Squeak the two ParrotRemoteTestCases: LookupTestCase and OperationalTestCase really screw everything up, do not save an image after running. I never run these tests until I get a better handle of serialization. Currently, do to a shift in progress to STON, the serialization tests fail, just the way we like it. Fix the tests then the system starts to work right. >>>>>> >>>>>> The shift away from vatId authorization should not adversely affect hubbub, we hope! When STON starts to work, and I think I need to turn off jsonMode, then traffic between vats can start to be analyzed and figure out how resolving is working with redirectors invoked remotely. >>>>>> >>>>>> - HH >>>>>> >>>>>>> -------- Original Message -------- >>>>>>> Subject: Re: [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations >>>>>>> Local Time: October 25, 2017 12:43 AM >>>>>>> UTC Time: October 25, 2017 4:43 AM >>>>>>> From: btc(a)openinworld.com >>>>>>> To: henry <henry(a)callistohouse.club>, Pharo Development List <pharo-dev(a)lists.pharo.org> >>>>>>> Stephane Ducasse <stepharo.self(a)gmail.com> >>>>>>> >>>>>>> If I google... parrottalk protocol >>>>>>> nothing seems related. So what is ParrotTalk? >>>>>>> >>>>>>> P.S... since this is not "part of" pharo, [pharo-users] would be a better place for discussion than [pharo-dev]. >>>>>>> Could you re-announce there, with some description of use cases and who/where the protocol is used? >>>>>>> >>>>>>> cheers -ben >>>>>>> >>>>>>> On Wed, Oct 25, 2017 at 1:42 AM, henry <henry(a)callistohouse.club> wrote: >>>>>>> >>>>>>>> Please excuse all the low-level detail, if inappropriate to the discussion. The protocol changes are here specified. >>>>>>>> >>>>>>>> - HH >>>>>>>> >>>>>>>> On Tue, Oct 24, 2017 at 13:40, henry <henry(a)callistohouse.club> wrote: >>>>>>>> >>>>>>>>> In order to bring ParrotTalk-3.6 support, alongside historical 3.5 support, the frame header stays the same and the processing of the ProtocolOffered would select "ParrotTalk-3.6" to use the compact protocol of >>>>>>>>> >>>>>>>>> - ProtocolOffered { offered, preferred } >>>>>>>>> - ProtocolAccepted { accepted } >>>>>>>>> - IWant|GiveInfo|ReplyInfo { v atId, domain, publicKey, cryptoProtocols, dataEncoders } >>>>>>>>> - IAm|ReplyInfo { vatId, domain, publicKey, cryptoProtocol, dataEncoder, dhParam } >>>>>>>>> - Go { cryptoProtocol, dataEncoder, dhParam, signature } >>>>>>>>> - GoToo { signature } >>>>>>>>> >>>>>>>>> Using eLinda : >>>>>>>>> >>>>>>>>> http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz >>>>>>>>> >>>>>>>>> Above the FrameBuffer, below the SessionOperations for each version of the protocol, an ELindaSession could be inserted. This session think would have the stacks for each protocol version SessionOperation registered by protocol in a Tuple, for eventual callback. When the ProtocolOffered comes in we publish the tuple frame, with set selected version, to route to the correct SessionOperation to support each version of the protocol. >>>>>>>>> >>>>>>>>> With a non-specific vatId required, anonymous connections would be supported. >>>>>>>>> >>>>>>>>> - HH >>>>>>>>> >>>>>>>>> On Tue, Oct 24, 2017 at 12:52, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Hi henry thanks for this announce. Can you tell where such protocols are used? Stef On Tue, Oct 24, 2017 at 6:33 PM, henry wrote: > Hi all, > > I am happy to announce the release of version 3.5 of ParrotTalk, for Squeak > and Pharo, found here: > > http://www.squeaksource.com/Cryptography/ParrotTalk-zzz.2.mcz > > It follows this specification: > https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFr… > > One item of note, in version 3.5, the system connecting to a server, sending > the IWant msg, must know the vatId of the system being connected to. I am > considering changing this to version 3.6 by removing one round-trip in > messaging. Therefore, these messages would be combined: IWant/GiveInfo, > IAm/ReplyInfo. I will keep ProtocolOffered and ProtocolAccepted to allow > eLindaSession to support both versions: 3.5 and 3.6. > > Thoughts please? > > - HH

Nov. 5, 2017

Re: [Pharo-users] Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk:Anonymous P2P encryption

by henry

Awesome, you are the first person I know to have tried using it, glad to hear of this. Glad itâs working! Sent from ProtonMail Mobile On Sun, Nov 5, 2017 at 06:59, Andrew Glynn <aglynn42(a)gmail.com> wrote: > Iâve been playing around with it, works well. > > Ty ð > > Andrew Glynn > > Sent from [Mail](https://go.microsoft.com/fwlink/?LinkId=550986) for Windows 10 > > From: [henry](mailto:henry@callistohouse.club) > Sent: Saturday, November 4, 2017 5:18 PM > To: [Squeak-dev](mailto:squeak-dev@lists.squeakfoundation.org); [Pharo-users list](mailto:pharo-users@lists.pharo.org); [Pharo Development List](mailto:pharo-dev@lists.pharo.org) > Subject: [Pharo-users] Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk:Anonymous P2P encryption > > I am preparing an Internet Draft for submission through IETF. Listed below. > > Sent from ProtonMail Mobile > >> ---------- Forwarded message ---------- >> From: Bob<robert.withers(a)protonmail.com> >> Date: On Sat, Nov 4, 2017 at 13:56 >> Subject: Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption >> To: Bob <robert.withers(a)protonmail.com> >> Cc: SAAG <saag(a)ietf.org> >> >> I updated the I-D located here: http://jmp.sh/VRejS2g >> >> Thank you for your consideration, >> >> - HH >> >>> -------- Original Message -------- >>> >>> Subject: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption >>> >>> Local Time: November 3, 2017 9:07 AM >>> >>> UTC Time: November 3, 2017 1:07 PM >>> >>> From: robert.withers(a)protonmail.com >>> >>> To: SAAG <saag(a)ietf.org> >>> >>> Good morning, >>> >>> I am forwarding this announcement of the ParrotTalk v3.6 specification and 2 reference implementations, in Squeak/Pharo and Java, to the SAAG list. I was advised that this mailing list regarding the Security Area is the correct home for this announcement. Below, I corrected the version of the Squeak/Pharo ParrotTalk code to version 11, interoperable with the Java version. I am proceeding to work on the Internet-Draft and I hope some discussion builds around this work. >>> >>> Thank you. >>> >>> - HH >>> >>>> -------- Original Message -------- >>>> >>>> Subject: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption >>>> >>>> Local Time: November 2, 2017 9:19 PM >>>> >>>> UTC Time: November 3, 2017 1:19 AM >>>> >>>> From: henry(a)callistohouse.club >>>> >>>> To: IETF <ietf(a)ietf.org> >>>> >>>> I have developed the ParrotTalk Protocol, and am starting an internet draft document[1] for submission to the process at IETF. >>>> >>>> ParrotTalk Protocol is documented in part here[2], while I have two implementations: 1 in Squeak/Pharo[3 a/b] and the other in Java[4 a/b]. The particulars of MAC key and ivSequence derivation, as well as constrained traffic signing, are the implementations, yet missing from the specification. They will be added to the internet-draft. >>>> >>>> How do I go about submitting a specification for ParrotTalk for IETF review and consideration? >>>> >>>> Thank you. >>>> >>>> - HH >>>> >>>> - HH >>>> >>>> - HH >>>> >>>> - HH >>>> >>>> - HH >>>> >>>> - HH >>>> >>>> - HH >>>> >>>> - HH

Nov. 5, 2017

Re: [Pharo-users] [squeak-dev] Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption

by henry

Thank you, Ben, weâll see Iâll let you know. Sent from ProtonMail Mobile On Sun, Nov 5, 2017 at 06:14, Ben Coman <btc(a)openinworld.com> wrote: > Good luck with it. > cheers -ben > > On Sun, Nov 5, 2017 at 5:17 AM, henry <henry(a)callistohouse.club> wrote: > >> I am preparing an Internet Draft for submission through IETF. Listed below. >> >> Sent from ProtonMail Mobile >> >>> ---------- Forwarded message ---------- >>> From: Bob<robert.withers(a)protonmail.com> >>> Date: On Sat, Nov 4, 2017 at 13:56 >>> Subject: Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption >>> To: Bob <robert.withers(a)protonmail.com > >>> Cc: SAAG <saag(a)ietf.org> >>> >>> I updated the I-D located here: http://jmp.sh/VRejS2g >>> >>> Thank you for your consideration, >>> - HH >>> >>>> -------- Original Message -------- >>>> Subject: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption >>>> Local Time: November 3, 2017 9:07 AM >>>> UTC Time: November 3, 2017 1:07 PM >>>> From: robert.withers(a)protonmail.com >>>> To: SAAG <saag(a)ietf.org> >>>> >>>> Good morning, >>>> >>>> I am forwarding this announcement of the ParrotTalk v3.6 specification and 2 reference implementations, in Squeak/Pharo and Java, to the SAAG list. I was advised that this mailing list regarding the Security Area is the correct home for this announcement. Below, I corrected the version of the Squeak/Pharo ParrotTalk code to version 11, interoperable with the Java version. I am proceeding to work on the Internet-Draft and I hope some discussion builds around this work. >>>> >>>> Thank you. >>>> - HH >>>> >>>>> -------- Original Message -------- >>>>> Subject: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption >>>>> Local Time: November 2, 2017 9:19 PM >>>>> UTC Time: November 3, 2017 1:19 AM >>>>> From: henry(a)callistohouse.club >>>>> To: IETF <ietf(a)ietf.org> >>>>> >>>>> I have developed the ParrotTalk Protocol, and am starting an internet draft document[1] for submission to the process at IETF. >>>>> >>>>> ParrotTalk Protocol is documented in part here[2], while I have two implementations: 1 in Squeak/Pharo[3 a/b] and the other in Java[4 a/b]. The particulars of MAC key and ivSequence derivation, as well as constrained traffic signing, are the implementations, yet missing from the specification. They will be added to the internet-draft. >>>>> >>>>> How do I go about submitting a specification for ParrotTalk for IETF review and consideration? >>>>> >>>>> Thank you. >>>>> >>>>> - HH >>>>> - HH >>>>> - HH >>>>> - HH >>>>> - HH >>>>> - HH >>>>> - HH >>>>> - HH

Nov. 5, 2017

Re: [Pharo-users] [Pharo7.0a] Next batch of enhancements

by Pavel Krivanek

Removing of the Watery theme is an enhancement in sense of "cleanup". The code was not maintained and partly broken. To have this theme in the image was a problem for management of the two default Pharo themes because the Watery theme was superclass of them and added a significant level of complexity and mess. But let's be positive. I can imagine that this thread has a huge flame potential so I spent a few minutes to prepare Watery Theme as a standalone package (see the attached *.st file). And no, it was not a simple file-out operation. So I hope that people that want to use the Watery Theme will rather discuss in what repository to place it and who will maintain it. In Pharo we want to focus on two basic themes - one white and one dark. We simply see no reason why this theme should not be an optional external package. Cheers, -- Pavel 2017-11-05 12:00 GMT+01:00 PBKResearch <peter(a)pbkresearch.co.uk>: > I waded through the list of 'enhancements', and was astonished to find > this. Is there to be an alternative way of producing the same appearance as > the 'Watery' theme? If not, how can the removal of a facility be called an > 'enhancement'? I always switch to this theme when I load a new image, > because I find the plain buttons in the standard theme ugly. > > I managed to find the fogbugz entry - not easy, because it has been > closed, so clicking on the link gives 404 - and it just says 'UIThemeWatery > should be removed according to the current Pharo 7 plans.' I can't recall > seeing these plans put up for discussion; if I had, I would certainly have > protested then. Does having this theme as an option cause any problems > elsewhere, so as to justify removing a facility. If not, can I put in a > plea to have this so-called enhancement reverted? It has been installed > only a week ago, so it can't be a major problem. > > Peter Kenny > > -----Original Message----- > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf > Of Stephane Ducasse > Sent: 05 November 2017 09:08 > To: Pharo Development List <pharo-dev(a)lists.pharo.org>; Any question > about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] [Pharo7.0a] Next batch of enhancements > > Report period: 23 October 2017 to 5 November 2017 > > * 20587-remove-UIThemeWatery > >> https://pharo.fogbugz.com/f/cases/20587-remove-UIThemeWatery > > Issue URL: https://pharo.fogbugz.com/f/cases/20587 > PR URL: https://github.com/pharo-project/pharo/pull/395 > Diff URL: https://github.com/pharo-project/pharo/pull/395/files > > Thanks to pavel-krivanek > > > > >

Nov. 5, 2017

Re: [Pharo-users] Embedded PDF viewer?

by Ben Coman

I'm looking into calling PDFium from Pharo via FFI. Currently I'm stalled a bit since it doesn't have a shared-library target. If you consider access to such a library would be useful to the community, please take a few moments to star this issue... https://bugs.chromium.org/p/pdfium/issues/detail?id=826 cheers -ben P.S. Can anyone comment on calling into a static library via FFI? On Wed, Oct 11, 2017 at 2:05 PM, Ben Coman <btc(a)openinworld.com> wrote: > > > On Wed, Oct 11, 2017 at 2:03 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> >> > On Tue, Oct 10, 2017 at 8:58 PM, Manuel Leuenberger >> > <leuenberger(a)inf.unibe.ch> wrote: >> > > Hi, >> > > >> > > I want to view a PDF within Pharo. I found that Athens has a PDF >> canvas, but I have no idea how to use it. Is there a way to view a PDF >> within Pharo, so that I can scroll, zoom, click links etc. in the PDF? >> > > >> > > Cheers, >> > > Manuel >> >> >> On Wed, Oct 11, 2017 at 3:04 AM, Stephane Ducasse < >> stepharo.self(a)gmail.com> wrote: >> > >> > Hi manuel >> > >> > So far I do not know if we have this is Pharo. >> > I imagine that we would have to build a renderer once we will have the >> > PDF reader from Christian library. >> > >> > Stef >> >> > [Edit: Update license link] > > >> A renderer will have great synergy with PDFTalk, but I think a proof of >> concept can be done independently. >> I've been poking at this topic for a while looking for options. >> Coincidentally a couple of days I discovered the PDFium library. >> I haven't had time yet to give it a run, but it seems a good candidate >> since... >> * Its a successful commercial product by Foxit built into Chrome >> converted to open source with Google's backing for use in Chromium >> https://www.foxitsoftware.com/company/press.php?id=305 >> * Its license is BSD style >> *https://github.com/hfiguiere/pdfium/blob/master/LICENSE >> <https://github.com/hfiguiere/pdfium/blob/master/LICENSE>* >> * Although written in C++ it has a C interface >> https://github.com/hfiguiere/pdfium/blob/master/public/fpdfview.h >> * Search here on " Function: " to skim through >> * Proof of concept seems to only need these key functions... >> * void FPDF_RenderPageBitmap( FPDF_BITMAP bitmap,FPDF_PAGE >> page, ... ) >> * FPDF_BITMAP FPDFBitmap_Create( int width, int height, int >> alpha); >> * FPDF_PAGE FPDF_LoadPage ( FPDF_DOCUMENT document, int >> page_index ) >> * FPDF_DOCUMENT FPDF_LoadMemDocument ( const void* data_buf >> ... ) >> * void FPDF_InitLibrary () >> * Has a concise getting started for POC... >> https://github.com/hfiguiere/pdfium/blob/master/docs/getting >> -started.md >> * Maybe useful fork with V8 disabled by default >> https://github.com/klokantech/pdfium >> * Master repo here >> https://pdfium.googlesource.com/pdfium/ >> >> So Pharo might load a PDF file into a ByteArray, pass that to >> FPDF_LoadMemDocument() & FPDF_LoadPage(), >> then get a bitmap back from FPDFBitmap_Create() & FPDF_RenderPageBitmap() >> and display the result in a Pharo window. >> >> The rest of this week I'm working 12 hour days on a mine site. I could >> try it out once I'm home, but in the meantime is anyone else keen to try >> it? >> >> cheers -ben >> > >

Nov. 5, 2017

Re: [Pharo-users] Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk:Anonymous P2P encryption

by Andrew Glynn

Iâve been playing around with it, works well. Ty ð Andrew Glynn Sent from Mail for Windows 10 From: henry Sent: Saturday, November 4, 2017 5:18 PM To: Squeak-dev; Pharo-users list; Pharo Development List Subject: [Pharo-users] Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk:Anonymous P2P encryption I am preparing an Internet Draft for submission through IETF. Listed below. Sent from ProtonMail Mobile ---------- Forwarded message ---------- From: Bob<robert.withers(a)protonmail.com> Date: On Sat, Nov 4, 2017 at 13:56 Subject: Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption To: Bob <robert.withers(a)protonmail.com> Cc: SAAG <saag(a)ietf.org> I updated the I-D located here: http://jmp.sh/VRejS2g Thank you for your consideration, - HH -------- Original Message -------- Subject: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption Local Time: November 3, 2017 9:07 AM UTC Time: November 3, 2017 1:07 PM From: robert.withers(a)protonmail.com To: SAAG <saag(a)ietf.org> Good morning, I am forwarding this announcement of the ParrotTalk v3.6 specification and 2 reference implementations, in Squeak/Pharo and Java, to the SAAG list. I was advised that this mailing list regarding the Security Area is the correct home for this announcement. Below, I corrected the version of the Squeak/Pharo ParrotTalk code to version 11, interoperable with the Java version. I am proceeding to work on the Internet-Draft and I hope some discussion builds around this work. Thank you. - HH -------- Original Message -------- Subject: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption Local Time: November 2, 2017 9:19 PM UTC Time: November 3, 2017 1:19 AM From: henry(a)callistohouse.club To: IETF <ietf(a)ietf.org> I have developed the ParrotTalk Protocol, and am starting an internet draft document[1] for submission to the process at IETF. ParrotTalk Protocol is documented in part here[2], while I have two implementations: 1 in Squeak/Pharo[3 a/b]Â and the other in Java[4 a/b]. The particulars of MAC key and ivSequence derivation, as well as constrainedÂ traffic signing, are the implementations, yet missing from the specification. They will be added to the internet-draft. How do I go about submitting a specification for ParrotTalk for IETF review and consideration? Thank you. - HH - HH - HH - HH - HH - HH - HH - HH

Nov. 5, 2017

Re: [Pharo-users] [squeak-dev] Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption

by Ben Coman

Good luck with it. cheers -ben On Sun, Nov 5, 2017 at 5:17 AM, henry <henry(a)callistohouse.club> wrote: > I am preparing an Internet Draft for submission through IETF. Listed below. > > > Sent from ProtonMail Mobile > > ---------- Forwarded message ---------- > From: Bob<robert.withers(a)protonmail.com> > Date: On Sat, Nov 4, 2017 at 13:56 > Subject: Fwd: Re: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous > P2P encryption > To: Bob <robert.withers(a)protonmail.com> > Cc: SAAG <saag(a)ietf.org> > I updated the I-D located here: http://jmp.sh/VRejS2g > > Thank you for your consideration, > - HH > > -------- Original Message -------- > Subject: [saag] Fw: [internet-draft-draft] ParrotTalk: Anonymous P2P > encryption > Local Time: November 3, 2017 9:07 AM > UTC Time: November 3, 2017 1:07 PM > From: robert.withers(a)protonmail.com > To: SAAG <saag(a)ietf.org> > > Good morning, > > I am forwarding this announcement of the ParrotTalk v3.6 specification and > 2 reference implementations, in Squeak/Pharo and Java, to the SAAG list. I > was advised that this mailing list regarding the Security Area is the > correct home for this announcement. Below, I corrected the version of the > Squeak/Pharo ParrotTalk code to version 11, interoperable with the Java > version. I am proceeding to work on the Internet-Draft and I hope some > discussion builds around this work. > > Thank you. > - HH > > -------- Original Message -------- > Subject: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption > Local Time: November 2, 2017 9:19 PM > UTC Time: November 3, 2017 1:19 AM > From: henry(a)callistohouse.club > To: IETF <ietf(a)ietf.org> > > I have developed the ParrotTalk Protocol, and am starting an internet > draft document[1] for submission to the process at IETF. > > ParrotTalk Protocol is documented in part here[2], while I have two > implementations: 1 in Squeak/Pharo[3 a/b] and the other in Java[4 a/b]. The > particulars of MAC key and ivSequence derivation, as well as > constrained traffic signing, are the implementations, yet missing from the > specification. They will be added to the internet-draft. > > How do I go about submitting a specification for ParrotTalk for IETF > review and consideration? > > Thank you. > > - HH > - HH > - HH > - HH > - HH > - HH > - HH > - HH > > > > > > >

Nov. 5, 2017