fluid-work IRC Logs-2009-12-21

[04:34:53 EST(-0500)] * sveto (n=sveto@95.111.16.213) has joined #fluid-work
[07:12:19 EST(-0500)] * boyan1 (n=boyan@95.111.16.213) has left #fluid-work
[07:12:24 EST(-0500)] * boyan1 (n=boyan@95.111.16.213) has joined #fluid-work
[08:36:36 EST(-0500)] * sveto_ (n=sveto@62.44.108.2) has joined #fluid-work
[08:49:56 EST(-0500)] * jessm (n=Jess@c-71-232-1-65.hsd1.ma.comcast.net) has joined #fluid-work
[08:53:06 EST(-0500)] * boyan2 (n=boyan@62.44.108.2) has joined #fluid-work
[09:27:35 EST(-0500)] * boyan1 (n=boyan@62.44.108.2) has joined #fluid-work
[09:52:32 EST(-0500)] * yura (n=yura@142.150.82.121) has joined #fluid-work
[10:25:48 EST(-0500)] * sveto (n=sveto@62.44.108.2) has left #fluid-work
[10:55:43 EST(-0500)] * colinclark (n=colin@bas2-toronto09-1176393776.dsl.bell.ca) has joined #fluid-work
[11:00:56 EST(-0500)] <colinclark> boyan1: It looks like you're making nice progress getting Capture working with the server.
[11:02:01 EST(-0500)] <boyan1> colinclark: yes, I am
[11:02:06 EST(-0500)] <colinclark> Nice work!
[11:02:35 EST(-0500)] <boyan1> I am currently adding an option telling whether you want to work with the server or not so that you can easily switch
[11:09:33 EST(-0500)] <colinclark> That makes a lot of sense.
[11:09:57 EST(-0500)] <colinclark> You'll see in other code we've written that you can often auto-detect the standalone vs. server-backed scenarios by checking window.location.
[11:10:17 EST(-0500)] <colinclark> If it's a file:// URL, you can be certain that you'll need to load local data instead of trying to communicate with a server.
[11:11:36 EST(-0500)] <colinclark> boyan1: You can see how this is done in Engage at the moment here:
[11:11:37 EST(-0500)] <colinclark> http://source.fluidproject.org/svn/fluid/engage/fluid-engage-core/trunk/framework/js/loadData.js
[11:12:14 EST(-0500)] <colinclark> I don't think this code is quite right at this point, but it does the trick.
[11:17:21 EST(-0500)] <boyan1> colinclark: that's right, but I also want to be able to communicate with the server even though I've opened the page from the local file system (so that I can test) - and that's currently what I'm doing
[11:17:32 EST(-0500)] <colinclark> ah, makes sense
[11:25:31 EST(-0500)] <boyan1> although this is somewhat problematic
[11:25:31 EST(-0500)] <boyan1> I want to make a call to the server that should delete a given image
[11:25:31 EST(-0500)] <boyan1> and I can't because i've loaded the file from file://...some-path and the server is running at http://localhost:8080
[11:25:31 EST(-0500)] <boyan1> and I expectedly get a 'Access to a restricted URI denied' error
[11:25:31 EST(-0500)] <boyan1> any ideas how to handle that?
[11:26:38 EST(-0500)] <boyan1> colinclark, what do you think?
[11:27:18 EST(-0500)] <colinclark> boyan1: Easiest thing to do is to deploy the html files from the same server as the services you're calling to get/delete/etc images
[11:27:27 EST(-0500)] <colinclark> So, I don't know a ton about how CherryPy works...
[11:27:44 EST(-0500)] <colinclark> but presumably it has some way to mount a directory of files onto its built-in web server
[11:29:11 EST(-0500)] <boyan1> colinclark: I think that should be pretty easy, will be the first thing to try tomorrow morning
[11:29:17 EST(-0500)] <colinclark> great!
[11:29:30 EST(-0500)] <colinclark> That's how we do it with Kettle-based apps
[11:30:10 EST(-0500)] <colinclark> Indeed, Kettle offers a pretty simple method, aptly named mountDirectory() that takes a path and makes it available at a certain root URL.
[11:31:08 EST(-0500)] <colinclark> It's safe to assume there's a Cherry equivalent tothat
[11:32:49 EST(-0500)] <boyan1> well, I'll dig into that tomorrow
[11:35:09 EST(-0500)] * boyan1 (n=boyan@62.44.108.2) has left #fluid-work
[12:24:14 EST(-0500)] <yura> hey colinclark, this is great, i was thinking myself that it would not be that straightforward to extract the exhibition data from the artifacts
[12:25:44 EST(-0500)] <colinclark> Yeah. It seems to me that it's well-enough described to be able to do so fairly easily, no?
[12:26:09 EST(-0500)] <colinclark> In other words, the stuff inside an <artifacts> tag represents the equivalent of what we've imported from Hugues in the past
[12:26:48 EST(-0500)] <colinclark> But I guess we'll probably have to create some rules to be able to define things that should become separate documents upon import.
[12:26:50 EST(-0500)] <yura> yes
[12:27:47 EST(-0500)] <yura> i m also thinking if there's a way to "crawl" that data somehow
[12:32:42 EST(-0500)] <yura> colinclark: also happy belated birthday
[12:32:53 EST(-0500)] <colinclark> thanks
[12:33:04 EST(-0500)] <colinclark> yura: crawl how?
[12:33:17 EST(-0500)] <colinclark> I guess we still have to crawl through the list of current exhibitions
[12:33:42 EST(-0500)] <colinclark> But at least all the artifacts are all nested in there once we've got an exhibition
[12:33:46 EST(-0500)] <yura> hmm, i dont think the data is there
[12:34:37 EST(-0500)] <yura> colinclark: yes, in the exhibition specific url, you are right
[13:17:01 EST(-0500)] <yura> hi colinclark, i was wondering if you had any thought to how/where the exhibition data should be stored?
[13:17:22 EST(-0500)] <colinclark> This is just off the top of my head, yura...
[13:17:37 EST(-0500)] <colinclark> but I imagined that an exhibit would be another example of a kind of collection...
[13:17:54 EST(-0500)] <colinclark> in this case, one with a fair bit of associated information, such as dates, descriptions, and so on.
[13:18:07 EST(-0500)] <colinclark> So they're certainly a document in themselves
[13:19:59 EST(-0500)] <yura> what about the lists of exhibitions (first couple urls that hugues has) ? is that supposed to be stored too, or we just have a document for exhibit itself and go from there?
[13:25:29 EST(-0500)] <colinclark> one sec, sorry
[13:26:32 EST(-0500)] <yura> sure np
[13:26:34 EST(-0500)] <colinclark> For the time being, we probably don't need the list of exhibits
[13:26:50 EST(-0500)] <colinclark> The information stored in it is already contained in the individual exhibit documents
[13:27:04 EST(-0500)] <colinclark> And presumably this represents just another view on the list of individual exhibits
[13:28:05 EST(-0500)] <yura> ok
[13:28:06 EST(-0500)] <yura> thanks
[13:45:09 EST(-0500)] <colinclark> yura: Excited to see what you build. Ping me if you need some code review
[13:45:15 EST(-0500)] <colinclark> or want to talk more about design
[13:45:46 EST(-0500)] <yura> colinclark: sure, will do
[17:30:56 EST(-0500)] * mackrauss (n=Armin@d5368bed.access.ecotel.net) has joined #fluid-work