Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 [18] [18]:: one page |
|
Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Dragonaire
Here there be Dragons
54
|
Posted - 2014.06.27 20:59:00 -
[511] - Quote
Okay been thinking about the above end of life on PHP 5.3 and thought I'd ask for some input from current users of Yapeal and other people interested in using it. You may have to do a little research with your hosting site for the answer.
If the next version of Yapeal required at least PHP 5.4 would anybody have problems with their site?
Main reason I'm asking is I would prefer with the current re-write to go ahead and make it for PHP 5.4 as there are some features that Yapeal can take advantage of if it's not going to cause to many problems for people. First thing that this would do is allow Yapeal to use PHP traits which because of both the design of Yapeal and the Eve APIs could be very useful.
Anyway would like to hear everyone's thoughts on this. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Tiberius Zol
19
|
Posted - 2014.06.30 13:12:00 -
[512] - Quote
Used 5.2 until now. But changed to 5.4 now. :) so no problem with it. |
Dragonaire
Here there be Dragons
55
|
Posted - 2014.07.10 15:37:00 -
[513] - Quote
Just a quick update for everyone. PHP5.4 will be required for the next version of Yapeal as some of the new language structures just make a huge difference on the amount of duplicate code needed. I've spent last week and a half or so on re-factoring a lot of stuff and now many of the class can have only a single method and maybe a single property vs 3-4 methods and several properties. The main thing that PHP 5.4 give is Traits which allows for a more horizontal sharing of code which better fits the APIs vs a parent-child inheritance PHP normally allows.
I'm going to try to get at least a good solid beta/RC version out before the new update to Eve comes out since it'll be making a lot of changes to industrial job and research stuff you'll need to be updating in your applications as well for those of you working with those things.
Anyway as always thank you for using Yapeal, Dragonaire Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Tiberius Zol
22
|
Posted - 2014.07.22 07:30:00 -
[514] - Quote
Guys... how is the update for the Crius API changes going? :-) |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.07.22 16:33:00 -
[515] - Quote
IndustryJobs ad History are out in WIP for testing but need to do some other updates to have corp ones ready as well. I'll be starting some short run jobs to have new test data but looks like they still have some issues at CCP that may cause a few issues too. https://forums.eveonline.com/default.aspx?g=posts&t=360020
I'm personally still downloading updated and should be able to try things out in an hour or less I hope. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
KnifeOrSpoon
Inter Stellar Kredit
4
|
Posted - 2014.07.23 09:04:00 -
[516] - Quote
Delicious! Thanks mate, my own implementation is a little dodgy for a hack of your work. I'd much prefer to have your own implementation instead of my rusty nail in the baseball bat. |
|
CCP FoxFour
C C P C C P Alliance
3386
|
Posted - 2014.07.23 10:19:00 -
[517] - Quote
Keep up the awesome work! CCP FoxFour // Game Designer // @regnerba
|
|
Dragonaire
Here there be Dragons
56
|
Posted - 2014.07.24 01:21:00 -
[518] - Quote
Lots of updates pushed today to 1.1.x-WIP branch including adding the corp versions of Industry stuff for people to try out. All the char versions seem to be working fine so I expect corp ones to be good as well. Fixed one typo (actually bad C/P) in createCorpTables.sql so make sure you update DB.
Just wanted to say something about a as yet to be documented feature of the bin\yc Database:Initialize command. The last thing it looks for is a bin/sql/CreateCustomTables.sql file. This can be used to automatically insert all your registered keys to save having to manually do so. I actually use this myself for that during testing. You can use it for other things as well as any SQL is generally allowed but I wouldn't try something like re-importing all of your tables data etc with it.
Please bug report anything that you find that's wrong and as always thank you for using Yapeal. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Legedric Striker
Blue Republic RvB - BLUE Republic
31
|
Posted - 2014.07.24 11:16:00 -
[519] - Quote
Hi Dragonaire!
First of all: Thank you for your awesome work, Yapeal is really great!
However, I am trying to intergate it into an existing PHP project and I have no experience with composer at all. You install.md is empty and points me towards composer. I installed it and I ran "composer install" in the folder I extracted yapeal to (without my existing project for now) but I get 34 "problems" from composer.
So is composer even the best way to integrate yapeal into an existing project or what else should I try? If you point me into the right direction or just say "follow an old version#s install instruction as far as it matches" I will do so ;)
Any help is much appreciated! Join R-v-B-- The MOST active PVP community in EVE! |
Tiberius Zol
22
|
Posted - 2014.07.24 11:25:00 -
[520] - Quote
I would also like to see an alternative to composer, cause my web-provider does not allow to install it. |
|
Dragonaire
Here there be Dragons
56
|
Posted - 2014.07.24 18:57:00 -
[521] - Quote
Tiberius Zol - How you install composer is really just copying composer.phar into a directory where you can run it with php CLI so your web-provider doesn't even need to be involved. There are some addition things you can do with it but for simple install and updating that all you need really.
Legedric Striker & everyone - Like always integrating a new library into an existing project can be hard at times or very easy depending on the project. There some questions you need to ask yourself about your project and your plan for it.
I'll assume your project doesn't current use composer already since if it does Yapeal can be added with a single line in your composer.json file.
First question is do you want to use composer in your project? I highly recommend that you do consider doing so as it brings a lot of great stuff with it not the least of which is the easy of changing or adding new dependences and largely solving problems with people having outdated versions of them and your own project. It also comes with a very good optimized class autoloader.
It's requirements aren't that much really either you need to make sure you project uses namespaces and works with a PSR-0 or PSR-4 autoloader. If your project already meets those requirements a simple 'composer init' in the root directory and answering a few questions and your done. You also have the option of just making a composer.json file yourself. Putting your project on Packagest is optional but a good idea as well.
If for now you decided NOT to use Composer then simple add Yapeal using Git like you would any other project you find on Github. If you are using git in your own project I would suggest you look into using GIt's subtree commands to integrate Yapeal with it as it'll make Yapeal more seamless for you. I did that myself in Yapeal to be able to work around some issues using Pimple 2.x because most of the other dependences were made to work with 1.0.x so composer wouldn't resolve to a workable set. By putting it into a subtree I can still use it and everything else can use Pimple 1.0.x as needed. Once everything Yapeal uses converts to version 2.x I can simple drop the subtree and everything is in sync going forward.
Whatever you decided to do make sure you read the INSTALL.md in the 1.1.x-WIP branch as it's been updated with some info on how to install Yapeal including the ZIp file way if you need to.
Legedric Striker - I'll assume since you seem to be following the new INSTALL.md instructions you are using the 1.1.x-WIP branch but you said it reported "problems" but didn't give what kind of problems. I'd need to know what it's reporting to help you try to resolve what's going on. I also need to know if you are using the current WIP or one of the other branches. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
Legedric Striker
Blue Republic RvB - BLUE Republic
31
|
Posted - 2014.07.24 19:21:00 -
[522] - Quote
Thanks for your reply!
The errors I encountered were like "unknown package php, no matching package found" and the same for nearly every packaged listed in your composer.lock file. I don't habe the exact messages at hand as I am not on my pc right now.
However, I will just redownload the WIP build and take a look at the new Install.md and try my best as the old one was empty ;) Join R-v-B-- The MOST active PVP community in EVE! |
Dragonaire
Here there be Dragons
56
|
Posted - 2014.07.24 23:01:00 -
[523] - Quote
OK just to let everyone know here I've start a new forum thread for the current version of Yapeal which you can find at https://forums.eveonline.com/default.aspx?g=posts&t=360758
Since 99% of this thread is only of historical interest to any current users I thought it was time. I'll continue to monitor this thread for awhile but I do ask that all new posts about any of the 1.1.x stuff got to the new thread as that is all going to be part of version 2.0.x which is where all new development will be done for now on.
Legedric Striker - Try code from master as the other branches are gone now and the code merged there. Finds camping stations from the inside much easier. Designer of Yapeal-á for Eve API. Check out the Yapeal PHP Library thread for more information. |
|
|
|
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 [18] [18]:: one page |
First page | Previous page | Next page | Last page |