Thanks for the feedback! About the .htaccess thing, for some reason, on my ubuntu laptop, it never works unless i use absolute urls.
The database-based configuration looks interesting, I'll look into that. I'll try to fit a preview somewhere on the page. I haven't added any AJAX yet -- I'm planning on doing that once I have all of the core functionality, so that it will still work on browsers that don't support AJAX. (BTW, not sure exactly what you mean by "limiting scope") I'm planning on using the textile editor helper too. Also, I agree about the textile behavior thing. By the way, should I include a WYSIWYG editor? It's hard for me decide. I don't want to, but some people will probably want to copy-paste from MS Word. I'm thinking about letting them upload a MS Word HTML file and then cleaning the HTML. What do you guys think? Your 5th comment is confusing me right now, I'll try reading it again later :P About #6 - are you talking about the install process? Thanks again for the feedback. On May 21, 4:01 am, Travis Cline <[EMAIL PROTECTED]> wrote: > > Let me know what you guys think! > > Looks pretty nice, I like that you're accepting a limited scope. > > A few issues: > 1. Was just playing around a bit, if you submit a blank note you get > an error -- there isn't handling of the save-failed case. Maybe > redirect back unconditionally and flash a fail/success message? > 2. I don't think the path-specific info you have in those > two .htaccess files is needed, the defaults should be fine. > > Possible improvements : > 1. You might consider at moving towards the a db-backed for site > configuration -- maybe check > outhttp://bakery.cakephp.org/articles/view/confcomponent-db-based-config... > > 3. An ajax preview. > I realize you're not currently using any JavaScript (and that helps in > terms of limiting scope) so I realize you may not want to do this. > I vote jQuery =) > > 2. Adding this:http://slateinfo.blogs.wvu.edu/plugins/textile_editor_helper > (Cake-port > here):http://bakery.cakephp.org/articles/view/textile-editor-helper-for-cake > It'd be conditional of course -- something to consider with #4 below > (maybe do an xhr request to get the editor for the current rendering- > path -- if present?) > > 4. Also, the way you're including Textile isn't very clean IMO, check > out my comment on this > articlehttp://bakery.cakephp.org/articles/view/textile-1 > > 5. I don't really dig the duplication and restriction of the rendering > paths as enums and how they're rendered. If you broke it out so adding > a new rendering path was a record-addition and a file addition (or > method addition) that'd rock. > > 6. I'd add in permission checks -- getting it to the state of drop in > and hit the browser would be pretty slick. > > Great stuff! > Get a few kinks out, an little install process and you've got a pretty > sweet app. > > -- > Travis --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
