# |
Sep 22nd 2011, 12:25 |
isaqual |
dakota: this or next week.. ;) |
# |
Sep 22nd 2011, 12:25 |
dakota |
fenix`: ? |
# |
Sep 22nd 2011, 12:24 |
isaqual |
dakota: Have to try it but not in this project :) |
# |
Sep 22nd 2011, 12:24 |
fenix` |
dakota: i think debian, may disagree with you... :) |
# |
Sep 22nd 2011, 12:24 |
dakota |
isaqual: what is the timeline for your app going to production? |
# |
Sep 22nd 2011, 12:24 |
dakota |
isaqual: 2.0rc is basically production ready |
# |
Sep 22nd 2011, 12:24 |
fenix` |
i had to make the jump to 2.0 because i couldn't get any of the known 1.3 methods for using html5 form elements working. |
# |
Sep 22nd 2011, 12:24 |
dakota |
fenix`: in the cakephp world beta == everybody else's RC and RC == everybody else's stable |
# |
Sep 22nd 2011, 12:24 |
isaqual |
FOR production use |
# |
Sep 22nd 2011, 12:24 |
isaqual |
Most of time RCs are good enought but I still prefer 1.3.xxx |
# |
Sep 22nd 2011, 12:23 |
fenix` |
it's still in RC. |
# |
Sep 22nd 2011, 12:23 |
isaqual |
to jump to 2 |
# |
Sep 22nd 2011, 12:23 |
dakota |
isaqual: to early for what? |
# |
Sep 22nd 2011, 12:23 |
dakota |
ACTION needs to get back to work |
# |
Sep 22nd 2011, 12:23 |
isaqual |
dakota: too early :D |
# |
Sep 22nd 2011, 12:22 |
dakota |
isaqual: switch to cakephp 2 :) |
# |
Sep 22nd 2011, 12:22 |
dakota |
isaqual: so no, you can't |
# |
Sep 22nd 2011, 12:22 |
dakota |
isaqual: helpers are for views, not shells |
# |
Sep 22nd 2011, 12:22 |
isaqual |
http://pastebin.com/8L4pjJBi |
# |
Sep 22nd 2011, 12:22 |
isaqual |
Any idea how I can get work custom made helpers in shell ? |
# |
Sep 22nd 2011, 12:22 |
dakota |
fenix`: cakephp supports database sessions |
# |
Sep 22nd 2011, 12:21 |
fenix` |
if i wanted to store session relevant data in the database. |
# |
Sep 22nd 2011, 12:21 |
dakota |
why? |
# |
Sep 22nd 2011, 12:21 |
fenix` |
is there a way to get some kind of session id? |
# |
Sep 22nd 2011, 12:20 |
dakota |
accessing other controllers won't help with getting information to persist across requests |
# |
Sep 22nd 2011, 12:19 |
dakota |
fenix`: if you want something like context to persist across requests then sessions is the way to do it |
# |
Sep 22nd 2011, 12:19 |
fenix` |
the working environment. |
# |
Sep 22nd 2011, 12:19 |
dakota |
ACTION doesn't understand what fenix`is trying to do |
# |
Sep 22nd 2011, 12:19 |
fenix` |
store .. context |
# |
Sep 22nd 2011, 12:19 |
dakota |
fenix`: to do what? |
# |
Sep 22nd 2011, 12:18 |
fenix` |
the other option im looking at is session->read/write |
# |
Sep 22nd 2011, 12:18 |
dakota |
imo |
# |
Sep 22nd 2011, 12:17 |
dakota |
then it isn't data |
# |
Sep 22nd 2011, 12:17 |
fenix` |
want* |
# |
Sep 22nd 2011, 12:17 |
fenix` |
what if the data i wan't isn't in a model? |
# |
Sep 22nd 2011, 12:17 |
dakota |
fenix`: controllers should not need to 'talk' to each other. Rather your controller should call the correct method in the model that corresponds to the data you wish to get |
# |
Sep 22nd 2011, 12:16 |
dakota |
fenix`: your controllers are for controlling flow of data from models to views. |
# |
Sep 22nd 2011, 12:16 |
dakota |
~why |
# |
Sep 22nd 2011, 12:16 |
dakota |
bleh |
# |
Sep 22nd 2011, 12:16 |
fenix` |
im thinking of using getters and setters |
# |
Sep 22nd 2011, 12:16 |
dakota |
~tell fenix`about why |