I updated Pharo with Style.
I updated Pharo with Style.
Hi, There is a new release of P3, the modern, lean and mean PostgreSQL client for Pharo. https://github.com/svenvc/P3 Version 1.2 contains the following changes: - P3PreparedStatement is now joined by a polymorphic P3FormattedStatement working client side on text strings - P3PreparedStatement & P3FormattedStatement now share the same double dispatch mechanism to process argument binding - Added convenience methods #listDatabases #listSchemas & #listTablesInSchema: to P3Client - Added convenience methods #firstColumnData & #firstFieldOfFirstRecord to P3Result - Added dynamic ENUM support via #loadEnums in P3Client - Add support for the 7 geometric types POINT, CIRCLE, LINE, LSEG, POLYGON & PATH with corresponding objects P3Point, P3Circle, P3Line, P3LineSegment, P3Polygon & P3Path - Add support for the INTERVAL type with P3Interval object - Added P3Client>>#serverVersion accessor - Add support for BIT & VARBIT types with P3FixedBitString & P3BitString objects - Add TIMETZ support - Organised P3 package with tags - More & better documentation & unit tests https://github.com/svenvc/P3/releases/tag/v1.2 The quality of open source software is determined by it being alive, supported and maintained. The first way to help is to simply use P3 in your projects and report back about your successes and the issues that you encounter. You can ask questions on the Pharo mailing lists. Enjoy, Sven
Dear all, I am pleased to announce that registration for Pharo Days 2019 is now open! Pharo days is a gathering of the Pharo community to exchange, discuss and code with your online colleagues. Join us to share your experiences and help to make a better Pharo! To register, please proceed to the Pharo Days 2019 web page: https://pharo.org/2019PharoDays <https://pharo.org/2019PharoDays>, or go directly to the association event: https://association.pharo.org/event-3255426 <https://association.pharo.org/event-3255426>. (Yes, the schedule is still to be defined, stay tuned). If there are any questions or problems, I am happy to answer them. Esteban Ps: I’m sorry for multiple posts ;)
Hi list, We started Pharo 8.0 development and we wanted to share (and discuss, if needed) what is our current Roadmap for Pharo 8.0. As you can see, Windows is getting some love, and also UI. Anyway, here it is: Image === 1) Missing parts for headless VM to work (explained a bit later) 2) We need to improve Epicea speed. And in general, source access speed. We want to remove the old changes file (since Epicea already does that works and a lot more). 3) Improve Refactors 4) Improve Calypso 5) Introduce Spec2 (our re-work on this framework). - We also want to migrate our tools to it (Inspector, Debugger, Spotter and Calypso are the remaining parts). We will see how much of this migration can be done. VM/Low-level side === 1) headless vm We want to have a real headless VM and make it our default VM. To it, most of the work vm-side is already made by Ronie, but there are missing parts: - a build on windows - image side capabilities: we use SDL2 to start the world, and it mostly works... but not completely. One cool thing of this is that we will -finally- be able to clean the event handling, which is ugly (and works bad). 2) Windows several missing/non working parts: - file primitives are slow. This is because they rely in old APIs and we need to put them in "state of the art". - libgit2 does not processes long paths. We workarounded the problem with tonel, but at a point we need to take care about this. Real problem with this is we need to contribute the solution to libgit2, but this is also good Open Source policy (contributing back). - OSSubprocess in windows. We believe we need to extend OSSubprocess (our solution to communicate with system) to windows. And we believe is possible ;) 3) ThreadedFFI. It is already too much time since we have this in agenda. Is time to make it real. 4) memory policies. Tweaking the VM to enhance its memory usage is possible, but hard. We want to adopt an scheme of "memory policies" that will allow users to pick what they need. Process === 1) We will add multiple source directories to Iceberg. This is needed to allow us to put all Pharo sub-projects into an unique project without breaking modularisations. Others === 1) Launcher - Launcher us getting a new UI - Tests - It needs to be more solid (in part, that's the reason why we want OSSubprocess in windows). 2) Cargo - We need to revisit cargo (a new dependency manager) and at a point decide if it will fly or not :) Nice to have (most probably not this version, but in our TODO) : - embedded VM - event driven VM - what happens if we split VM into main thread and vm thread?
Hi all, Pharo Launcher 1.6 has just been released! It is available from http://pharo.org/download. This new version introduces two major changes: the list of template sources is now externalized as a Ston file. Pharo Launcher will check regularly (at startup and each day) if there are changes between your local source of templates and the one hosted in Pharo file server. If so, Pharo Launcher will propose you to update your template sources. It is a way to automatically get new official sources or to keep stable, dev versions up to date. a small UI is now available to manage VMs of PharoLauncher (update, remove, list). Also, this is the first release done with all sources coming from GitHub (https://github.com/pharo-project/pharo-launcher). Big thanks to all contributors, including issue reports. Here is the changelog: Pharo Launcher v1.6 <https://github.com/pharo-project/pharo-launcher/releases/tag/1.6> New features: #283 <https://github.com/pharo-project/pharo-launcher/issues/283> Template sources should be editable without modifying PL code #172 <https://github.com/pharo-project/pharo-launcher/issues/172> Provide a way to update / remove VMs #131 <https://github.com/pharo-project/pharo-launcher/issues/131> Display date for "Last Modified" on the form of "X day/month/year ago" Improvements: #295 <https://github.com/pharo-project/pharo-launcher/issues/295> Pharo 7 marked as (development version) #290 <https://github.com/pharo-project/pharo-launcher/issues/290> Add "latest" to indicate dynamic version development versions for Pharo 7.0 #299 <https://github.com/pharo-project/pharo-launcher/issues/299> About hot (more recently used) coloring schema #287 <https://github.com/pharo-project/pharo-launcher/issues/287> Launch button is enabled despite no Current image being selected (or present) #274 <https://github.com/pharo-project/pharo-launcher/issues/274> Copy and Rename command should not add a "-01" Bug fixes: #293 <https://github.com/pharo-project/pharo-launcher/issues/293> zipfile from 85bebb7 <https://github.com/pharo-project/pharo-launcher/commit/85bebb7dc75e7e78fac0f2cb02fde3ec384edbf0> has no source file #291 <https://github.com/pharo-project/pharo-launcher/issues/291> FileDoesNotExist error at Launcher startup #286 <https://github.com/pharo-project/pharo-launcher/issues/286> Buttons (Import > Launch an image...) are cut off in Windows 10 #281 <https://github.com/pharo-project/pharo-launcher/issues/281> Pharo Launcher does not go beyond Pharo 7 #1384 image Regards, The Pharo team.