Pages: 1 2 3 4 5 [6] 7 8 9 10 11 .. 11 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Tesla Ming Chent-Shi
The Traders
10
|
Posted - 2014.09.23 19:53:11 -
[151] - Quote
Thanks - I had found that table, but its always empty. I have a few corps which are letting me use them as guinie pigs, yet that table is always empty.
What am I missing with this? Are the above-stated problems related to this issue? Do I need to upgrade Yapeal?
Thanks for your time. I'll post the finished product of my site when its done :D |
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.23 21:08:29 -
[152] - Quote
Make sure the corp keys you have include MemberTracking in their mask. There are a couple of bits in the mask that control this API. One doesn't include as much details about the members location etc as the other which you can read more about on the MemberTracking API page from the above link. Some corporation are a bit touchy about including the more complete location Info I know or even the lesser API because it does give a lot more detail than their member might want available about their location even with the longish cache time used.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Tesla Ming Chent-Shi
The Traders
10
|
Posted - 2014.09.23 22:16:17 -
[153] - Quote
I might follow - I thought the table "corpCorporationSheet" contained only the generic publicly available info.
Do I need the special permission you speak of for this table? Otherwise, what else could stop this table from populating? |
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.24 04:17:29 -
[154] - Quote
Corporation member information isn't in CorporationSheet just the memberCount and memberLimit info is available from that API. To get the info about the actual members in the corp you need to use MemberTracking. I did push out some updates to Yapeal to fix an issue with the ceoName column as well today that I had forgotten to push out plus the other fixes to FactionName etc that Tiberius Zol found which could be causing you the same issue in CorporationSheet.
You should always make sure to update any time I put out updates to tables/APIs you are using since sometimes there can be additional small fixes that don't make it into the commit messages for things I notice while fixing the main issue I'm working on. I have been trying to always create a new issue for those things with its own commit but a lot of times I'll not do so when the fixes are inter-related and/or its only a couple of lines of code. A good example of something I usually don't include in the commit message since I decided to make Yapeal require PHP 5.4 is that as I make any changes in any of the PHP files in Yapeal I'm updating all of the arrays to use short syntax. Since this really doesn't effect how it works I don't usually feel that it needs to be included in the commit message. There can be other minor things like this as well from time to time that I don't expect to effect how Yapeal works.
I was a little unclear from your post if you were saying you CorporationSheet tables were empty or just the MemberTracking table which is a different API. Either way hopeful the above answered your question If not maybe you can try explain in a bit more detail what info your need and where you are looking for it so someone can help direct you to it.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Tesla Ming Chent-Shi
The Traders
10
|
Posted - 2014.09.24 05:53:45 -
[155] - Quote
Thanks for the reply. I'm not always good at explaining my issues
The issue is simply that the CorporationSheet table is empty. I see the columns in that table would be quite useful, yet they don't seem to populate.
The Member tracking table does populate, depending on access permissions.
So simply stated, the only issue I'm having is the corporation sheet table remaining empty. Other than that, perfection
Here you can see what I am working on:
http://www.evecorps.co/
On this page you can see how the CorporationSheet will come in handy, allowing me to pre-fill a lot of corp info to the right of the corp icon:
http://blazn-dragunz.evecorps.co/ |
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.25 23:53:06 -
[156] - Quote
So I put out a few updates to Yapeal and I wanted to briefly go over them a little.
The first one is the new User-Agent header stuff. If you don't know anything about what the User-Agent header is you can read about it at http://en.wikipedia.org/wiki/User_agent. In the past Yapeal kind of allowed for a custom setting but it was added and implemented in a way that made it hard to use and as best I can tell never really was. I'm hoping that with the better design I used this time that everyone will find it easier and it will get used more this time around. Have a look at the config/yapeal-example.yaml for more info on the settings and let me know if anything is still unclear.
The other new thing is the stuff to do with corporationSheet and using corporationIDs found in some of the other APIs. The CorporationSheet API allows you to get the same public information that available in game using just the corporationID argument. There are now a couple of new API classes I added to take advantage of the corp info available in a couple of the existing APIs.
The first one is account/YapealCorporationSheet.php and uses the info from the accountCharacters table. To avoid conflicts with any exist corporation keys that might have the CorporationSheet API active they are filtered out so the less complete public info doesn't overwrite the detailed info from the regular API. This one is active by default as it adds little load and most apps should find the addition info useful.
The other new class/API is eve/YapealCorporationSheet.php. It uses corp info from the eveMemberCorporation table which is part of the eve/AllianceList API. This one is still considered experimental and is NOT active by default. On average in Eve there are ~13k corps in some kind of alliance and getting even just the public information on them adds a lot of load to Yapeal and the Eve API servers. I made the cache interval a day long as that should be often enough since corps are limited on how quickly they can leave and join alliances. Note that at this time the corp IDs are not filtered like with the other API so more detailed info can end up being overwritten but I plan on fixing that in the future. Note that during testing it's been taking up to 1.5 hours to run this API. I believe why it's taking so long for me is do to the high latency I have since I'm on the West Coast in the States and the servers are a 1/3 of the way around the world from me. It would be nice if someone in Europe which should have less latency would try it for me so I'll know for sure if that's really the issue I've been having. Anyway as I said this one is experimental still and I'd like to get some feedback on how it's working from people before I make any additional changes.
As always thank you for use Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.25 23:56:12 -
[157] - Quote
Tesla Ming Chent-Shi - I just notice the forums eat my reply to you it seems Have a look at post 142 above as it's about the same API and has info on what to look for.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.28 02:48:29 -
[158] - Quote
So added SkillInTraining API for anyone that uses it instead of the SkillQueue API. I'd like to thank Icy0ne for his work on it. It's actual very rare to have someone add code to Yapeal other than myself so it does mean a lot to me that someone took the time to do so. Also his work on a couple of the other APIs in his branch lead to me fixing a couple of the issues I've pushed out over the last couple of days.
As always thank you for using Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.09.30 08:49:05 -
[159] - Quote
HI all thought I'd let you know I've update the 'yc D:I' and 'yc D:U' commands. Probably the most noticeable change will be they now are better integrated with the rest of Yapeal and can be ran from directories other than the base directory. So where before you couldn't run them from the 'bin/' directory you can now.
The other thing I did while I was working on them is made them a little smarter so now some of the stuff that use to be in the SQL files can be removed. I updated the existing SQL files but no updating is needed to the tables etc.
The next time you run the 'yc D:U' command you should notice it being a bit faster as it no longer is adding and dropping the procedure over and over again for each file. This will probably be more noticeable when there are multiple update files to bring your database current.
As always thank you for using Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.10.02 14:38:50 -
[160] - Quote
Okay like to thank Xinryu for noticing and working with me while I figured out an issue with the corp/WalletJournal and Transactions. Seems it wouldn't update the cachedUntil date-time for non-faction warfare corporations and I'd never noticed it https://github.com/Dragonrun1/yapeal/issues/63
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.10.09 20:10:40 -
[161] - Quote
Ok I pushed out a couple fixes today for everyone. First one for char/ContactNotifications which was mostly typos that QA (me) missed The other was on the new char/SkillInTraining where Yapeal was modifying the cached XML in a way that made it invalid when it tried to get it from the filesystem.
Be aware there are some changes coming to char/CharacterSheet which will mean Yapeal will probably be broken until you update after its deployed. An update is in the works and I should have it deployed on the same day when it goes live on TQ. I'd deploy it sooner but since the changes are NOT going to be backwards compatible they have to wait. For anyone that missed the thread about the changes check out https://forums.eveonline.com/default.aspx?g=posts&t=378333&find=unread
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.10.20 03:35:13 -
[162] - Quote
Hi everyone just thought I'd let people know about some of the updates I been putting out over the last week or two. Mostly some small issues with some lesser used API like eve/CharacterInfo. I also did some refactoring on how Yapeal does it's XSL transforms which should help out with future Eve API changes since CCP is paying more attention to it again and seem that there is a full-time person in CCP FoxFour working on it and the CREST stuff which is great, but means things change more often which can cause more updates for me to do as well in Yapeal. The XSL changes should more future proof against any reordering of the XML etc that sometimes happens which breaks the XSDs. This mostly happened on Eve APIs that used a lot of elements instead of attributes in the rows.
After the last update I just finished Yapeal should now have all the updates it'll need for Phoebe which is expected Nov 4th. That of course is assuming there aren't any more made by FoxFour before then He have hinted he might look at a couple more things after getting back from the get together in Vegas which I was sad to miss
On some other sad news I will probably NOT have as much time to work on stuff in Yapeal do to RL issues so I will probably need someone to take over again and keep Yapeal going. I would like to have someone step forward now so I can help them get up to speed and give them access on GIthub etc so if I do end up NOT having any time they can keep everything going. This really needs to happen in the next day or two because after that I'm NOT sure I'll be where they can contact me. So please if you can help out let me know.
As always thank you for use Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.10.29 05:41:27 -
[163] - Quote
Hi everyone, So I been working on another little project over the last couple of days and while doing some testing using Yapeal version history I noticed that Yapeal is coming up on its 6th year here at the end of the month. Yapeal had existed for a few months as part of another corporation project before this and even as a separate project but the old Sourceforge SVN has long ago been deleted so records of the earlier code is probably lost now.
We do have the history starting from when I start working with some other developers on what was going to be a open source Eve API framework that everyone could use to make their own tools. Yapeal was going to be the core API library for the tool and one of the developers suggested that GoogleCode might be better place to do it than Sourceforge. I liked some of the features GoogleCode had at the time too so I moved Yapeal over. When I made that move there wasn't any good tools to import from one SVN into another so I simple created the new project and copied over the files and committed them. Yapeal has of course been host other places since then in several different versioning software (SVN, Mercurial, GIt) but I've been able to import the history from one to the other every since when I changed Yapeal over.
As I was saying Yapeal has been hosted on SF, GoogleCode, BitBucket (Not public), back to SF, and finally the move to GitHub. In most cases I made the move because either the new host offered one or more things I found useful or in one case (GoogleCode) they removed features that I needed and/or wanted. I probably would have moved directly from GC to GitHub but at the time I still didn't know enough about Git to see the advantage of using it vs Mercurial which Yapeal was using at the time.
For those of you that want to have a look at this very early version of Yapeal you can see it here.
A few things to notice is that even though it was called Yapeal there was no yapeal.php file yet you actually ran it using the backend/eve-api-pull.php file. One thing I just noticed while looking at that file is the old SVN revision number that would have come directly from the old SVN on SF since I hadn't set it up yet on GC to update.
$Revision: 20 $ $Date:: 2008-10-24 00:48:59 #$
The reason it was so low is I had just make Yapeal public on SF not more than a couple weeks before as I remember it. Before that I'd hosted on a private server either at my home or probably at a friend's place because he had a better internet connection and more HD space Just a few other things to notice is that Yapeal was mostly procedural code at this time with just a few classes being used. It only worked with about a dozen APIs from the eve, corp, and char sections. Most of the char APIs were very new since the eve and corp ones had been the main focus of development up to that time. It's worth looking through the Docs/User Guide/User Guide.xml file to get a bit of an overview on my vision for Yapeal etc. It's actually the source DocBook file for the HTML and PDF files that would have been included in the tgz and zip files that was the expected way for people to install it at the time. Unlike now where the developer tools are just included with Yapeal I actually had another separate project for all of the development stuff I also had to maintain etc.
What I notice when looking back on this original code is how many of the ideas that I had already developed about how to make things work already existed and can still be seen at least by me even today in it. There are also parts of it that just make me want to hide because some of the code has some really ugly hacks in it. I have to give myself a little credit though because I was working within the limits set by PHP 5.2 and this was really my first project written in PHP. I was in many case still learning about all the commands etc of PHP and first applying what I'd just learned in Yapeal. I think I'd first become interest in learning PHP only 6 months to a year before I start Yapeal and it was by far the biggest project I had ever done. Before this I had always been more into hardware than software and playing around with some JS for web pages.
Anyway I hope everyone has enjoyed the little trip with me down memory lane and here's to at least another 6 years for Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.10.29 17:30:20 -
[164] - Quote
So after StGoe reminded me that it didn't exist I've added an option to turn off the file system caching for the XML. The new default is for it to be off as that's probably the most useful for people at least in production. Also while I was at it I added a setting to allow you to change the name and location of the main cache directory with the default being its current location. If you just want to use the defaults you don't need to update your config/yapeal.yaml file although it wouldn't hurt to do so
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.11.04 03:14:34 -
[165] - Quote
So just finished pushing out an update that should have all the updates needed for Phoebe. Only real breaking things should be the changes to the CharacterSheet tables so if you use it make sure you don't do this update until the Eve update happens. I may have another small update after it comes out in case there are any differences that I couldn't test for on the test server or if CCP made any last minute updates etc
Make sure you've read https://developers.eveonline.com/ for all the API changes that might be affecting any tables you use. Basically for charCharacterSheet there some new columns and the charAttributeEnhancers table is gone and replaced by charImplants table that will also have the slot 6-10 implants as well. Also two new tables charJumpClones, and charJumpCloneImplants. There are a couple other changes to some other APIs but I've already deployed them as they didn't make any breaking changes just add a couple of new columns in tables and I set them as optional which I'll probably update sometime after this update to make them required as needed.
Let me know about any problems and I'll make sure to do updates to fix anything I missed.
As always thanks for using Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Tiberius Zol
turaagaq GANOR INC.
33
|
Posted - 2014.11.04 10:08:56 -
[166] - Quote
As always...good work. I am really excited about your work here. :) |
Tiberius Zol
turaagaq GANOR INC.
33
|
Posted - 2014.11.04 10:29:12 -
[167] - Quote
Run in an error after the update:
......CALL "evedb"."AddOrModifyColumn"('evedb', 'yp2_charCharacterSheet', 'DoB', 'DATETIME NOT NULL AFTER "corporationName"') Sql failed in /htdocs/eve/yapealneu/bin/sql/updates/201411031600.sql on statement 6 with (22007) SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '0000-00-00 00:00:00' for column 'DoB' at row 1
|
Legedric Striker
Blue Republic RvB - BLUE Republic
53
|
Posted - 2014.11.04 11:28:40 -
[168] - Quote
I am getting this at some point:
Quote:[2014-11-04 11:25:27] yapeal.DEBUG: Class not found Yapeal\Database\Eve\CertificateTree [] []
Join R-v-B -- The MOST active PVP community in EVE!
EVE-Skillplan.net - Plan your skill training online using a PC, tablet or smartpho
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.11.04 15:47:37 -
[169] - Quote
Legedric Striker - that's normal for any API that haven't been implemented yet.
Tiberius Zol - Looks like some how you already have some invalid existing rows in your charCharacterSheet table. Probably the best way to handle it is to just truncate it and let Yapeal do it's thing to refill it. Might delete any characterSheet rows in utilCachedUntil to speed up the process.
The only reason I was updating that column is it was out of order and I didn't change it in any other way. DoB has always been a required column with no default value so you really shouldn't be getting an error there except if you have edit the row or found a way to import it without the DB giving the same error before and you worked around it
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Dragonaire
Here there be Dragons
64
|
Posted - 2014.11.04 20:07:15 -
[170] - Quote
Some of you might have noticed a small problem with the cloneImplants stuff but I've already pushed an update. https://github.com/Dragonrun1/yapeal/issues/80
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
|
Norian Lonark
Black Thorne Corporation Black Thorne Alliance
143
|
Posted - 2014.11.10 11:48:22 -
[171] - Quote
Hello Everyone,
I have been using Yapeal for a while now to run a couple of corporation apps but my knowledge of web programming is quite limited. I had no problems getting the old versions up and running (quite simple unpack, upload, run the install file), but am at a bit of a loss with the latest update and how to actually install it.
I am using a host so only have access to ssh command line and just wondered if anyone had some hints or tips / guide for setting up the new version of Yapeal not locally on your on machine but with a webhost as I am a bit lost
Many thanks for any help
Start wide, expand further, and never look back
|
Dragonaire
Here there be Dragons
65
|
Posted - 2014.11.10 22:22:28 -
[172] - Quote
Norian Lonark - Since you have SSH access you have several options. If you are working on a new project or a major update to an existing one if you converted to using Composer for your dependances it's simple to add Yapeal as one of them. Another option since you can also get Yapeal as a zip file directly from Github is to get it that way and just unzip it where you need it. If you are using some kind of version control like Git you can also setup Yapeal as a subtree like I did with Pimple so you can import it and update stuff as bugs and other updates are done to Yapeal. Git has option to create a compress or uncompressed archive which can be sent over a SSH connection as well. Those are just the options I came up with off the top of my head
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Norian Lonark
Black Thorne Corporation Black Thorne Alliance
143
|
Posted - 2014.11.11 15:53:34 -
[173] - Quote
Thanks a lot for the help. I am making progress :)
I uploaded the files, did the composor bit and then ran the yc D:U command but get the following error:
Sql failed in DatabaseUpdater::addDatabaseProcedure on statement 0 with (HY000) SQLSTATE[HY000]: General error: 1548 Cannot load from mysql.proc. The table is probably corrupted
Just wondered if you had any ideas?
Start wide, expand further, and never look back
|
Battle On
DaZeD and ConFuseD Sorry We're In Your Space Eh
133
|
Posted - 2014.11.13 18:52:47 -
[174] - Quote
Hi,
I've just pulled in yapeal 2.0 using composer and I wanna start using it. I created the database and setted up the config file, but i miss the documentation on how to use this library? I looked trough the github wiki but everything seems to be for 1.*... my question, is there a guide somewhere for 2.0 already? I'd love to start using this library :)
Thanks in advance, Battle On
[url=https://forums.eveonline.com/default.aspx?g=posts&t=168748&find=unread][Service] Battle On's Custom and Colored Overviews![/url]
|
Dragonaire
Here there be Dragons
66
|
Posted - 2014.11.13 19:11:22 -
[175] - Quote
Thought I'd documented that some where but easiest way to manually start Yapeal or use it in a crontab etc is to use bin/yapeal.php. It works basically the same as the old yapeal.php did. There are also options to call any of the per API classes directly for one-shot type needs as that was one of the planned features to be added with this rewrite.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Battle On
DaZeD and ConFuseD Sorry We're In Your Space Eh
133
|
Posted - 2014.11.13 19:37:26 -
[176] - Quote
Dragonaire wrote:Thought I'd documented that some where but easiest way to manually start Yapeal or use it in a crontab etc is to use bin/yapeal.php. It works basically the same as the old yapeal.php did. There are also options to call any of the per API classes directly for one-shot type needs as that was one of the planned features to be added with this rewrite.
Do you have some examplecode that can be used for certain standard calls like validating an Character Api Key with keycode and validationcode or retrieve the Charactersheet? This way its earier to understand.
[url=https://forums.eveonline.com/default.aspx?g=posts&t=168748&find=unread][Service] Battle On's Custom and Colored Overviews![/url]
|
Dragonaire
Here there be Dragons
66
|
Posted - 2014.11.16 19:40:22 -
[177] - Quote
Battle On - There really aren't any tutorial type docs like you are looking for. One reason for that is that I find it very hard to write anything useful to anyone new to Yapeal since I wrote 95+% of the code and have been work with it for over 6 years now. I just don't see it the way someone looking from outside does. In the past there has been a couple people that wrote about how to use the old version that I then edit and tried to maintain but so far no one has done the same thing for the current version. My suggestion on how to learn to use the individual API classes is to follow the code from bin/yapeal.php through lib/Yapeal.php and on to how the AutoMagic() calls oneShot() in the class you are interested in. It would be great if someone like you that is just learning to use Yapeal would write about it but so far no one has.
If after looking through stuff you still have questions you are welcome to ask on this thread or even contact me via E-mail etc. I'm also usually available on G-Talk and IRC when I'm at home near the computer. And for those that prefer talking to typing I can usually be talked into some voice comms as well if you really prefer that.
In other news I decided since I'm current not doing much new development work on Yapeal right now and the rate of bugs being reported is slowed down it was about time to do a tagged release so now you'll see a 2.0.0 version on GitHub and at Packagest as well if you look. I'd been thinking about doing this for at least a month but decided to wait until after Phoebe changes were merged into master and any needed fixes had been done.
As always thank you for using Yapeal, Dragonaire.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Battle On
DaZeD and ConFuseD Sorry We're In Your Space Eh
133
|
Posted - 2014.11.17 08:44:29 -
[178] - Quote
Dragonaire wrote:Battle On - There really aren't any tutorial type docs like you are looking for. One reason for that is that I find it very hard to write anything useful to anyone new to Yapeal since I wrote 95+% of the code and have been work with it for over 6 years now. I just don't see it the way someone looking from outside does. In the past there has been a couple people that wrote about how to use the old version that I then edit and tried to maintain but so far no one has done the same thing for the current version. My suggestion on how to learn to use the individual API classes is to follow the code from bin/yapeal.php through lib/Yapeal.php and on to how the AutoMagic() calls oneShot() in the class you are interested in. It would be great if someone like you that is just learning to use Yapeal would write about it but so far no one has.
If after looking through stuff you still have questions you are welcome to ask on this thread or even contact me via E-mail etc. I'm also usually available on G-Talk and IRC when I'm at home near the computer. And for those that prefer talking to typing I can usually be talked into some voice comms as well if you really prefer that.
In other news I decided since I'm current not doing much new development work on Yapeal right now and the rate of bugs being reported is slowed down it was about time to do a tagged release so now you'll see a 2.0.0 version on GitHub and at Packagest as well if you look. I'd been thinking about doing this for at least a month but decided to wait until after Phoebe changes were merged into master and any needed fixes had been done.
As always thank you for using Yapeal, Dragonaire.
Oke ill fool around with it then and see if i can get it to work. As of the "turoial/examples", if i get it to work i'll make a simple setup guide for it so that others will have a easier way of setting it all up.
Kind Regards, Battle On
[url=https://forums.eveonline.com/default.aspx?g=posts&t=168748&find=unread][Service] Battle On's Custom and Colored Overviews![/url]
|
Battle On
DaZeD and ConFuseD Sorry We're In Your Space Eh
133
|
Posted - 2014.11.17 15:07:39 -
[179] - Quote
Oke so far i've been able to pull yapeal in using composer, setted up the database and config and managed to get the autoloading to work. Also i've tested if it worked by adding my own API key into the utilRegisteredKey table and running bin/yapeal.php in CLI and it correctly populated the database.
First, lets start with some problems i ran in to along the way:
First of all, when fetching with composer, it gives an error that "dragonrun1/file_path_normalizer" cannot be found in packagist. Probably because the version changed or something. I'd suggest looking into this. It's easily fixable by pulling it in manually, but it would be nice if it was included in de dependancy of yapeal.
Secondly, I had a hard time setting up the autoloading. In the tutorials i could find there was a UtilRegisteredKey class, which uses a keyid as parameter for its constructor, which was used for adding keys to the database. However, in 2.0.0, this class is nowhere to be found. Instead there is the bin/UtilRegisterKey class which needs and instance of PDO and in instance of CommenSqlQueries. However, i have no idea how to set these two up, since im not familliar with PDO (I'm used to using mysqli, or use a framework like Laravel which comes with eloquent, which handles everything for me) nor the CommenSqlQueries class.
It would be nice to have some kind of helper class/method that can give you these two instances based on the yapeal.yaml config file that you used earlier. This way, yapeal can live completely on its own without the user needing to make an own instance of PDO and such, but only needs to add the keys he needs and populate the database using bin/yapeal.php.
I dont know if you already have such class or method, i looked through the files and couldnt find anything like it. If you have, or have some example code how to make those instances yourself, that would be very helpful!
Kind Regards, Battle On
[url=https://forums.eveonline.com/default.aspx?g=posts&t=168748&find=unread][Service] Battle On's Custom and Colored Overviews![/url]
|
Dragonaire
Here there be Dragons
66
|
Posted - 2014.11.17 20:23:30 -
[180] - Quote
Battle On - https://github.com/Dragonrun1/yapeal/issues/82 - fixed
Quote:First of all, when fetching with composer, it gives an error that "dragonrun1/file_path_normalizer" cannot be found in packagist. Probably because the version changed or something. I'd suggest looking into this. It's easily fixable by pulling it in manually, but it would be nice if it was included in de dependancy of yapeal.
Think it was because I was working on that class yesterday and did several commits in short order etc so it should be working right now. If it still seems to be giving trouble try deleting the composer.lock file and use composer update -o to have it recreate it. also worth having something like the include_once - die block from bin/bootstrap.php in your own code to take advantage of the great PSR-0/PSR-4 auto class loader that composer generates for you. I found the code some where in another composer package and added a few improvements/tweaks to it as well. You should be able to just drop it some where in your project and it'll manage finding the autoloader and than you don't have to worry about doing any more includes for classes etc.
Quote:Instead there is the bin/UtilRegisterKey class which needs and instance of PDO and in instance of CommenSqlQueries. However, i have no idea how to set these two up, since im not familliar with PDO (I'm used to using mysqli, or use a framework like Laravel which comes with eloquent, which handles everything for me) nor the CommenSqlQueries class.
CommonSqlQueries you'll find in lib/Database/ and is just a simple class I use to collect up all the SQL queries into. Just pass it the database name and table prefix you are using in the constructor. PDO isn't really that much different from mysqli and is probably what Laravel uses as well internally. I would suggest learning to use it instead of mysqli as in some future version of PHP mysqli is going away plus the PDO prepare statements, if used, can go a long ways towards preventing DB ejections which is near impossible without a lot of code with mysqli. If you have a look in lib/Configuration/Wiring::wireDatabase() and ::wireDefaults() you can see how PDO is setup normally in Yapeal but utilRegisterKey takes care of it's own init stuff so you just need to give it an active PDO and it'll take it from there.
Quote:Furthermore, it would be nice to have some kind of helper class/method that can give you these two instances based on the yapeal.yaml config file that you used earlier. This way, yapeal can live completely on its own without the user needing to make an own instance of PDO and such, but only needs to add the keys he needs and populate the database using bin/yapeal.php.
That already exists it's called lib/Yapeal.php. It was made to be extended as needed and used. Its only requirement is a working autoloader and a ContainerInterface compatible class. You can find info on the interface and the default class that Yapeal uses in lib/Container/PimpleContainer. It's basically a wrapper around Pimple 2.0 which you can find in subtree/Pimple/. I use a git subtree for Pimple instead of through Composer because most things are still using version 1.x and Composer errors out on the conflict when I do. You might also look at bin/yc and the lib/Console/Command classes to see some possible less complex ways to do things like reading yapeal.yaml and DB setup stuff. You should find that extending the Yapeal class is really easy as all the walking APIs stuff in contained in autoMagic() and can be ignored if you don't need it and just add your own methods to it for what you need. You will probably want to look at how autoMagic() grabs the DB info, calls the per API classes etc. I did a 10 minute quick example of how part of a signup check and registering might look like which you can find here that I made to show extending the Yapeal class. Maybe it'll give you some ideas how to do what you are trying to do.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
|
|
|
|
Pages: 1 2 3 4 5 [6] 7 8 9 10 11 .. 11 :: one page |
First page | Previous page | Next page | Last page |