Comments (21)
from phpspreadsheet.
I think if you target the modern PHP community, Composer is the thing to get users :) The PHP community is well educated regarding semver with Composer, so as long as you follow it and don't abuse of it it should go well even if the package is far from being stable.
from phpspreadsheet.
@ligeirinhorj according to the stack trace you are missing the extension gd
. That said I advise you to try an actual support plaftorm, e.g. StackOverflow, rather than highjacking an unrelated issue for it
from phpspreadsheet.
Not until it's properly stable enough
from phpspreadsheet.
Forced to make a choice at this point, I'd recommend using a more up-to-date version of PHPExcel (1.8.1 is the last production release of PHPExcel); but to be aware that a change to using PHPSpreadsheet in the future won't be backward compatible with PHPExcel
from phpspreadsheet.
As @shadiakiki1986 says above, if you're happy to accept the current instability and recommendations above, you can install with composer like this:
{
"repositories": [
{
"type": "vcs",
"url": "https://github.com/PHPOffice/PhpSpreadsheet"
}
],
"require": {
"PHPOffice/PhpSpreadsheet": "dev-master"
}
}
from phpspreadsheet.
@caponica Agreed. The section https://github.com/PHPOffice/PhpSpreadsheet#phpexcel-vs-phpspreadsheet- in the README.md mainly addresses contributions but should probably mention that PhpSpreadsheet is still in development
from phpspreadsheet.
I think it would be a good thing. We are far from being stable, but it would allow us to explicitly mark the code as alpha (and beta later on).
from phpspreadsheet.
+1 for Composer. I'd use it if it was available, alpha or beta. That means I'd discover bugs and report them, which would help improve the software overall. Without Composer I will not use it for the reasons mentioned by @theofidry.
I think that pattern applies to a lot of users. I don't see how making it available on composer would do any harm.
from phpspreadsheet.
@adamhopkinson the issue is about making good use of Composer for managing this package, stable or not, instead of giving a workaround to install a GitHub package with Composer.
from phpspreadsheet.
You can use the composer repositories
tag, documented here
from phpspreadsheet.
Not until it's properly stable enough
Would you rather recommend sticking to PHPExcel then? I'm starting a new feature on a project which already has PHPExcel 1.7.9 in it, and would like to know if you (the author's) would recommend using PHPSpreadsheet or PHPExcel?
from phpspreadsheet.
Could I recommend that you put a note in the root README.md that this project is not yet stable and that people coming to this new should still use PhpExcel?
Then, when PhpSpreadsheet is stable, update the README.md again.
from phpspreadsheet.
addressed in 699d11f
from phpspreadsheet.
Any reason why not using Composer still? I personally know no one using custom autoloader except for legacy reasons, and that's strongly discouraged as you can't benefit from the performance gains offered by composer and with the --authoritative-classmap
option, files autoloaded another way than composer will simply fail.
If the release is not stable, you can still tag it as alpha
, beta
or rc
. You have several PHP projects as examples.
from phpspreadsheet.
I am not against submitting to packagist as an alpha (or even without any releases), but unfortunately I don't have access to PHPOffice namespace over there. So that's up to @Progi1984 or @MarkBaker ...
from phpspreadsheet.
I let @MarkBaker choosing as lead dev of the project. But if he accepts, i can push the package on Packagist.
from phpspreadsheet.
I've added PHPSpreadsheet to Packagist, but I haven't modified the composer in any way to flag it as alpha yet
from phpspreadsheet.
👍
from phpspreadsheet.
Thanks, @mark, I'll tag an alpha release as soon as we decide whether the next version should be a 2.0 (because following PHPExcel versioning), or a 1.0 (because PhpSpreadsheet is a "new" project).
I would personally go for a 1.0 to break away as much as possible from PHPExcel. What do you think ?
from phpspreadsheet.
Can someone help me with the error below?
$ composer require phpoffice/phpspreadsheet
Using version ^1.2 for phpoffice/phpspreadsheet
./composer.json has been created
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- phpoffice/phpspreadsheet 1.2.1 requires ext-gd * -> the requested PHP extension gd is missing from your system.
- phpoffice/phpspreadsheet 1.2.0 requires ext-gd * -> the requested PHP extension gd is missing from your system.
- Installation request for phpoffice/phpspreadsheet ^1.2 -> satisfiable by phpoffice/phpspreadsheet[1.2.0, 1.2.1].
To enable extensions, verify that they are enabled in your .ini files:
- C:\Users\Ligeirinho\Downloads\php-7.2.4-nts-Win32-VC15-x64\php.ini
You can also run php --ini
inside terminal to see which files are used by PHP in CLI mode.
Installation failed, deleting ./composer.json.
from phpspreadsheet.
Related Issues (20)
- Cannot set culumn width HOT 2
- Axis Bounds not Recognised Correctly HOT 2
- Unable to hide comments if saving using data that already contains VML drawings. HOT 2
- Incorrect Attribute Value for forceFullCalc in writeCalcPr Method HOT 2
- Your requested sheet index: -1 is out of bounds. The actual number of sheets is 1 HOT 3
- Bug in "Trunc" class HOT 13
- Certain currency formats are handled incorrectly by formatter HOT 1
- Currency and Accounting format wizards unable to generate formats with ISO code currencies. HOT 1
- unable to install in latest version HOT 1
- Error open file Xlsx when modify value HOT 13
- Issue saving PDF file from Excel
- Applying data validation to an entire column HOT 2
- iconv(): Wrong encoding, conversion from "CP936" to "UTF-8" is not allowed HOT 2
- [Bug]: Incorrect definition of date data type HOT 1
- Error in MS Excel after filling XLSX form with PhpOffice\PhpSpreadsheet HOT 2
- Error exporting excel,zipstream usage error HOT 4
- slow execution introduced in pull request #4073 HOT 1
- CVE-2024-45048 in 1.x version
- Mark CVE-2024-45048 as fixed in version 1.29.1 HOT 3
- Unexpected Php8.4 Change Regarding CSV's HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from phpspreadsheet.