[10:25:36 CST(-0600)] <athena> EricDalquist: can you build the weather portlet right now?
[10:25:45 CST(-0600)] <athena> i keep getting [ERROR] Failed to execute goal on project WeatherPortlet: Could not resolve dependencies for project org.jasig.portlet:WeatherPortlet:war:1.0.8-SNAPSHOT: Could not find artifact javax.script:groovy-engine:jar:jdk14:1.1 in central (http://repo1.maven.org/maven2) -> [Help 1]
[10:25:52 CST(-0600)] <EricDalquist> no idea ...
[10:25:52 CST(-0600)] <EricDalquist> huh
[10:25:57 CST(-0600)] <athena> been having problems with random stuff like that ever since i switched to maven 3
[10:30:18 CST(-0600)] <athena> uhoh.
[10:30:31 CST(-0600)] <athena> he just decided a 50ft coil of ethernet cable was a toy
[10:30:39 CST(-0600)] <athena> should probably get kris down here or put him in his crate
[10:30:48 CST(-0600)] <EricDalquist> lol
[10:30:57 CST(-0600)] <EricDalquist> yeah I'll be more help tomorrow if everything goes well
[10:31:03 CST(-0600)] <EricDalquist> preping for our 3.2 upgrade tomorrow at 5am
[10:32:13 CST(-0600)] <athena> hope that goes well!
[13:26:05 CST(-0600)] <EricDalquist> athena: time to test your JS skills ... can you do sub-classing with fluid components?
[13:26:20 CST(-0600)] <athena> hm
[13:26:33 CST(-0600)] <athena> kind of depends what you mean by subclassing, perhaps
[13:26:35 CST(-0600)] <EricDalquist> like if I write a Search component that has a bunch of helper methods. Can I write a UWGoogleSearch component that overrides those ethods?
[13:26:50 CST(-0600)] <athena> typically you might have a component with subcomponents
[13:26:59 CST(-0600)] <EricDalquist> I did a bunch of JS work on the search portlet in trunk to make it more extensible
[13:26:59 CST(-0600)] <athena> and you could have different implementations of those subcomponents, sort of
[13:27:03 CST(-0600)] <EricDalquist> at least the JS part so far
[13:27:04 CST(-0600)] <athena> oh fantastic 
[13:27:15 CST(-0600)] <EricDalquist> I'll post some examples of what I have now
[13:27:37 CST(-0600)] <athena> like with the pager, there's a default implementation of a lot of the little subcomponents, but you can plug in alternate implementations
[13:27:37 CST(-0600)] <EricDalquist> up-search.js: http://uportal.pastebin.com/uq08xs1J
[13:27:46 CST(-0600)] <athena> is that the kind of thing you were looking for?
[13:27:57 CST(-0600)] <athena> awesome
[13:28:13 CST(-0600)] <EricDalquist> uwgooglesearch.js: http://uportal.pastebin.com/E7FEYHsp
[13:28:39 CST(-0600)] <EricDalquist> and how I init them: http://uportal.pastebin.com/4MbbSW5m
[13:29:03 CST(-0600)] <EricDalquist> so essentially I defined a bunch of methods in search.js using function pointers in the options
[13:29:35 CST(-0600)] <athena> gotcha
[13:29:56 CST(-0600)] <EricDalquist> then when initializing Search I just pass in new function pointers for the methods I want to override
[13:29:58 CST(-0600)] <athena> so i wonder if it's worth talking to fluid about some of the new IoC stuff
[13:29:58 CST(-0600)] <EricDalquist> it works
[13:30:02 CST(-0600)] <EricDalquist> and I'm fairly happy with it
[13:30:08 CST(-0600)] <EricDalquist> but just wondering about a better way
[13:30:13 CST(-0600)] <athena> because i think that's sort of eventually goign to be the answer to this question
[13:30:17 CST(-0600)] <EricDalquist> ok I'll go bug antranig
[13:30:23 CST(-0600)] <athena> there's a preview of the IoC as of 1.3, which just got released
[13:30:31 CST(-0600)] <athena> i know next to nothing about it yet, but i'd really like to know more
[13:30:45 CST(-0600)] <athena> he suggested it might help with some of the problems i ran into while developing the gallery stuff
[13:30:57 CST(-0600)] <EricDalquist> post-upgrade I'm going to be getting these changes back to trunk
[13:31:01 CST(-0600)] <athena> awesome
[13:31:05 CST(-0600)] <athena> sounds really great
[13:31:11 CST(-0600)] <EricDalquist> the JS code is mostly shared
[13:31:39 CST(-0600)] <athena> would be interesting to talk about what we'd need to do to start creating a uportal search index - maybe just starting out with the CMS portlet even
[13:32:37 CST(-0600)] <EricDalquist> yeah
[13:40:50 CST(-0600)] <EricDalquist> for the search portlet, I'm thinking that it would be a reasonable approach that someone should just have to do 3 things to create a new search provider:
[13:40:50 CST(-0600)] <EricDalquist> - create a fooSearch.js like: http://uportal.pastebin.com/E7FEYHsp
[13:40:50 CST(-0600)] <EricDalquist> - create a fooSearch.jsp with the RSF results template
[13:40:50 CST(-0600)] <EricDalquist> - create the search ajax controller and map it in mvcServletContext.xml
[13:41:05 CST(-0600)] <EricDalquist> so in theory the only file you need to actually modify is mvcServletContext.xml
[13:41:20 CST(-0600)] <EricDalquist> and everything else is just a few portlet preferences
[13:44:48 CST(-0600)] <EricDalquist> oh did you ever get the weather portlet thing figure out?
[14:20:06 CST(-0600)] <athena> no
[14:20:26 CST(-0600)] <athena> i've got a pretty huge backlog of tasks right now, so i'm not likely to look at it again soon unless i absolutely have to
General
Content
Integrations