Re: Unoffical API / Beta RFC [new]
Tarique, I'm definitely not 'copying out' ;-) I'd love to contribute to CakePHP as I believe its the best thing to happen to PHP in all the time I've been programming with it (since PHP3). I was trying to illustrate that perhaps, if the documentation was available then the learning process would be faster and I would be in a better position to help others. As it stands, I'm no-where near up to speed with CakePHP to help out in any substantial way. And your are right, this is one of the most friendly, a knowledgeable lists I've subscribed to and I'm keen to take a more active roll. I understand how OSS projects are developed, but lack of documentation has sunk other worthy projects in the past. I'd hate to see cake suffer the same misfortune. I'm not asking for wikipedia scale documentation. What would really be useful would be to extend the sample Blog application to cover the stuff that make a site 'work'. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC [new]
On 1/22/07, RichardAtHome [EMAIL PROTECTED] wrote: I'd love to contribute to CakePHP as I believe its the best thing to happen to PHP in all the time I've been programming with it (since PHP3). Nice to know that - I wont go as far as saying CakePHP is the best thing or bother with I am older than you in this ;) I was trying to illustrate that perhaps, if the documentation was available then the learning process would be faster and I would be in a better position to help others. As it stands, I'm no-where near up to speed with CakePHP to help out in any substantial way. Again a common fallacy on public forums - I am too new/know too less to help - You teach best what you want to learn the most. And your are right, this is one of the most friendly, a knowledgeable lists I've subscribed to and I'm keen to take a more active roll. I notice that you *are* already more active than I am so I understand how OSS projects are developed, but lack of documentation has sunk other worthy projects in the past. I'd hate to see cake suffer the same misfortune. Oh! its not that bad... I'm not asking for wikipedia scale documentation. What would really be useful would be to extend the sample Blog application to cover the stuff that make a site 'work'. The IBM tutorials just provided that bit - and thank god they did not do another blog Cheers Tarique P.S. This thread has gone too off topic so EOT form my side -- = PHP Applications for E-Biz: http://sanisoft.com Cheesecake-Photoblog: http://cheesecake-photoblog.org = --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC [new]
Ok I am going to throw my 2 cents into this conversation and put a stop to it. The code is what is important, the documentation is being worked on by volunteers, as is the rest of the project. The only person who works full time on this code is me. Nate works on the code, but he also has a job outside of CakePHP. Garret is the project manager, but he also does work outside of CakePHP. John, the person who has taken charged of the documentation since joining me on this project, also has a job outside of CakePHP. It should also be noted that John has been working with me on this project longer then anyone else, so give him a break, I am not the easiest person to work with. No one is paid to do this development, be it the code or the documentation. The few donations that come into this project help cover the cost of the services that are offered to people for free. One of the things that motivates me to do what I do on this project is the people who use it. Trust me the skills I have could be worth a lot if I accepted a job offer if it came my way. From the start I have been totally dedicate to the success of this project, and will continue to be dedicated until my last breath. I have no doubt that CakePHP will continue on its path as the best PHP framework. So be patient and things will come. If you feel like something is taking too long, step up. There are many things that can be done outside of the code development. If you are not able to contribute by helping with documentation or patches to bugs on the Trac site, ask how else you might be able to contribute, I am sure someone will reply in a positive way. So there is my 2 cents, for what it is worth to anyone reading. And get this thread back on topic again... -- /** * @author Larry E. Masters * @var string $userName * @param string $realName * @returns string aka PhpNut * @access public */ On 1/22/07, RichardAtHome [EMAIL PROTECTED] wrote: Tarique, I'm definitely not 'copying out' ;-) I'd love to contribute to CakePHP as I believe its the best thing to happen to PHP in all the time I've been programming with it (since PHP3). I was trying to illustrate that perhaps, if the documentation was available then the learning process would be faster and I would be in a better position to help others. As it stands, I'm no-where near up to speed with CakePHP to help out in any substantial way. And your are right, this is one of the most friendly, a knowledgeable lists I've subscribed to and I'm keen to take a more active roll. I understand how OSS projects are developed, but lack of documentation has sunk other worthy projects in the past. I'd hate to see cake suffer the same misfortune. I'm not asking for wikipedia scale documentation. What would really be useful would be to extend the sample Blog application to cover the stuff that make a site 'work'. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
RE: Unoffical API / Beta RFC [new]
Hi Yeah, this topic ended up with people discussing the quality of Cake docs/manual instead of discussion WHAT I could add to improve the situation for new Bakers The ~3 first posts had relevance for the original topic, and then it went completely off track :( I'm sitting here now, with the feeling that I don't have a clue what people felt about the API app I'm making, but a clear feeling that most people aren't very happy about the current situation... And without sounding like a saint or angel, I'm beginning to feel some of the frustration the core team problem has when reading the group and looking at one post after another with the endless discussion on how many things there need improvement in the API/DOC/Manual, and yet so little action behind those words. I felt like doing this app for Cake because I wanted to contribute to the project - I'm far from some godlike baker, actually, phpnut would probably slap me around if he saw the code, but I don't care.. I'm just putting action behind my words when I told gwoo I felt like API lacked some features So please, feedback on the TOPIC, not about how bad/lacking the current is... /Jippi Ps. Yes, my English suck, and yes, I'm a little pissed off right :P -Original Message- From: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Dr. Tarique Sani Sent: 22. januar 2007 10:40 To: cake-php@googlegroups.com Subject: Re: Unoffical API / Beta RFC [new] On 1/22/07, RichardAtHome [EMAIL PROTECTED] wrote: I'd love to contribute to CakePHP as I believe its the best thing to happen to PHP in all the time I've been programming with it (since PHP3). Nice to know that - I wont go as far as saying CakePHP is the best thing or bother with I am older than you in this ;) I was trying to illustrate that perhaps, if the documentation was available then the learning process would be faster and I would be in a better position to help others. As it stands, I'm no-where near up to speed with CakePHP to help out in any substantial way. Again a common fallacy on public forums - I am too new/know too less to help - You teach best what you want to learn the most. And your are right, this is one of the most friendly, a knowledgeable lists I've subscribed to and I'm keen to take a more active roll. I notice that you *are* already more active than I am so I understand how OSS projects are developed, but lack of documentation has sunk other worthy projects in the past. I'd hate to see cake suffer the same misfortune. Oh! its not that bad... I'm not asking for wikipedia scale documentation. What would really be useful would be to extend the sample Blog application to cover the stuff that make a site 'work'. The IBM tutorials just provided that bit - and thank god they did not do another blog Cheers Tarique P.S. This thread has gone too off topic so EOT form my side -- = PHP Applications for E-Biz: http://sanisoft.com Cheesecake-Photoblog: http://cheesecake-photoblog.org = --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC [new]
tbh, I wasn't being off topic (kinda ;-). Jippi was asking what people would like to see in a documentation project and I answered: Example code. It snowballed from there. I'm definitely not having a dig at all the hard work done by everyone on the CakePHP project. If I didn't think it had potential I wouldn't have bothered righting the post. Jippi, the app is looking great :-) How about posting a few tutorials on how you glued all the various bits together? Include that in the documentation and I think you are on to a winner! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
RE: Unoffical API / Beta RFC [new]
I have created a IRC channel on Freenode for the relevant discussions: #cakephp.doc ( irc://irc.rizon.net/cakephp.doc ) /jippi -Original Message- From: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of RichardAtHome Sent: 22. januar 2007 12:16 To: Cake PHP Subject: Re: Unoffical API / Beta RFC [new] tbh, I wasn't being off topic (kinda ;-). Jippi was asking what people would like to see in a documentation project and I answered: Example code. It snowballed from there. I'm definitely not having a dig at all the hard work done by everyone on the CakePHP project. If I didn't think it had potential I wouldn't have bothered righting the post. Jippi, the app is looking great :-) How about posting a few tutorials on how you glued all the various bits together? Include that in the documentation and I think you are on to a winner! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC [new]
Well Mariano I don't blame you for writing that. I tried not to sound like a whiner, but evidently I didn't succeed, and I regret that. As for contributing some documentation, as I pointed out in the earlier message, I do not think I am a good person to write about Cake because I don't properly understand the unifying concepts behind it. I have yet to see a decent set of explanations and examples which might help me properly understand those concepts. Maybe it's because I'm not sufficiently skilled in this particular style of object-oriented framework programming, or maybe I'm just obtuse, or maybe I really am a rotten whiner. I don't know. But let me say one thing, again not nice or polite, and yes, in advance, I apologize: I would never release so much uncommented and undocumented code into the wild. For my part, I created what I think is a nice little system in Cake, for a school, involving students, teachers, courses and schedule blocks. I recently posted in this forum something about my use of SQL views, using some of those multi-table joins. I wrote that in response to someone's question about the use of SQL views, which I think have a lot of potential to simplify complex queries and improve the ease of thinking about a database structure. My little application also features a specialized multi-record edit screen, styled for user ease. Getting that particular screen to work compelled me to reverse engineer the code for saving data from many-to-many relationships in Cake. I wrote quite a few revisions of the code and finally got it working properly. But then another client materialized, and I wanted to use Cake to set up his authorization system. Probably I shouldn't have done it this way, but I fetched a copy of the pre-release Bakery and used the auth from that. I got the authorization to work, but then I had to take a break from using Cake because it was simply too difficult for me to work with. Even relatively simple changes would have me scratching my head, and then while putting in the changes I would wind up breaking something else. If I had just had some more documentation, I think I would still be using Cake in the most recent parts of my current project. Instead I used one of those code-gen packages for Windows, which bugs the hell out of me, because it's intrinsically so inelegant and like a black box. But it does work. On that topic, the role of code generation in Cake is very unclear to me. Bake is very, very helpful in getting started, but it could do so much more, and it could generate code which would illuminate the very problems I've been struggling with. That can be one of the great advantages of code generation within a framework: it can be so helpful in showing a programmer how to code properly for the framework. A framework is not just about code. It's about an overall point of view and a style about how things can best be done when trying to utilize that body of code. I think the whole huge Perl system is a good example of this problem. How many people really understand enough to take advantage of all the much-touted Perl code that's available? Not many, I'm guessing, and I suspect that's why Perl has apparently fallen behind other languages such as php in popularity over the past few years. It's just too confusing. I've tried to show that I'm not just sitting on my rear end complaining about things. I sincerely believe that the lack of a certain minimal level of explanation and documentation is a serious, sometimes even fatal weakness, especially in a project as wide-ranging and ambitious as this one. Oh, what the hell. It's not my project. I think it's a very, very interesting effort, with a great deal of merit, but I fear for its long-term success if the documentation does not start to keep up with the coding. I am truly sorry to be so cranky, and I hope lots of readers will correct my egregious errors and general wrong-headedness. Thank you, Mariano, for taking a stab at straightening me out. Regards, Ralph --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC [new]
Hi Ralph, contributing is the way to go ;) but if you can't contribute - make a ticket - not with the exact documentation but with what you would like to find in the manual ... its a good way of informing people from the docs team what is missing ... btw. come to #cakephp people will always help :) enough OT :) Jippi great work ! i would like to see the cakephp manual look the same (as php manual) with comment etc it's a great idea :) greets, Marcin --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC [new]
Ralph, This is why I pointed out maybe you are not like that at all. I wasn't making a judgement about the way you behave, I was just pointing out that it's so simple to contribute, you don't need to be a Cake expert to do so. Just small things you found on the way are good enough. Like your SQL views example. Those are the things that make the learning curve an even better experience. When we all have the philosophy of i solved a problem I didn't see somewhere on the net, so I'll post a blog entry to prevent other bakers from having to deal with the same issues. As to your comment about Cake future, it all depends on the community. Personally I have over 16 years of programming (I started very young) and I've been involved on several open source projects (on PHP, Java, C++, C# and Perl.) Cake is by far the only project where I found a community that is very dynamic and eager to learn / share. This tells me that Cake has a great future ahead, and no one should think different. But then again, it's just MHO. However I don't think there's a framework, or any technology for that matter, that can pinpoint the exact needs of every user level. It can't be excellent on every aspect, and solve every specific need. Just take the new ribbon system on Microsoft Office, while some say is great for begginners, some believe it'll present an adaptation issue for current office users. It's a give and take situation. I do believe CakePHP is a RAPID development framework. It has speed up my PHP development, no doubt. But it has also improved the way I code on PHP, letting me feel things are more elegant (the way I feel when I program in Java, C#, or C++.) Cake is bringing a structured way of programming to PHP that other frameworks have yet to proove they can. Stay with Cake. You won't regret it. We may have some long way to go regarding documentation, but if we all give our two cents, that's going to be a problem in the past very soon. PS: Thanks for the 3 star rating ;) On 21 ene, 07:02, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Well Mariano I don't blame you for writing that. I tried not to sound like a whiner, but evidently I didn't succeed, and I regret that. I am truly sorry to be so cranky, and I hope lots of readers will correct my egregious errors and general wrong-headedness. Thank you, Mariano, for taking a stab at straightening me out. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC [new]
Kudos for ralph who elequently illustrated my *only *problem with CakePHP. Cake is a top bit of coding. Seems to do so much of what I want, but the practical documentation is lacking. Code examples are crutial. Even generic ones. Specific ones are even better. No-one comes to Cake without a good understanding of PHP. What we need are concrete examples of how common stuff is done. From there we can piece together the intricacies. IMHO, the best introduction to cake was done on the IBM site: http://www-128.ibm.com/developerworks/edu/os-dw-os-php-cake1.html They showed, from first priciples how to put together a cake app. That's what the documentation needs. API documention is fine for CakePHP guru's, but it was only after reading the IBM stuff I *got* it. I learned more from lesson 1, than I did from anything on the Cake site. This is defintely not a winge. I'm loving Cake. If my proffessional deadlines were'nt so tight in my projects I'd be contributing documentation about what I've got it to do right now. Cake *feels* right to me, and I know this is the direction my own code should be going. As it stands, if a commercial project comes up that I think: 'This would be perfect for a Cake'. I have to pass and go back to what I know I can get working. If you want Cake to be defacto, you are going to have to publish basic tutorials on: Authentication. Showing how to develop a system where users register, sign in, sign out, have access to certain pages, how user_id's are used to filter data, etc. How a page is put together: Sounds simple I know, but I'm still struggling to see how a cake app would build a comercial (not some toy blog you couldn't charge for) site. Real websites are much more than a common header, footer and one action. *Show* how components and elements are brought together to build a page. Gah, feels like a rant - but I'm not ranting ;-) Just frustrated when I can feel the potential, but the practicallity is missing some important steps. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC [new]
On 1/22/07, RichardAtHome [EMAIL PROTECTED] wrote: IMHO, the best introduction to cake was done on the IBM site: http://www-128.ibm.com/developerworks/edu/os-dw-os-php-cake1.html And that just illustrates why great code should be released often and early. People do contribute :) I agree that those 5 lessons are the best out there for cake BUT does it really matter that they were not written by someone on the cake development team? I think the cakephp.org should just have a link to those articles (is there anybody out there...) OSS projects do not become *most* popular because of documentation alone - in most cases documentation details are put in as an *after effect* @Richard - this is not an attack on you but the cop out I would have contributed only if... sounds a bit selfish. As far as commercial projects go - it largely depends on your own skills, but on the other hand this list is one of the most helpful and very newbie tolerant that I have come across even though some do get the their head bitten off once in a while (No reference to Larry or Nate ) So my point in this counter rant is that we as a group just have to sit and write our 2bit part of the documentation for all the others to read and learn from - TINA Cheers Tarique -- = PHP Applications for E-Biz: http://sanisoft.com Cheesecake-Photoblog: http://cheesecake-photoblog.org = --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC [new]
Certainly the PHP manual is an excellent example to copy. But the PHP manual is full of much more detailed explanations... I should say that it HAS some explanations. If your discuss feature could lead into some true augmentation of the documentation, that would really be wonderful. But I don't think I'd use the term discuss. Maybe explain or comment on or add documentation for -- the idea being that the Cake API needs more explanations by people who actually understand what's going on. Right now, sad to say, I find this level of explanation to be almost entirely lacking in Cake. And so I look at the code, but the code isn't even commented, except for some banner-style comments telling what a function is supposed to do. Sigh. I often feel like I'm flying blind, trying to guess where the runway might lie beneath the clouds. Sometimes you just really want to land, know what I mean, without having to guess all the time. Maybe I should feel flattered that the authors think I'm so smart that I can figure everything out without documentation. All I can say is that I used to think I was smart, but now I'm actually smart enough (or just old enough) to know that I'm not all that smart. I find Cake difficult to learn in depth. I have achieved some good, even impressive results using Cake, but I wouldn't say the development was easy, or by any stretch of the imagination rapid. If I really did have something like the PHP manual for Cake, I think I could be ten times more productive with the framework. By comparison, I've been coding in PHP for about ten years now, and I still use the manual quite frequently. I used it today to refresh my memory on rand() and ucfirst() and strtolower(). PHP has a lot of functions, and C/C++ uses different names for most of them; how am I supposed to remember all of this basically meaningless stuff without a reference? Fortunately, PHP's manual, once you learn how to use it, and understand a few quirks, is about the best example of documentation I know of. Since I'm ranting, I guess I'll just continue right on to the bitter end. At the considerable risk of pissing some people off, I think that if there aren't enough writers available to document Cake, then maybe some of the developers -- at least one developer -- might consider taking time off from adding to the framework in order to document what already exists. Because right now, and forgive me, that's what's really missing. And I know I'm not qualified to take on that job, because I just don't understand Cake that well yet. /rant --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC [new]
Hi, This is senthil , if you find any such manual for cakephp , please inform me also. with regards, senthil On 1/20/07, Jonathon Davis [EMAIL PROTECTED] wrote: Looks like a great work in progress. I would definitely go there as a resource to find out how to unleash more power of CakePHP. I can see a few places where you might be able to Web 2.0 it up a little bit with Sciptaculous or Mootools ( I prefer Scripta because of the ample documentation. I won't even comment on Moo. ) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC [new]
And what about contributing, instead of asking for things? If you *did* understand some things that are not yet documented, then why haven't you documented and submitted them? Maybe I'm wrong here, and you are not like that at all, but IMHO a lot of open source projects suffer of people demanding things without even giving a glimpse of intention to give something back to the community. I guess the question is, don't only ask what Cake can do for you, but also what you can do for Cake :) If we are all relying on the Cake team to do everything there's to be done (development, planning, testing, promoting, evangelization, documentation, etc. etc.) then we are doomed. Look at the bakery. Look at the myriad CakePHP blogs. Look at the trac. There are a lot of people contributing, why not just jumping in, instead of waiting by the side of the road? Just my two cents. -MI [EMAIL PROTECTED] ha escrito: At the considerable risk of pissing some people off, I think that if there aren't enough writers available to document Cake, then maybe some of the developers -- at least one developer -- might consider taking time off from adding to the framework in order to document what already exists. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC
Christian Winther [cwi.dk] [EMAIL PROTECTED] wrote: The login system shouldn't require any special browser enabled features... Its just a plain old 'POST' form. Does it not work for you or ? I enter a login and password, hit Submit and it displays the same page again. It's a POST form, so I suspect cookies are required, but it doesn't say that on the page to persuade me to manually enable it, and there's no privacy policy, P3P or similar, so it doesn't get cookie permission automatically. Hope that explains, -- MJR --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC
Hi It does use Session's - Not any cookies :) ( 'Remember Me' hasnt been implemented yet :) ) I tried to sign up and login with a test user, and it does work fine for me :o --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Unoffical API / Beta RFC [new]
Greetings list As we all know CakePHP has a great API website ( http://api.cakephp.org ) However, it lacks some features / goodies that can raise it to 'the next level'. So after some reading and learning - I have come up with a draft on how it COULD look / work. -- http://docs.cakephp.nu/ -- It's still in very early beta / testing, so don't expect the perfect golden solution for now :) This post is meant as a RFC ( Request For Comments ) post on how it should look, or perhaps some features that would be nice. Please note that this is not meant to 'overtake' any official CakePHP websites, and thus I'm not going to implement features that would compete with The Bakery or its friends. Its however most likely that if this little project of mine turns out successful, it will be donated to Cake Foundation, and linked to The Bakery user database and become tighter integrated with the CakePHP websites. Features I plan to implement is: - Manual page php.net style for each method or perhaps class - Comment archive for each function ( Imagine 900 Model posts :p ) - RSS feeds - Search Best regards Christian 'Jippi' Winther :) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC
Posted a new one at http://groups-beta.google.com/group/cake-php/t/c0189bfe2a49a9cc :) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC [new]
That is very cool - it could be very handy. But unless you want to be moderating it, you'll want a rule of no questions asked here - otherwise the discuss this function could get clagged up with people asking the same questions. This is what happens to the Macromedia Livedocs (of course, a little more popular than the Cake docs), which have a similar structure. Well done though. I'd actually be interested in a local version too - perhaps something to add to your features is the possibility of an automatically packaged static copy. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC [new]
Jippi wrote: As we all know CakePHP has a great API website ( http://api.cakephp.org ) However, it lacks some features / goodies that can raise it to 'the next level'. So after some reading and learning - I have come up with a draft on how it COULD look / work. -- http://docs.cakephp.nu/ -- Initial looks this is a great idea, well done Jipi. Features I plan to implement is: - Manual page php.net style for each method or perhaps class - Comment archive for each function ( Imagine 900 Model posts :p ) - RSS feeds - Search One idea will be to make sure each fuunction has it's introduction version and if it is deprecated, the date for deprecation, adn then subequent removal date. Maybe display the function details inline instead of jumping to the relevant section. Comment archive is good, and a link to examples in the Bakery that use a function may be good. RSS feeds? What were you invisioning to use them for? Search would be a great addition Output to a suitable print layout would be good, with ability to print a whole section. There you go - my two pennies worth. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC [new]
Looks like a great work in progress. I would definitely go there as a resource to find out how to unleash more power of CakePHP. I can see a few places where you might be able to Web 2.0 it up a little bit with Sciptaculous or Mootools ( I prefer Scripta because of the ample documentation. I won't even comment on Moo. ) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Unoffical API / Beta RFC
Greetings list As we all know CakePHP has a great API website ( http://api.cakephp.org ) However, it lacks some features / goodies that can raise it to 'the next level'. So after some reading and learning - I have come up with a draft on how it COULD look / work. -- http://docs.cakephp.nu/ -- It's still in very early beta / testing, so don't expect the perfect golden solution for now :) This post is meant as a RFC ( Request For Comments ) post on how it should look, or perhaps some features that would be nice. Please note that this is not meant to 'overtake' any official CakePHP websites, and thus I'm not going to implement features that would compete with The Bakery or its friends. Its however most likely that if this little project of mine turns out successful, it will be donated to Cake Foundation, and linked to The Bakery user database and become tighter integrated with the CakePHP websites. Features I plan to implement is: - Manual page php.net style for each method or perhaps class - Comment archive for each function ( Imagine 900 Model posts :p ) - RSS feeds Best regards Christian 'Jippi' Winther :) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC
Christian Winther [cwi.dk] [EMAIL PROTECTED] wrote: -- http://docs.cakephp.nu/ -- [...] This post is meant as a RFC ( Request For Comments ) post on how it should look, or perhaps some features that would be nice. Try resizing the window and fonts: 600px width, for example, to see page elements and lines colliding with each other. What are the requirements of the login system? Javascript? Moderator approval? Sending data to a foreign country? Also seems some bug with symbols, but I guess you know that. - Manual page php.net style for each method or perhaps class - Comment archive for each function ( Imagine 900 Model posts :p ) - RSS feeds I can't see how to get from the function description to its source code. A very useful thing might be linking to the php manual for things searched if they're not cakephp functions, or at least having an easily-grabbable (accesskey or maybe style=position:fixed) search box for it. Another useful thing would be to document the changes in functions (additions, removal, parameters) between cakephp versions over time. Hope that helps, -- MJR/slef http://www.ttllp.co.uk/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
RE: Unoffical API / Beta RFC
Hi The login system shouldn't require any special browser enabled features... Its just a plain old 'POST' form. Does it not work for you or ? -Original Message- From: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of MJ Ray Sent: 19. januar 2007 00:48 To: cake-php@googlegroups.com Subject: Re: Unoffical API / Beta RFC Christian Winther [cwi.dk] [EMAIL PROTECTED] wrote: -- http://docs.cakephp.nu/ -- [...] This post is meant as a RFC ( Request For Comments ) post on how it should look, or perhaps some features that would be nice. Try resizing the window and fonts: 600px width, for example, to see page elements and lines colliding with each other. What are the requirements of the login system? Javascript? Moderator approval? Sending data to a foreign country? Also seems some bug with symbols, but I guess you know that. - Manual page php.net style for each method or perhaps class - Comment archive for each function ( Imagine 900 Model posts :p ) - RSS feeds I can't see how to get from the function description to its source code. A very useful thing might be linking to the php manual for things searched if they're not cakephp functions, or at least having an easily-grabbable (accesskey or maybe style=position:fixed) search box for it. Another useful thing would be to document the changes in functions (additions, removal, parameters) between cakephp versions over time. Hope that helps, -- MJR/slef http://www.ttllp.co.uk/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
Re: Unoffical API / Beta RFC
Christian Winther [cwi.dk] wrote: Greetings list As we all know CakePHP has a great API website ( http://api.cakephp.org ) However, it lacks some features / goodies that can raise it to 'the next level'. So after some reading and learning - I have come up with a draft on how it COULD look / work. I think it looks pretty good so far. Keep up the good work, I'm looking forward to working with it. :-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Cake PHP group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~--~~~~--~~--~--~---
