[3:16]<dmachi> Hey deanlandolt you around? [3:16]<deanlandolt> hey [3:17]<dmachi> you up to date on pintura et al? [3:17]<deanlandolt> yep [3:17]<dmachi> I am doing a clean checkout and can't seem to get it to run [3:17]<dmachi> (the example [3:17]<deanlandolt> node or rhino? [3:17]<dmachi> complaining that app isn't found [3:17]<dmachi> rhino [3:17]<deanlandolt> svn cho? [3:18]<deanlandolt> s/cho/co [3:18]<dmachi> git [3:18]<deanlandolt> hmm, how'd you structure it? [3:18]<dmachi> basically those manual directions http://docs.persvr.org/pintura-documentation/installation [3:19]<dmachi> though there are a few additional modules missing there so i got them as well, but basically just narwhal/ and then clone all that stuff into narwhal/packages/ and run the two sea commands. [3:19]<deanlandolt> it's very likely that you just need to do a require("util/narwhal-compat") because of the new package mappings stuff, but let me see if i can't reproduce [3:19]<deanlandolt> aye, heh...yeah, you don't need to do any of that anymore [3:20]<deanlandolt> if you download the nightly persevereJSGI you'll see how it's structured...but you just do a bin\persvr example and you're in business [3:21]<dmachi> i had been using one but i'm adding a store and stuff and was tyring to figure out how to check it out. [3:21]<deanlandolt> i should ask kris for write access to the docs, they're a few weeks out of date [3:21]<deanlandolt> yeah, still easy to do... [3:21]<dmachi> kris checked in some changes friday to change the object getting and i need to pull them in. :) [3:22]<deanlandolt_home> ugh, stupid work computer froze [3:22]<deanlandolt_home> okay...so here's what you'd do [3:22]<deanlandolt_home> just rm -rf the package(s) you want to pull in... [3:23]<deanlandolt_home> and then git clone them, add your fork and change away [3:24]<dmachi> ok, thats pretty close to what i had done a couple days ago, but i hadn't done my own clone and screwed up somewhere along the line so went on this goose chase to get a clean checkout. I'll follow those directions, thanks :) [3:24]<deanlandolt_home> i'll try to reproduce, but i'd say just try the vanilla persevereJSGI zip first and see if you're getting the example to work...if it works, you can rm -rf packages/perstore [3:24]<dmachi> well i wasn't runng persvr for one, i wonder if it would change if ido that [3:25]<deanlandolt_home> try it...no seas necessary [3:25]<deanlandolt_home> though i can't for the life of me figure out how to run the tests in that kind of setup [3:26]<dmachi> how do you set yours up? [3:26]<deanlandolt_home> just like that...the same structure as the persevereJSGI zip...packages in the top level beside your project, with narwhal as just another package [3:27]<dmachi> ah, ok, i can do that, i had actually moved the persevere wiki out there already [3:27]<deanlandolt_home> it's a nice set up but i /really/ have to figure out how to get the tests to behave [3:28]<dmachi> i dont' seem to even have a persvr command so i must be missing something? [3:28]<deanlandolt_home> in the top level bin folder? hmm, let me check out the latest nightly [3:28]<dmachi> i'm sure its there, where is the source repostiory for those nightlies? [3:29]<dmachi> (I was talking about not having it anywhere in what i had already checked out) [3:29]<deanlandolt_home> oh wow... [3:29]<deanlandolt_home> they haven't been built in over a month [3:30]<deanlandolt_home> well, in any event, let me point you to the up to date docs... [3:30]<deanlandolt_home> you can actually do an svn co that uses git/svn for the EXTERNALS that gives you the structure i'm using [3:30]<dmachi> oh, that'd be perfect [3:31]<deanlandolt_home> svn checkout http://persevere-framework.googlecode.com/svn/trunk/ persevere [3:32]<deanlandolt_home> and you can do the same thing w/ the packages folders -- just rm -rf and git clone away [3:32]<dmachi> right [3:32]<dmachi> thanks, i appreciate it [3:32]<deanlandolt_home> certainly [3:33]<dmachi> building a filesystem store [3:33]<deanlandolt_home> oh really?! [3:33]<deanlandolt_home> awesome! [3:33]<dmachi> just to read/store docs (rst for this ver) [3:33]<deanlandolt_home> if there's anything i can help you with just ping me...i've built several stores [3:34]<deanlandolt_home> should be a lot easier now that the recent content-disposition stuff is in [3:34]<dmachi> had it working for /Doc/FooBar, but /Doc/FooBar/Baz nogo, and kris said he was making some changes so it'd be doing something like getStore("doc").get("FooBar").get("Baz"); [3:34]<deanlandolt_home> (so that you can prevent it from serializing all your files on the way out) [3:35]<deanlandolt_home> heh, yeah, i just noticed a single line changed in pintura/lib/jsgi/rest-store that makes that possible [3:35]<deanlandolt_home> i was wondering what he was angling at [3:36]<deanlandolt_home> alternatively it's always been possible to do nested packages with openObjectStore (or something like that) [3:36]<dmachi> yeah, i got errors like that today and then i realized my updated to kris' code hadn't taken affect, and now i'm talking to you :) [3:36]<deanlandolt_home> so you can register submodels with a model and it'll allow you to recurse using slashes [3:37]<dmachi> Might ahve to come back to that depending on my luck today, the way that i created my store at the moment i think is basically that, but i didn't have permission to call that openObjectStore [3:38]<deanlandolt_home> really? hmm...it's not really something you call...it's something your store (or model) provides that will get called in rest-store to find the particular store in question... [3:38]<deanlandolt_home> let me point you to some code and it should make it clearer... [3:38]<dmachi> well i had something like if isDirectory(id) return new FileStore() [3:39]<dmachi> so that the following get on it would be in the correct place [3:39]<deanlandolt_home> well, if you want to debug this is the place you should be poking at: http://github.com/kriszyp/pintura/blob/master/lib/jsgi/rest-store.js#L18 [3:40]<deanlandolt_home> that's the line he just changed -- it used to be an openObjectStore there, now it calls into the store's get method directly [3:40]<dmachi> yep, filled with prints already :) [3:40]<deanlandolt_home> heh [3:40]<dmachi> so do i put narwhal in th epackages directory of this checkout or as a peer? [3:40]<deanlandolt_home> packages [3:41]<deanlandolt_home> it should have checked out in packages with all the other packages IIRC [3:41]<deanlandolt_home> makes it a /lot/ easier to hack on the packages, that's for sure [3:41]<dmachi> hmm, yes, but when i run persvr it doesn't have anything in the path [3:42]<deanlandolt_home> try going to the top level and running bin\persvr example [3:42]<dmachi> i put p2/bin in my path [3:42]<dmachi> ok [3:42]<dmachi> FTW! [3:42]<deanlandolt_home> sweet...now hack away [3:42]<dmachi> gracias [3:43]<deanlandolt_home> i also have a modified persvr.cmd file that lets you pass additional args down into jackup if you want [3:43]<dmachi> how do i force it to be in debug/verbose mode ? [3:44]<dmachi> edit narwhal.conf? [3:44]<deanlandolt_home> hrm, perhaps, though you could probably use an env var [3:44]<deanlandolt_home> i think it's NARWHAL_DEBUG [3:44]<dmachi> yeah thats what the docs said, bt havne't been able to make that work [3:45]<dmachi> i ended up enabling in narwhal.js [3:45]<deanlandolt_home> oh really? i should look closer at that [3:45]<deanlandolt_home> i've just been working without decent debug information...kinda painful for productivity [3:46]<dmachi> yeah, well i had a syntax error in a file and it was just silently going on by [3:46]<dmachi> i couldnt' figure out what was going on until i made it show the require debug statements. [3:46]<deanlandolt_home> oh? odd, that doesn't happen to me...but in persvr i lose the stack that narwhal otherwise gives me and i'd really like to know why...i can't even get filename/line no [3:47]<deanlandolt_home> syntax errors are the only errors i /can/ see :) [3:47]<dmachi> do you have readline support at the persvr console in p2? [3:48]<deanlandolt_home> i don't think anything would disable it...the jline jar is there [3:48]<deanlandolt_home> it's picking up the other jars [3:48]<dmachi> right, its never worked for me in p2 though (on my mac), though works fine in p1 [3:48]<deanlandolt_home> and the readline package is there [3:49]<deanlandolt_home> perhaps that's it [3:49]<dmachi> exception from uncaught JavaScript throw: TypeError: [JavaPackage jline.ConsoleReader] is not a function, it is object. [3:50]<dmachi> anyway, going to hack for a bit before bed, i'll try to give you a few minutes peace. [3:50]<dmachi> :) [3:50]<deanlandolt_home> heh...ping me whenever -- though we should probably take it to the #persevere channel [3:50]<dmachi> ah, yah, my bad [3:51]<dmachi> sry #commonjs