archive-org.com » ORG » R » REPOZE.ORG

Total: 111

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Repoze Blog :)
    untouched Reducing the amount of unique to Plone stuff that is important to getting started can help reduce fear of the unknown and learning curve Sometimes this design already exists and doesn t need to be compiled into ZPT packages Web designers probably don t want to run a Plone install to maintain the the branding Theme resources such as CSS and JS will be served from the HTTP server directly Focusing Plone on the semantic information unique to a single resource URL will promote other goals such as integration It is possible that performance improves if less is done in ZPT and Zope If Plone moves to a more Python friendly WSGI philosophy then theming non Plone sites with the same artifacts is a benefit Again just to be clear the single biggest goal is to be kind to civilians Sitetheming in a nutshell First a point about nomenclature Since theming was introduced as a Plone word that covers skinning templating and to a degree programming this proposal temporarily chooses a new word We will call this new facility sitetheming to disambiguate jargon skew Perhaps at the end we ll just call this theming Most pages in a site share lots of common elements Logo site menu links footer links to CSS and JS etc This is usually referred to branding look and feel or corporate identity On larger projects the people managing the branding have little desire to learn a new system On smaller projects with people just learning they haven t mastered enough yet to make the pages their own Sitetheming is a facility for imposing a common look and feel on most site pages using no templating Instead the designer or customizer maintains a pile of HTML CSS JS PNG artifacts at some reachable location The

    Original URL path: http://blog.repoze.org/what-sitetheming-2-20080218/ (2016-01-08)
    Open archived version from archive


  • Repoze Blog :)
    some of these concerns up front If any of this sounds like you please speak up during this process The goal is to make something uniquely useful and simple for the non core developer audience We certainly don t want to do something that you won t like If you simply must read more about site themes here is a writeup I made long ago on the Zope wiki and here is the introduction to Deliverance Alternatively wait until my next few posts Why Not Plone 2 5 and or Plone 3 0 is easy enough to theme Falls into the ain t broke don t fix it category My sense is that theming is hard is a common complaint by the target audience but perhaps I m mis reading the tea leaves It s hard but worth it Currently theming skinning templating programming are all part of the same facility This lets you do just about anything Creating an isolated stripped down theme engine thus breaks that proposition I m both the developer and the UI person If you re mostly a developer who also does the UI you might not want to learn a new facility as you re still going to be the person doing the page content generation People will invariably stray over the line We always encourage a clear line between presentation and content However the moment you have something straddling the line e g the contents of a calenar portlet that discipline feels restraining I ll never have non Plone As part of this proposal we d like to encourage moving stuff out the Zope stack allowing it to be applied across other Python stuff However that might not be your itch Having a corporate ID that could be used with other Plone apps

    Original URL path: http://blog.repoze.org/why-sitetheming-1-20080214/ (2016-01-08)
    Open archived version from archive

  • Repoze Blog :)
    but are document in its INSTALL txt bin easy install buildbot zope interface The remaining dependency is Twisted which can t be installed via easy install its setup is complex and hasn t yet adapted to the setuptools regime So I installed it the old fashined distutils way mkdir src cd src wget http tmrc mit edu mirror twisted Twisted 2 5 Twisted 2 5 0 tar bz2 tar xjf Twisted 2 5 0 tar bz2 cd Twisted 2 5 0 bin python setup py install Now I could verify that the buildbot application was working bin buildbot version Buildbot version 0 7 6 Twisted version 2 5 0 I then created and initiailzed the buildbot master work area and set up a configuration lots of iterative tweakage elided here mkdir p var masters repoze bin buildbot create master var masters repoze cp var masters repoze master cfg sample vim var masters repoze master cfg bin buildbot start var masters repoze Setting up a buildslave Next I could work on setting up the first buildslave mkdir p var slaves repoze bin buildbot create slave var slaves repoze repoze org 9980 laguna I used the slavename password which I had created in the master cfg file Then I edited the two info files identifying me and my host and then started the buildbot slave daemon vim slave repoze info admin host bin buildbot start slave repoze It connected and I could see it on the status page Now I tried a forced build which worked after more iterative tweakage The builder recipe I m using does the following whenever it is triggered either manually or when its change source notices a change checks out the branch containing the change e g repoze kiss trunk runs bin python setup py test in

    Original URL path: http://blog.repoze.org/continuous_integration_via_buildbot-20080214/ (2016-01-08)
    Open archived version from archive

  • Repoze Blog :)
    at the Seattle Plone Gathering February 12th Chris McDonough will be making a presentation on Repoze to the Seattle Plone Gathering this Tuesday February 12th starting at 6 00 PM Thanks very much to Andrew Burkhalter for organizing the event

    Original URL path: http://blog.repoze.org/seattle_plone_gathering-20080212/ (2016-01-08)
    Open archived version from archive

  • Repoze Blog :)
    3 were put up yesterday The major change to all of them is that we made it easier to install these without relying on the repozeproject installer wrapper Instead the preferred installation mechanism is to create a virtualenv by hand Their respective README txt files have the new regime documented and Carlos has kindly updated his tutorials on getting both Grok and Plone installed under mod wsgi to reflect these

    Original URL path: http://blog.repoze.org/carlos-updates-tutorials-20080206/ (2016-01-08)
    Open archived version from archive

  • Repoze Blog :)
    sees Repoze Deliverance in Plone s Future In a fascinating bit of science fiction Martin Aspeli explores the possible user experience of Pete and Andy the next generation of Plone newbies His tale features both Repoze and Deliverance prominently as the favored means for skinning and deploying Plone Martin then follows up by examining his flight of fancy as a roadmap forward for Plone in particular highlighting the need for

    Original URL path: http://blog.repoze.org/aspeli-crystal_ball-200800205/ (2016-01-08)
    Open archived version from archive

  • Repoze Blog :)
    Carlos de la Guardia s repoze grok Tutorial on grok zope org Carlos has written an excellent tutorial on running a Grok application under repoze grok and mod wsgi Check it out Update 2 4 Carlos blogs about this tutorial

    Original URL path: http://blog.repoze.org/cguardia-repoze.grok-tutorial-20080130/ (2016-01-08)
    Open archived version from archive

  • Repoze Blog :)
    so of our PyATL talk about repoze zope2 The video is just talking heads you can t see slides or anything but cool nevertheless Relevant links PyATL Video Slides Noah s post on WSGI as Howard Roark of Python web development Noah s post on the simplest possible WSGI app as developed at the PyATL sprint Many thanks to Noah Derek Richardson Brandon Craig Rhodes who most graciously put us

    Original URL path: http://blog.repoze.org/pyatl-video-20071223/ (2016-01-08)
    Open archived version from archive