Only a few days left for 2017. Thanks to all who helped shaping Pharos future.
May the lighthouse be with you in 2018 as well:
OpenSSL-Pharo now works on Windows. Tested on Windows 10 with a fresh 32-bit
Pharo 6.1 zip package downloaded from pharo.org. On Windows this library uses
libeay.dll which is bundled with the Pharo VM.
smalltalkhubUser: ‘PierceNg’ project: ‘OpenSSL-Pharo’;
And now I have added #macModuleName to the library and tested it successfully
with 64-bit Pharo on my Mac that runs Sierra.
Developed by students from FIT CTU in Prague and supervised by Prof. R. Pergl.
I’ve migrated Glorp v130, including GlorpSQLite, from smalltalkhub to
github using Peter Uhnak’s excellent git-migration tool, see:
To load Glorp:
To load Glorp with the UDBC SQLite drivers:
I’m not familiar with the other drivers, so I’m happy to help, but would
like some assistance before migrating the other drivers.
If I don’t hear any complaints in the next week I’ll eventually get
around to modifying the ConfigurationOfGlorp on smalltalkhub to use the
github version for Pharo 6.1 and 7.0. Older versions of Pharo will
continue to load Glorp from smalltalkhub.
If there’s an official account that should own this project, I’m more
than happy to hand it over.
> I guess part of what I’m interested in are patterns for hooking
> NeoJSON up to parse a REST response into objects to build a wrapper
> around a REST service. I see a chapter in Enterprise Pharo, which I’ll
> get to that soon. Perhaps I was premature asking before reading that,
> but its good to have a few paths to explore.
I’ve made a few REST Clients
And the elasticsearch one but its been advanced mostly lately by Sho Yoshida
He has also made REST clients for Twilio, AWS, SendGrid, Salesforce, and
Mixpanel among others.
Norbert Hartl made one for Mandrill (Mailchimps transactional email service)
And Francois Stephany made one for Postmark (another transactional email
So those are some examples of different approaches.
I also started/made a cross platform web client wrapper (just wraps calls to
ZnClient or WebClient on Squeak)
But IIRC I only used it in the Stripe API client.
Hope this gives you some ideas about how to approach your own solution
Thus, edges form constraints, and constraints are what layouts deal with. That is one reason why elements in bloc have the ability of defining layout-specific constraints. Using this, we can nicely define edges between elements as a plugin to Bloc, but still be able to connect arbitrary elements. What’s more, it turns out that we need constraints for other layouts as well. For example, an element in a grid layout might specify the span.