Paths represent the outline of a shape which can be filled, stroked, used as a clipping path, or any combination of the three. (See Filling, Stroking and Paint Servers and Clipping, Masking and Compositing.)
A path is described using the concept of a current point. In an analogy with drawing on paper, the current point can be thought of as the location of the pen. The position of the pen can be changed, and the outline of a shape (open or closed) can be traced by dragging the pen in either straight lines or curves.
Path Finder 8.3.8
Download Zip: https://urlcod.com/2vBd5R
Paths represent the geometry of the outline of an object, defined in terms of moveto (set a new current point), lineto (draw a straight line), curveto (draw a curve using a cubic Bézier), arc (elliptical or circular arc) and closepath (close the current shape by drawing a line to the last moveto) elements. Compound paths (i.e., a path with multiple subpaths) are possible to allow effects such as "donut holes" in objects.
Example triangle01 specifies a path in the shape of a triangle. (The M indicates a moveto, the Ls indicate linetos, and the z indicates a closepath).
Path data can contain newline characters and thus can be broken up into multiple lines to improve readability. Because of line length limitations with certain related tools, it is recommended that SVG generators split long path data strings across multiple lines, with each line not exceeding 255 characters. Also note that newline characters are only allowed at certain places within path data.
The syntax of path data is concise in order to allow for minimal file size and efficient downloads, since many SVG files will be dominated by their path data. Some of the ways that SVG attempts to minimize the size of path data are as follows:
The path data syntax is a prefix notation (i.e., commands followed by parameters). The only allowable decimal point is a Unicode U+0046 FULL STOP (".") character (also referred to in Unicode as PERIOD, dot and decimal point) and no other delimiter characters are allowed [UNICODE]. (For example, the following is an invalid numeric value in a path data stream: "13,000.56". Instead, say: "13000.56".)
The "moveto" commands (M or m) establish a new current point. The effect is as if the "pen" were lifted and moved to a new location. A path data segment (if there is one) must begin with a "moveto" command. Subsequent "moveto" commands (i.e., when the "moveto" is not the first command) represent the start of a new subpath:
The "closepath" (Z or z) ends the current subpath and causes an automatic straight line to be drawn from the current point to the initial point of the current subpath. If a "closepath" is followed immediately by a "moveto", then the "moveto" identifies the start point of the next subpath. If a "closepath" is followed immediately by any other command, then the next subpath starts at the same initial point as the current subpath.
Example cubic01 shows some simple uses of cubic Bézier commands within a path. The example uses an internal CSS style sheet to assign styling properties. Note that the control point for the "S" command is computed automatically as the reflection of the control point for the previous "C" command relative to the start point of the "S" command.
The following picture shows some how cubic Bézier curves change their shape depending on the position of the control points. The first five examples illustrate a single cubic Bézier path segment. The example at the lower right shows a "C" command followed by an "S" command.
Example quad01 shows some simple uses of quadratic Bézier commands within a path. Note that the control point for the "T" command is computed automatically as the reflection of the control point for the previous "Q" command relative to the start point of the "T" command.
The following illustrates the four combinations of large-arc-flag and sweep-flag and the four different arcs that will be drawn based on the values of these flags. For each case, the following path data command was used:
Each of the two lists are always kept synchronized. Modifications to one list will immediately cause the corresponding list to be modified. Modifications to normalizedPathSegList might cause entries in pathSegList to be broken into a set of normalized path segments.
Hi @BernSh, I'll give you MY perspective on PF, but YMMV. I've used PF since version 4 I think until version 8 came out. With version 8, they decided to start from scratch to get with Apples new way of doing things under the hood and make a more modern version of their software. This is all good in theory, but in practice, well, not so much. You were talking about synching favorites from the Finder to PF, well, in version 7, it worked, in 8 it doesn't. Granted, in 7 it was a hack and they wanted to be a good Apple citizen so now they go by the rules, but for people who have used the software for while, this was a big issue. Stability with version 8 is still an issue if you look at the forum so I removed it completly from all my computers and either use the finder, or if I want two panel browsing, which was one of the nice feature of PF, I now use Forklift. I also liked the dropstack feature, which still works in v8, but now I'm using Yoink to do the same. Granted I need two software to do what PF was doing all on it's own, but for stability and speed, I decided to leave PF. I might check on it a bit later, or at version 9, you never know, but for now, no. Like I said, this is just MY experience with the software. I agree that they could be more transparent about how they release update, what gets fixed and have support team that actually answers your questions, but hey, it's a hard business and wish them all good luck.To make this post a bit more relevant to the forum we are using to discuss it. I don't know how @peternlewis is doing all this by himself, hats off to him!
The Pathfinder team did not help their case when PF 8 was introduced by poor/no communication. There is no obvious person fronting Pathfinder in the manner of KM. Also, some of the support persons responses were perplexing.
So users have no idea where Pathfinder is going, or even if there is serious attempt to rectify things like lack of Favourites Sync with Finder, (or if it is even feasible). You will note despite a tumultuous launch the Pathfinder Web Pages contain only a launch blog/commentary and this has never been added to.
The big picture here is that Pathfinder by its nature is a central platform for the workflows of users both consumer and business; yet the experience of recent months could lead users to wonder about its future & development pathway.
Pathfinder (8) is a great App and I am still using it. The Pathfinder team need to find a way to communicate better with their users who will be more supportive if they could understand better what is going on and the road ahead.
The one downside to Pathfinder has always been, they will acknowledge bugs/issues, and say they will investigate. History shows though, that years on, or many months on, nothing is done and users don't know where they stand. This uncertainty is really frustrating and self-defeating as PF must have lost a lot of users to Forklift post launch of PF8. Forklift by comparison has generally very positive feedback from users about the communication with the developer.
In the sidebar, Folders can be dragged to the area headed Favourites. This has caused confusion because it is not the same as Favourites in the User Library, however, a user can drag this folder on to the sidebar and have Favourites Folder under Favourites. This has lead to the suggestion that Pathfinder should change the name of this section to Places. The sidebar seemingly continues to be the most contentious area of PF8. Some of the equivalent stuff presentation/layout wise in Forklift is far better.
The one downside to Pathfinder has always been, they will acknowledge bugs/issues, and say they will investigate. History shows though, that years on, or many months on, nothing is done and users don't know where they stand.
Problem 1 - drupal/console 1.8.0 requires drupal/console-core 1.8.0 -> satisfiable by drupal/console-core[1.8.0]. - drupal/console 1.7.0 requires drupal/console-core 1.7.0 -> satisfiable by drupal/console-core[1.7.0]. - drupal/console 1.6.1 requires drupal/console-core 1.6.1 -> satisfiable by drupal/console-core[1.6.1]. - drupal/console 1.6.0 requires drupal/console-core 1.6.0 -> satisfiable by drupal/console-core[1.6.0]. - drupal/console 1.5.0 requires drupal/console-core 1.5.0 -> satisfiable by drupal/console-core[1.5.0]. - drupal/console 1.4.0 requires drupal/console-core 1.4.0 -> satisfiable by drupal/console-core[1.4.0]. - drupal/console 1.3.2 requires drupal/console-core 1.3.2 -> satisfiable by drupal/console-core[1.3.2]. - drupal/console 1.3.1 requires drupal/console-core 1.3.1 -> satisfiable by drupal/console-core[1.3.1]. - drupal/console 1.3.0 requires drupal/console-core 1.3.0 -> satisfiable by drupal/console-core[1.3.0]. - drupal/console 1.2.0 requires drupal/console-core 1.2.0 -> satisfiable by drupal/console-core[1.2.0]. - drupal/console 1.1.1 requires drupal/console-core 1.1.1 -> satisfiable by drupal/console-core[1.1.1]. - drupal/console 1.1.0 requires drupal/console-core 1.1.0 -> satisfiable by drupal/console-core[1.1.0]. - drupal/console 1.0.2 requires drupal/console-core 1.0.2 -> satisfiable by drupal/console-core[1.0.2]. - drupal/console 1.0.1 requires drupal/console-core 1.0.1 -> satisfiable by drupal/console-core[1.0.1]. - drupal/console 1.0.0-rc26 requires drupal/console-core 1.0.0-rc26 -> satisfiable by drupal/console-core[1.0.0-rc26]. - drupal/console 1.0.0-rc25 requires drupal/console-core 1.0.0-rc25 -> satisfiable by drupal/console-core[1.0.0-rc25]. - drupal/console 1.0.0-rc24 requires drupal/console-core 1.0.0-rc24 -> satisfiable by drupal/console-core[1.0.0-rc24]. - drupal/console 1.0.0-rc23 requires drupal/console-core 1.0.0-rc23 -> satisfiable by drupal/console-core[1.0.0-rc23]. - drupal/console 1.0.0-rc22 requires drupal/console-core 1.0.0-rc22 -> satisfiable by drupal/console-core[1.0.0-rc22]. - drupal/console 1.0.0-rc21 requires drupal/console-core 1.0.0-rc21 -> satisfiable by drupal/console-core[1.0.0-rc21]. - drupal/console 1.0.0-rc20 requires drupal/console-core 1.0.0-rc20 -> satisfiable by drupal/console-core[1.0.0-rc20]. - drupal/console 1.0.0 requires drupal/console-core 1.0.0 -> satisfiable by drupal/console-core[1.0.0]. - drupal/console-core 1.8.0 requires webflo/drupal-finder ^1.0 -> satisfiable by webflo/drupal-finder[1.0.0, 1.1.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.7.0 requires webflo/drupal-finder ^1.0 -> satisfiable by webflo/drupal-finder[1.0.0, 1.1.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.6.1 requires webflo/drupal-finder ^1.0 -> satisfiable by webflo/drupal-finder[1.0.0, 1.1.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.6.0 requires webflo/drupal-finder ^1.0 -> satisfiable by webflo/drupal-finder[1.0.0, 1.1.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.5.0 requires webflo/drupal-finder ^1.0 -> satisfiable by webflo/drupal-finder[1.0.0, 1.1.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.4.0 requires webflo/drupal-finder ^1.0 -> satisfiable by webflo/drupal-finder[1.0.0, 1.1.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.3.2 requires webflo/drupal-finder ^1.0 -> satisfiable by webflo/drupal-finder[1.0.0, 1.1.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.3.1 requires webflo/drupal-finder ^1.0 -> satisfiable by webflo/drupal-finder[1.0.0, 1.1.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.3.0 requires webflo/drupal-finder ^1.0 -> satisfiable by webflo/drupal-finder[1.0.0, 1.1.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.2.0 requires webflo/drupal-finder ^1.0 -> satisfiable by webflo/drupal-finder[1.0.0, 1.1.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.1.1 requires webflo/drupal-finder ^1.0 -> satisfiable by webflo/drupal-finder[1.0.0, 1.1.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.1.0 requires webflo/drupal-finder ^1.0 -> satisfiable by webflo/drupal-finder[1.0.0, 1.1.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.0.2 requires webflo/drupal-finder ^1.0 -> satisfiable by webflo/drupal-finder[1.0.0, 1.1.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.0.1 requires webflo/drupal-finder ^1.0 -> satisfiable by webflo/drupal-finder[1.0.0, 1.1.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.0.0-rc26 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.0.0-rc25 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.0.0-rc24 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.0.0-rc23 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.0.0-rc22 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.0.0-rc21 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.0.0-rc20 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0] but these conflict with your requirements or minimum-stability. - drupal/console-core 1.0.0 requires webflo/drupal-finder ^0.3.0 -> satisfiable by webflo/drupal-finder[0.3.0] but these conflict with your requirements or minimum-stability. - Conclusion: don't install symfony/config v2.8.46 - Conclusion: don't install symfony/config v2.8.45 - Conclusion: don't install symfony/config v2.8.44 - Conclusion: don't install symfony/config v2.8.43 - Conclusion: don't install symfony/config v2.8.42 - Conclusion: don't install symfony/config v2.8.41 - Conclusion: don't install symfony/config v2.8.40 - Conclusion: don't install symfony/config v2.8.39 - Conclusion: don't install symfony/config v2.8.38 - Conclusion: don't install symfony/config v2.8.37 - Conclusion: don't install symfony/config v2.8.36 - Conclusion: don't install symfony/config v2.8.35 - Conclusion: don't install symfony/config v2.8.34 - Conclusion: don't install symfony/config v2.8.33 - Conclusion: don't install symfony/config v2.8.32 - Conclusion: don't install symfony/config v2.8.31 - Conclusion: don't install symfony/config v2.8.30 - Conclusion: don't install symfony/config v2.8.29 - Conclusion: don't install symfony/config v2.8.28 - Conclusion: don't install symfony/config v2.8.27 - Conclusion: don't install symfony/config v2.8.26 - Conclusion: don't install symfony/config v2.8.25 - Conclusion: don't install symfony/config v2.8.24 - Conclusion: don't install symfony/config v2.8.23 - Conclusion: don't install symfony/config v2.8.22 - Conclusion: don't install symfony/config v2.8.21 - Conclusion: don't install symfony/config v2.8.20 - drupal/console 1.0.0-rc19 requires drupal/console-core 1.0.0-rc19 -> satisfiable by drupal/console-core[1.0.0-rc19]. - Conclusion: don't install drupal/console-core 1.0.0-rc19 - Conclusion: don't install symfony/config v2.8.19 - Conclusion: don't install symfony/config v2.8.18 - Conclusion: don't install symfony/config v2.8.17 - Conclusion: don't install symfony/config v2.8.16 - Conclusion: don't install symfony/config v2.8.15 - Conclusion: don't install symfony/config v2.8.14 - Conclusion: don't install symfony/config v2.8.13 - Conclusion: don't install symfony/config v2.8.12 - Conclusion: don't install symfony/config v2.8.11 - Conclusion: don't install symfony/config v2.8.10 - Conclusion: don't install symfony/config v2.8.9 - Conclusion: don't install symfony/config v2.8.8 - Conclusion: don't install symfony/config v2.8.7 - Conclusion: don't install symfony/config v2.8.6 - Conclusion: don't install symfony/config v2.8.5 - Conclusion: don't install symfony/config v2.8.4 - Conclusion: don't install symfony/config v2.8.3 - Conclusion: don't install symfony/config v2.8.2 - Conclusion: don't install symfony/config v2.8.1 - Conclusion: don't install symfony/config v2.8.0 - drupal/console 1.0.0-rc18 requires drupal/console-core 1.0.0-rc18 -> satisfiable by drupal/console-core[1.0.0-rc18]. - Conclusion: don't install drupal/console-core 1.0.0-rc18 - Conclusion: don't install drupal/console 1.0.0-rc17 - Conclusion: don't install drupal/console 1.0.0-rc16 - Conclusion: don't install drupal/console 1.0.0-rc15 - Conclusion: don't install drupal/console 1.0.0-rc14 - Conclusion: don't install drupal/console 1.0.0-rc13 - Conclusion: don't install drupal/console 1.0.0-rc12 - Installation request for drupal/core 8.0 -> satisfiable by drupal/core[8.0.0, 8.0.0-beta10, 8.0.0-beta11, 8.0.0-beta12, 8.0.0-beta13, 8.0.0-beta14, 8.0.0-beta15, 8.0.0-beta16, 8.0.0-beta6, 8.0.0-beta7, 8.0.0-beta8, 8.0.0-beta9, 8.0.0-rc1, 8.0.0-rc2, 8.0.0-rc3, 8.0.0-rc4, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.x-dev, 8.1.0, 8.1.0-beta1, 8.1.0-beta2, 8.1.0-rc1, 8.1.1, 8.1.10, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.x-dev, 8.2.0, 8.2.0-beta1, 8.2.0-beta2, 8.2.0-beta3, 8.2.0-rc1, 8.2.0-rc2, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.x-dev, 8.3.0, 8.3.0-alpha1, 8.3.0-beta1, 8.3.0-rc1, 8.3.0-rc2, 8.3.1, 8.3.2, 8.3.3, 8.3.4, 8.3.5, 8.3.6, 8.3.7, 8.3.8, 8.3.9, 8.3.x-dev, 8.4.0, 8.4.0-alpha1, 8.4.0-beta1, 8.4.0-rc1, 8.4.0-rc2, 8.4.1, 8.4.2, 8.4.3, 8.4.4, 8.4.5, 8.4.6, 8.4.7, 8.4.8, 8.4.x-dev, 8.5.0, 8.5.0-alpha1, 8.5.0-beta1, 8.5.0-rc1, 8.5.1, 8.5.2, 8.5.3, 8.5.4, 8.5.5, 8.5.6, 8.5.7, 8.5.8, 8.5.x-dev, 8.6.0, 8.6.0-alpha1, 8.6.0-beta1, 8.6.0-beta2, 8.6.0-rc1, 8.6.1, 8.6.2, 8.6.x-dev, 8.7.x-dev]. - Conclusion: don't install drupal/console 1.0.0-rc11 - Conclusion: don't install drupal/console 1.0.0-rc10 - Conclusion: don't install drupal/console 1.0.0-rc9 - Conclusion: don't install drupal/console 1.0.0-rc8 - Conclusion: don't install drupal/console 1.0.0-rc7 - Conclusion: don't install drupal/console 1.0.0-rc6 - Conclusion: don't install drupal/console 1.0.0-rc5 - Conclusion: don't install drupal/console 1.0.0-rc4 - Conclusion: don't install drupal/console 1.0.0-rc3 - Conclusion: don't install drupal/console 1.0.0-rc2 - Conclusion: don't install drupal/console 1.0.0-rc1 - Conclusion: don't install symfony/config v2.8.0-BETA1 - Installation request for drupal/og 1.x-dev -> satisfiable by drupal/og[1.x-dev]. - drupal/console 1.0.0-alpha1 requires symfony/config 2.8 -> satisfiable by symfony/config[2.8.x-dev, v2.8.0, v2.8.0-BETA1, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.40, v2.8.41, v2.8.42, v2.8.43, v2.8.44, v2.8.45, v2.8.46, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9]. - drupal/console 1.0.0-alpha2 requires symfony/config 2.8 -> satisfiable by symfony/config[2.8.x-dev, v2.8.0, v2.8.0-BETA1, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.40, v2.8.41, v2.8.42, v2.8.43, v2.8.44, v2.8.45, v2.8.46, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9]. - drupal/console 1.0.0-beta1 requires symfony/config 2.8 -> satisfiable by symfony/config[2.8.x-dev, v2.8.0, v2.8.0-BETA1, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.40, v2.8.41, v2.8.42, v2.8.43, v2.8.44, v2.8.45, v2.8.46, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9]. - drupal/console 1.0.0-beta2 requires symfony/config 2.8 -> satisfiable by symfony/config[2.8.x-dev, v2.8.0, v2.8.0-BETA1, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.40, v2.8.41, v2.8.42, v2.8.43, v2.8.44, v2.8.45, v2.8.46, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9]. - drupal/console 1.0.0-beta3 requires symfony/config 2.8 -> satisfiable by symfony/config[2.8.x-dev, v2.8.0, v2.8.0-BETA1, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.40, v2.8.41, v2.8.42, v2.8.43, v2.8.44, v2.8.45, v2.8.46, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9]. - drupal/console 1.0.0-beta4 requires symfony/config 2.8 -> satisfiable by symfony/config[2.8.x-dev, v2.8.0, v2.8.0-BETA1, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.40, v2.8.41, v2.8.42, v2.8.43, v2.8.44, v2.8.45, v2.8.46, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9]. - drupal/console 1.0.0-beta5 requires symfony/config 2.8 -> satisfiable by symfony/config[2.8.x-dev, v2.8.0, v2.8.0-BETA1, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.34, v2.8.35, v2.8.36, v2.8.37, v2.8.38, v2.8.39, v2.8.4, v2.8.40, v2.8.41, v2.8.42, v2.8.43, v2.8.44, v2.8.45, v2.8.46, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9]. - Conclusion: don't install symfony/config 2.8.x-dev - Installation request for drupal/console 1.0 -> satisfiable by drupal/console[1.0.0, 1.0.0-alpha1, 1.0.0-alpha2, 1.0.0-beta1, 1.0.0-beta2, 1.0.0-beta3, 1.0.0-beta4, 1.0.0-beta5, 1.0.0-rc1, 1.0.0-rc10, 1.0.0-rc11, 1.0.0-rc12, 1.0.0-rc13, 1.0.0-rc14, 1.0.0-rc15, 1.0.0-rc16, 1.0.0-rc17, 1.0.0-rc18, 1.0.0-rc19, 1.0.0-rc2, 1.0.0-rc20, 1.0.0-rc21, 1.0.0-rc22, 1.0.0-rc23, 1.0.0-rc24, 1.0.0-rc25, 1.0.0-rc26, 1.0.0-rc3, 1.0.0-rc4, 1.0.0-rc5, 1.0.0-rc6, 1.0.0-rc7, 1.0.0-rc8, 1.0.0-rc9, 1.0.1, 1.0.2, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.3.1, 1.3.2, 1.4.0, 1.5.0, 1.6.0, 1.6.1, 1.7.0, 1.8.0]. 2ff7e9595c
Comments