Monthly Archiv: November, 2018

Trans Fats banned in New York City restaurants

I wrote a bit a couple of weeks ago about Trans fats and the fact that New York city was going to be perhaps banning trans fats in restaurants. Well it has happened. I just saw the news break and that means that today there will be stories in the news all about What trans fats are, how they are bad for us, and how much we should consume. I hope that you remember that past article as it seems that there is not healthy amount of trans fats to consume so any amount is to much. It will be interesting to see what happens now as I once heard that there are 20 or so Macdonalds restaurants in Manhattan itself let alone the other outlying boroughs.

As you probably remember trans fats are create by making hydrogenated vegetable oil, that is pumping hydrogen through Vegetable oil to give it a longer shelf life and

The Board of Health has voted to make New York the first city in the nation to ban artificial trans fats in restaurant food. The board is expected to give restaurants a slight break by relaxing what had been considered a tight deadline for compliance.

The board also ordered restaurants to standardize how they display the number of calories in dishes on their menus in an effort to combat obesity. This means that perhaps we will start to get better information on fat and calorie contents of foods everywhere so that we can make better decisions than just picking the “healthy Choice menu item at the local restaurant.

Here is a graph from the Associated Press showing some trans fat facts:

Trans Fats banned in New York City restaurants

PHP Reference Variable Debug

Package:
PHP Reference Variable Debug
Summary:
Check if a variable is a reference to another one
Groups:
Debug, Language, PHP 5
Author:
zinsou A.A.E.Moïse
Description:
This class can check if a variable is a reference to another one...

Read more at https://www.phpclasses.org/package/10915-PHP-Check-if-a-variable-is-a-reference-to-another-one.html#2018-11-01-13:20:55

Trans Fats banned in New York City restaurants

I wrote a bit a couple of weeks ago about Trans fats and the fact that New York city was going to be perhaps banning trans fats in restaurants. Well it has happened. I just saw the news break and that means that today there will be stories in the news all about What trans fats are, how they are bad for us, and how much we should consume. I hope that you remember that past article as it seems that there is not healthy amount of trans fats to consume so any amount is to much. It will be interesting to see what happens now as I once heard that there are 20 or so Macdonalds restaurants in Manhattan itself let alone the other outlying boroughs.

As you probably remember trans fats are create by making hydrogenated vegetable oil, that is pumping hydrogen through Vegetable oil to give it a longer shelf life and

The Board of Health has voted to make New York the first city in the nation to ban artificial trans fats in restaurant food. The board is expected to give restaurants a slight break by relaxing what had been considered a tight deadline for compliance.

The board also ordered restaurants to standardize how they display the number of calories in dishes on their menus in an effort to combat obesity. This means that perhaps we will start to get better information on fat and calorie contents of foods everywhere so that we can make better decisions than just picking the “healthy Choice menu item at the local restaurant.

Here is a graph from the Associated Press showing some trans fat facts:

Trans Fats banned in New York City restaurants

Garcinia Cambogia Extract Market Analysis, Trends, Forecast, 2017-2027

Garcinia Cambogia a small, sweet tropical tree fruit also known as Malabar tamarind. Other names for Garcinia Cambogia are Assam Fruit, Gorakkapulli, Panampulli, Manda Huli, Goraka Pulli, Mangosteen, and Vadakkan Puli. Garcinia Cambogia is obtained in different colors depending on the spices such as yellow, green and red. Garcinia Cambogia extract is a hub of vitamins B, Thiamin, Folic Acid, Niacin, Magnesium, Vitamin C, Manganese, Potassium and Hydroxycitric Acid (HCA). Hydroxycitric Acid in Garcinia Cambogia Extract is appetite suppressant which reduces cravings and decrease the urge to consume calories. Hydroxycitric Acid also helps in managing stress hormones, increase serotonin level, speed up metabolism leading to better mood sleep and reduce belly fat. Garcinia Cambogia Extract not only improves your overall health, but also prohibits the conversion of calories into fat. Hydroxycitric Acid inhibits the production of an enzyme that slows down the metabolism rate of the body. Because of this, the body converts the extra calories into glycogen. Garcinia Cambogia extract also helps the body to build more muscles.

Market Segmentation:

Garcinia Cambogia Extract market is segment on the basis of form, distribution channel and region. On the basis of form market is segmented into powder, capsule and liquid.Garcinia Cambogia Extract come in different forms but the most popular form is the powdered form. Weight loss has become a common desire for many people these days and with huge rage of alternatives available it becomes quite difficult task for consumers to select one which they want for themselves. Exactly what makes garcinia cambogia extract powder hugely popular is the fact that it is natural, safe to consume and has proven positive results for weight loss. Garcinia cambogia extract powder with 100% HCA is probably the best remedies for weight loss. On the basis of distribution channel the market is segmented into supermarkets/hypermarkets, convenience stores, medical stores and online stores. Online Stores is expected to hold a relatively high share in the garcinia cambogia extract market. Medical stores have also contributed significantly to the growth of Garcinia cambogia extract market over the forecast period. On the basis of region garcinia cambogia extractmarket is segmented into North America, Latin America, Western Europe, Eastern Europe, Asia Pacific, MEA and Japan.

Market Regional Outlook: Regional segment for the market of asparagus is divided into seven different regions: North America, Latin America, Western Europe, Eastern Europe, Asia Pacific, MEA and Japan. Among these segment Asia Pacific is expected to have the major market share globally, as it is the largest consumer of garcinia cambogia extract. In Asia Pacific region the India is generating the major revenue. In terms of revenue Africa is the second prominent contributor in the garcinia cambogia extractmarket.

Market Drivers: The rise in demand for weight loosing supplement is expected to drive the growth of global garcinia cambogia extract market. Garcinia cambogia extract is not only used as a supplement for weight reduction but it also exhibits some special properties such as it helps to reduce the cortisol level, reduce risk of heart disease, reduce risk of ulcer and improve lipid profile. It also helps in maintaining better metabolism and better cardiovascular health. The versatile properties of garcinia cambogia extracthas defiantly attracted the pharmaceutical companies which will drive the garcinia cambogia extract market to a greater extent.Moreover, the market is also driven by the increasing awareness among the consumers about the health benefits associated with garcinia cambogia extract.

Market Key Players:

Some of the key players in garcinia cambogia extractmarket are Power up health, BioGanix, Nature wise, Naturabest, NOW Foods, Top Secret Nutrition, Natrol, Global Health Ideas, Quality Encapsulations, shape organics,Search Results, Potent Organics, St.Botanica, Healthawin, Whole Body Research, NutriRise, PureNutria, Gaia Science? and  Morpheme Remedies among others.

Request for sample report: https://www.futuremarketinsights.com/reports/sample/rep-gb-2587

Article source: https://www.findmarketresearch.org/2018/11/garcinia-cambogia-extract-market-analysis-trends-forecast-2017-2027/

Quarterly Updates | Q3 2018

To keep everyone aware of big projects and efforts across WordPress contributor teams, I’ve reached out to each team’s listed representatives. I asked each of them to share their Top Priority (and when they hope for it to be completed), as well as their biggest Wins and Worries. Have questions? I’ve included a link to each team’s site in the headings.

Accessibility

  • Contacted: @joedolson, @audrasjb, @arush
  • Priority: Work on authoring a manual for assistive technology users on Gutenberg, led by Claire Brotherton (@abrightclearweb). Continue to work on improving the overall user experience in Gutenberg. Update and organize the WP A11y handbook.
  • Struggle: Lack of developers and accessibility experts to help test and code the milestone issues. Still over 100 outstanding issues, and developing the Gutenberg AT manual helps expose additional issues. The announcement of an accessibility focus on 4.9.9 derailed our planning for Gutenberg in September with minimal productivity, as that goal was quickly withdrawn from the schedule.
  • Big Win: Getting focus constraint implemented in popovers and similar components in Gutenberg.

CLI

  • Contacted: @danielbachhuber, @schlessera
  • Priority: Current priority is v2.1.0 of WP-CLI, to polish the major refactoring v2.0.0 introduced. You can join in or follow progress on their site.
  • Struggle: Getting enough contributors to make peer-review possible/manageable.
  • Big Win: The major refactoring of v2 was mostly without any negative impacts on existing installs. It provided substantial improvements to maintainability including: faster and more reliable testing, more straight-forward changes to individual packages, and simpler contributor on-boarding.

Community

Core

  • Contacted: @jeffpaul
  • Priority: Continued preparation for the 5.0 release cycle and Gutenberg.
  • Struggle: Identifying tasks for first time contributors, as well as for new-to-JS contributors.

Design

  • Contacted: @melchoyce, @karmatosed, @boemedia, @joshuawold, @mizejewski
  • Priority: Preparing for WordPress 5.0 and continuing to work on better onboarding practices.
  • Struggle: Identifying tasks for contributor days, especially for small- to medium-sized tasks that can be fit into a single day.
  • Big Win: Regular contributions are starting to build up.

Documentation

  • Contacted: @kenshino
  • Priority: Getting HelpHub out before WordPress 5.0’s launch to make sure Gutenberg User Docs have a permanent position to reside
  • Struggle: Getting the documentation from HelpHub into WordPress.org/support is more manual than initially anticipated.
  • Big Win: Had a good discussion with the Gutenberg team about their docs and how WordPress.org expects documentation to be distributed (via DevHub, Make and HelpHub). Getting past the code blocks to release HelpHub (soon)

Hosting

  • Contacted: @mikeschroder, @jadonn
  • Priority: Helping Gutenberg land well at hosts for users in 5.0.
  • Struggle: Short time frame with few resources to accomplish priority items.
  • Big Win: Preparing Try Gutenberg support guide for hosts during the rollout and good reception from users following it.

Marketing

  • Contacted: @bridgetwillard
  • Priority: Continuing to write and publish case studies from the community.
  • Big Win: Onboarding guide is going well and is currently being translated.

Meta (WordPress.org Site)

  • Contacted: @tellyworth, @coffee2code
  • Priority: Support for other teams in the lead up to, and the follow-up of, the release of WP 5.0. ETA is the WP 5.0 release date (Nov 19) and thereafter, unless it gets bumped to next quarter.
  • Struggle: Maintaining momentum on tickets (still).
  • Big Win: Launch of front-end demo of Gutenberg on https://wordpress.org/gutenberg/

Mobile

  • Contacted: @elibud
  • Priority: Have an alpha version of Gutenberg in the WordPress apps, ETA end of year 2018.
  • Struggle: Unfamiliar tech stack and the goal of reusing as much of Gutenberg-web’s code as possible.
  • Big Win: Running mobile tests on web’s PRs.

Plugins

  • Contacted: @ipstenu
  • Priority: Cleaning up ‘inactive’ users, which was supposed to be complete but some work preparing for 5.0 was necessary.
  • Struggles: Devnotes are lacking for the upcoming release which slows progress.
  • Big Win: No backlog even though a lot were out!

Polyglots

Support

  • Contacted: @clorith
  • Priority: Preparing for the upcoming 5.0 release
  • Struggle: Finding a good balance between how much we want to help people and how much we are able to help people. Also, contributor recruitment (always a crowd favorite!)
  • Big Win: How well the team, on a global level, has managed to maintain a good flow of user engagement through support.

Theme Review

  • Contacted: @acosmin, @rabmalin, @thinkupthemes, @williampatton
  • Priority: Implementing the Theme Sniffer plugin on WordPress.org which is one step forward towards automation. ETA early 2019
  • Struggle: Not having so many contributors/reviewers.
  • Big Win: Implementing multiple requirements into our review flow, like screenshots and readme.txt requirements.

Training

  • Contacted: @bethsoderberg, @juliek
  • Priority: Getting the learn.wordpress.org site designed, developed, and being able to publish lesson plans to it.
  • Struggle: Getting contributors onboard and continually contributing. Part of that is related to the learn.wordpress.org site. People like to see their contributions.
  • Big Win: We have our new workflow and tools in place. We are also streamlining that process to help things go from idea to publication more quickly.

Interested in updates from the last quarter? You can find those here: https://wordpress.org/news/2018/07/quarterly-updates-q2-2018/

The Month in WordPress: October 2018

Teams across the WordPress project are working hard to make sure everything is ready for the upcoming release of WordPress 5.0. Find out what’s going on and how you can get involved.


The Plan for WordPress 5.0

Early this month, the planned release schedule was announced for WordPress 5.0, which was updated a few weeks later. WordPress 5.0 is a highly anticipated release, as it’s the official  launch of Gutenberg — the new block editor for WordPress Core. For more detail, check out this  granular timeline.

Along with the planned release schedule, @matt, who is heading up this release, announced leads for critical focuses on the project, including @matveb, @karmatosed, @laurelfulford, @allancole, @lonelyvegan, @omarreiss, @antpb, @pento, @chanthaboune, @danielbachhuber, and @mcsf.

WordPress 5.0 is currently in its second beta phase and will soon move to the release candidate status. Help test this release right now by installing the WordPress Beta Tester plugin on your site.

Want to get involved in building WordPress Core? Follow the Core team blog and join the #core channel in the Making WordPress Slack group. You can also help out by testing or translating the release into a local language.

New Editor for WordPress Core

Active development continues on Gutenberg, the new editing experience for WordPress Core. The latest release is feature complete, meaning that all further development on it will be to improve existing features and fix outstanding bugs.

Some have raised concerns about Gutenberg’s accessibility, prompting the development team to detail some areas in which the new editor is accessible. To help improve things further, the team has made a public call for accessibility testers to assist.

Want to get involved in building Gutenberg? Follow the Gutenberg tag on the Core team blog and join the #core-editor channel in the Making WordPress Slack group. Read this guide to find areas where you can have the most impact.

Migrating HelpHub to WordPress.org

HelpHub is an ongoing project to move all of WordPress’ user documentation from the Codex to the WordPress Support portal.

HelpHub has been developed on a separate staging server and it’s now time to migrate the new documentation to its home on WordPress.org. The plan is to have everything moved over  before WordPress 5.0 is released, so that all the new documentation will be available on the new platform from the start.

The HelpHub team has published a call for volunteers to help with the migration. If you would like to get involved, join the #docs channel in the Making WordPress Slack group, and contact @atachibana to get started.

A New Default Theme for WordPress

A brand new default theme — Twenty Nineteen — has been announced with development being led by @allancole. The theme is packaged with WordPress 5.0, so it will be following the same release schedule as Core.

The new theme is designed to integrate seamlessly with Gutenberg and showcase how you can build a theme alongside the new block editor and take advantage of the creative freedom that it offers.

Want to help build Twenty Nineteen? Join in on the theme’s GitHub repo and join the #core-themes channel in the Making WordPress Slack group.


Further Reading:

  • The Support team are putting together more formal Support Guidelines for the WordPress Support Forums.
  • The group focused on privacy tools in Core has released some details on the work they have been doing recently, with a roadmap for their plans over the next few months.
  • The Core team released an update about how WordPress will be compatible with PHP 7.3.
  • The Theme Review Team have published some new requirements regarding child themes, readme files and trusted authors in the Theme Directory.
  • The WordCamp Europe team are working on a PWA service for all WordCamp websites.

If you have a story we should consider including in the next “Month in WordPress” post, please submit it here.

Powered by Gewgley