Subpage under development, new version coming soon!
Topic closed!!!
Subject: Sokker-Manager.net
noooo the worst new of the day! it needs to be fixed! please
It's only the section NT-scouting. Till yesterday it worked.
I have already send a mail to Ramonymous.
The rest of the page is working fine.
I have already send a mail to Ramonymous.
The rest of the page is working fine.
Thanks to tsolias and obviously ramonymous! :)
Thank you very much it is the part of the page that I use the most.
your contribution is excellent.
your contribution is excellent.
Thank you! I do it also for myself! ;P LOL
I use it to decide on when I will transfer my players and on how to train them
and I also use it for my U21-database and U21 oponent scouting.
I think sokker experience is much better with sokker-manager.net, with Asistente and with SETE. I love these tools! :)
I use it to decide on when I will transfer my players and on how to train them
and I also use it for my U21-database and U21 oponent scouting.
I think sokker experience is much better with sokker-manager.net, with Asistente and with SETE. I love these tools! :)
This tool is perfect. I have one proposal for improvement.
Show not just age and date of transfer, but also which week of the season it was
Show not just age and date of transfer, but also which week of the season it was
Yes, week of transfer can be very important and it' already implemented!
;D
;D
For me it lacks a great feature (which existed in previous transfer comparison apps): enter the player ID of a current player in transfer, then the app retrieves all the data and compares with the closest transfers (primary skills/position score and age/week).
Hi juytt,
I was thinking about this feature as well and I even thought about taking it one step further. Why not provide comparable transfers for each player of the user's own squad? E.g. my website would prompt the user to enter his sokker-credentials again, so it could access the skills via sokker-XML and then calculate comparable transfers.
Yet there is one reason why I hesitate to implement any new features: I'm already too busy adapting my website to sudden changes on sokker.org. And each additional feature means "one more feature that could be broken already tomorrow".
Btw: I still don't have access to the test-server of sokker.org and I feel like in a constant battle trying to keep my website up and running :-(.
I was thinking about this feature as well and I even thought about taking it one step further. Why not provide comparable transfers for each player of the user's own squad? E.g. my website would prompt the user to enter his sokker-credentials again, so it could access the skills via sokker-XML and then calculate comparable transfers.
Yet there is one reason why I hesitate to implement any new features: I'm already too busy adapting my website to sudden changes on sokker.org. And each additional feature means "one more feature that could be broken already tomorrow".
Btw: I still don't have access to the test-server of sokker.org and I feel like in a constant battle trying to keep my website up and running :-(.
you could parse (html) skills on page player/ID, off course it could be broken in future but also could be easily update, not a big deal. Or maybe store user login in your user session, so we don’t need to enter again?
Juytt, he explained clearly and in detail why this feature is not implemented yet, without confusing the readers about specific technical details.
I think you already have your answer.
-------------------------------------------------------------
He also wrote that he is too busy.
I write this, because I am the one who came in contact with Ramonymous and told him "look at the forum, a french man proposed a nice idea"
But now I will not tell him the french guy wrote "I do not give a penny about your reasons not to do it, just parse this and even if it breaks the next day it will be easy..."
If it's so easy, do it yourself man!
I think it is very rude for the other person to give you an answer and for you to answer him like that.
I think you already have your answer.
-------------------------------------------------------------
He also wrote that he is too busy.
I write this, because I am the one who came in contact with Ramonymous and told him "look at the forum, a french man proposed a nice idea"
But now I will not tell him the french guy wrote "I do not give a penny about your reasons not to do it, just parse this and even if it breaks the next day it will be easy..."
If it's so easy, do it yourself man!
I think it is very rude for the other person to give you an answer and for you to answer him like that.
in future parsing html will probably be impossible as it will be html-s like this (more or less, dont remember exactly and I didnt use proper html syntax but its obvious anyway):
html
-head
--blah blah blah
/head
-body
--script some-random-hash-1.js
--script some-random-hash-2.js
--script some-random-hash-3.js
...
--script some-random-hash-N.js
/body
/html
unless You have something that could properly process loaded javascripts (you can try http request of /overview page to check this)
however, maybe it will be super comfortable and easy as there are now many requests to /api/* on new pages e.g.
https://sokker.org/api/junior/{junior-id}/graph
https://sokker.org/api/pub/player/{player-id}/face
https://sokker.org/api/training?filter[currentWeek]=no&filter[week]=949
which returns json-s with data
maybe in future there will be possible something like https://sokker.org/api/pub/player/{player-id}/profile
html
-head
--blah blah blah
/head
-body
--script some-random-hash-1.js
--script some-random-hash-2.js
--script some-random-hash-3.js
...
--script some-random-hash-N.js
/body
/html
unless You have something that could properly process loaded javascripts (you can try http request of /overview page to check this)
however, maybe it will be super comfortable and easy as there are now many requests to /api/* on new pages e.g.
https://sokker.org/api/junior/{junior-id}/graph
https://sokker.org/api/pub/player/{player-id}/face
https://sokker.org/api/training?filter[currentWeek]=no&filter[week]=949
which returns json-s with data
maybe in future there will be possible something like https://sokker.org/api/pub/player/{player-id}/profile
I suppose that tech talks is rude for you, so you couldn’t understand my answer wasn’t rude, also, I didn't ask any German guys to deliver my own messages. Especially if he doesn't understand. And Yes, this sentence is rude :-p
—-
Also as kryminator said, html parsing is maybe not a good idea.
But for SURE xml data will not be broken by the Devs in the coming seasons, and/or without prior announcement. They recently reaffirmed this.
it doesn’t help for the feature « comparing price for a player in market » since, as far as I know there is no skills data for xml player id (even those in market?) :-/ but you can Safely (against sokker changes) write « a team players comparison price feature », that will be a great feature too ;-)
(edited)
(edited)
—-
Also as kryminator said, html parsing is maybe not a good idea.
But for SURE xml data will not be broken by the Devs in the coming seasons, and/or without prior announcement. They recently reaffirmed this.
it doesn’t help for the feature « comparing price for a player in market » since, as far as I know there is no skills data for xml player id (even those in market?) :-/ but you can Safely (against sokker changes) write « a team players comparison price feature », that will be a great feature too ;-)
(edited)
(edited)