- Zope - Zope lists

RE: [Zope] Zope Consulting Available
by Paul Everitt 15 Jun '99

15 Jun '99

I just wanted to follow up and say that I'm happy to see this happening! Those of us in the Python and ILU communities certainly know about Jody, so I find it exciting that his formidable skills are available in the commercial side of Zope. We do have to be careful not to let this list get too far on the crass commercial messages, so I'll point out that Jody contacted me directly before posting this. I asked him to go ahead and told him I'd follow up with an endorsement. Welcome, Jody! --Paul Paul Everitt Digital Creations paul(a)digicool.com 540.371.6909 ----------------------------------------- The Open Source Zope application server http://www.zope.org/ ----------------------------------------- > -----Original Message----- > From: Jody Winston [mailto:jody@ldeo.columbia.edu] > Sent: Tuesday, June 15, 1999 9:35 AM > To: zope(a)zope.org > Subject: [Zope] Zope Consulting Available > > > xprt Computer Consulting, Inc. provides consulting, software > engineering, software support, and training. We have particular > expertise in the following areas that may be of interest to Zope > users: > o Designing and developing Zope applications for the > scientific community. > o Designing and developing very large Python applications. > o Designing and developing Distributed Object Oriented > applications in Python, C++, Java, and C. > If we can assist you in your project please contact Jody Winston. > > Sincerely > Jody Winston > xprt Computer Consulting, Inc. > jody(a)sccsi.com > 281 480 8649 > > > > _______________________________________________ > Zope maillist - Zope(a)zope.org > http://www.zope.org/mailman/listinfo/zope > > (For developer-specific issues, use the companion list, > zope-dev(a)zope.org - http://www.zope.org/mailman/listinfo/zope-dev ) >

1 0

RE: [Zope] How to configure Zope & Python environment
by Michel Pelletier 15 Jun '99

15 Jun '99

> -----Original Message----- > From: steve(a)hosys.com [mailto:steve@hosys.com] > Sent: Tuesday, June 15, 1999 12:33 AM > To: zope(a)zope.org > Subject: [Zope] How to configure Zope & Python environment > > > Hello, > I am running Zope on windows using the builtin webserver and > attempting to > add a new Product. The way > I've been going about using Zope so far is to install a new > "Zope directory" > for each new project...not so > bad until I started trying to "compile" python code. It seems > to me I should > create a "default" install of > Zope and point my python path to those directories ? > > I am trying to compile the following Product code (below) and get the > following err message: > > Traceback (innermost last): > File > "C:\Tech\Lang\Python\Python152\Pythonwin\pywin\framework\scrip > tutils.py", > line 237, in RunScript > exec codeObject in __main__.__dict__ > File > "C:\Zope\ProjectMgt\lib\python\Products\ProjectMgt\projobjs.py", line > 1, in ? > from Globals import HTMLFile, MessageDialog, Persistent > File "C:\Zope\ProjectMgt\lib\python\Globals.py", line 90, in ? > import Acquisition, ComputedAttribute, App.PersistentExtra, os > File > "C:\Zope\ProjectMgt\lib\python\App\PersistentExtra.py", line 87, in ? > from Persistence import Persistent > ImportError: cannot import name Persistent > First, you want to put any "Zope Products" in Zopedir/lib/python/Products. Here, your products can find everything they need. Also, Persistent is in the Persistence package. from Persistence import Persistent I'm not sure if it's still in Globals, but you should get it from Persistence anyway. -Michel

1 0

Zope Consulting Available
by Jody Winston 15 Jun '99

15 Jun '99

xprt Computer Consulting, Inc. provides consulting, software engineering, software support, and training. We have particular expertise in the following areas that may be of interest to Zope users: o Designing and developing Zope applications for the scientific community. o Designing and developing very large Python applications. o Designing and developing Distributed Object Oriented applications in Python, C++, Java, and C. If we can assist you in your project please contact Jody Winston. Sincerely Jody Winston xprt Computer Consulting, Inc. jody(a)sccsi.com 281 480 8649

1 0

How to configure Zope & Python environment
by steve＠hosys.com 15 Jun '99

15 Jun '99

Hello, I am running Zope on windows using the builtin webserver and attempting to add a new Product. The way I've been going about using Zope so far is to install a new "Zope directory" for each new project...not so bad until I started trying to "compile" python code. It seems to me I should create a "default" install of Zope and point my python path to those directories ? I am trying to compile the following Product code (below) and get the following err message: Traceback (innermost last): File "C:\Tech\Lang\Python\Python152\Pythonwin\pywin\framework\scriptutils.py", line 237, in RunScript exec codeObject in __main__.__dict__ File "C:\Zope\ProjectMgt\lib\python\Products\ProjectMgt\projobjs.py", line 1, in ? from Globals import HTMLFile, MessageDialog, Persistent File "C:\Zope\ProjectMgt\lib\python\Globals.py", line 90, in ? import Acquisition, ComputedAttribute, App.PersistentExtra, os File "C:\Zope\ProjectMgt\lib\python\App\PersistentExtra.py", line 87, in ? from Persistence import Persistent ImportError: cannot import name Persistent My path settings are at the end of the code below. #-------projobjs.py--------------------------------------------------------- ------------------------ from Globals import HTMLFile, MessageDialog, Persistent import OFS.SimpleItem, Acquisition, AccessControl.Role import sys,DocumentTemplate projectDict = {} #MAPS PROJECT id string to PROJECT object taskDict = {} #MAPS TASK id string to TASK object class Project( OFS.SimpleItem.Item, Persistent, Acquisition.Implicit, AccessControl.Role.RoleManager, ): index_html = DocumentTemplate.HTMLFile("c:\Zope\ProjectMgt\lib\python\Products\ProjectMgt \project.dtml") _id = '' _name = '' _descr = '' _tasks = {} #list of Tasks I contain def __init__(self, projectID): self._id = projectID #setters def set_id(self, anID): self._id = anID def set_name(self, aName): self._name = aName def set_descr(self, aDescr): self._descr = aDescr def addTask(self, aTask): #require aTask not nul self._tasks[aTask.id()] = aTask #getters def id(self): return self._id def name(self): return self._name def descr(self): return self._descr #end class Project class Task: index_html = DocumentTemplate.HTMLFile("c:/Zope/ProjectMgt/lib/python/Products/ProjectMgt /task.dtml") _id = '' _name = '' _descr = '' _owner = '' #Person responsible for the task _project = '' #the project that contains me _budgeted_units = 0 _budgeted_unit_type = '' _budgeted_mhrs = 0 def __init__(self,ID): self._id = ID def test(self): #dump internals print('in Task test') #setters def set_id(self,anID): self._id = anID def set_name(self, aName): self._name = aName def set_descr(self, aDescr): self._descr = aDescr def set_project(self, aProject): #aProject: PROJECT self._project = aProject def set_budgeted_units(self,aUnits): #must match unit type self._budgeted_units = aUnits def set_budgeted_units__type(self,aUnitType): self._budgeted_units_type = aUnitType def set_budgeted_mhrs(self,aMHRS): self._budgeted_mhrs = aMHRS #getters def id(self): return self._id def name(self): return self._name def descr(self): return self._descr def budgeted_units(self): return self._budgeted_units def budgeted_units_type(self): return self._budgeted_units_type def budgeted_mhrs(self): return self._budgeted_mhrs #end class Task #---------------Call back functions for GUI------------------------ def addTaskToProject(aTaskID, aProjectID): #require valid id's and exist in the dictionaries prj = projectDict[aProjectID] task = taskDict[aTaskID] prj.addTask(task) #end addTaskToProject def createNewProject(anID,aName): p = Project(anID) p.set_name(aName) projectDict[p.id()] = p def createNewTask(anID,aName): t = Task(anID) t.set_name(aName) taskDict[t.id()]= t def dumpProjectDictContents(): for prjKey in projectDict.keys(): print 'project key: ' + prjKey + ' name: ' + projectDict[prjKey].name() def dumpTaskDictContents(): for key in taskDict.keys(): print 'task key: ' + key + ' name: ' + taskDict[key].name() def projectReport(): for prjKey in projectDict.keys(): print 'project key: ' + prjKey + ' name: ' + projectDict[prjKey].name() for taskKey in projectDict[prjKey]._tasks.keys(): print 'task key: ' + taskKey taskKey = '' #end createNewProject #-------------------------------------------------------------------- def testRun(): createNewProject('x123','Project A') createNewProject('y124','Project B') createNewProject('z125','Project C') # dumpProjectDictContents() createNewTask('t1231','Task A') createNewTask('t1232','Task B') createNewTask('t1233','Task C') createNewTask('t1241','Task D') createNewTask('t1242','Task E') createNewTask('t1251','Task F') createNewTask('t1252','Task G') # dumpTaskDictContents() addTaskToProject('t1231','x123') #some how all the tasks are added to all the projects addTaskToProject('t1241','y124') projectReport() #end testRun def testHTML(): t = Task('123') t.set_name('abc') t.set_descr('This is task abc easy as 123') print t.index_html(t) p = Project('456') p.set_name('def') p.set_descr('This is cool') print p.index_html(p) if __name__ == '__main__': #testRun() testHTML() set PYTHONPATH=.;c:\tech\lang\python\python152\lib;c:\tech\lang\python\python152 \lib-tk;c:\tech\lang\python\tcl\lib;c:\tech\lang\python\tcl\bin set PYTHONPATH=%PYTHONPATH%;c:\tech\lang\python\zopemodules set PYTHONPATH=%PYTHONPATH%;c:\tech\lang\python\zopemodules\DocumentTemplate set PYTHONPATH=%PYTHONPATH%;c:\tech\lang\python\zopemodules\Ofs set PYTHONPATH=%PYTHONPATH%;c:\tech\lang\python\zopemodules\ZPublisher set PYTHONPATH=%PYTHONPATH%;c:\tech\lang\python\zopemodules\Shared set PYTHONPATH=%PYTHONPATH%;c:\tech\lang\python\zopemodules\DateTime regards, Steve

2 1

Software for Zope
by Tom Deprez 15 Jun '99

15 Jun '99

Hi, I've here a proposition and I'm wondering if people would find it usefull or not. At the Zope site, you can find a directory with all the contributed software in one list. I'm wondering if we can't split it up a bit and with some more information. Maybe we can start a new Zope Site? or if we may, put it in Zope site itself, ... or perhaps in ZDP (although this is not really full documentation related). What about splitting up the software in categories, like Portals, news group software, navigation, .... Then for every product, we place the following info (besides of the creators, home-page?, ...) : -An introduction to what the product does and is. -A small demo example (like slides or animated gifs we've seen at Portal toolkit) -For which versions of Zope it is tested. -A newsgroup or mailing list to which people can subscribe to kept informed about that product. What you all think about this? Tom.

3 3

Re: [Zope] DTML reformulated as XML (was RE: [Zope] <% ... %> ?)
by Tony McDonald 15 Jun '99

15 Jun '99

>> I do want to point one thing out, though: adding namespaces does break >> the DTD. Currently there is no way to validate a document that uses > > Hmm, didn't realize that. > There's a big difference between validation (against a DTD) and well-formedness however. I suppose ideally you'll want validity, but for now (IMHO) stick with well-formedness (is that a word?). > > Here's one thing in DTML that would be awfully obscure in XML: > > <a href=""> > > That is, putting a tag inside an attribute. Chris Petrilli and Jim > talked about this today, perhaps as as entity references. > That'd be ok for the Zope variables that take no arguments (BASEn, URLn etc.) ie map BASE1 to &BASE1; but what about Zope variables that take attributes, eg ZopeTime fmt=whatever (for example, you'd use this awful construct to create a URL that had subparts such as /990612/) A very hairy problem. >> > At any rate, I'd love for someone in the Zope community to march off and >> > take a look at this, then make a proposal for how things should be >> > changed. As always, patches are accepted. :^) >> >> I've been meaning to do something like this. I might just spend some >> time thinking about it this weekend. Any actual coding probably won't >> happen, though. :) > > Understood. If you produced a clear definition of the goals, some > samples for the syntax, and a list of things that are good and bad about > it, then that would be a major win. > >> The simple stuff is easy: >> >> <?xml version='1.0'?> >> <xdtml:xdtml xmlns:xdtml="http://www.zope.org/xdtml" >> xmlns="http://www.w3.org/TR/xhtml1"> >> >> <xdtml:var name='standard_html_header'/> >> <h1><xdtml:var name='title'/></h1> >> This is a paragraph. >> >> <xdtml:if expr='age > 18'> >> Text not everyone should read. >> </xdtml:if> >> >> <xdtml:var name='standard_html_footer'/> >> >> </xtml:xdtml> > > I'd love to do a straw vote from the "I hate SSI" crowd: is the above > better? > No dis to Otto, but NIMHO. Too much typing. I'm from a PHP background where blocks of code exist in tandem with HTML. At first I had a real problem with DTML (still do, but that's another story :), but reading Paul and Chris' posts about separating code and data I realise that the DTML way is probably the best way to do it (as with so many other Zopey things). ps I don't hate SSI, and I don't have an alternative to the syntax Otto is describing - I should shut up now. >> The if gets really strange when you start adding 'elif' and 'else' >> clauses. I'll have to think about that one. >> >> The containing xdtml element is just there as a place to hang the >> namespace declarations off of. Also, it's there to make the DTML object >> a full-fledged self-contained XML document, needed to make any kind of >> editor useful. > > Precisely. It comes from the namespace declaration at the top. > > One more thing to muse over is whether other things from XML land should > surface. > > For instance, I've long wondered if the ubiquitous var tag should be > broken apart. People ask: why can't you give me a list of the things > that can go in the var tag? Why doesn't Zope check to see if my > documents reference subdocuments that no longer exist? The answer of > "it's too dynamic" feels like less than an answer. > > Instead, we could begin granularizing the tags, perhaps into things that > describe better where they came from. > > For instance, instead of saying , which > means insert a subdocument, why not use the XLink syntax from XML? > Would that not imply Zope parsing all elements in a page/object looking for attributes called xml:link? Isn't this a largeish overhead? It could also mean people writing <a xml:link="simple" href="standard_html_header" show="embed"/> instead of the above. Of course, if you get XLink stuff working in Zope, then presumably you get other interesting possibilities out too. rambling-ly yours, tone.

3 2

1st european zope hosting provider
by webman 15 Jun '99

15 Jun '99

hello all, beehive is pleased to announce that as of now we are the first company in europe to offer zope hosting services. we will initially offer 2 packages: *** Real Zope Site *** This is a complete zope server including product directory, and control panel. "Real" Zope installation 40 MB Hard Disk space 1 GB Data Transfer per month 5 POP Email Accounts Access log files FTP Access AND use of beehive's Dynamic Gif Generator Product monthlmy cost 85,- DM (43.46 Euro) (price does not include VAT) *** Euro Zope Site *** This is a complete zope server including product directory, and control panel. 50 MB Hard Disk space 1 GB Data Transfer 5 POP Email Accounts Access to log files FTP Access Confera, Tinytables preinstalled use of beehive Dynamic Gif Generator AND use of the new beeShop zope product. monthly cost: 99,- DM (50.62 Euro) (price does not include VAT) these prices do not include a domain. you may "bring your own" or have us reserve a domain for you (for a fee). mail mark(a)beehive.de for more details. or check out www.beehive.de "Zope Hosting Services". regards, webman --------------------------------------------------------------------------- webman | _ beehive GmbH | ASCII ribbon campaign ( ) berlin, Germany | - against HTML email X http://www.beehive.de | & vcards / \

1 0

RE: [Zope] <% ... %> ?
by Alexander Staubo 15 Jun '99

15 Jun '99

Very lucid and intelligent discussion, Paul. As an eager fan of XML, I second the idea to push XHTML as the next-generation Zope DTML syntax. If this is the goal, the "tag" syntax currently used by Zope can be preserved, with some modifications. I've jotted down a few examples of how such a modified syntax might look, at least as I see it. At least this is one possible angle. (Note: Best read in a monospaced font.) XML syntax:: Equivalent legacy syntax:: <zope:tree expr="PARENTS[-1]">  ... stuff ... ... stuff ... </zope:tree>  <zope:var expr="id()"/>  <zope:var obj="standard_html_header"/>  <zope:var>index_html</zope:var>  For non-XMLists, notice the use of the slash ("/") character to close up empty elements. Also note how all parameters to a tag are wrapped in true attributes. Something like <var "foo"> simply isn't permitted. Here's a sample of specifying a default namespace, so you that you use Zope tags without qualifying them with the "zope" namespace. Notice how this -- if it is to be done cleanly -- requires that you prefix HTML tags with the "html" namespace. I have not decided whether this is entirely necessary, since Zope will preprocess the DTML and in this case, would have to remote the "html:" prefix anyway. <in xmlns="http://www.zope.org/schema/1.0" expr="objectValues('DTML Document')"> <var>title_or_id</var><html:br> </in> Unfortunately, the idea that you can write something like <var standard_html_header> is rescinded by XML, unless ASP-like "blocks" of code as Jules Allen proposes can be included. Given the current syntax I can't conceive of a way that this can be done elegantly -- the minute we step into "ASP-like"-ness, we're in the realm of "defining a new language". While Jules' example syntax would certainly work on a technical level, the question is, as much as we abhor the current SSI syntax, do we really want to become more like ASP? -- Alexander Staubo http://www.mop.no/~alex/ "`This must be Thursday,' said Arthur to himself, sinking low over his beer, `I never could get the hang of Thursdays.'" --Douglas Adams, _The Hitchhiker's Guide to the Galaxy_ >-----Original Message----- >From: zope-admin(a)zope.org [mailto:zope-admin@zope.org]On Behalf Of Paul >Everitt >Sent: 11. juni 1999 20:09 >To: 'Jules Allen'; zope(a)zope.org >Subject: RE: [Zope] <% ... %> ? > > > >Jules wrote: >> Has it been suggested that the SSI-type syntax of Zope isn't the most >> readable thing in the world? Is this even the right list to >> suggest this >> heresy or should I strap on the asbestos underwear and wander >> over to zopedev? > >I'll comment first on the multiline statement. Let me reinforce the >idea that The Zope Way is to separate presentation and logic. While we >should have some kind of object that better deals with logic, I don't >think there will be much sympathy for creating something that >looks like >ASP or PHP. > >Let me limit the conversation back to your subject line: <% vs. <!--# > >The latter was originally chosen to be like the dominant syntax at the >time (SSI) and to be "legal HTML". I think the latter has proven to be >total bunk, as almost no DTML Documents are valid (they get nearly >everything from the fragments of standard header and footer). > >What are some reasons to consider changing from the SSI syntax? > > o It's hideous, cumbersome, and everybody hates it > > o No tools support editing it > > o It isn't conformant with the direction of HTML > > o Any others? > >Let's evaluate the situation in light of these. > >It's Hideous >------------ > >Yes. > >Tool Support >------------ > >The SSI syntax just happens to enjoy nearly zero support out there. >Things like Netscape Composer, Dreamweaver, and Emacs HTML Mode just >can't be convinced to handle it nicely. > >Does anyone view this issue as important? > >Future of HTML >-------------- > >What role does SSI play in the future of HTML? Zero. Of course, >neither do any of the alternative syntaxes mentioned previously. > >Thus, I'd like to list some requirements for a future syntax: > >1) Within reach of "content managers". I won't budge on this one. I >think XSL will have a role in Zope, but *NOT* as a DTML replacement. > >2) Reasonably close to DTML. The current DTML accomplishes some level >of functionality. While some small amount might not be permitted in >some change, or might be permitted in a clumsy way, there should be a >reasonable match. > >3) Coherent with the HTML future. We have a choice: invent a syntax >and, one by one, support every web authoring tool. Alternatively, we >can stick to standards and wait for them to support it. > >Proposal >-------- > >_If_ these were the requirements, then I think a reasonable proposal is >XHTML: > > http://wdvl.com/Authoring/Languages/XML/XHTML/ > > http://www.w3.org/MarkUp/#future > >XHTML reworks HTML as an XML-compliant language. Most imporantly, you >can extend it with new namespaces (like Zope instructions) without >breaking the DTD, as is the case with ColdFusion et al. > >Why? > >1) Alledgely it is the future of HTML. > >2) Becoming well-formed means the authors can be given hints before >saving changes, and Zope can do smarter things with structured data on >the server. > >Why Not? > >1) A number of differences with HTML might drive people off. > >2) It isn't here yet. > >3) Zope syntax might not be mappable into XML. > >At any rate, I'd love for someone in the Zope community to >march off and >take a look at this, then make a proposal for how things should be >changed. As always, patches are accepted. :^) > >--Paul > >Paul Everitt Digital Creations >paul(a)digicool.com 540.371.6909 >----------------------------------------- >The Open Source Zope application server >http://www.zope.org/ >----------------------------------------- > >_______________________________________________ >Zope maillist - Zope(a)zope.org >http://www.zope.org/mailman/listinfo/zope > >(For developer-specific issues, use the companion list, >zope-dev(a)zope.org - http://www.zope.org/mailman/listinfo/zope-dev ) >

2 1

[ANN: Zope2.0.0a2+ Win32 source patch]
by Anthony Pfrunder 15 Jun '99

15 Jun '99

BASE-RELEASE: Zope2_0_0a2-src.tgz RELEASE-DATE: 15-6-99 CONTACT: Anthony Pfrunder bruce_cop(a)bigfoot.com What is this? This zip file contains files and instructions for compiling Zope2 on Win32. This package features: * Automagic generation of *.dsp and *.dsw files for Microsoft Visual C 6.0. This is based on David Ascher's compile.py with heavy mods to allow recursive generation from the Setup files. [Thanks SquishDot guys!] * Support for dynamically loadable pyd's which can be used with any python binary * Independant of source code. This means that as python code is shifted to c and back the the *.dsp / *.dsw file's can be re-generated with a single stroke of "make" * A build environment which will generate a standalone directory structure for a zope console binary. This directory can be zipped up and moved to another machine without python and it will work out of the zip. Where to get? Email me at bruce_cop(a)bigfoot.com and I will email you the zopewin32.zip file. PS: It would be great if someone could place this into the distribution (my internet access is firewalled ,hence, no CVS access) Hope this helps some people, Anthony Pfrunder

2 1

<% ... %> ?
by Jules Allen 15 Jun '99

15 Jun '99

Has it been suggested that the SSI-type syntax of Zope isn't the most readable thing in the world? Is this even the right list to suggest this heresy or should I strap on the asbestos underwear and wander over to zopedev? I've used a bunch of Web-apps such Cold Fusion, PHP, ASP, etc., and the ones that have the cleanest organization to me seem to allow code blocks rather than single statements. So, to me, PHP and ASP are easier to maintain than Cold Fusion. Doesn't something like this - - - Cut Here - - - <% call "REQUEST.set('thistitle', title_or_id())" in "PARENTS[0].objectValues(['DTML Document', 'Folder'])" if "_.has_key('IsPublic') and IsPublic" if "thistitle == title_or_id()" %> <img src="/Images/activedoc.gif" width="8" height="8"><% var title_or_id %> <% else %> <img src="/Images/spacer.gif" width="8" height="8"><a href="<% var id url_quote %>"><% var title_or_id %></a> <% /if /if /in %> - - - Cut Here - - - seem easier to read than this? - - - Cut Here - - -     <img src="/Images/activedoc.gif" width="8" height="8">  <img src="/Images/spacer.gif" width="8" height="8"><a href=""></a>    - - - Cut Here - - - Yeah, easy for me to say "oh just go rewite the parser" and then walk away... Just a thought. -- Codito, ergo sum.

3 2