Blog

February 18th 2019

February 17th 2019

February 16th 2019

February 15th 2019

February 14th 2019

February 12th 2019

Final day of an 8-day long non-stop fulltime development sprint on the eno libraries! 🎉

Huge progress was made on a lot of tricky architectural questions for the next generation of eno libraries, restructuring and separation of concerns between the different repositories and projects happened, some 80% of the way to get all 4 existing eno libraries compatible with the final specification was traveled.

The coming weeks will see plenty of cleanup on the results, tying up loose ends and getting everything in shape for gradual release and announcement. Aaand a lot of documentation will need to be written or updated. ;)

February 4th 2019

February 3rd 2019

February 2nd 2019

January 26th 2019

January 19th 2019

January 16th 2019

January 14th 2019

January 13th 2019

January 12th 2019

January 10th 2019

January 6th 2019

January 4th 2019

January 3rd 2019

January 2nd 2019

January 1st 2019

December 31st 2018

December 30th 2018

December 25th 2018

December 23rd 2018

December 22nd 2018

December 21st 2018

December 15th 2018

December 14th 2018

December 11th 2018

December 9th 2018

December 8th 2018

December 7th 2018

December 5th 2018

December 4th 2018

December 2nd 2018

December 1st 2018

November 30th 2018

November 8th 2018

November 5th 2018

November 4th 2018

November 3rd 2018

November 2nd 2018

November 1st 2018

October 31st 2018

October 30th 2018

Today enophp reached feature-complete state! In the coming days the remaining missing parts of the testsuite will be implemented (which will likely entail some bugfixing), alongside some detail considerations around loaders. Also, importantly, the documentation for enophp on eno-lang.org will be set up. After that it's release time!

October 28th 2018

October 27th 2018

October 26th 2018

October 24th 2018

October 23rd 2018

After some time off to a) earn money and thereby cross-finance the next months of eno development, b) gather more insights in the currently largest production usecase of eno and c) recharge batteries :) development is now continuing!

Getting the enophp implementation feature-complete in november is the current development target, with the enors (rust) implementation coming up next on the roadmap, likely to commence around december.

September 25th 2018

September 9th 2018

September 2nd 2018

August 26th 2018

August 22nd 2018

August 19th 2018

August 18th 2018

August 17th 2018

August 15th 2018

August 13th 2018

August 9th 2018

August 4th 2018

July 28th 2018

July 28th 2018

July 27th 2018

July 26th 2018

July 25th 2018

July 24th 2018

July 22nd 2018

July 21st 2018

Dictionary elements are now called Fieldset elements. This change was long in the making, addressing a few issues and improving a few aspects of the original terminology, e.g.: Conceptually, sections are dictionaries as well (in the generic sense of the term), so this was rather ambiguous. Fieldset indicates the strong relation to fields - it's really just a way of grouping fields - whereas dictionary possibly indicated some larger, non-existant difference. Fieldset as a term also hints at fieldsets in HTML and forms in general, which is also desired because it's a more user-facing and user-friendly wording and concept.

Note that in the eno language context this is purely a non-functional change, it only modifies how the language construct is referred to in documentation, error messages, and by the APIs, but it does not change the way fieldsets/dictionaries work in any way.

July 20th 2018

July 18th 2018

July 17th 2018

July 15th 2018

July 14th 2018

July 13th 2018

July 11th 2018

July 10th 2018

July 9th 2018

July 8th 2018

July 7th 2018

July 6th 2018

July 5th 2018

July 4th 2018

July 3rd 2018

July 2nd 2018

July 1st 2018

June 30th 2018

June 29th 2018

June 28th 2018

June 27th 2018

June 26th 2018

June 25th 2018

June 24th 2018

June 23rd 2018

June 22nd 2018

June 21st 2018