tag:old.nabble.com,2006:forum-28539Nabble - Fluid2009-12-21T11:16:01Z<a href="http://fluidproject.org/" target="_top" rel="nofollow">Fluid</a> is a worldwide collaborative project to help improve the usability and accessibility of community open source projects with a focus on academic software for universities. We are developing and will freely distribute a library of sharable customizable user interfaces designed to improve the user experience of web applications.
<br><br><a href="http://fluidproject.org/index.php/aboutfluid" target="_top" rel="nofollow">Read more about Fluid...</a>tag:old.nabble.com,2006:post-26878681Re: [Tech] IE issue2009-12-21T11:16:01Z2009-12-21T11:16:01ZColin Clark-2Hey Aron,
<br><br>You bring up a good point. I'll defer to Justin Obara, Fluid's QA
<br>Lead, to share his thoughts on automated browser testing tools. My
<br>short-form summary is probably this:
<br><br>Automated acceptance testing is a holy grail we've been questing after
<br>for about three years now. It'll be awesome when we can do it. Biggest
<br>problems: brittleness and "reach." Many scripted acceptance tests tend
<br>to come crashing down when design changes occur because they're tied
<br>to concrete features in the markup such IDs and the like. The reach
<br>issue is simply that it can be hard to automate some tasks that extend
<br>beyond the insides of the browser frame.
<br><br>Justin can fill you in on the specifics, and where he plans to go from
<br>here on the quest. :)
<br><br>Hope this helps,
<br><br>Colin
<br><br>On 21-Dec-09, at 2:05 PM, Aron Roberts wrote:
<br><div class='shrinkable-quote'><br>> On Mon, Dec 21, 2009 at 10:08 AM, Colin Clark
<br>> <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26878681&i=0" target="_top" rel="nofollow">colinbdclark@...</a>> wrote:
<br>>> To avoid future confusion, I've drafted a super-simple browser
<br>>> support chart
<br>>> for CollectionSpace, intended to keep testing as easy as possible.
<br>>> When we
<br>>> have a QA person involved in the community, we can revise this list
<br>>> and
<br>>> extend it as needed.
<br>>>
<br>>> <a href="http://wiki.collectionspace.org/display/collectionspace/Browser+Support" target="_top" rel="nofollow">http://wiki.collectionspace.org/display/collectionspace/Browser+Support</a><br>>
<br>> Thanks, Colin.
<br>>
<br>> On a related topic, at some point there may be a need to look at
<br>> tools for automated testing of the CollectionSpace system through the
<br>> browser. Open source examples of these tools include the likes of
<br>> Canoo WebTest, Selenium, Sahi et al.; there are apparently commercial
<br>> counterparts as well. A couple of starting point links:
<br>>
<br>> <a href="http://delicious.com/aronr/web+testing" target="_top" rel="nofollow">http://delicious.com/aronr/web+testing</a><br>>
<br>> What have been the Fluid team's experiences with this? At a quick
<br>> glance at the Fluid wiki, I see user testing-related pages but not
<br>> automated testing-related pages - might there be something relevant
<br>> elsewhere on the wiki, or in other documents or maillist archives,
<br>> etc.?
<br>>
<br>> Aron
</div><br>---
<br>Colin Clark
<br>Technical Lead, Fluid Project
<br><a href="http://fluidproject.org" target="_top" rel="nofollow">http://fluidproject.org</a><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26878681&i=1" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26878627Re: Engage / ArtifactView / Comments / Storing documents in couchdb and other things2009-12-21T11:10:05Z2009-12-21T11:10:05ZColin Clark-2Hey all,
<br><br>[Joan, I know you're currently away from work due to an injury, so
<br>don't worry about the details of this. My main goal in responding to
<br>your questions (sorry for the delay!) is so that the whole community
<br>has clarity on our next steps in terms of data access.]
<br><br>I like the concept of the database.js implementation. Since it was
<br>written, we uncovered two JavaScript APIs that ship directly with
<br>CouchDB:
<br><br><a href="http://titan.atrc.utoronto.ca:5984/_utils/script/couch.js" target="_top" rel="nofollow">http://titan.atrc.utoronto.ca:5984/_utils/script/couch.js</a><br><a href="http://titan.atrc.utoronto.ca:5984/_utils/script/jquery.couch.js" target="_top" rel="nofollow">http://titan.atrc.utoronto.ca:5984/_utils/script/jquery.couch.js</a><br><br>One is a plain JavaScript API, and the other is designed as a jQuery
<br>plugin. They offer overlapping functionality, but in general a
<br>preference is emerging for the jQuery plugin--it's properly
<br>namespaced, and a bit better structured. Here's a thread on the fluid-
<br>work list from last week where Antranig and I discuss the issues:
<br><br><a href="http://old.nabble.com/Fluid-Engage-nightly-build-broken-td26785515.html#a26832718" target="_top" rel="nofollow">http://old.nabble.com/Fluid-Engage-nightly-build-broken-td26785515.html#a26832718</a><br><br>I think we're always better to contribute back to existing projects
<br>rather than rolling our own where it's appropriate, so I'd like to
<br>suggest that instead of working on database.js, we contribute some
<br>patches back to Couch for their jQuery plugin. One area where we'll
<br>need to contribute back, in addition to the ones mentioned by
<br>Antranig, is support for Couch Lucene views, which we use frequently.
<br><br>Antranig also has some code in his FLUID-213 patch that illustrates
<br>some slightly higher-level ways of making Couch requests within Kettle:
<br><br><a href="http://issues.fluidproject.org/secure/attachment/10833/ENGAGE-213-demonstration.patch" target="_top" rel="nofollow">http://issues.fluidproject.org/secure/attachment/10833/ENGAGE-213-demonstration.patch</a><br><br>This covers the low-level issues of data access. I think our second
<br>goal is to provide nice abstractions so that every Engage service
<br>developer doesn't have to write the same data access boiler plate
<br>goal. In a recent development meeting, we talked a little bit about
<br>the notion of "data source specs," which would provide all of the
<br>information needed to retrieve and save data to/from Couch in a
<br>declarative way.
<br><br>This data source spec would include the URL in Couch that identifies
<br>the document or set of documents being used by a particular data feed
<br>and component. It would also include the requisite model mapping
<br>information required to correctly reshape the model into a form the
<br>component can suitably use. You can see a rough sketch of our current
<br>model mapping code in this file:
<br><br><a href="http://source.fluidproject.org/svn/fluid/engage/fluid-engage-core/trunk/framework/js/Engage.js" target="_top" rel="nofollow">http://source.fluidproject.org/svn/fluid/engage/fluid-engage-core/trunk/framework/js/Engage.js</a><br><br>Take a look at the fluid.engage.collections data structure for an
<br>example of the model maps we're currently using. This code needs quite
<br>a bit of work to be correctly parameterized and generalized, but the
<br>idea is to be able to have a document in Couch that represents the
<br>necessary transformations required on the model for a particular view
<br>context. The framework will include a number of "canned reshapers" for
<br>common mapping tasks, and museums could extend this with their own
<br>specific code if needed.
<br><br>This second layer of data access will take a bit longer for us to
<br>implement, so let's focus first on the task--contributing back to
<br>Couch's jquery.couch.js file based on our own needs.
<br><br>I hope this helps clarify the issue of data access in Engage a bit.
<br>This is all still very much in the concept stage, so no doubt it also
<br>opens up some new questions. Everyone, please don't hesitate to
<br>respond to this thread with thoughts, comments, and questions.
<br><br>Colin
<br><br><br>On 1-Dec-09, at 9:31 AM, Joan Garcia Vila wrote:
<br><div class='shrinkable-quote'><br>> Hi all.
<br>>
<br>> Recently I've posted an alpha implementation of the Database
<br>> component (which has to become, I suppose, a subcomponent of
<br>> ArtifactComments [server side]).
<br>> Needs a conceptual review.
<br>>
<br>> - Talking about storing data on couchdb, this has been my first
<br>> approach:
<br>>
<br>> // Artifact Comment example.
<br>> var artifactComment = {};
<br>> artifactComment.engage_type = "artifact-comment";
<br>> artifactComment.artifact_id =
<br>> "00311f0d3f5456c91934e472b880e9c5";
<br>> artifactComment.insertDate = "2009-11-30";
<br>> artifactComment.name = "Juan";
<br>> artifactComment.location = "Barcelona, Catalonia, Spain";
<br>> artifactComment.abuse = false;
<br>> artifactComment.info = "Barcelona is a beautiful
<br>> mediterranian city.";
<br>>
<br>> There are few essential key points to check (understand / validate /
<br>> talk about):
<br>>
<br>> 1.- This document has a field that identifies its type
<br>> ("engage_type").
<br>> If we store different object types inside the same database this
<br>> will help and give higher scores in lucene fulltext search if we add
<br>> the document type in the query
<br>> (Please see/run the example).
<br>>
<br>> 2 .- This document has a reference to another document. See field
<br>> "artifact_id". Important to have good views with high selectivity.
<br>> This will help us to create "in-server" high speed paged queries.
<br>> Views for each document type if we need this functionality.
<br>> (Please see/run the example).
<br>>
<br>> 3.- The object also gets its _id and _rev attributes after it has
<br>> been stored.
<br>> This is coherent with couchdb (object oriented database) and the key
<br>> is an uuid.
<br>> (Please see/run the example).
<br>>
<br>> 4.- Data attributes is stored as a fixed text with pattern "YYYY-MM-
<br>> DD".
<br>> This will help us to have date sorted field views.
<br>>
<br>> 5.- One important thing is that having the documents (2 diferent
<br>> types) inside the same database allows us to create fast views (see
<br>> Database.js).
<br>> We can also create "pseudo joins" [complex views using map/reduce
<br>> _design functions]
<br>>
<br>> - Other things that come to my mind, while developing the component,
<br>> are:
<br>> 1. - How do we know who we are?, I haven't see a login page in the
<br>> wireframes.
<br>> But there is behaviour that seems to depend on knowing who we are.
<br>> Like report abuse or delete, for an example.
<br>> makes sense?
<br>>
<br>> 2.- How do we know that the user is the moderator?
<br>> makes sense?
<br>>
<br>> Cheers,
<br>> joan
<br>>
<br>> ps: you can find (Database. [js/html] on scratchpad/bug-parade.
<br>> _______________________________________________________
<br>> fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26878627&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>> To unsubscribe, change settings or access archives,
<br>> see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a></div><br>---
<br>Colin Clark
<br>Technical Lead, Fluid Project
<br><a href="http://fluidproject.org" target="_top" rel="nofollow">http://fluidproject.org</a><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26878627&i=1" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26877534Re: review: bug parade component patch2009-12-21T09:49:37Z2009-12-21T09:49:37ZColin Clark-2Hi Andrea,
<br><br>On 18-Dec-09, at 8:24 AM, Andrea Leutgoeb . wrote:
<br><br>> Patch to be reviewed pls:
<br>>
<br>> <a href="http://issues.fluidproject.org/browse/FLUID-3305?focusedCommentId=16874&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_16874" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3305?focusedCommentId=16874&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_16874</a><br>>
<br>> *Changes*
<br>> - Jslinted parade.html & parade.js
<br>> - New jslinted standalone version parade-standalone.html
<br><br>Thanks for the patch!
<br><br>I'm wondering if you can explain a bit more about your goals with the
<br>parade-standalone.html page? At first glance, I'm not sure if it's the
<br>best approach to duplicate all the markup and code from parade.html.
<br>Is it the case that you're trying to switch between loading data from
<br>the server and from a local test file?
<br><br>If that's the case, you can probably use a common technique we use
<br>throughout Engage: check the URL at window.location to see if it's a
<br>file:// URL instead of a server-based URL. Here's an example of some
<br>sketch code in Engage for this task:
<br><br><a href="http://source.fluidproject.org/svn/fluid/engage/fluid-engage-core/trunk/framework/js/loadData.js" target="_top" rel="nofollow">http://source.fluidproject.org/svn/fluid/engage/fluid-engage-core/trunk/framework/js/loadData.js</a><br><br>As for the rest of the patch, I'm wondering if you could address a few
<br>structural issues before running JSLint. I think this will make it
<br>easier to read, review, and lint:
<br><br>1. Remove the unnecessary code from the script block in parade.js. It
<br>looks like Joan still has code in here that has been cut and pasted
<br>from a demo related to instantiating Inline Edits. No need to lint
<br>code that is old and unused.
<br><br>2. Move the remaining code located in parade.html into the Parade.js
<br>file. This way, the component can be entirely self-contained and can
<br>be initialized and run with a single function call. I can help you
<br>with the specifics of
<br><br>Here's a code review from Michelle that outlines a few of these issues:
<br><br><a href="http://old.nabble.com/Bug-Parade-Component-Review-td26504172.html#a26504172" target="_top" rel="nofollow">http://old.nabble.com/Bug-Parade-Component-Review-td26504172.html#a26504172</a><br><br>I hope this helps, and please don't hesitate to ping us in the channel
<br>in the New Year if you want someone to walk you through the specifics
<br>of these fixes. We're happy to help.
<br><br>Colin
<br><br>---
<br>Colin Clark
<br>Technical Lead, Fluid Project
<br><a href="http://fluidproject.org" target="_top" rel="nofollow">http://fluidproject.org</a><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26877534&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26876480Fwd: Ajax Image Zoom (Zoomify)2009-12-21T08:35:25Z2009-12-21T08:35:25ZcolinbdclarkA note from Hugues about zoomable images with Flash...
<br><br>Colin
<br><br>Begin forwarded message:
<br><div class='shrinkable-quote'><br>> From: Hugues Boily <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26876480&i=0" target="_top" rel="nofollow">hugues.boily@...</a>>
<br>> Date: December 18, 2009 5:42:42 PM GMT-05:00
<br>> To: James William Yoon <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26876480&i=1" target="_top" rel="nofollow">james.yoon@...</a>>, Colin Clark <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26876480&i=2" target="_top" rel="nofollow">colin.clark@...</a>
<br>> >
<br>> Subject: Ajax Image Zoom (Zoomify)
<br>>
<br>> Just had thought about zooming object images.
<br>>
<br>> Our website uses a flash component called zoomify (<a href="http://www.zoomify.com/" target="_top" rel="nofollow">http://www.zoomify.com/</a>
<br>> ). It is based on multiples resolutions of an image sliced up in
<br>> jpeg tiles. All our object images have been 'zoomified'.
<br>>
<br>> Apparently, these files could be used by an AJAX based zoomer :
<br>> *
<br>> Zoomify Tiles using JavaScript (AJAX)*
<br>> <a href="http://www.staremapy.cz/zoomifyjs/" target="_top" rel="nofollow">http://www.staremapy.cz/zoomifyjs/</a><br>>
<br>> Cheers,
<br>> Hugues
</div><br>---
<br>Colin Clark
<br>Technical Lead, Fluid Project
<br>Adaptive Technology Resource Centre, University of Toronto
<br><a href="http://fluidproject.org" target="_top" rel="nofollow">http://fluidproject.org</a><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26876480&i=3" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26875802Re: Continuum doesn't like directory restructuring2009-12-21T07:48:37Z2009-12-21T07:48:37ZColin Clark-2<br>On 21-Dec-09, at 10:41 AM, Laurel Williams wrote:
<br>> Can you clarify what you mean by "zap"? I'm thinking that means log
<br>> into the server and delete the working copy so that the next
<br>> checkout is a clean one. Or is there a way to do that via continuum?
<br><br>As far as I can tell, at least with the older version of Continuum we
<br>are running on the main build site, you'll have to ssh into the build
<br>server and delete the contents of Continuum's working copy for that
<br>project. It'll do the right thing from there and check out a fresh copy.
<br><br>I could be missing an option there somewhere, but don't have time to
<br>look at it closely.
<br><br>Colin
<br><br>---
<br>Colin Clark
<br>Technical Lead, Fluid Project
<br><a href="http://fluidproject.org" target="_top" rel="nofollow">http://fluidproject.org</a><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26875802&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26875709Re: Continuum doesn't like directory restructuring2009-12-21T07:41:56Z2009-12-21T07:41:56ZLaurel WilliamsHappy Holiday Colin? Hope you aren't in the grant cave today working on
<br>next year's proposals, but if you are, I hope you are enjoying a purring
<br>cat and your favourite festive drink along with the work.
<br><br>Can you clarify what you mean by "zap"? I'm thinking that means log into
<br>the server and delete the working copy so that the next checkout is a
<br>clean one. Or is there a way to do that via continuum?
<br><br>Laurel
<br><br>Colin Clark wrote:
<div class='shrinkable-quote'><br>> Hey all,
<br>>
<br>> You may have noticed that the daily build of the incubator with
<br>> Continuum has been failing since Friday. It looks like Continuum isn't
<br>> really smart about dealing with directory restructuring--we had moved
<br>> Builder out of the incubator, and then put back in a new directory
<br>> with same name containing only branches for non-committers.
<br>>
<br>> As a result, it looks like we should remember to zap Continuum's
<br>> working copy of incubator and scratchpad whenever we move things
<br>> around, just to ensure that it's correctly building the freshest stuff.
<br>>
<br>> Colin
<br>>
<br>> ---
<br>> Colin Clark
<br>> Technical Lead, Fluid Project
<br>> <a href="http://fluidproject.org" target="_top" rel="nofollow">http://fluidproject.org</a><br>>
<br>> _______________________________________________________
<br>> fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26875709&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>> To unsubscribe, change settings or access archives,
<br>> see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a></div><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26875709&i=1" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26874857Continuum doesn't like directory restructuring2009-12-21T06:38:24Z2009-12-21T06:38:24ZColin Clark-2Hey all,
<br><br>You may have noticed that the daily build of the incubator with
<br>Continuum has been failing since Friday. It looks like Continuum isn't
<br>really smart about dealing with directory restructuring--we had moved
<br>Builder out of the incubator, and then put back in a new directory
<br>with same name containing only branches for non-committers.
<br><br>As a result, it looks like we should remember to zap Continuum's
<br>working copy of incubator and scratchpad whenever we move things
<br>around, just to ensure that it's correctly building the freshest stuff.
<br><br>Colin
<br><br>---
<br>Colin Clark
<br>Technical Lead, Fluid Project
<br><a href="http://fluidproject.org" target="_top" rel="nofollow">http://fluidproject.org</a><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26874857&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26850095What would you like to build?2009-12-18T13:41:01Z2009-12-18T13:41:01ZJustin Obara-3We have been putting in some work on a tool to create a custom build of Fluid Infusion. While it is not quite yet ready for release, you are welcome to take a sneak peak at our nightly build.
<br><br><a href="http://forge.fluidproject.org/infusionBuilder/html/InfusionBuilder.html" target="_top" rel="nofollow">http://forge.fluidproject.org/infusionBuilder/html/InfusionBuilder.html</a><br><br>One thing that I'm quite interested in, is what configurations would you like to build? Please send a reply to this thread to let us know.
<br><br>Thanks
<br>Justin
<br><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26850095&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26844016Asynchronous server side ajax calls throwing an exception2009-12-18T06:11:52Z2009-12-18T06:11:52ZSvetoslav Nedkov<br>Hello all,
<br><br>The problem with asynchronous ajax calls is described with more details in:
<br><br><a href="http://issues.fluidproject.org/browse/ENGAGE-219" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/ENGAGE-219</a><br><br><br>Best regards,
<br><br>Svetoslav
<br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26844016&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26843345review: bug parade component patch2009-12-18T05:24:44Z2009-12-18T05:24:44ZAndrea Leutgoeb .Patch to be reviewed pls:
<br><br><a href="http://issues.fluidproject.org/browse/FLUID-3305?focusedCommentId=16874&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_16874" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3305?focusedCommentId=16874&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_16874</a><br><br>*Changes*
<br>- Jslinted parade.html & parade.js
<br>- New jslinted standalone version parade-standalone.html
<br><br />_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26843345&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26834194Re: My Collection - request for review2009-12-17T12:08:35Z2009-12-17T12:08:35ZBoyan SheytanovHi all!
<br><br>Just one note - if the link Sveto provided doesn't work, try replacing
<br>'unistud' in it with 'megastud' (this is because of ISP switching).
<br>Also, GMail cuts the trailing :"3" from the url, so do not forget to
<br>add it if needed.
<br><br>Greetings,
<br><br>Boyan
<br><br>2009/12/17 Svetoslav Nedkov <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26834194&i=0" target="_top" rel="nofollow">snedkov@...</a>>:
<div class='shrinkable-quote'><br>>
<br>> A little update - the redirects are working now, so the URL to run locally
<br>> should be something like:
<br>>
<br>> <a href="http://host:port/artifacts/myCollection.html?db=users&q=userid:" target="_top" rel="nofollow">http://host:port/artifacts/myCollection.html?db=users&q=userid:</a>"3"
<br>>
<br>> There is already one instance running at:
<br>>
<br>> <a href="http://unistud.asteasolutions.net:11930/artifacts/myCollection.html?db=users&q=userid:" target="_top" rel="nofollow">http://unistud.asteasolutions.net:11930/artifacts/myCollection.html?db=users&q=userid:</a>"3"
<br>>
<br>> If you need just see the functionality.
<br>>
<br>> The modified files are in
<br>>
<br>> fluid-engage-kettle/src/main/webapp/services/myCollection
<br>>
<br>> and
<br>>
<br>> fluid-engage-core/components/myCollection
<br>>
<br>> I've also made a minor change to Engage.js so it will map the artifact
<br>> '_id's and make them available once the translation has been performed.
<br>>
<br>> Once again the project svn branch is
<br>> <a href="https://source.fluidproject.org/svn/scratchpad/myCollection-tryout" target="_top" rel="nofollow">https://source.fluidproject.org/svn/scratchpad/myCollection-tryout</a>.
<br>>
<br>>
<br>> Cheers,
<br>>
<br>> Svetoslav
<br>>
<br>>
<br>>>
<br>>> Hello,
<br>>>
<br>>> I've completed a stage for My Collection view and will be happy if
<br>>> somebody can make a review of the current code.
<br>>>
<br>>> Unfortunately the code is hard to run as I'm using my local machine as
<br>>> CouchDB server and at the moment can't provide a public URL for accessing
<br>>> it.
<br>>>
<br>>> Functionality in place:
<br>>>
<br>>> - grid view - ENGAGE-150
<br>>> - list view - ENGAGE-152
<br>>> - ability to reorder artifacts - ENGAGE-157
<br>>> - transition between grid and list views as part of the top navigation bar
<br>>> - ENGAGE-154
<br>>> - user collection assembled from its own data feed and user collection
<br>>> updated on CouchDB once the artifact order changes - ENGAGE-162
<br>>>
<br>>> Here is the svn repository location where the code lives:
<br>>>
<br>>> <a href="https://source.fluidproject.org/svn/scratchpad/myCollection-tryout" target="_top" rel="nofollow">https://source.fluidproject.org/svn/scratchpad/myCollection-tryout</a><br>>>
<br>>>
<br>>> Regards,
<br>>>
<br>>> Svetoslav
<br>>> _______________________________________________________
<br>>> fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26834194&i=1" target="_top" rel="nofollow">fluid-work@...</a>
<br>>> To unsubscribe, change settings or access archives,
<br>>> see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br>>
<br>> _______________________________________________________
<br>> fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26834194&i=2" target="_top" rel="nofollow">fluid-work@...</a>
<br>> To unsubscribe, change settings or access archives,
<br>> see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br>>
</div>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26834194&i=3" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26833301Infusion Builder testing2009-12-17T11:05:13Z2009-12-17T11:05:13ZJustin Obara-3<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello,<div><br></div><div>Today we are going to be doing some testing for the Infusion Builder.</div><div><br></div><div>If you have time to help with testing, it would be well appreciated.</div><div><br></div><div><ul class="MailOutline"><li>Available Tasks</li><ul><li><a href="http://wiki.fluidproject.org/display/fluid/Release+Testing+Tasks" target="_top" rel="nofollow">http://wiki.fluidproject.org/display/fluid/Release+Testing+Tasks</a></li></ul><li>Test Protocol</li><ul><li><a href="http://wiki.fluidproject.org/display/fluid/Infusion+Builder+QA+Test+Plan" target="_top" rel="nofollow">http://wiki.fluidproject.org/display/fluid/Infusion+Builder+QA+Test+Plan</a></li></ul><li>Test Page</li><ul><li><a href="http://forge.fluidproject.org/infusionBuilder/html/InfusionBuilder.html" target="_top" rel="nofollow">http://forge.fluidproject.org/infusionBuilder/html/InfusionBuilder.html</a></li></ul></ul><div><br></div><div>Please feel free to contact me with any questions.</div><div><br></div><div>Thanks for the help</div><div>Justin</div></div></body></html><br />_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26833301&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26833147Re: Couch access, ENGAGE-213, etc.2009-12-17T10:54:28Z2009-12-17T10:54:28ZColin Clark-2Hi again,
<br><br>On 17-Dec-09, at 1:26 PM, Antranig Basman wrote:
<div class='shrinkable-quote'><br>>>> <link type="text/css" rel="stylesheet" href="../../../../fluid-
<br>>>> infusion/src/webapp/framework/fss/css/fss-layout.css"></link>
<br>>>>
<br>>>> As you can see it has grown four up-segments where only two are
<br>>>> required. I've filed ENGAGE-216 and also want to draw attention to
<br>>>> Justin's ENGAGE-193.
<br>>> Can you elaborate on ENGAGE-216? You say that the "standalone
<br>>> version of Engage is almost certainly broken again," but the daily
<br>>> build link I sent along earlier is indeed the standalone version of
<br>>> Engage. It seems to be working just fine. The Eclpise build is
<br>>> similarly working.
<br>>
<br>> OK, then I should have said the standalone version is *certainly*
<br>> broken
<br>> since it is from that markup that I pasted the text above with the
<br>> broken recursion depth. This probably means that *all* configurations
<br>> are currently broken and only appearing to work through being given a
<br>> path depth greater than that in any current URL mount.
</div><br>Yeah, I see what you're saying. It's working because of the way Tomcat
<br>is parsing these URLs and simply ignoring path depths that go too deep.
<br><br>This seems like something Yura or Justin can fix as they're
<br>refactoring View and Browse to support the new exhibit features.
<br><div class='shrinkable-quote'><br>>>> In this patch are also the beginnings of a rudimentary Couch "API"
<br>>>> similar to some of Joan's work in the scratchpad, including
<br>>>> demonstration of how to issue an HTTP HEAD request to retrieve a
<br>>>> document revision number from etags supplied by Couch. We should
<br>>>> talk about these directions further at the tech meeting on Thursday.
<br>>> Tell us more about how this new code relates to the couch.js and
<br>>> jquery.couch.js utilities that ship directly with Couch?
<br>>> <a href="http://titan.atrc.utoronto.ca:5984/_utils/script/couch.js" target="_top" rel="nofollow">http://titan.atrc.utoronto.ca:5984/_utils/script/couch.js</a><br>>> <a href="http://titan.atrc.utoronto.ca:5984/_utils/script/jquery.couch.js" target="_top" rel="nofollow">http://titan.atrc.utoronto.ca:5984/_utils/script/jquery.couch.js</a><br>>
<br>> Well, looking over the code in these files, one important difference
<br>> seems to be that the Couch shipping utils appear to be entirely unsafe
<br>> for use on the server. couch.js for example uses a single globally
<br>> shared cached array of document uuids which will become corrupted by
<br>> multi-threaded access. However it does show an interesting strategy
<br>> for
<br>> assigning the document id - it appears Couch does not need to see
<br>> that a
<br>> document revision submitted agrees with a particular one in the
<br>> database, but only requires that it is "recent enough" - see the
<br>> workflow leading from "this.save" to newUuuids in couch.js. We will
<br>> need
<br>> something like this cache, but it will need to be implemented
<br>> differently.
<br>>
<br>> The JQuery couch code on the other hand *does* appear to be thread-
<br>> safe,
<br>> at least from a general eyeball (hard to *prove* that code is
<br>> thread-safe) but on the other hand does not make any attempt to help
<br>> the
<br>> issue of a PUT to an already existing document - in particular I don't
<br>> see any functionality to quickly acquire the version info for an
<br>> existing document using for example the HEAD/getResponseHeader combo
<br>> that I had written in my version. The JQuery plugin is unusually
<br>> repetitive for code connected to the JQuery base - perhaps we can
<br>> ship a
<br>> condensed version back to them :P
<br>> I see the beginnings of a "ViewParameters" like system in the
<br>> "encodeOptions" call at the base of jquery.couch.js ... in general, I
<br>> suggest we use these two files as inspiration and perhaps even API
<br>> contract but perhaps not use them directly. The JQuery one at least
<br>> could be cleaned up I suppose, by being given docs and a code
<br>> sweeping.
</div><br>This makes sense. Honestly, I'm leaning heavily towards the option of
<br>refactoring jquery.couch and submitting a patch back to the Couch
<br>community. It's a good in with them, and a chance to get to know them
<br>better. I'm not surprised that the code isn't great, since we've
<br>encountered lots of jQuery plugin code that doesn't uphold the same
<br>excellent code quality standards that jQuery itself does.
<br><br>Anyway, yes, let's look at the feasibility of improving
<br>jquery.couch.js for our needs and sharing it back with the Couch
<br>community.
<br><br>Can you elaborate on what you're seeing in encodeOptions() and how it
<br>leads you towards the beginnings of a ViewParameters-like system?
<br>Glancing at it quickly awhile back, it struck me as somewhat
<br>overlapping with jQuery's own code for converting objects into URL
<br>query parameters.
<br><br>Great thread, let's keep it going.
<br><br>Colin
<br><br>---
<br>Colin Clark
<br>Technical Lead, Fluid Project
<br><a href="http://fluidproject.org" target="_top" rel="nofollow">http://fluidproject.org</a><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26833147&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26832718Couch access, ENGAGE-213, etc.2009-12-17T10:26:17Z2009-12-17T10:26:17ZAntranig Basman-2Colin Clark wrote:
<div class='shrinkable-quote'><br>> Hey Antranig,
<br>>
<br>> On 15-Dec-09, at 4:16 AM, Antranig Basman wrote:
<br>>
<br>>> Actually although everything looks hot, it is in fact not - we have a
<br>>> recurrence of the "excessive path depth" syndrome in the mounted URLs
<br>>> which will mean that the standalone version of Engage is almost
<br>>> certainly broken again. Here is a standard link from the head of the
<br>>> page below:
<br>>>
<br>>> <link type="text/css" rel="stylesheet"
<br>>> href="../../../../fluid-infusion/src/webapp/framework/fss/css/fss-layout.css"></link>
<br>>>
<br>>>
<br>>> As you can see it has grown four up-segments where only two are
<br>>> required. I've filed ENGAGE-216 and also want to draw attention to
<br>>> Justin's ENGAGE-193.
<br>>
<br>> Can you elaborate on ENGAGE-216? You say that the "standalone version of
<br>> Engage is almost certainly broken again," but the daily build link I
<br>> sent along earlier is indeed the standalone version of Engage. It seems
<br>> to be working just fine. The Eclpise build is similarly working.
</div><br>OK, then I should have said the standalone version is *certainly* broken
<br>since it is from that markup that I pasted the text above with the
<br>broken recursion depth. This probably means that *all* configurations
<br>are currently broken and only appearing to work through being given a
<br>path depth greater than that in any current URL mount.
<br><div class='shrinkable-quote'><br>>> In this patch are also the beginnings of a rudimentary Couch "API"
<br>>> similar to some of Joan's work in the scratchpad, including
<br>>> demonstration of how to issue an HTTP HEAD request to retrieve a
<br>>> document revision number from etags supplied by Couch. We should talk
<br>>> about these directions further at the tech meeting on Thursday.
<br>>
<br>> Tell us more about how this new code relates to the couch.js and
<br>> jquery.couch.js utilities that ship directly with Couch?
<br>>
<br>> <a href="http://titan.atrc.utoronto.ca:5984/_utils/script/couch.js" target="_top" rel="nofollow">http://titan.atrc.utoronto.ca:5984/_utils/script/couch.js</a><br>> <a href="http://titan.atrc.utoronto.ca:5984/_utils/script/jquery.couch.js" target="_top" rel="nofollow">http://titan.atrc.utoronto.ca:5984/_utils/script/jquery.couch.js</a></div><br>Well, looking over the code in these files, one important difference
<br>seems to be that the Couch shipping utils appear to be entirely unsafe
<br>for use on the server. couch.js for example uses a single globally
<br>shared cached array of document uuids which will become corrupted by
<br>multi-threaded access. However it does show an interesting strategy for
<br>assigning the document id - it appears Couch does not need to see that a
<br>document revision submitted agrees with a particular one in the
<br>database, but only requires that it is "recent enough" - see the
<br>workflow leading from "this.save" to newUuuids in couch.js. We will need
<br>something like this cache, but it will need to be implemented differently.
<br><br>The JQuery couch code on the other hand *does* appear to be thread-safe,
<br>at least from a general eyeball (hard to *prove* that code is
<br>thread-safe) but on the other hand does not make any attempt to help the
<br>issue of a PUT to an already existing document - in particular I don't
<br>see any functionality to quickly acquire the version info for an
<br>existing document using for example the HEAD/getResponseHeader combo
<br>that I had written in my version. The JQuery plugin is unusually
<br>repetitive for code connected to the JQuery base - perhaps we can ship a
<br>condensed version back to them :P
<br>I see the beginnings of a "ViewParameters" like system in the
<br>"encodeOptions" call at the base of jquery.couch.js ... in general, I
<br>suggest we use these two files as inspiration and perhaps even API
<br>contract but perhaps not use them directly. The JQuery one at least
<br>could be cleaned up I suppose, by being given docs and a code sweeping.
<br><br>> It's clear that, for the low-level database access, we'll want as little
<br>> of our own code as possible--either of these seem to be a suitable
<br>> alternative to Joan's database.js. At the high level, you and Michelle
<br>> and I have chatted about some exciting framework supports for data
<br>> access that I still need to document in the wiki. Expect more in the new
<br>> year for sure.
<br><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26832718&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26831291Re: My Collection - request for review2009-12-17T08:57:06Z2009-12-17T08:57:06ZSvetoslav Nedkov<br>A little update - the redirects are working now, so the URL to run
<br>locally should be something like:
<br><br><a href="http://host:port/artifacts/myCollection.html?db=users&q=userid:" target="_top" rel="nofollow">http://host:port/artifacts/myCollection.html?db=users&q=userid:</a>"3"
<br><br>There is already one instance running at:
<br><br><a href="http://unistud.asteasolutions.net:11930/artifacts/myCollection.html?db=users&q=userid:" target="_top" rel="nofollow">http://unistud.asteasolutions.net:11930/artifacts/myCollection.html?db=users&q=userid:</a>"3"
<br><br>If you need just see the functionality.
<br><br>The modified files are in
<br><br>fluid-engage-kettle/src/main/webapp/services/myCollection
<br><br>and
<br><br>fluid-engage-core/components/myCollection
<br><br>I've also made a minor change to Engage.js so it will map the artifact
<br>'_id's and make them available once the translation has been performed.
<br><br>Once again the project svn branch is
<br><a href="https://source.fluidproject.org/svn/scratchpad/myCollection-tryout" target="_top" rel="nofollow">https://source.fluidproject.org/svn/scratchpad/myCollection-tryout</a>.
<br><br><br>Cheers,
<br><br>Svetoslav
<br><br><div class='shrinkable-quote'><br>>
<br>> Hello,
<br>>
<br>> I've completed a stage for My Collection view and will be happy if
<br>> somebody can make a review of the current code.
<br>>
<br>> Unfortunately the code is hard to run as I'm using my local machine as
<br>> CouchDB server and at the moment can't provide a public URL for
<br>> accessing it.
<br>>
<br>> Functionality in place:
<br>>
<br>> - grid view - ENGAGE-150
<br>> - list view - ENGAGE-152
<br>> - ability to reorder artifacts - ENGAGE-157
<br>> - transition between grid and list views as part of the top navigation
<br>> bar - ENGAGE-154
<br>> - user collection assembled from its own data feed and user collection
<br>> updated on CouchDB once the artifact order changes - ENGAGE-162
<br>>
<br>> Here is the svn repository location where the code lives:
<br>>
<br>> <a href="https://source.fluidproject.org/svn/scratchpad/myCollection-tryout" target="_top" rel="nofollow">https://source.fluidproject.org/svn/scratchpad/myCollection-tryout</a><br>>
<br>>
<br>> Regards,
<br>>
<br>> Svetoslav
<br>> _______________________________________________________
<br>> fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26831291&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>> To unsubscribe, change settings or access archives,
<br>> see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a></div><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26831291&i=1" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26830888Re: ENGAGE-213 and Re: Fluid Engage nightly build broken2009-12-17T08:32:17Z2009-12-17T08:32:17ZColin Clark-2Hey Antranig,
<br><br>On 15-Dec-09, at 4:16 AM, Antranig Basman wrote:
<br><div class='shrinkable-quote'><br>> Actually although everything looks hot, it is in fact not - we have
<br>> a recurrence of the "excessive path depth" syndrome in the mounted
<br>> URLs which will mean that the standalone version of Engage is almost
<br>> certainly broken again. Here is a standard link from the head of the
<br>> page below:
<br>>
<br>> <link type="text/css" rel="stylesheet" href="../../../../fluid-
<br>> infusion/src/webapp/framework/fss/css/fss-layout.css"></link>
<br>>
<br>> As you can see it has grown four up-segments where only two are
<br>> required. I've filed ENGAGE-216 and also want to draw attention to
<br>> Justin's ENGAGE-193.
</div><br>Can you elaborate on ENGAGE-216? You say that the "standalone version
<br>of Engage is almost certainly broken again," but the daily build link
<br>I sent along earlier is indeed the standalone version of Engage. It
<br>seems to be working just fine. The Eclpise build is similarly working.
<br><br>This highlights to a certain extent, I think, the ongoing fuzziness we
<br>all have about how the path rewriting system in Kettle works, and the
<br>need to keep everything working across three environments--local
<br>filesystem, Eclipse, and standalone. We'll get it.
<br><br>> I have committed a fix for ENGAGE-213 reworked slightly from Sveto's
<br>> original patch to supply content length as well as to guarantee
<br>> stream closing. We should now be able to use POST and PUT
<br>> successfully from within Kettle, and I have also added a
<br>> "demonstration" patch to the ENGAGE-213 issue which elaborates
<br>> engageDemo.js to demonstrate this.
<br><br>Excellent!
<br><br>> In this patch are also the beginnings of a rudimentary Couch "API"
<br>> similar to some of Joan's work in the scratchpad, including
<br>> demonstration of how to issue an HTTP HEAD request to retrieve a
<br>> document revision number from etags supplied by Couch. We should
<br>> talk about these directions further at the tech meeting on Thursday.
<br><br>Tell us more about how this new code relates to the couch.js and
<br>jquery.couch.js utilities that ship directly with Couch?
<br><br><a href="http://titan.atrc.utoronto.ca:5984/_utils/script/couch.js" target="_top" rel="nofollow">http://titan.atrc.utoronto.ca:5984/_utils/script/couch.js</a><br><a href="http://titan.atrc.utoronto.ca:5984/_utils/script/jquery.couch.js" target="_top" rel="nofollow">http://titan.atrc.utoronto.ca:5984/_utils/script/jquery.couch.js</a><br><br>It's clear that, for the low-level database access, we'll want as
<br>little of our own code as possible--either of these seem to be a
<br>suitable alternative to Joan's database.js. At the high level, you and
<br>Michelle and I have chatted about some exciting framework supports for
<br>data access that I still need to document in the wiki. Expect more in
<br>the new year for sure.
<br><br>Colin
<br><br>> Colin Clark wrote:
<br>>> Hey again,
<br>>> Since I sent my last note, it noticed that Jacob has fixed the
<br>>> issue in Engage trunk at r8878. I rebuilt the daily build, and it's
<br>>> looking hot again:
<br>>> <a href="http://build.fluidproject.org:8095/engage/artifacts/browse.html?db=mmi&q=Merchandising" target="_top" rel="nofollow">http://build.fluidproject.org:8095/engage/artifacts/browse.html?db=mmi&q=Merchandising</a>
<br>>> Just a reminder to those of us committing code that breaking the
<br>>> build makes everyone sad. :P
<br><br>---
<br>Colin Clark
<br>Technical Lead, Fluid Project
<br><a href="http://fluidproject.org" target="_top" rel="nofollow">http://fluidproject.org</a><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26830888&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26830323Your FLUID-3305 changes as a patch2009-12-17T08:01:18Z2009-12-17T08:01:18ZcolinbdclarkHi Andrea,
<br><br>Thanks so much for JSLinting some of Joan's code, we really appreciate
<br>it. The Fluid community has a well-defined process for committers and
<br>code, which is documented here:
<br><br><a href="http://wiki.fluidproject.org/display/fluid/Coding+and+Commit+Standards" target="_top" rel="nofollow">http://wiki.fluidproject.org/display/fluid/Coding+and+Commit+Standards</a><br><a href="http://wiki.fluidproject.org/display/fluid/Process+for+Granting+Commit+Access" target="_top" rel="nofollow">http://wiki.fluidproject.org/display/fluid/Process+for+Granting+Commit+Access</a><br><br>Access to SVN is on a per-user basis, and shouldn't be shared between
<br>users. New contributors to Fluid generally start out submitting
<br>patches, and as your work ramps up we can assign you a mentor and give
<br>you an account to the incubator space in our SVN.
<br><br>We really do want your submissions! Instead of using Joan's account,
<br>can you create a patch with these changes and attach them to the
<br>appropriate JIRA issue instead? One of the committers in the community
<br>will review the changes, share feedback, and commit them to the
<br>repository for you.
<br><br>Thanks again, and sorry for any confusion,
<br><br>Colin
<br><br>---
<br>Colin Clark
<br>Technical Lead, Fluid Project
<br>Adaptive Technology Resource Centre, University of Toronto
<br><a href="http://fluidproject.org" target="_top" rel="nofollow">http://fluidproject.org</a><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26830323&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26815794Re: Content architecture file added2009-12-16T10:12:11Z2009-12-16T10:12:11ZJames William YoonThanks, Alistair!<br><br>I was wondering if you could repackage the file as a flat Omnigraffle file? svn really sucks at handling non-flat Mac files.<br><br>To do this in Omnigraffle, open the file, go to the documents panel (command-4), click on the documents tab (second tab), and force "Save as flat file" under file format options, then re-save.<br>
<br>Cheers,<br>James<br><br><div class="gmail_quote">On Wed, Dec 16, 2009 at 10:59 AM, Alistair Jones <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26815794&i=0" target="_top" rel="nofollow">ajonesolt@...</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Vicki,<br>
<br>
I added the omnigrafflized version of your content architecture<br>
powerpoint to the repository. You can find it here:<br>
<br>
<a href="http://source.fluidproject.org/svn/design/engage/kiosk/wireframes/content-architecture/" target="_blank" rel="nofollow">http://source.fluidproject.org/svn/design/engage/kiosk/wireframes/content-architecture/</a><br>
<br>
I'll be updating it and developing it with content soon.<br>
<br>
Cheers,<br>
Alistair<br>
_______________________________________________________<br>
fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26815794&i=1" target="_top" rel="nofollow">fluid-work@...</a><br>
To unsubscribe, change settings or access archives,<br>
see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_blank" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br>
</blockquote></div><br>
<br />_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26815794&i=2" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26814565Re: [Decapod] Styling Capture component2009-12-16T09:00:11Z2009-12-16T09:00:11ZJacob F<div>Ok, so I'm going to have to make more tweaks to the CSS but the idea is you can use the FSS button class names to make the buttons look a little nicer.<br></div><div>So, for exaple, the fix image button could go from </div>
<div><br></div><div><font face="courier new,monospace"><button class="flc-capture-button-fix">Fix Image</button></font></div><div><br></div><div>to a styled theme button when you use:</div><div><br></div>
<div><font face="courier new,monospace"><button class="flc-capture-button-fix fl-button-left"><span class="fl-button-inner">Fix Image</span></button></font></div><div><br></div>
<div>The thing is, a little CSS needs to be added to the Capture.css file as well (to fix the bug) which looks like:</div><div><br></div><div><font face="courier new,monospace">.fl-theme-coal .fl-button-left {</font><div style="margin-left: 40px">
<font face="courier new,monospace"> </font><font face="courier new,monospace">background-color:transparent !important;</font></div><div style="margin-left: 40px"><font face="courier new,monospace"> padding-left:13px;</font></div>
<div style="margin-left: 40px"><font face="courier new,monospace"> border:none;</font></div><div style="margin-left: 40px"><font face="courier new,monospace"> overflow:visible;</font></div><div><font face="courier new,monospace">}</font></div>
<div><font face="courier new,monospace">.fl-theme-coal .fl-button-inner {</font></div><div style="margin-left: 40px"><font face="courier new,monospace"> float:none;</font></div><div style="margin-left: 40px"><font face="courier new,monospace"> display:block;</font></div>
<div style="margin-left: 40px"><font face="courier new,monospace"> padding-bottom:7px;</font></div><div><font face="courier new,monospace">}</font></div><div><font face="courier new,monospace"><br></font></div><div><font face="arial,helvetica,sans-serif">I'm just fixing the actual button graphics at the moment, but this should be good enough for now.</font><font face="courier new,monospace"><br>
</font></div><div><font face="arial,helvetica,sans-serif">Give me a shout if you have any questions.<br></font></div><div><font face="arial,helvetica,sans-serif">Jacob<br></font></div><div><font face="courier new,monospace"><br>
</font></div></div><div><br></div><br><div class="gmail_quote">On Wed, Dec 16, 2009 at 10:22 AM, Jacob Farber <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814565&i=0" target="_top" rel="nofollow">jacob.farber@...</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>I'm testing their viability before I recommend them :)<br></div><div>I was thinking to use the fss button styles, but it seems there is a bug in FF when they're applied to buttons. I would like to solve this before I post how to use them.</div>
<div>Jacob</div><div><div class="h5"><br><div class="gmail_quote">On Wed, Dec 16, 2009 at 10:12 AM, Colin Clark <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814565&i=1" target="_top" rel="nofollow">colinbdclark@...</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Jacob,<br>
<div><br>
On 16-Dec-09, at 9:59 AM, Jacob Farber wrote:<br>
<br>
> Nicely done.<br>
> There are a few little tweaks I would like to suggest (not important<br>
> things, but they're easy and look nice, like using themed buttons),<br>
> but overall I think it's looking good.<br>
<br>
</div>What are the tweaks you'd like to suggest? :)<br>
<br>
Colin<br>
<br>
---<br>
<font color="#888888">Colin Clark<br>
Technical Lead, Fluid Project<br>
<a href="http://fluidproject.org" target="_blank" rel="nofollow">http://fluidproject.org</a><br>
</font><div><div><br>
--<br>
<br>
You received this message because you are subscribed to the Google Groups "Decapod Internal" group.<br>
To post to this group, send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814565&i=2" target="_top" rel="nofollow">decapod-internal@...</a>.<br>
To unsubscribe from this group, send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814565&i=3" target="_top" rel="nofollow">decapod-internal%2Bunsubscribe@...</a>.<br>
For more options, visit this group at <a href="http://groups.google.com/group/decapod-internal?hl=en" target="_blank" rel="nofollow">http://groups.google.com/group/decapod-internal?hl=en</a>.<br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br></div></div><div><div class="h5">-- <br>Jacob Farber<br>University of Toronto - ATRC<br>Tel: (416) 946-3002<br><a href="http://www.fluidproject.org" target="_blank" rel="nofollow">www.fluidproject.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Jacob Farber<br>University of Toronto - ATRC<br>Tel: (416) 946-3002<br><a href="http://www.fluidproject.org" target="_top" rel="nofollow">www.fluidproject.org</a><br>
<br />_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814565&i=4" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26814501Re: Work for the week2009-12-16T08:56:43Z2009-12-16T08:56:43Ztona monjoHi all, <br><br>I'll be working this week on: <br><br>1. Mobile wireframes draft 9 with James <br>2. Starting storycards for mobile design draft 9 with James<br>3. Attending a meeting with a Barcelona's museum to talk about the FE project<br>
4. Attending a coordination meeting with the UOC's Fluid team<br><br>Best, <br><br>Tona<br><br><br><br><br><br><div class="gmail_quote">On Wed, Dec 16, 2009 at 4:01 PM, James William Yoon <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814501&i=0" target="_top" rel="nofollow">james.yoon@...</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Till the end of the week:<br>1. Working on mobile wireframes draft 9 with Tona<br>2. Starting storycards for mobile design draft 9 with Tona<br>
3. Revisit our previous kiosk work<br>4. Fleshing out the next iteration of kiosk design with Leah <br>
5. Coordinating next steps for kiosk with Jess and Jennifer<br><br>Cheers,<br><font color="#888888">James</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Tue, Dec 15, 2009 at 5:52 PM, Victoria Moulder <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814501&i=1" target="_top" rel="nofollow">vmoulder@...</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi All;<br>
<div><br>
I will be working on the following:<br>
<br>
</div>1 - Finish writing content for kiosk wireframes<br>
[<a href="http://wiki.fluidproject.org/display/fluid/Content+Mapping" target="_blank" rel="nofollow">http://wiki.fluidproject.org/display/fluid/Content+Mapping</a>]<br>
2 - Plan orientation for Vicky<br>
3 - Work on fleshing out content for [<a href="http://wiki.fluidproject.org/display/fluid/Kiosk+Interactions" target="_blank" rel="nofollow">http://wiki.fluidproject.org/display/fluid/Kiosk+Interactions</a>]<br>
<br>
Best, Vicki<br>
<div><div></div><div><br>
<br>
<br>
----- Original Message -----<br>
From: "Leah Maestri" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814501&i=2" target="_top" rel="nofollow">leahm@...</a>><br>
To: "Alistair Jones" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814501&i=3" target="_top" rel="nofollow">ajonesolt@...</a>><br>
Cc: "fluid-work List" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814501&i=4" target="_top" rel="nofollow">fluid-work@...</a>><br>
Sent: Tuesday, 15 December, 2009 14:36:46 GMT -08:00 US/Canada Pacific<br>
Subject: Re: Work for the week<br>
<br>
Hi all,<br>
I will be working on the following:<br>
<br>
1- Write out use-case scenarios for the alternative 'map kiosk' proposal<br>
2- 'Elevator pitch' or rationale for why we feel the map kiosk proposal is worth tabling (audience > DIA)<br>
3- Storyboard sketches (if there's time) to illustrate map kiosk use (visual aids for Use-case scenarios)<br>
4- Help out others who need a hand with wireframing<br>
<br>
Ciao,<br>
Lee<br>
<br>
----- Original Message -----<br>
From: "Alistair Jones" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814501&i=5" target="_top" rel="nofollow">ajonesolt@...</a>><br>
To: "fluid-work List" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814501&i=6" target="_top" rel="nofollow">fluid-work@...</a>><br>
Sent: Tuesday, December 15, 2009 2:28:44 PM GMT -08:00 US/Canada Pacific<br>
Subject: Work for the week<br>
<br>
Hi Team,<br>
<br>
What I would like to get done before vacation:<br>
<br>
1) Completing omnigraffle wireframes for the content architecture and<br>
2) Researching museum maps (to later create some sketches of what the<br>
DIA's map should look like<br>
<br>
Thanks!<br>
Alistair<br>
_______________________________________________________<br>
fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814501&i=7" target="_top" rel="nofollow">fluid-work@...</a><br>
To unsubscribe, change settings or access archives,<br>
see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_blank" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br>
_______________________________________________________<br>
fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814501&i=8" target="_top" rel="nofollow">fluid-work@...</a><br>
To unsubscribe, change settings or access archives,<br>
see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_blank" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br>
_______________________________________________________<br>
fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814501&i=9" target="_top" rel="nofollow">fluid-work@...</a><br>
To unsubscribe, change settings or access archives,<br>
see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_blank" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br>
</div></div></blockquote></div><br>
</div></div><br>_______________________________________________________<br>
fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814501&i=10" target="_top" rel="nofollow">fluid-work@...</a><br>
To unsubscribe, change settings or access archives,<br>
see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_blank" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Tona Monjo<br>Disseny d'interficies | Diseño de interfaces | Interface design<br><a href="http://www.tonamonjo.com" target="_top" rel="nofollow">http://www.tonamonjo.com</a><br>
<br />_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26814501&i=11" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26813534Content architecture file added2009-12-16T07:59:19Z2009-12-16T07:59:19ZAlistair JonesHi Vicki,
<br><br>I added the omnigrafflized version of your content architecture
<br>powerpoint to the repository. You can find it here:
<br><br><a href="http://source.fluidproject.org/svn/design/engage/kiosk/wireframes/content-architecture/" target="_top" rel="nofollow">http://source.fluidproject.org/svn/design/engage/kiosk/wireframes/content-architecture/</a><br><br>I'll be updating it and developing it with content soon.
<br><br>Cheers,
<br>Alistair
<br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26813534&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26812800Re: [Decapod] Styling Capture component2009-12-16T07:22:10Z2009-12-16T07:22:10ZJacob F<div>I'm testing their viability before I recommend them :)<br></div><div>I was thinking to use the fss button styles, but it seems there is a bug in FF when they're applied to buttons. I would like to solve this before I post how to use them.</div>
<div>Jacob</div><br><div class="gmail_quote">On Wed, Dec 16, 2009 at 10:12 AM, Colin Clark <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812800&i=0" target="_top" rel="nofollow">colinbdclark@...</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hey Jacob,<br>
<div class="im"><br>
On 16-Dec-09, at 9:59 AM, Jacob Farber wrote:<br>
<br>
> Nicely done.<br>
> There are a few little tweaks I would like to suggest (not important<br>
> things, but they're easy and look nice, like using themed buttons),<br>
> but overall I think it's looking good.<br>
<br>
</div>What are the tweaks you'd like to suggest? :)<br>
<br>
Colin<br>
<br>
---<br>
<font color="#888888">Colin Clark<br>
Technical Lead, Fluid Project<br>
<a href="http://fluidproject.org" target="_blank" rel="nofollow">http://fluidproject.org</a><br>
</font><div><div class="h5"><br>
--<br>
<br>
You received this message because you are subscribed to the Google Groups "Decapod Internal" group.<br>
To post to this group, send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812800&i=1" target="_top" rel="nofollow">decapod-internal@...</a>.<br>
To unsubscribe from this group, send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812800&i=2" target="_top" rel="nofollow">decapod-internal%2Bunsubscribe@...</a>.<br>
For more options, visit this group at <a href="http://groups.google.com/group/decapod-internal?hl=en" target="_blank" rel="nofollow">http://groups.google.com/group/decapod-internal?hl=en</a>.<br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Jacob Farber<br>University of Toronto - ATRC<br>Tel: (416) 946-3002<br><a href="http://www.fluidproject.org" target="_top" rel="nofollow">www.fluidproject.org</a><br>
<br />_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812800&i=3" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26812640Re: [Decapod] Styling Capture component2009-12-16T07:12:57Z2009-12-16T07:12:57ZColin Clark-2Hey Jacob,
<br><br>On 16-Dec-09, at 9:59 AM, Jacob Farber wrote:
<br><br>> Nicely done.
<br>> There are a few little tweaks I would like to suggest (not important
<br>> things, but they're easy and look nice, like using themed buttons),
<br>> but overall I think it's looking good.
<br><br>What are the tweaks you'd like to suggest? :)
<br><br>Colin
<br><br>---
<br>Colin Clark
<br>Technical Lead, Fluid Project
<br><a href="http://fluidproject.org" target="_top" rel="nofollow">http://fluidproject.org</a><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812640&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26812460Re: Work for the week2009-12-16T07:01:47Z2009-12-16T07:01:47ZJames William YoonTill the end of the week:<br>1. Working on mobile wireframes draft 9 with Tona<br>2. Starting storycards for mobile design draft 9 with Tona<br>3. Revisit our previous kiosk work<br>4. Fleshing out the next iteration of kiosk design with Leah <br>
5. Coordinating next steps for kiosk with Jess and Jennifer<br><br>Cheers,<br>James<br><br><div class="gmail_quote">On Tue, Dec 15, 2009 at 5:52 PM, Victoria Moulder <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812460&i=0" target="_top" rel="nofollow">vmoulder@...</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi All;<br>
<div class="im"><br>
I will be working on the following:<br>
<br>
</div>1 - Finish writing content for kiosk wireframes<br>
[<a href="http://wiki.fluidproject.org/display/fluid/Content+Mapping" target="_blank" rel="nofollow">http://wiki.fluidproject.org/display/fluid/Content+Mapping</a>]<br>
2 - Plan orientation for Vicky<br>
3 - Work on fleshing out content for [<a href="http://wiki.fluidproject.org/display/fluid/Kiosk+Interactions" target="_blank" rel="nofollow">http://wiki.fluidproject.org/display/fluid/Kiosk+Interactions</a>]<br>
<br>
Best, Vicki<br>
<div><div></div><div class="h5"><br>
<br>
<br>
----- Original Message -----<br>
From: "Leah Maestri" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812460&i=1" target="_top" rel="nofollow">leahm@...</a>><br>
To: "Alistair Jones" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812460&i=2" target="_top" rel="nofollow">ajonesolt@...</a>><br>
Cc: "fluid-work List" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812460&i=3" target="_top" rel="nofollow">fluid-work@...</a>><br>
Sent: Tuesday, 15 December, 2009 14:36:46 GMT -08:00 US/Canada Pacific<br>
Subject: Re: Work for the week<br>
<br>
Hi all,<br>
I will be working on the following:<br>
<br>
1- Write out use-case scenarios for the alternative 'map kiosk' proposal<br>
2- 'Elevator pitch' or rationale for why we feel the map kiosk proposal is worth tabling (audience > DIA)<br>
3- Storyboard sketches (if there's time) to illustrate map kiosk use (visual aids for Use-case scenarios)<br>
4- Help out others who need a hand with wireframing<br>
<br>
Ciao,<br>
Lee<br>
<br>
----- Original Message -----<br>
From: "Alistair Jones" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812460&i=4" target="_top" rel="nofollow">ajonesolt@...</a>><br>
To: "fluid-work List" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812460&i=5" target="_top" rel="nofollow">fluid-work@...</a>><br>
Sent: Tuesday, December 15, 2009 2:28:44 PM GMT -08:00 US/Canada Pacific<br>
Subject: Work for the week<br>
<br>
Hi Team,<br>
<br>
What I would like to get done before vacation:<br>
<br>
1) Completing omnigraffle wireframes for the content architecture and<br>
2) Researching museum maps (to later create some sketches of what the<br>
DIA's map should look like<br>
<br>
Thanks!<br>
Alistair<br>
_______________________________________________________<br>
fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812460&i=6" target="_top" rel="nofollow">fluid-work@...</a><br>
To unsubscribe, change settings or access archives,<br>
see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_blank" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br>
_______________________________________________________<br>
fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812460&i=7" target="_top" rel="nofollow">fluid-work@...</a><br>
To unsubscribe, change settings or access archives,<br>
see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_blank" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br>
_______________________________________________________<br>
fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812460&i=8" target="_top" rel="nofollow">fluid-work@...</a><br>
To unsubscribe, change settings or access archives,<br>
see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_blank" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br>
</div></div></blockquote></div><br>
<br />_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812460&i=9" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26812430Re: [Decapod] Styling Capture component2009-12-16T06:59:38Z2009-12-16T06:59:38ZJacob F<div>Nicely done.<br></div><div>There are a few little tweaks I would like to suggest (not important things, but they're easy and look nice, like using themed buttons), but overall I think it's looking good.</div><div>
Jacob</div><div><br></div><br><div class="gmail_quote">On Wed, Dec 16, 2009 at 5:31 AM, Boyan Sheytanov <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812430&i=0" target="_top" rel="nofollow">boyan.sheytanov@...</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi!<br>
<br>
I made a first pass on styling the capture component (committed in the<br>
SVN repo under scratchpad/decapod/components/capture). I added a<br>
2-column layout and a theme and changed markup a bit (list items for<br>
the images, buttons instead of anchors). It's not looking anything<br>
much and seems somewhat unfinished (probably because it is!). You can<br>
have a look at it and decide how far we should get this for the<br>
deliverable (as it is a demonstration only, it doesn't need much, I<br>
think).<br>
<br>
Greetings,<br>
<br>
Boyan<br>
<font color="#888888"><br>
--<br>
<br>
You received this message because you are subscribed to the Google Groups "Decapod Internal" group.<br>
To post to this group, send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812430&i=1" target="_top" rel="nofollow">decapod-internal@...</a>.<br>
To unsubscribe from this group, send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812430&i=2" target="_top" rel="nofollow">decapod-internal%2Bunsubscribe@...</a>.<br>
For more options, visit this group at <a href="http://groups.google.com/group/decapod-internal?hl=en" target="_blank" rel="nofollow">http://groups.google.com/group/decapod-internal?hl=en</a>.<br>
<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Jacob Farber<br>University of Toronto - ATRC<br>Tel: (416) 946-3002<br><a href="http://www.fluidproject.org" target="_top" rel="nofollow">www.fluidproject.org</a><br>
<br />_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26812430&i=3" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26809118[Decapod] Styling Capture component2009-12-16T02:31:51Z2009-12-16T02:31:51ZBoyan SheytanovHi!
<br><br>I made a first pass on styling the capture component (committed in the
<br>SVN repo under scratchpad/decapod/components/capture). I added a
<br>2-column layout and a theme and changed markup a bit (list items for
<br>the images, buttons instead of anchors). It's not looking anything
<br>much and seems somewhat unfinished (probably because it is!). You can
<br>have a look at it and decide how far we should get this for the
<br>deliverable (as it is a demonstration only, it doesn't need much, I
<br>think).
<br><br>Greetings,
<br><br>Boyan
<br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26809118&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26807697Re: UI Integration with Server2009-12-16T00:16:47Z2009-12-16T00:16:47ZBoyan SheytanovHi Michelle!
<br><br>I believe we can build a demo with the CherryPy server. I will start
<br>working on integration with it once I finish the work I started on
<br>basic FSS styling (hopefully that will be today).
<br><br>Greetings,
<br><br>Boyan
<br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26807697&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26804199Bug Parade Infusion Builder: Update 42009-12-15T16:10:23Z2009-12-15T16:10:23ZColin Clark-2* Needs Review: FLUID-3407
<br>* Punted: FLUID-3399
<br>* Escalated: FLUID-3417, FLUID-3429
<br><br>========================================================================
<br>***This is a special mini-bug parade that only affects the Infusion
<br>Builder. Other parts of the repository are still open for commits***
<br><br>Bug Parade Infusion Builder
<br><br>* JIRA filters:
<br><a href="http://issues.fluidproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=10287" target="_top" rel="nofollow">http://issues.fluidproject.org/secure/IssueNavigator.jspa?mode=hide&requestId=10287</a><br><br>* Commit standards:
<br><a href="http://wiki.fluidproject.org/display/fluid/Coding+and+Commit+Standards#CodingandCommitStandards-CommittingDuringtheBugParadeandCodeFreezePeriods" target="_top" rel="nofollow">http://wiki.fluidproject.org/display/fluid/Coding+and+Commit+Standards#CodingandCommitStandards-CommittingDuringtheBugParadeandCodeFreezePeriods</a><br><br><br>Infusion Builder:
<br><br>Blocker
<br><br> FLUID-3417:
<br> Alter builder deploy and build process to use new targets in ant script
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3417" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3417</a><br><br> FLUID-3429:
<br> The titles and descriptions of our dependency modules can be improved
<br>to be clearer and more explanatory when displayed in the Builder
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3429" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3429</a><br><br> FLUID-3409:
<br> move Infusion Builder in svn for QA
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3409" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3409</a><br><br> FLUID-3407: **REVIEW**
<br> Alter builder to use minification step on deploy
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3407" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3407</a><br><br> FLUID-3427: **CLOSED**
<br> At the moment, the PHP and JavaScript unit tests for Infusion aren't
<br>publicly visible on the daily build
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3427" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3427</a><br><br> FLUID-3425: **CLOSED**
<br> Bring back the user-visible descriptions for each module in the
<br>Infusion Builder
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3425" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3425</a><br><br> FLUID-3423: **CLOSED**
<br> Builder won't load in IE
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3423" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3423</a><br><br> FLUID-3359: **CLOSED**
<br> Design and implement a new "lightweight" look and feel for the
<br>Infusion Builder, independent of our Fluid web site
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3359" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3359</a><br><br> FLUID-3162: **CLOSED**
<br> Add the Infusion builder to the Fluid daily build server
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3162" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3162</a><br><br><br>Critical
<br><br> FLUID-3428: **CLOSED**
<br> The Infusion Builder QA test plan currently has out-of-date links to
<br>the Builder. These should be updated to point to the new Builder daily
<br>build
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3428" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3428</a><br><br> FLUID-3412: **CLOSED**
<br> add hidden span with component description for each module
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3412" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3412</a><br><br><br>Major
<br><br> FLUID-3426:
<br> Add links to the Infusion Builder daily on the main
<br>build.fluidproject.org page
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3426" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3426</a><br><br> FLUID-3414:
<br> Code cleanup for Infusion Builder Bug Parade 1.1.2
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3414" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3414</a><br><br> FLUID-3430: **CLOSED**
<br> cache key is not generated for single module "framework"
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3430" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3430</a><br><br> FLUID-3419: **CLOSED**
<br> revise code to remove parts no longer needed since the new re-design
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3419" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3419</a><br><br> FLUID-3413: **CLOSED**
<br> Unit tests are broken
<br> <a href="http://issues.fluidproject.org/browse/FLUID-3413" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3413</a><br><br>---
<br>Colin Clark
<br>Technical Lead, Fluid Project
<br><a href="http://fluidproject.org" target="_top" rel="nofollow">http://fluidproject.org</a><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26804199&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26803311Re: Work for the week2009-12-15T14:52:33Z2009-12-15T14:52:33ZVictoria MoulderHi All;
<br><br>I will be working on the following:
<br><br>1 - Finish writing content for kiosk wireframes
<br>[<a href="http://wiki.fluidproject.org/display/fluid/Content+Mapping" target="_top" rel="nofollow">http://wiki.fluidproject.org/display/fluid/Content+Mapping</a>]
<br>2 - Plan orientation for Vicky
<br>3 - Work on fleshing out content for [<a href="http://wiki.fluidproject.org/display/fluid/Kiosk+Interactions" target="_top" rel="nofollow">http://wiki.fluidproject.org/display/fluid/Kiosk+Interactions</a>]
<br><br>Best, Vicki
<br><br><br><br>----- Original Message -----
<br>From: "Leah Maestri" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26803311&i=0" target="_top" rel="nofollow">leahm@...</a>>
<br>To: "Alistair Jones" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26803311&i=1" target="_top" rel="nofollow">ajonesolt@...</a>>
<br>Cc: "fluid-work List" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26803311&i=2" target="_top" rel="nofollow">fluid-work@...</a>>
<br>Sent: Tuesday, 15 December, 2009 14:36:46 GMT -08:00 US/Canada Pacific
<br>Subject: Re: Work for the week
<br><br>Hi all,
<br>I will be working on the following:
<br><br>1- Write out use-case scenarios for the alternative 'map kiosk' proposal
<br>2- 'Elevator pitch' or rationale for why we feel the map kiosk proposal is worth tabling (audience > DIA)
<br>3- Storyboard sketches (if there's time) to illustrate map kiosk use (visual aids for Use-case scenarios)
<br>4- Help out others who need a hand with wireframing
<br><br>Ciao,
<br>Lee
<br><br>----- Original Message -----
<br>From: "Alistair Jones" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26803311&i=3" target="_top" rel="nofollow">ajonesolt@...</a>>
<br>To: "fluid-work List" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26803311&i=4" target="_top" rel="nofollow">fluid-work@...</a>>
<br>Sent: Tuesday, December 15, 2009 2:28:44 PM GMT -08:00 US/Canada Pacific
<br>Subject: Work for the week
<br><br>Hi Team,
<br><br>What I would like to get done before vacation:
<br><br>1) Completing omnigraffle wireframes for the content architecture and
<br>2) Researching museum maps (to later create some sketches of what the
<br>DIA's map should look like
<br><br>Thanks!
<br>Alistair
<br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26803311&i=5" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26803311&i=6" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26803311&i=7" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26803076Re: Work for the week2009-12-15T14:36:46Z2009-12-15T14:36:46ZLeah Maestri-2Hi all,
<br>I will be working on the following:
<br><br>1- Write out use-case scenarios for the alternative 'map kiosk' proposal
<br>2- 'Elevator pitch' or rationale for why we feel the map kiosk proposal is worth tabling (audience > DIA)
<br>3- Storyboard sketches (if there's time) to illustrate map kiosk use (visual aids for Use-case scenarios)
<br>4- Help out others who need a hand with wireframing
<br><br>Ciao,
<br>Lee
<br><br>----- Original Message -----
<br>From: "Alistair Jones" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26803076&i=0" target="_top" rel="nofollow">ajonesolt@...</a>>
<br>To: "fluid-work List" <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26803076&i=1" target="_top" rel="nofollow">fluid-work@...</a>>
<br>Sent: Tuesday, December 15, 2009 2:28:44 PM GMT -08:00 US/Canada Pacific
<br>Subject: Work for the week
<br><br>Hi Team,
<br><br>What I would like to get done before vacation:
<br><br>1) Completing omnigraffle wireframes for the content architecture and
<br>2) Researching museum maps (to later create some sketches of what the
<br>DIA's map should look like
<br><br>Thanks!
<br>Alistair
<br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26803076&i=2" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26803076&i=3" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26802968Work for the week2009-12-15T14:28:44Z2009-12-15T14:28:44ZAlistair JonesHi Team,
<br><br>What I would like to get done before vacation:
<br><br>1) Completing omnigraffle wireframes for the content architecture and
<br>2) Researching museum maps (to later create some sketches of what the
<br>DIA's map should look like
<br><br>Thanks!
<br>Alistair
<br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26802968&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26802209state of infusion builder release2009-12-15T13:36:26Z2009-12-15T13:36:26ZLaurel WilliamsHi all,
<br><br>I am very very close to completing
<br><a href="http://issues.fluidproject.org/browse/FLUID-3417" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3417</a> which is one of the
<br>last few tasks before we start QA.
<br><br>I have integrated the pretreatMinify step into the deploy scripts
<br>successfully (some testing still required and not checked in). I am
<br>about 60% of my way through changing the php to use the new builderBuild
<br>target in the infusion build scripts and anticipate being able to
<br>complete that fix tomorrow morning.
<br><br><br>Laurel
<br><br><br /><tt>[laurel_williams.vcf]</tt><br /><hr align="left" width="300" /><tt>begin:vcard
<br>fn:Laurel A. Williams
<br>n:Williams;Laurel
<br>org:Faculty of Information, University of Toronto;Adaptive Technology Resource Centre (ATRC)
<br>email;internet:<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26802209&i=0" target="_top" rel="nofollow">laurel.williams@...</a>
<br>title:Accessibility Software Designer
<br>x-mozilla-html:TRUE
<br>version:2.1
<br>end:vcard
<br><br></tt><hr align="left" width="300" /><br />_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26802209&i=1" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26800939Re: [Decapod] FLUID-3314 Request for a code review2009-12-15T12:08:11Z2009-12-15T12:08:11ZMichelle D'SouzaThanks for your detailed updates Boyan - it's really useful. You are right that it's time to do a full code review of this code and it's on my todo list.
<br><br>Michelle
<br><br><br>On 2009-12-11, at 8:33 AM, Boyan Sheytanov wrote:
<br><div class='shrinkable-quote'><br>> Hi all,
<br>>
<br>> I've made the finishing touches on Decapod's Capture screen
<br>> functionality. My code is committed in the SVN repository and supports
<br>> the following:
<br>>
<br>> 1. When you open the capture screen, a thumbnail with text "No images
<br>> captured yet" is the only one shown. The preview area says "No preview
<br>> available". You are able to take pictures.
<br>> 2. When you click on the 'Take picture' button, the empty thumbnail is
<br>> replaced by a picture from the local file system (in
<br>> ../../server/testData/). This *does not* make calls to the server. The
<br>> image taken is selected (focused), which makes the full-sized version
<br>> appear in the preview area. Behind the scenes, the image is added to
<br>> the component's model.
<br>> 3. You can take as many pictures as you like. The interface will
<br>> repeatedly iterate over the sample pictures we have currently (some
<br>> nice nature photos I've taken, we need a better set of test data
<br>> (images with dewarped text, etc.) prior to releasing).
<br>> 4. You can delete pictures by... (surprise) pressing the 'Delete'
<br>> button. This will remove the image from the model and from the markup
<br>> and will select the next image. If the last image is deleted, the
<br>> previous image will be selected.
<br>> 5. If you delete all images, the blank thumbnail and preview area are
<br>> shown (as in 1).
<br>> 6. Links for fixing, comparing and exporting images are clickable, but
<br>> do nothing currently as we do not have the screens for these
<br>> components.
<br>>
<br>> I'll be happy to see your notes and comments on the code I've written
<br>> as there might be a fair amount of things to be improved (The fact
<br>> that the code works doesn't mean that it is written in the best
<br>> possible way, probably there are things I have not thought about).
<br>> I'll be travelling today and won't be able to join the daily stand-up
<br>> meeting, so consider this a status update as well.
<br>>
<br>> The next steps I will take are (not necessarily in the order specified):
<br>> 1. Write some unit tests for the Capture component (ah, I've been
<br>> promising this for a week or so).
<br>> 2. Get acquainted in more detail with the FSS, probably apply some
<br>> basic styling (depending on the discussion on Monday).
<br>> 3. Get acquainted with Michelle's work on Kettle and work together
<br>> with her on integrating the UI and the server.
<br>>
<br>> Have a wonderful sunny/snowy weekend everyone,
<br>>
<br>> Boyan
<br>>
<br>> --
<br>>
<br>> You received this message because you are subscribed to the Google Groups "Decapod Internal" group.
<br>> To post to this group, send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26800939&i=0" target="_top" rel="nofollow">decapod-internal@...</a>.
<br>> To unsubscribe from this group, send email to <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26800939&i=1" target="_top" rel="nofollow">decapod-internal+unsubscribe@...</a>.
<br>> For more options, visit this group at <a href="http://groups.google.com/group/decapod-internal?hl=en" target="_top" rel="nofollow">http://groups.google.com/group/decapod-internal?hl=en</a>.
<br>>
<br>>
</div><br><br><br>------------------------------------------------------
<br>Michelle D'Souza
<br>Software Developer, Fluid Project
<br>Adaptive Technology Resource Centre
<br>University of Toronto
<br><br><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26800939&i=2" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26800375Re: Infusion Build Script Status2009-12-15T11:32:15Z2009-12-15T11:32:15ZYura ZenHi Michelle, as per our discussion these are some issues related to the build scripts testing that I found:<div>* When running a script to make a custom build with no minification (<span class="Apple-style-span" style="font-family: Verdana, arial, sans-serif; font-size: 11px; border-collapse: collapse; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">ant customBuild -DnoMinify="true"<span class="Apple-style-span" style="border-collapse: separate; font-family: arial; line-height: normal; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; font-size: small; ">) it produces infusion-1.2.zip. Since noMinify options is set to true, it might be sensible to have the zip file called infusion-1.2-src to indicate that it's not minified. </span></span></div>
<div><span class="Apple-style-span" style="font-family: Verdana, arial, sans-serif; font-size: 11px; border-collapse: collapse; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><span class="Apple-style-span" style="border-collapse: separate; font-family: arial; line-height: normal; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; font-size: small; ">* When running Infusion Test build (<span class="Apple-style-span" style="font-family: Verdana, arial, sans-serif; font-size: 11px; border-collapse: collapse; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">ant infusionAllBuilds<span class="Apple-style-span" style="border-collapse: separate; font-family: arial; line-height: normal; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; font-size: small; ">) there were 2 main issues found with the new builds:</span></span></span></span></div>
<div><span class="Apple-style-span" style="font-family: Verdana, arial, sans-serif; font-size: 11px; border-collapse: collapse; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><span class="Apple-style-span" style="border-collapse: separate; font-family: arial; line-height: normal; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; font-size: small; "><span class="Apple-style-span" style="font-family: Verdana, arial, sans-serif; font-size: 11px; border-collapse: collapse; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><span class="Apple-style-span" style="border-collapse: separate; font-family: arial; line-height: normal; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; font-size: small; ">** <span class="Apple-style-span" style="font-family: Verdana, arial, sans-serif; font-size: 11px; border-collapse: collapse; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">Tests/manual-tests/lib/fckeditor/editor/_source/internals/fcktools_ie.js: is empty in the new build (both minified and not minified): <a href="http://issues.fluidproject.org/browse/FLUID-3431" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3431</a></span></span></span></span></span></div>
<div><span class="Apple-style-span" style="font-family: Verdana, arial, sans-serif; font-size: 11px; border-collapse: collapse; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><span class="Apple-style-span" style="border-collapse: separate; font-family: arial; line-height: normal; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; font-size: small; "><span class="Apple-style-span" style="font-family: Verdana, arial, sans-serif; font-size: 11px; border-collapse: collapse; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><span class="Apple-style-span" style="border-collapse: separate; font-family: arial; line-height: normal; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; font-size: small; "><span class="Apple-style-span" style="font-family: Verdana, arial, sans-serif; font-size: 11px; border-collapse: collapse; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">** New minified build has all files included in components/uiOptions/html/UIOptions.html and components/uploader/html/Uploader.html when the old one includes InfusionAll.js : <a href="http://issues.fluidproject.org/browse/FLUID-3432" target="_top" rel="nofollow">http://issues.fluidproject.org/browse/FLUID-3432</a></span></span></span></span></span></div>
<div><span class="Apple-style-span" style="font-family: Verdana, arial, sans-serif; font-size: 11px; border-collapse: collapse; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><span class="Apple-style-span" style="border-collapse: separate; font-family: arial; line-height: normal; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; font-size: small; "><span class="Apple-style-span" style="font-family: Verdana, arial, sans-serif; font-size: 11px; border-collapse: collapse; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><span class="Apple-style-span" style="border-collapse: separate; font-family: arial; line-height: normal; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; font-size: small; "><span class="Apple-style-span" style="font-family: Verdana, arial, sans-serif; font-size: 11px; border-collapse: collapse; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><br>
</span></span></span></span></span></div><div><font class="Apple-style-span" face="Verdana, arial, sans-serif" size="3"><span class="Apple-style-span" style="border-collapse: collapse; font-size: 11px; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px;">Detailed testing process is recorded as mentioned before here: <a href="http://wiki.fluidproject.org/display/fluid/Build+Scripts+Improvements+Notes,+Testing" target="_top" rel="nofollow">http://wiki.fluidproject.org/display/fluid/Build+Scripts+Improvements+Notes,+Testing</a></span></font></div>
<div><font class="Apple-style-span" face="Verdana, arial, sans-serif" size="3"><span class="Apple-style-span" style="border-collapse: collapse; font-size: 11px; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px;"><br>
</span></font></div><div><font class="Apple-style-span" face="Verdana, arial, sans-serif" size="3"><span class="Apple-style-span" style="border-collapse: collapse; font-size: 11px; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px;">Yura</span></font></div>
<div><br><div class="gmail_quote">On Tue, Dec 15, 2009 at 10:47 AM, Yura Zenevich <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26800375&i=0" target="_top" rel="nofollow">yura.zenevich@...</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Michelle,<div><br></div><div>I added the wiki page with the up to date summary of the builder testing: <a href="http://wiki.fluidproject.org/display/fluid/Build+Scripts+Improvements+Notes,+Testing" target="_blank" rel="nofollow">http://wiki.fluidproject.org/display/fluid/Build+Scripts+Improvements+Notes,+Testing</a> . We will be updating the chart as we go along. <br>
<br></div><div>Yura</div><div><div></div><div class="h5"><div><br><div class="gmail_quote">On Mon, Dec 14, 2009 at 5:40 PM, Colin Clark <span dir="ltr"><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26800375&i=1" target="_top" rel="nofollow">colinbdclark@...</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Michelle,<div><br>
<br>
On 14-Dec-09, at 4:39 PM, Michelle wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The main problem is the difficulty in testing the changes properly. Yura and Laurel have been testing this afternoon however there is still a lot of testing that remains. We should put our testing and results on the wiki - Yura, would you be willing to do this? The quick summary is that we still need to test the daily build, the release builds and the custom build. There are several minor differences that we've noticed between the old and new builds for things we have already tested. The biggest difference is in the unminified builds where we now include a war file and we no longer include the json dependency files. I'm not sure if this is a bug or a feature. Thoughts?<br>
</blockquote>
<br></div>
Does anyone have a wiki URL where these test results have been posted?<br>
<br>
As for your question about the minor build differences, I think it's reasonable to include a war file in the non-minified builds, and to prune out the dependency files. I think, in the long run, we may want to look at the structure of these "source" builds and ensure that they provide everything required to rebuild them into a minified release. This would include the build scripts themselves, dependency files, and so on. But since that's a large and separate task, I think it's reasonable enough to provide symmetrical builds instead.<br>
<br>
I can understand an argument where we want to ensure that 1.1.2.1 build products are 100% identical to those produced by the 1.1.2 build, but I think even with these slight variations this is still a "no feature" release. What do you think?<div>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The one issue that we've found so far is that my changes to the Infusion build have broken the Engage build. This is actually not a blocker for the infusion builder release since we'll be branching for that release. It does, however, mean that I can't commit my patch into trunk until I get the Engage build going again.<br>
</blockquote>
<br></div>
You can still commit your changes to the Infusion 1.1.2.x branch (that's a lot of dots!), allowing us to continue with the release of Builder while trunk and Engage stay slightly behind the curve for an extra day or two until we update Engage's build. Seem reasonable, or am I missing some key details?<br>
<br>
Colin<br>
<br>
---<br><font color="#888888">
Colin Clark<br>
Technical Lead, Fluid Project<br>
<a href="http://fluidproject.org" target="_blank" rel="nofollow">http://fluidproject.org</a></font><div><div></div><div><br>
<br>
_______________________________________________________<br>
fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26800375&i=2" target="_top" rel="nofollow">fluid-work@...</a><br>
To unsubscribe, change settings or access archives,<br>
see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_blank" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
<br />_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26800375&i=3" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>tag:old.nabble.com,2006:post-26800279UI Integration with Server2009-12-15T11:25:25Z2009-12-15T11:25:25ZMichelle D'SouzaHi Boyan,
<br><br>As you know I've been distracted from the Kettle work that I was slated to do by the upcoming Infusion Builder release. The work that I'm doing for the release is taking me longer then I expected. I will complete the work on Kettle in January.
<br><br>In the mean time, I know that you had originally integrated with the Cherry Py server. Is that still the case? Would we be able to put together an end to end demo using the UI that you've built and the Cherry Py server?
<br><br>Thanks,
<br><br>Michelle
<br><br><br><br>------------------------------------------------------
<br>Michelle D'Souza
<br>Software Developer, Fluid Project
<br>Adaptive Technology Resource Centre
<br>University of Toronto
<br><br><br><br>_______________________________________________________
<br>fluid-work mailing list - <a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26800279&i=0" target="_top" rel="nofollow">fluid-work@...</a>
<br>To unsubscribe, change settings or access archives,
<br>see <a href="http://fluidproject.org/mailman/listinfo/fluid-work" target="_top" rel="nofollow">http://fluidproject.org/mailman/listinfo/fluid-work</a><br><p>From forum: <a href="http://old.nabble.com/Fluid---Work-f28540.html" embed="fixTarget[28540]" target="_top" >Fluid - Work</a></p>