| benji_york | projekt01, fdrake has left the channel, if it's important, I can ask him to come back | 00:04 |
|---|---|---|
| *** bskahan has quit IRC | 00:06 | |
| projekt01 | benji_york, thanks no that's ok. just wrote a mail to him, found a bug in zpkg. | 00:07 |
| benji_york | ok | 00:08 |
| srichter | benji_york: I thought browser.get() would take by default the name? | 00:10 |
| *** bradb-bbl is now known as bradb | 00:11 | |
| benji_york | srichter, I just repliled to your message :) | 00:14 |
| projekt01 | srichter, did you wrote a document about the zpkg release process for 3.1? Are there any docs about which *.map to use? | 00:14 |
| srichter | projekt01: yes, see MakingARelease | 00:15 |
| projekt01 | srichter, thanks a lot, found it at: http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/MakingARelease | 00:17 |
| srichter | yes | 00:18 |
| srichter | that's it | 00:18 |
| srichter | I keep this document up-to-date, since I use it to make releases | 00:18 |
| srichter | note that Fred said that the current zpkgtools is broken with the Zope 3.1 release | 00:19 |
| projekt01 | Why? | 00:19 |
| srichter | you have to ask him | 00:19 |
| srichter | he made some changes today | 00:20 |
| srichter | benji_york: maybe ask Fred to come online again to talk to Roger ;-) | 00:20 |
| benji_york | sure | 00:21 |
| *** fdrake has joined #zope3-dev | 00:22 | |
| fdrake | Yo! | 00:22 |
| srichter | benji_york: ok, I like Gary's answer, but not yours, so I give up; I just do not have enough energy today ;-) | 00:22 |
| benji_york | :) | 00:23 |
| projekt01 | Hi fdrake, srichter told that zpkg is broken with 3.1 | 00:23 |
| fdrake | the zpkg trunk, yes | 00:23 |
| fdrake | i have a patch for 3.1 already | 00:23 |
| *** timte has quit IRC | 00:24 | |
| fdrake | but I'm not entirely ready to commit since it impacts packages from the ZODB project | 00:24 |
| *** gintas has quit IRC | 00:24 | |
| fdrake | don't use the zpkg trunk for 3.1; use two zpkg changesets back | 00:24 |
| fdrake | (for now) | 00:24 |
| srichter | will the two changesets back work on Windows? | 00:25 |
| projekt01 | what's that, changeset? | 00:25 |
| srichter | what do you need roger to test there? Run tests and build the TAR ball? | 00:25 |
| srichter | projekt01: two revisions back | 00:25 |
| fdrake | for Windows, get the trunk and undo the changeset before the last :-) | 00:25 |
| projekt01 | Ah, you mean the zpkg checkout | 00:26 |
| projekt01 | Or the z3 trunk? | 00:26 |
| srichter | zpkgtools checkout | 00:26 |
| projekt01 | Ok. | 00:26 |
| projekt01 | I think I have a different issue where I first have to solve. | 00:26 |
| projekt01 | could not load from svn://svn.zope.org/repos/main/zpkgtools/trunk/zpkgsetup (exit code 1) | 00:26 |
| fdrake | i don't think the branch will let me commit to the ZODB packages any more than the trunk will | 00:26 |
| projekt01 | Or is this what you mean? | 00:26 |
| srichter | fdrake: nope | 00:27 |
| srichter | the disadvantage of svn:externals | 00:27 |
| fdrake | projekt01, you should use svn://svn.zope.org/repos/main/zpkgtools/trunk/ | 00:27 |
| projekt01 | That was not me, this is called from a *.map I guess | 00:28 |
| fdrake | ah; remove the support map from your config :-) | 00:28 |
| fdrake | that's optional now; zpkg will use it's own sources if no entry is configured for zpkgsetup | 00:29 |
| fdrake | that change to the map file is safe to commit | 00:29 |
| fdrake | srichter, when is the Zope-3.1c2 release scheduled? | 00:30 |
| projekt01 | Ok, but then I get the following error | 00:30 |
| projekt01 | could not load from svn://svn.zope.org/repos/main/Zope3/trunk/releases/ZopeX3 (exit code 1) | 00:30 |
| fdrake | remove the X3; jim changed some things | 00:30 |
| srichter | fdrake: I dunno :-) I'll shoot for the weekend | 00:30 |
| fdrake | are you using a private .map file? | 00:30 |
| fdrake | or releases/Zope.map? | 00:31 |
| fdrake | i think I need to release zpkg so we can say "use this version" | 00:31 |
| projekt01 | I use a zpkg.conf in my users home like described in the quickstart.txt of zpkg | 00:32 |
| fdrake | Jim doesn't like that; I need to update that doc | 00:32 |
| fdrake | use: "zpkg -C releases/Zope.cfg -cav 3.1.0cX Zope" | 00:33 |
| fdrake | that'll be getting simpler, too, but I don't want to move too fast | 00:33 |
| projekt01 | IOError: [Errno 2] No such file or directory: 'releases/Zope.cfg' | 00:34 |
| projekt01 | if I try: python zpkg -C releases/Zope.cfg -cav 3.1.0cX Zope | 00:34 |
| fdrake | i just sprung a set of coming changes on Tim today; I need to finish those so he can proceed | 00:34 |
| fdrake | is this from the top of the checkout | 00:34 |
| fdrake | ?? | 00:34 |
| projekt01 | Ah, no, Ok I have to call this in the trunk checkout. | 00:35 |
| fdrake | (the Zope-3.1 checkout) | 00:35 |
| fdrake | for the relative path | 00:35 |
| fdrake | you can adjust that however you want; paths are resolved relative to where they're expressed | 00:36 |
| projekt01 | I get the same error: | 00:37 |
| projekt01 | could not load from svn://svn.zope.org/repos/main/zpkgtools/trunk/zpkgsetup (exit code 1) | 00:37 |
| fdrake | just a sec... | 00:38 |
| projekt01 | Where do I get this path? Is there a wrong path from a *.map loaded? | 00:38 |
| projekt01 | Ok | 00:39 |
| fdrake | update Zope-3.1 and try again with the cmd line i gave you | 00:41 |
| fdrake | the "-C" must be upper case | 00:42 |
| projekt01 | Ok, Ah, you mean the branch Zope3-1, I have to checkout first, will take a moment. | 00:44 |
| fdrake | yes, the branch, since that's the source of the next release :-) | 00:44 |
| fdrake | we can forward-port once we're done playing around | 00:44 |
| projekt01 | Yes, that's Ok, I just like to bring zpkg up and running on windows, no need to make a release now. | 00:45 |
| *** bskahan has joined #zope3-dev | 00:46 | |
| fdrake | that should avoid the need for the quoting fix as well, since the files will be pulled from the checkout | 00:46 |
| fdrake | IOW, you should be able to use zpkg revision 37845, no changes | 00:48 |
| projekt01 | I just checked out revision 37851 from zpkg. Is this Ok or should I set it back to 37845 | 00:50 |
| projekt01 | I think the "windows cmd quote fix" is done in the revision 37850 | 00:51 |
| fdrake | back up to 37845; you don't want the Includes/ directory change | 00:51 |
| projekt01 | Ok | 00:51 |
| fdrake | you shouldn't need the quoting fix since you'll be avoiding cvs/svn now | 00:51 |
| fdrake | which speeds things up a lot :-) | 00:52 |
| projekt01 | Ok, done, the branch is still downloading | 00:52 |
| fdrake | aren't networks great? | 00:53 |
| fdrake | where are you? | 00:53 |
| projekt01 | Yeah, in switzerland, Zug | 00:53 |
| fdrake | ah | 00:53 |
| fdrake | so your connection is distinctly worse than mine today :-) | 00:55 |
| projekt01 | btw, is it normal that after changing the external (like ZODB etc) in subversion, that I get ZODB.OLD everytime | 00:56 |
| projekt01 | Yup | 00:56 |
| fdrake | it appears to be; I get those as well | 00:56 |
| projekt01 | Ok | 00:56 |
| projekt01 | That's wired. I get the following error: but the releases folder exist. | 01:00 |
| projekt01 | IOError: [Errno 2] no such file or directory: '\\..\\releases\\Zope' | 01:00 |
| projekt01 | is this another quoting problem? | 01:00 |
| srichter | from where do you execute what? | 01:01 |
| projekt01 | from the root where the /src is a child of | 01:02 |
| srichter | what command do you run? | 01:02 |
| projekt01 | But doesn't work in the src folder too | 01:02 |
| projekt01 | python D:\projektDemo\zpkgtools\bin\zpkg -C releases/Zope.cfg -cav 3.1.0cX Zope | 01:02 |
| srichter | mmh, loos like a bug | 01:02 |
| fdrake | i run from the parent of src | 01:02 |
| *** dman13_ is now known as dman13 | 01:03 | |
| fdrake | looks like a WIndows-compatibility bug | 01:03 |
| projekt01 | Yes the root is the parent of the src | 01:03 |
| benji_york | projekt01, are you typing the double backslashes? | 01:03 |
| projekt01 | No | 01:03 |
| benji_york | oh, is that a repr of a string | 01:03 |
| fdrake | IOW, a Windows bug | 01:03 |
| benji_york | oh, ok | 01:03 |
| projekt01 | btw, I didn't set zpkg as a global script | 01:04 |
| projekt01 | I guess it's ok, or is it used somewhere else | 01:05 |
| fdrake | that shouldn't matter | 01:05 |
| projekt01 | Ok | 01:05 |
| fdrake | i wonder if you need this change: http://svn.zope.org/zpkgtools/trunk/zpkgtools/config.py?rev=37846&r1=37756&r2=37846 | 01:07 |
| fdrake | it's a part of the Includes/ removal, but may be relevant | 01:07 |
| *** dman13 has quit IRC | 01:07 | |
| fdrake | at least on Windows | 01:07 |
| fdrake | are z3.py and utilities/runurl.py supposed to be installed on any platform? | 01:11 |
| *** SureshZ has quit IRC | 01:11 | |
| *** yota has quit IRC | 01:12 | |
| *** dman13 has joined #zope3-dev | 01:12 | |
| projekt01 | Yes, they are on my checkout | 01:12 |
| projekt01 | I'll try to apply the patch | 01:13 |
| fdrake | they're marked as scripts in the setup.py, but are they useful? | 01:13 |
| fdrake | z3.py seems not, given that the instance contains runzope/zopectl | 01:13 |
| fdrake | (don't know about Windows, though) | 01:13 |
| projekt01 | I only use "python z3.py" for starting zope during development on my win box, I never used something else | 01:15 |
| fdrake | what do you use for production? | 01:15 |
| projekt01 | python z3.py | 01:16 |
| fdrake | (I don't want to remove z3.py or utilities/runurl.py, I just don't want to install them if they're not used that way) | 01:16 |
| fdrake | ah | 01:16 |
| fdrake | I'm not sure what the Windows service story is right now; I know for a recent project, we install and run as a service. | 01:17 |
| fdrake | Not sure how much of that is part of the stock Zope 3 yet, though. | 01:17 |
| projekt01 | Ah, I don't use the distributed zope. I always build zope with msvc ++ 7.0 with py 2.4.1 by myself, also for production | 01:18 |
| fdrake | do you use an installer for Windows platforms? | 01:18 |
| projekt01 | I update to the latest zpkg version which includes the fix and get the following error | 01:19 |
| projekt01 | could not load from svn://svn.zope.org/repos/main/Zope3/trunk/zopeskel/ (exit code 1) | 01:19 |
| fdrake | weird | 01:19 |
| projekt01 | Was that wrong should I only apply the patch to the version 37845? | 01:19 |
| fdrake | i think that's right | 01:21 |
| projekt01 | Hm, I double checked the svn url. The location svn://svn.zope.org/repos/main/Zope3/trunk/zopeskel/ exists. | 01:21 |
| fdrake | i wonder why it's looking there | 01:22 |
| projekt01 | Where does this url came from? | 01:22 |
| projekt01 | Yes me too | 01:22 |
| fdrake | there's some code in zpkg that tries to "prefer" svn:/cvs: URLs; I think that was a mistake, though it fit the original requirements | 01:23 |
| fdrake | perhaps it's time to rip that out as well | 01:23 |
| fdrake | unfortunately, that means reading through the tests again and seeing what has to change there | 01:23 |
| fdrake | other than what just breaks | 01:24 |
| projekt01 | the test of zpkg are running well on my win box | 01:24 |
| fdrake | that's a good start, but means it needs more tests :-( | 01:25 |
| fdrake | (not surprising really) | 01:25 |
| projekt01 | Ok, I'm not in hurry. Take your time, you can drop me a note if I should test it again | 01:25 |
| projekt01 | If this is fine with you. | 01:25 |
| fdrake | ok, i'll see what I can get done over the next day | 01:25 |
| *** SureshZ has joined #zope3-dev | 01:25 | |
| projekt01 | I think we are ready to make a release in a month or so. | 01:26 |
| fdrake | ok, my target's Zope 3.1.0 if possible, so I think you'll be set | 01:28 |
| fdrake | Tim likes to build his own tarball for the Windows installer, so the Windows testing will get done before long | 01:29 |
| projekt01 | Oh, cool | 01:29 |
| philiKON | fdrake, i presume your changes to zpkg will also effect the X3.0 branch. will there be a note as to what needs to be changed in the package configuration? | 01:30 |
| projekt01 | fdrake, let me know if I can test or help something | 01:30 |
| fdrake | presumably that, or I'll just change things :-) | 01:30 |
| fdrake | projekt01, thanks! | 01:30 |
| philiKON | fdrake, ok | 01:31 |
| projekt01 | fdrake, thanks a lot to you! | 01:31 |
| fdrake | hmm, building a Zope-3.1c2 release from the branch, I don't end up using any svn URLs | 01:31 |
| fdrake | so i'm really confused about what's happening | 01:31 |
| fdrake | i'll go rip some code out :-) | 01:32 |
| fdrake | that should be therapeutic, at least | 01:32 |
| projekt01 | ;-) | 01:32 |
| *** benji_york has quit IRC | 01:32 | |
| philiKON | +1 to resource maps being gone... it took me two releases to finally understand how zpkg works :) | 01:38 |
| philiKON | srichter, are you using the -k switch of wget? | 01:42 |
| srichter | no, but this did not matter | 01:44 |
| philiKON | ic | 01:45 |
| philiKON | it should matter for links though | 01:45 |
| srichter | how so? | 01:45 |
| philiKON | with the -k switch, wget postprocesses html files and changes all links so that they work from the filesystem | 01:46 |
| fdrake | philiKON, maps aren't gone, but no longer require a separate file | 01:46 |
| philiKON | fdrake, that's what i meant | 01:46 |
| *** SureshZ has quit IRC | 01:46 | |
| philiKON | fdrake, the number of files required for a zpkg setup was (probably still is) just too high | 01:46 |
| srichter | I thought it worked otherwise too | 01:46 |
| srichter | I think I checked this | 01:46 |
| philiKON | wget leaves the html pagees intact otherwise | 01:47 |
| srichter | I see | 01:47 |
| *** SureshZ has joined #zope3-dev | 01:47 | |
| philiKON | the -p switch is also useful | 01:48 |
| philiKON | it fetches page requisites | 01:48 |
| philiKON | such as CSS | 01:48 |
| philiKON | and JS | 01:48 |
| srichter | philiKON: btw, I think Node.expand() does not behave correctly | 01:48 |
| fdrake | philiKON, there were definately too many files | 01:48 |
| philiKON | srichter, :( | 01:48 |
| *** niemeyer has quit IRC | 01:48 | |
| srichter | when I say Node.expand(True), the _expanded_noeds attribute does not get updated | 01:48 |
| srichter | but it should | 01:48 |
| philiKON | oh | 01:48 |
| fdrake | the current practice is moving to avoid centralized maps so everything can be versioned as a unit | 01:49 |
| fdrake | except zpkg itself, which remains versionless :-( | 01:49 |
| philiKON | :( | 01:49 |
| philiKON | would be cool if there was a zpkg release | 01:49 |
| fdrake | that will be fixed | 01:49 |
| philiKON | at some point i wanna try running zope inside an egg | 01:50 |
| philiKON | srichter, if you can't fix it, file a bug and assign it to me; i'll have a look next week | 01:52 |
| philiKON | good night all | 01:52 |
| fdrake | philiKON, me too! I wanna run with the dependencies (esp. ZODB) in separate eggs | 01:52 |
| fdrake | g'nite | 01:52 |
| philiKON | fdrake, yes, that'd be cool | 01:52 |
| philiKON | or, even, with zope.interface, zope.testing etc. in eggs | 01:52 |
| philiKON | be very modular | 01:52 |
| philiKON | like debian does it with the zope3-lib package and python24-zopeinterface etc. already | 01:53 |
| fdrake | yes, those as well | 01:57 |
| fdrake | i'm more concerned about ZODB for that since it's handled in a completely separate tree, and we keep ending up with *.OLD turds | 01:58 |
| fdrake | that doesn't seem to happen as much for zope.testing, and not at all for zope.interface (since it's not an external) | 01:58 |
| *** bradb is now known as bradb-bbl | 02:10 | |
| fdrake | ok, the zpkg quick start has been updated to better reflect the current state; the online version is up to date as well | 02:12 |
| fdrake | http://www.zope.org/Members/fdrake/zpkgtools/quickstart.html | 02:12 |
| *** suresh has joined #zope3-dev | 02:25 | |
| *** SureshZ has quit IRC | 02:26 | |
| projekt01 | fdrake, thanks that helps to understand it better. | 03:00 |
| *** suresh has quit IRC | 03:16 | |
| bob2 | hm | 03:27 |
| bob2 | is fp known to be broken in the trunk? | 03:27 |
| *** SteveA has quit IRC | 03:36 | |
| *** SteveA has joined #zope3-dev | 03:38 | |
| *** jinty has left #zope3-dev | 03:56 | |
| bob2 | I wish all the ECM demos weren't flash | 03:57 |
| *** MiUlEr has joined #zope3-dev | 04:19 | |
| *** d2m has quit IRC | 04:20 | |
| *** MiUlEr has quit IRC | 04:21 | |
| *** projekt01 has quit IRC | 04:49 | |
| *** fdrake has quit IRC | 05:01 | |
| srichter | fp? | 05:18 |
| bob2 | er, FTP | 05:19 |
| srichter | no, it should work | 05:20 |
| srichter | good night | 05:20 |
| bob2 | ls: Fatal error: 500 Internal error: AttributeError: 'FTPRequest' object attribute '__provides__' is read-only | 05:21 |
| bob2 | I guess I should file a bug | 05:21 |
| *** MiUlEr has joined #zope3-dev | 05:22 | |
| *** SureshZ has joined #zope3-dev | 05:40 | |
| *** bskahan has quit IRC | 05:41 | |
| *** RaFromBRC has quit IRC | 05:48 | |
| *** SureshZ has quit IRC | 05:51 | |
| *** tvon has quit IRC | 06:38 | |
| *** tvon has joined #zope3-dev | 07:04 | |
| *** zagy_ has quit IRC | 08:03 | |
| *** zagy_ has joined #zope3-dev | 08:09 | |
| *** RaFromBRC has joined #zope3-dev | 08:19 | |
| zagy_ | moin | 08:19 |
| *** zagy_ is now known as zagy | 08:23 | |
| *** srichter has quit IRC | 08:25 | |
| *** sashav has quit IRC | 08:50 | |
| *** RaFromBRC has quit IRC | 09:05 | |
| *** hdima has joined #zope3-dev | 09:11 | |
| *** zagy has quit IRC | 09:22 | |
| *** zagy has joined #zope3-dev | 09:22 | |
| *** MJ has quit IRC | 09:44 | |
| *** yota has joined #zope3-dev | 10:13 | |
| *** sashav has joined #zope3-dev | 10:30 | |
| *** sashav has joined #zope3-dev | 10:31 | |
| *** Aiste has joined #zope3-dev | 10:47 | |
| *** mgedmin has joined #zope3-dev | 10:57 | |
| *** ignas has joined #zope3-dev | 11:05 | |
| *** MJ has joined #zope3-dev | 11:06 | |
| *** gintas has joined #zope3-dev | 11:07 | |
| *** anguenot has quit IRC | 11:32 | |
| *** projekt01 has joined #zope3-dev | 11:33 | |
| *** alga has joined #zope3-dev | 12:14 | |
| *** faassen has joined #zope3-dev | 12:20 | |
| *** ignas has quit IRC | 12:55 | |
| *** ignas has joined #zope3-dev | 12:59 | |
| *** d2m has joined #zope3-dev | 13:00 | |
| *** stub has quit IRC | 13:11 | |
| *** stub has joined #zope3-dev | 13:11 | |
| *** MrTopf has joined #zope3-dev | 13:13 | |
| *** stub has quit IRC | 13:14 | |
| *** stub has joined #zope3-dev | 13:17 | |
| *** bskahan has joined #zope3-dev | 13:28 | |
| *** gintas has quit IRC | 13:48 | |
| *** MrTopf has quit IRC | 13:57 | |
| *** jinty has joined #zope3-dev | 14:49 | |
| *** bskahan has quit IRC | 14:53 | |
| *** bskahan has joined #zope3-dev | 15:00 | |
| *** bradb-bbl is now known as bradb | 15:00 | |
| *** vlado has joined #zope3-dev | 15:27 | |
| *** anguenot has joined #zope3-dev | 15:41 | |
| *** MJ has quit IRC | 15:49 | |
| faassen | what's the way in Zope 3 to find out where ones INSTANCE_HOME is? or specifically, I want to get to the var directory | 15:50 |
| *** ignas has quit IRC | 15:52 | |
| *** bradb is now known as bradb-bbl | 15:56 | |
| *** benji_york has joined #zope3-dev | 16:00 | |
| *** bradb-bbl is now known as bradb | 16:01 | |
| projekt01 | anguenot, ayt? | 16:06 |
| *** niemeyer has joined #zope3-dev | 16:07 | |
| *** MJ has joined #zope3-dev | 16:10 | |
| philiKON | faassen, os.environ['INSTANCE_HOME'] ? | 16:11 |
| * genconc is back | 16:16 | |
| anguenot | projekt01: hi | 16:28 |
| projekt01 | hi, I have a question about the ecm wfmc state. | 16:28 |
| projekt01 | What can we use right now? | 16:28 |
| anguenot | I focused right now on xpdlcore / zope.wfmc | 16:29 |
| projekt01 | the migration from xpdlcore to z3, right? | 16:29 |
| anguenot | the ecm part is proto | 16:29 |
| anguenot | http://svn.nuxeo.org/trac/pub/browser/z3lab/xpdlcore/trunk/ | 16:30 |
| anguenot | http://svn.nuxeo.org/trac/pub/browser/z3lab/zope/wfmc/trunk/ | 16:30 |
| anguenot | this you can use together now | 16:30 |
| projekt01 | Is it working? I think with the buddy demo? | 16:31 |
| anguenot | Yeah it works. | 16:31 |
| anguenot | the tests from the zope.wfmc are passing | 16:31 |
| anguenot | now I'm waiting for the lxml proposal to be accepted to go further on the ecm layer | 16:32 |
| projekt01 | Does it provide a UI part for see the transitions? or do you call it workItems? | 16:32 |
| anguenot | The ecm layer will | 16:32 |
| anguenot | the ecm layer will be document oriented | 16:32 |
| anguenot | hopefuly :) | 16:32 |
| projekt01 | You mean with "ecm layer" a layer for a skin? | 16:32 |
| anguenot | no non | 16:33 |
| anguenot | the ecm layer as in xpdlcore / zope.wfmc / ecmworkflow | 16:33 |
| projekt01 | Ah, you mean the concept | 16:33 |
| anguenot | yeah | 16:33 |
| projekt01 | I was reading the doc on the z3lab. In the first part you describe the integration for adding content types as a process. | 16:34 |
| anguenot | it's a possiblity | 16:34 |
| anguenot | The process can create the content object right | 16:35 |
| anguenot | http://www.z3lab.org/sections/front-page/white-papers/xpdlcore-zope-wfmc | 16:35 |
| anguenot | did you check the draft ? | 16:35 |
| projekt01 | Should this not be the standard? | 16:35 |
| projekt01 | Yes | 16:35 |
| anguenot | standard ? | 16:35 |
| projekt01 | create content types with a own process | 16:36 |
| anguenot | it's a possiblity | 16:36 |
| anguenot | another one is firing the process event based | 16:36 |
| anguenot | after the creation | 16:36 |
| anguenot | but then the process doesn't control the creation | 16:36 |
| anguenot | It's a possiblity | 16:37 |
| anguenot | If yo wanna drop comment / questions about it I would be very happy | 16:37 |
| projekt01 | I would like to see that all is process oriented, also the creation of a content type. | 16:37 |
| anguenot | It's pretty easy I think | 16:38 |
| projekt01 | Yes, but I have to get into the project first. I don't have a clear vision on this right now. | 16:38 |
| anguenot | You register a callbable as a factory | 16:38 |
| anguenot | callable sorry | 16:38 |
| projekt01 | I will do some prototyping now. | 16:38 |
| projekt01 | Yes I was thinking about this like you described in the draft | 16:39 |
| anguenot | why don't you want to do it with us in Z3/ECM ? | 16:39 |
| anguenot | Just ask for a svn account ;) | 16:39 |
| projekt01 | That's not a problem to do it with the Z3/ECM. I have just a time line till 4 weeks where I need a working prototype. | 16:40 |
| anguenot | fine | 16:40 |
| anguenot | I might work with you on this | 16:41 |
| projekt01 | I think about a small prototype just for fins out what all is needed and how it's fit together. | 16:41 |
| anguenot | http://svn.nuxeo.org/trac/pub/browser/z3lab/ecmworkflow/trunk/ | 16:41 |
| anguenot | This is there for this | 16:41 |
| projekt01 | Cool, I think next week I know how all this works | 16:41 |
| projekt01 | fins out/find out | 16:42 |
| anguenot | I'll be glad to work with you on this | 16:42 |
| projekt01 | Are working on this next week? | 16:42 |
| anguenot | I can yeah | 16:42 |
| projekt01 | Cool, let's do it. Can you open a commit access for me? | 16:43 |
| anguenot | sure | 16:43 |
| anguenot | Can you mail me for this ? | 16:43 |
| projekt01 | Ok, will do | 16:43 |
| anguenot | cool ! | 16:43 |
| projekt01 | What are the next steps in the project? | 16:44 |
| anguenot | ecmworkflow ? or Zope3/ECM ? | 16:44 |
| projekt01 | Hm, both | 16:44 |
| projekt01 | I think Zope3/ECM needs the Ok for lxml? right? | 16:45 |
| anguenot | exactly | 16:45 |
| anguenot | at least for the workflow sub-project | 16:45 |
| anguenot | I'm stuck with the zope.wfmc within the z3lab repo otherweise | 16:45 |
| anguenot | which is bad :( | 16:45 |
| projekt01 | But I saw you moved the wmfc package to the z3lab repos for a initial integration? right? | 16:46 |
| anguenot | yes | 16:46 |
| projekt01 | Can we move this to a z3 branch? | 16:46 |
| anguenot | we could | 16:46 |
| anguenot | sure | 16:46 |
| anguenot | Was just waiting for the lxml acceptance | 16:46 |
| anguenot | otherweise it's useless | 16:46 |
| projekt01 | If we start a branch, this will show the needs of lxml for z3 | 16:47 |
| anguenot | Ok I can do this today or tomorrow | 16:47 |
| anguenot | If you think it will help ;) | 16:47 |
| projekt01 | Cool, if we don't get the aceptance, is it possible to do it with antoher xml parser? | 16:47 |
| anguenot | argh | 16:48 |
| anguenot | yeah we could | 16:48 |
| anguenot | but lxml rocks I mean | 16:48 |
| anguenot | ;) | 16:48 |
| anguenot | but yeah it would | 16:48 |
| anguenot | be possible | 16:48 |
| projekt01 | I think this will show that we have a clear vision and the z3lab is participating on z3 if it's useful | 16:48 |
| anguenot | I think this point was clear for a while, wasn't it ? | 16:49 |
| anguenot | for the z3lab participation | 16:49 |
| projekt01 | It think this is a important part (perhaps also helps for build a stronger commitment from the different projects) and shows that we all woring more or less on the same | 16:49 |
| projekt01 | Yes it is clear, but that was just a statement nothing happens at all, except your and Jean Marc's work | 16:51 |
| projekt01 | I think its important that the people see that something happens now. | 16:51 |
| projekt01 | Ok, I try to setup all for starting. Do you have some hints about the installation? Which package do I need? I guess the z3 trunk is Ok? right? | 16:54 |
| anguenot | z3 trunk | 16:54 |
| anguenot | xpdlcore within src | 16:54 |
| anguenot | zope.wfmc | 16:54 |
| anguenot | and you go | 16:54 |
| projekt01 | zope.wmfc from the z3 trunk? | 16:55 |
| anguenot | no | 16:55 |
| anguenot | from z3lab repo | 16:55 |
| projekt01 | Ok, I give you a feed back if it's setup. | 16:56 |
| anguenot | ok | 16:56 |
| *** sashav has quit IRC | 16:57 | |
| *** _projekt01 has joined #zope3-dev | 17:01 | |
| *** projekt01 has quit IRC | 17:01 | |
| *** hdima has quit IRC | 17:15 | |
| *** philiKON has quit IRC | 17:24 | |
| *** timte has joined #zope3-dev | 17:27 | |
| *** ignas has joined #zope3-dev | 17:27 | |
| *** srichter has joined #zope3-dev | 17:28 | |
| *** strichter has joined #zope3-dev | 17:28 | |
| *** strichter has quit IRC | 17:28 | |
| *** ChanServ sets mode: +o srichter | 17:28 | |
| SteveA | srichter: when's the next zope3 bug day? i'm going to be on vacation for 1.5 weeks starting next week, so if something needs to be arranged during that time, i need to know now. | 17:30 |
| srichter | no, not that soon | 17:31 |
| srichter | I am not planning to do anything before beginning of September | 17:31 |
| SteveA | okay, fine | 17:31 |
| *** bskahan has quit IRC | 17:53 | |
| *** MJ has quit IRC | 17:57 | |
| *** MJ has joined #zope3-dev | 17:58 | |
| *** vlado has quit IRC | 18:01 | |
| _projekt01 | anguenot, ayt? | 18:04 |
| anguenot | _projeckt01: yop | 18:04 |
| _projekt01 | We really need a release for lxml, It's horrible to build it on windows! | 18:04 |
| anguenot | It's horrible to work on windows :) | 18:05 |
| srichter | _projekt01: ST decided to go with your pagelet code, so I'll have a review of the implementation soon :-) | 18:05 |
| _projekt01 | Cooooool | 18:05 |
| _projekt01 | I can do a review next week, perhaps they have to provide ILocation | 18:06 |
| _projekt01 | anguenot, ;-) | 18:06 |
| *** mkerrin has joined #zope3-dev | 18:07 | |
| anguenot | _projekt01: BTW, for the windows release Martijn posted couple of days ago on the lxml-dev list | 18:07 |
| anguenot | _projekt01: looking for people to help regarding this | 18:08 |
| _projekt01 | Ok, will do, just saw the mailinglist | 18:09 |
| *** stub has left #zope3-dev | 18:16 | |
| _projekt01 | faassen, do you have any hints about installing lxml on a windows box? Or can you at least say if it's possible? | 18:17 |
| *** alga has quit IRC | 18:41 | |
| *** mexiKON has joined #zope3-dev | 18:49 | |
| *** wiggy has quit IRC | 18:56 | |
| *** BjornT has joined #zope3-dev | 19:05 | |
| *** BjornT_ has quit IRC | 19:05 | |
| *** alga has joined #zope3-dev | 19:13 | |
| *** MJ has quit IRC | 19:19 | |
| *** Ega has joined #zope3-dev | 19:22 | |
| *** sashav has joined #zope3-dev | 19:31 | |
| *** JZ has joined #zope3-dev | 19:46 | |
| *** sashav has quit IRC | 19:53 | |
| *** Ega has left #zope3-dev | 19:59 | |
| *** bradb is now known as bradb-lunch | 20:04 | |
| *** zagy has quit IRC | 20:06 | |
| *** horizon5 has joined #zope3-dev | 20:14 | |
| *** mkerrin has left #zope3-dev | 20:19 | |
| *** fdrake has joined #zope3-dev | 20:20 | |
| fdrake | i'm going to make some packaging changes to ZODB | 20:44 |
| fdrake | Tim's going to hold off knitting in the new version until I've got the corresponding Zope 3 changes done | 20:44 |
| srichter | yipee! | 20:44 |
| fdrake | it's all packaging stuff | 20:44 |
| fdrake | ZODB will be using zpkg for ALL builds, including building the checkout itself | 20:45 |
| srichter | cool | 20:46 |
| fdrake | done, in case anyone wants to play with the ZODB trunk directly | 20:46 |
| srichter | does this mean you have to have zpkgtools to compile ZODB and thus Zope 3? | 20:46 |
| fdrake | the setup.py is a lot simpler | 20:46 |
| srichter | (in this case I would like an external in in Zope 3) | 20:46 |
| fdrake | it only needs zpkgsetup, which is included in the checkout via an external | 20:46 |
| fdrake | an external for what in Zope 3? | 20:47 |
| srichter | cool, zpkgsetup is an external, so fine | 20:47 |
| fdrake | in ZODB, yes | 20:47 |
| fdrake | it's not in Zope 3 yet | 20:47 |
| srichter | ok | 20:47 |
| fdrake | i expect it'll be done the same way | 20:48 |
| fdrake | the new ZODB setup.py names a lot of specific things zpkg should look like; we want to avoid that for Zope 3 itself | 20:48 |
| fdrake | so it's not so hard to work with the checkout | 20:49 |
| fdrake | (you don't want to have to munge the setup.py to add packages!) | 20:49 |
| srichter | right | 20:50 |
| fdrake | actually, you wouldn't need to, unless you had C extensions or the like | 20:52 |
| *** faassen has quit IRC | 20:57 | |
| *** bradb-lunch is now known as bradb | 20:59 | |
| *** anguenot has quit IRC | 21:00 | |
| *** mtiger has joined #zope3-dev | 21:10 | |
| *** sashav has joined #zope3-dev | 21:15 | |
| *** mgedmin has quit IRC | 21:18 | |
| *** sashav has quit IRC | 21:20 | |
| *** mtiger has left #zope3-dev | 21:20 | |
| *** tvon has quit IRC | 21:31 | |
| *** MJ has joined #zope3-dev | 21:32 | |
| *** sashav has joined #zope3-dev | 21:40 | |
| MJ | Assumption: utilities registered by name can discover the names by which they are registered through the IRegistered interface.. | 21:45 |
| *** tvon has joined #zope3-dev | 21:47 | |
| MJ | So if I can find IFoo utilities with queryUtility(IFoo, 'bar', context) | 21:47 |
| MJ | Then the returned IFoo utility should find 'bar' in IRegistered(self).registrations()? | 21:48 |
| MJ | Oops. That method returns objects | 21:49 |
| MJ | So it can grep it's own __name__ then? | 21:50 |
| MJ | What I am trying to do: | 21:50 |
| MJ | I have the keys that are distinguishable by their id and the domain in which they have meaning | 21:51 |
| MJ | So you can get a key with a domain name and a key id | 21:51 |
| MJ | A domain is a simple mapping | 21:51 |
| MJ | So domain['id'] is a key | 21:52 |
| MJ | At the moment I have a top-level utility (keydomains) that is a mapping of domains. | 21:52 |
| MJ | So keydomains['domain']['id'] gets you a key. | 21:53 |
| MJ | The one problem I have is that keys must have a domain attribute so's you can always recreate the key with only a domain and id value. | 21:54 |
| MJ | So keys returned from keydomains['domain']['id'] need to have their domains attr set to 'domain'. | 21:55 |
| MJ | That's easy in the keydomains utility scenario. | 21:55 |
| MJ | But I am thinking that the keydomains object is in fact redundant if I make the domains themselves local utilities registered under their domain name. | 21:56 |
| MJ | So when you get your domain through queryUtility using the domain interface and the domain name, the returned object should know how you found it in the first place. | 21:58 |
| *** FarcePest has quit IRC | 22:01 | |
| MJ | Hmm, as local utilities always have a __name__, that's the name they are registered by | 22:10 |
| *** sashav has quit IRC | 22:11 | |
| fdrake | MJ: no, 'fraid not: that's the name of the object in it's container | 22:11 |
| fdrake | last I looked, the registration machinery was so bloody baroque I decided it wasn't worth understanding | 22:12 |
| MJ | just found that too | 22:18 |
| MJ | The IRegistered interface gives me a sequence of registrations | 22:18 |
| fdrake | if that's working these days, then that's likely as good as it gets | 22:19 |
| MJ | And those tell me by what name they are registered | 22:19 |
| fdrake | until we re-do the whole bloody things | 22:19 |
| fdrake | right | 22:19 |
| MJ | I think I'll stick with my top-level keydomains mapping maybe | 22:19 |
| MJ | Not doing that would make domains more flexible | 22:20 |
| MJ | And reusable between different sites as they can be looked up higher up | 22:20 |
| MJ | Durn this... | 22:21 |
| MJ | Sigh | 22:21 |
| MJ | 2 evils to choose from then.. | 22:22 |
| MJ | Is there any way I can force the use of a name when a domain gets registered in the ZMI? | 22:23 |
| fdrake | i don't think so | 22:24 |
| MJ | Then I'll have to stick with my current setup as I fear that things will get too complicated for site managers otherwise. | 22:26 |
| *** ignas has quit IRC | 22:27 | |
| * MJ muses on this some more | 22:27 | |
| MJ | Or I'll have to provide the manager with UI to support the most common cases... | 22:27 |
| MJ | And leave the options open for complex setups later | 22:28 |
| fdrake | that probably makes more sense than anything, but I've only skimmed the full explanation of what you want to do | 22:28 |
| *** roym has quit IRC | 22:40 | |
| *** RaFromBRC has joined #zope3-dev | 22:40 | |
| MJ | I just experimented somewhat | 22:50 |
| MJ | And created a simple persistent key domain | 22:51 |
| MJ | And creating one with a name neatly registered it with that name | 22:51 |
| MJ | As long as I use the registration name I should be fine. | 22:51 |
| MJ | Thanks for Duckheading Fred, I think I figured it out for now | 22:53 |
| *** zagy has joined #zope3-dev | 22:55 | |
| *** _projekt01 is now known as projekt01 | 22:57 | |
| *** sashav has joined #zope3-dev | 22:59 | |
| fdrake | MJ, cool, glad you figured out something that made sense for you | 23:01 |
| *** sashav has quit IRC | 23:08 | |
| *** alienoid has joined #zope3-dev | 23:08 | |
| srichter | fdrake: you contacted me? | 23:18 |
| *** alga has quit IRC | 23:19 | |
| fdrake | hey | 23:21 |
| fdrake | i have changes to a Zope-3.1 checkout that allow it to build in-place using zpkg | 23:21 |
| fdrake | the setup includes a list of the packages that include C extensions; it doesn't scan everything | 23:22 |
| srichter | ok, cool | 23:22 |
| fdrake | that means it can be used for build_ext -i (an in-place build), not not a conventional build | 23:22 |
| fdrake | (in the build/ tree) | 23:22 |
| srichter | can you change the Makefile? | 23:23 |
| fdrake | but that's sufficient for most development | 23:23 |
| srichter | I only use the Makefile (for this reason) | 23:23 |
| fdrake | if it's ok to simply remove the out-of-place builds, sure | 23:23 |
| fdrake | otherwise it needs no changes | 23:23 |
| srichter | ok, cool | 23:23 |
| fdrake | the question is: Is it ok to toss out-of-place builds? (including installation from a checkout) | 23:24 |
| fdrake | so that out-of-place builds and installation reqiure is packaged distro | 23:24 |
| srichter | fdrake: what does this mean in plain english? :-) | 23:26 |
| *** roym has joined #zope3-dev | 23:26 | |
| srichter | if I can build a checkout without changes and build a release without modifications, I am fine | 23:26 |
| fdrake | that would all work | 23:26 |
| srichter | then I see no problem | 23:27 |
| roym | folks, is there a way to set the skin a user sees, based on their role (and without doing a ++skin++XX in the URL)? | 23:27 |
| fdrake | what would not would be: "python setup.py build" or "python setup.py install" | 23:27 |
| srichter | roym: yes, see the skin preference demo in zope.app.demo | 23:27 |
| srichter | the trunk and 3.1 branch uses the demo | 23:27 |
| roym | srichter: thanks. | 23:28 |
| srichter | fdrake: fine with me | 23:28 |
| fdrake | think it'll piss people off? | 23:28 |
| fdrake | we can add a more magical scan later, if anyone cares | 23:28 |
| fdrake | (I don't, Jim may well) | 23:28 |
| srichter | well, for now we check it in | 23:29 |
| fdrake | ok | 23:30 |
| srichter | if anyone gets pissed we deal with it then | 23:30 |
| fdrake | it shouldn't be too hard to make a setup.py that at least scans for packages containing extension code or other special things | 23:30 |
| fdrake | (since they'll contain a SETUP.cfg file) | 23:30 |
| srichter | right | 23:31 |
| fdrake | ok, i'll get Tim to push the ZODB release button, and then commit the rest of the needed changes | 23:31 |
| srichter | thanks | 23:32 |
| *** RaFromBRC is now known as RaFromBRC|away | 23:38 | |
| yota | mexiKON: ping | 23:43 |
| yota | who manages translations ? | 23:45 |
| yota | only mexiKON ? | 23:45 |
| fdrake | srichter, the ZODB button has been pressed, I'm testing with the tagged ZODB version on the Zope-3.1 branch | 23:49 |
| fdrake | when that's done and passed, and the built distro from that has also been tested, i'll commit | 23:49 |
| *** FarcePest has joined #zope3-dev | 23:50 | |
| *** _projekt01 has joined #zope3-dev | 23:56 | |
| *** projekt01 has quit IRC | 23:56 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!