Thanks for making the issues, got to practice using commit to close the tickets :)
-Thadeus On Sun, Jan 24, 2010 at 7:48 PM, Thadeus Burgess <thade...@thadeusb.com> wrote: > Interesting, because HazelCMS is the werkzeug clone of frogcms which > is the clone of radiantcms. > > Funny how the wheel turns round, everyone wants to implement the same > thing in their own framework.... i'm sure there is a django clone of > this as well. I just liked the Admin page layout and felt it was > suiting. > > -Thadeus > > > > > > On Sun, Jan 24, 2010 at 7:43 PM, Richard <richar...@gmail.com> wrote: >> Thanks for taking the effort to extract this from your personal site. >> Have submitted those issues as tickets. >> >> Ah I thought the admin layout seemed familiar - I had been evaluating >> RadiantCMS (RoR), which FrogCMS is a PHP clone of. >> >> Richard >> >> >> On Jan 25, 12:15 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: >>> And the problem with not adding categories is probably a simple fix in >>> the SQLFORM requires. >>> >>> DO you mind filling out issue tickets on google code for these? >>> >>> -Thadeus >>> >>> >>> >>> On Sun, Jan 24, 2010 at 7:13 PM, Thadeus Burgess <thade...@thadeusb.com> >>> wrote: >>> > thadeusb.com is running blogitizor :) >>> >>> > the admin panel comes from frogcms. >>> >>> > So here is the story, I started this to be my website, so I have a >>> > theme based around python variables (if you visit my site you will >>> > quickly see). This is just part of that theme, and these should be >>> > included in the Configure() settings database at some point. There is >>> > still alot left to do to add features, and there is still a bit of >>> > cleanup that needs to be done. So what I did for blogitizor was take >>> > my website, strip it of as much personal things as I could such as my >>> > site theme etc etc, and then posted it. >>> >>> > oops, my bad on the broken symlinks. The py2jquery I don't even use >>> > except for a better alternative to response.files. I need to remove >>> > the dependency for it. >>> >>> > the layout.html simlink is because I have several layouts that can be >>> > used, and it allows to easily switch between them. Since my layout is >>> > mine I did not want to include it in blogitizor so I had to hack up a >>> > quick template, I don't like it and might use something like wordpress >>> > default theme. >>> >>> > I don't use localhost for developement, I bind to my PC's ip on the >>> > router, since I like to be able to fire up my windows box and check >>> > the site on IE, I suppose its one of those things everyone will need >>> > to edit for their self, but perhaps a meta is_devel() or PRODUCTION = >>> > True to be used in the end. >>> >>> > thanks for the patches >>> >>> > the XML is a patch that Massimo has obviously yet to apply. It is a >>> > bug in web2py WIKI helper instead of passing extras to markdown its >>> > passing extras to XML which is incorrect, you can look at my google >>> > clone of web2py gluon/contrib/markdown/__init__.py for the patch. >>> >>> > -Thadeus >>> >>> > On Sun, Jan 24, 2010 at 6:13 PM, Richard <richar...@gmail.com> wrote: >>> >> hi Thadeus, >>> >>> >> this code has heaps of awesome snippets that will be useful to reuse - >>> >> thanks for sharing! >>> >>> >> I love the black admin layout you've used with the flash message >>> >> embedded in the top section - do you mind if I reuse it? >>> >> And do you have a live website using blogitizer? >>> >>> >> I noticed a few problems, which I will email to you. >>> >>> >> Richard >>> >>> >> On Jan 24, 9:48 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: >>> >>> Ok. So I give it to you, the source of blogitizor. Its not my best >>> >>> work, but I am limited by the quirks of web applications :( >>> >>> >>>http://code.google.com/p/blogitizor/ >>> >>> >>> There is a install notes and dependencies on the wiki. >>> >>> >>> Just some notes to help navigate, I use letters to execute models in >>> >>> the correct order, I have a class that handles configurations and in >>> >>> the progress of merging all of the code to use a settings database >>> >>> where applicable. >>> >>> >>> There is also a menumanager class to help handle/render menus. >>> >>> >>> Output is automatically compressed when in an production environment. >>> >>> >>> models/z_migrate will actually migrate your wordpress over if you have >>> >>> any, to do this go to admin controller, and imex, then browse for your >>> >>> wordpress.xml export file, and click wordpress import. >>> >>> >>> layout.html is just a softlink to efflorescenetorange, so you might >>> >>> need to recreate it. I would suggest making your own layout, I don't >>> >>> like the orange one but was wanting to get this out there at least. >>> >>> >>> you will need to install guppy and pygments to use this, hopefully I >>> >>> can have these optional dependencies instead of required later on. >>> >>> >>> If anybody would like to start helping me with this let me know, it >>> >>> would be awesome if we can get a single official web2py blog, I know a >>> >>> handful of us are working on our own blog implementations, I think we >>> >>> would really benefit by combining our skills together on one system. >>> >>> >>> Hope yall enjoy the code :) >>> >>> >>> -Thadeus >>> >>> >> -- >>> >> You received this message because you are subscribed to the Google >>> >> Groups "web2py-users" group. >>> >> To post to this group, send email to web...@googlegroups.com. >>> >> To unsubscribe from this group, send email to >>> >> web2py+unsubscr...@googlegroups.com. >>> >> For more options, visit this group >>> >> athttp://groups.google.com/group/web2py?hl=en. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "web2py-users" group. >> To post to this group, send email to web...@googlegroups.com. >> To unsubscribe from this group, send email to >> web2py+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/web2py?hl=en. >> >> > -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.