[13:04:42 CDT(-0500)] <drewwills1> thanks btw EricDalquist, for excellent coverage of the uPlatform concept
[13:04:57 CDT(-0500)] <EricDalquist> np
[13:05:39 CDT(-0500)] <drewwills1> it's nice to show ssp around a bit again, since at the conference there wasn't much of the new version to show
[13:05:48 CDT(-0500)] <EricDalquist> yeah
[13:05:52 CDT(-0500)] <EricDalquist> it looks pretty cool
[13:05:57 CDT(-0500)] <EricDalquist> I need to email russ about bamboo
[13:06:30 CDT(-0500)] <drewwills1> cool
[13:13:15 CDT(-0500)] <chris_cousquer> hi
[13:13:54 CDT(-0500)] <chris_cousquer> does ssp have sencha touch in it ?
[13:15:48 CDT(-0500)] <drewwills1> i don't think so, chris... not at this point
[13:16:11 CDT(-0500)] <chris_cousquer> ok great
[13:16:18 CDT(-0500)] <drewwills1> it uses the extjs framework for rendering the UI in a browser
[13:16:36 CDT(-0500)] <chris_cousquer> oh yeah that 's it
[13:17:00 CDT(-0500)] <drewwills1> we need to develop our mobile plans more clearly
[13:17:16 CDT(-0500)] <drewwills1> some of the tools are probably too heavy to simply port to mobile
[13:17:23 CDT(-0500)] <chris_cousquer> I've got problem with extjs and fluid in some french portlet
[13:17:27 CDT(-0500)] <drewwills1> but the early alert would be a great mobile tool
[13:17:40 CDT(-0500)] <drewwills1> using them together? or either?
[13:17:47 CDT(-0500)] <chris_cousquer> yeah
[13:18:09 CDT(-0500)] <chris_cousquer> extjs enters in conflict with fluid
[13:18:12 CDT(-0500)] <chris_cousquer> and
[13:19:01 CDT(-0500)] <chris_cousquer> some UX (old ones…) included prototype.js witch enter in conflict with jQuery
[13:19:10 CDT(-0500)] <chris_cousquer> :-@
[13:19:27 CDT(-0500)] <drewwills1> only 1 portlet uses extjs at this point, the big one
[13:20:03 CDT(-0500)] <drewwills1> which we deploy on its own tab, without portlet chrome (at least that''s how we do it)
[13:20:17 CDT(-0500)] <drewwills1> there would still be fluid in other page components though
[13:20:38 CDT(-0500)] <drewwills1> i think we'll have to troubleshoot when we get there
[13:21:29 CDT(-0500)] <chris_cousquer> somethimes with etxjs (the last version) the equivalent of jQuery's ready() (Ithink it's onready()) didn't fire
[13:21:55 CDT(-0500)] <chris_cousquer> so for extjs the DOm is never ready...
[13:22:27 CDT(-0500)] <drewwills1> do you think it has some connection with french?
[13:22:34 CDT(-0500)] <chris_cousquer> nope
[13:22:35 CDT(-0500)] <drewwills1> or internationalization?
[13:22:42 CDT(-0500)] <chris_cousquer> it's extjs
[13:22:54 CDT(-0500)] <chris_cousquer> morehover
[13:23:44 CDT(-0500)] <chris_cousquer> extjs implement Microsoft box model by default to firefox chrome & safari
[13:23:55 CDT(-0500)] <chris_cousquer> the crappy one
[13:25:13 CDT(-0500)] <drewwills1> shawn gormly is doing the UX work... i haven't looked too closely at how it uses the DOM, perhaps he has
[13:27:41 CDT(-0500)] <drewwills1> were any of these concerns related to load?
[13:28:04 CDT(-0500)] <chris_cousquer> you can see on the body tag the classe .x-border-box
[13:28:44 CDT(-0500)] <chris_cousquer> it apply box-sizing : border-box
[13:29:02 CDT(-0500)] <chris_cousquer> and then see : https://developer.mozilla.org/en-US/docs/CSS/box-sizing
[13:29:27 CDT(-0500)] <drewwills1> <body id="portal" class="up fl-theme-mist x-body x-webkit x-chrome x-reset">
[13:29:37 CDT(-0500)] <chris_cousquer> yes
[13:29:52 CDT(-0500)] <chris_cousquer> The https://developer.mozilla.org/en-US/docs/CSS/width and https://developer.mozilla.org/en-US/docs/CSS/height properties include the padding and border, but not the margin. This is the https://developer.mozilla.org/en-US/docs/CSS/Box_model used by Internet Explorer when the document is in Quirks mode.
[13:32:08 CDT(-0500)] <chris_cousquer> so it's funny uP reset the css for all browser and after that etxjs put the crappy box model for every one...
[13:35:15 CDT(-0500)] <chris_cousquer> oh no sorry it's ok for you you don't have .x-border-box do-you have pick up the body tag in Internet explorer ?
[13:35:15 CDT(-0500)] <drewwills1> i'm sending these notes to shawn... what's the consequence of the change in box model? I don't see a visual change (afaik), but perhaps by this point it's been skinned to account for that
[13:35:37 CDT(-0500)] <drewwills1> i can check that
[13:35:56 CDT(-0500)] <chris_cousquer> was it in firefox ?
[13:36:40 CDT(-0500)] <drewwills1> that was chrome
[13:36:46 CDT(-0500)] <drewwills1> this is IE: <body id="portal" class="up fl-theme-mist">
[13:37:12 CDT(-0500)] <chris_cousquer> can you test firefox ?
[13:37:21 CDT(-0500)] <drewwills1> that may not be right for IE
[13:38:28 CDT(-0500)] <drewwills1> up fl-theme-mist x-body x-gecko x-reset
[13:38:32 CDT(-0500)] <drewwills1> that's FF
[13:38:44 CDT(-0500)] <chris_cousquer> ok you are ok
[13:39:06 CDT(-0500)] <drewwills1> i'll still point shawn this way
[13:39:59 CDT(-0500)] <chris_cousquer> if you see "box-sizing : border-box" it's very bad
[13:42:42 CDT(-0500)] <chris_cousquer> we've got this in france and it change the layout of other jasig's portlets
[13:44:15 CDT(-0500)] <chris_cousquer> so I remove 95% of etxjs 's css, it's more light for me now 
[13:44:25 CDT(-0500)] <drewwills1> hah! nice
[13:44:51 CDT(-0500)] <chris_cousquer> it damn too heavy for me
[13:45:24 CDT(-0500)] <drewwills1> we are experiencing some load slowness
[13:46:13 CDT(-0500)] <drewwills1> there's an extjs-provided (iirc) facility for minnified builds of your JS, and we've discovered it improves things quite a bit
[13:46:24 CDT(-0500)] <drewwills1> i don't have it turned on yet on my local
[13:47:36 CDT(-0500)] <chris_cousquer> iirc
[13:48:16 CDT(-0500)] <chris_cousquer> good luck
[13:51:58 CDT(-0500)] <chris_cousquer> ext-all.js + all-classes.js = 372KB + 773 KB (minnified)
[13:53:06 CDT(-0500)] <chris_cousquer> jQuery 32KB
[13:53:26 CDT(-0500)] <chris_cousquer> (A)
[14:14:19 CDT(-0500)] <b-cause> hello uPortal devs. we recently went live with 4.0.5 yesterday. earlier today 2 of our 3 nodes started going to the error page. I didn't see anything alarming in the ROOT.log uPortal log or the t-cat localhost.logs. Just interested if others here may have seen something like this on the 4.0.5 build? I did read the release notes for 4.0.6 and didn't see anthing that obvious that relates to this issue.
[14:14:53 CDT(-0500)] <EricDalquist> if the error page is coming up an exception must be getting thrown
[14:15:01 CDT(-0500)] <EricDalquist> it would end up in catalina.out or localhost.log I believe
[14:15:55 CDT(-0500)] <b-cause> yes thats what I thought too. Its just the timestamps in the log files don't match fully with when the error for the user occured. there are exceptions in the logs but they didin't occur at the same timeframe
[14:17:25 CDT(-0500)] <b-cause> I would pastebin some here but it feels like I've seen these traces in our logs for quite a while. also we've been rujnning 4.0.5 in our dev and stage enviornments the whole time its been available.
[14:17:46 CDT(-0500)] <b-cause> where this didn't happen.
[14:19:41 CDT(-0500)] <b-cause> I guess I'm just fishing here to find if this would be something known with the build. All the reports we are getting othewise have been really positive so far. Many are liking the mobile capabilities it provides.
[14:19:59 CDT(-0500)] <EricDalquist> yeah we haven't seen any issues
[14:20:13 CDT(-0500)] <EricDalquist> though we've been on a modified version of 4.0.5 with all the stats work that we did for 4.0.6
[14:20:18 CDT(-0500)] <b-cause> good to know. could very will be something in out environment
[14:21:57 CDT(-0500)] <b-cause> I do want to start back down in 4.0.6 to stay current but can I apply the db updates for 4.0.6 and still run the 4.0.5 build as well?
[14:22:15 CDT(-0500)] <EricDalquist> yes I believe so
[14:22:22 CDT(-0500)] <b-cause> that is good news.
[14:22:40 CDT(-0500)] <EricDalquist> you might get errors from your event processing code in 4.0.5
[14:22:48 CDT(-0500)] <EricDalquist> but it should just fail without breaking anything
[14:22:53 CDT(-0500)] <b-cause> I'll be able to rollback if needed anyway but that would allow us to stat all the more soon
[14:23:33 CDT(-0500)] <b-cause> thanks for all of your hard work on this release EricDalquest athena and company!
[14:24:16 CDT(-0500)] <athena> glad things are working well!
[14:24:33 CDT(-0500)] <athena> so you have users making use of the browser-based mobile stuff now?
[14:25:12 CDT(-0500)] <b-cause> yes athena. we do. we should have a better idea of the stats on that later next week from our google analytics
[14:25:22 CDT(-0500)] <athena> oh that's terrific
[14:25:26 CDT(-0500)] <athena> will be interested to see them 
[14:25:48 CDT(-0500)] <b-cause> yeah. I'm sure someone here can make them avaialbe to you and hopefully the community.
[14:26:30 CDT(-0500)] <athena> awesome
[14:26:35 CDT(-0500)] <athena> still encountering problems w/ shibboleth and the native app?
[14:27:01 CDT(-0500)] <b-cause> we haven't made more progress with that so far.
[14:27:11 CDT(-0500)] <athena> sorry to hear that
[14:27:22 CDT(-0500)] <athena> were you ever able to identify the problem? and is it ios or android or both?
[14:27:36 CDT(-0500)] <b-cause> np. I think maybe in the coming months threre will be more than myself to work on it.
[14:27:46 CDT(-0500)] <b-cause> I think it is both so far.
[14:28:00 CDT(-0500)] <b-cause> I haven't tried the lastest build or the latest titanium sdk.
[14:28:01 CDT(-0500)] <athena> ah
[14:28:12 CDT(-0500)] <athena> you're using the jasig custom sdk though, right?
[14:28:12 CDT(-0500)] <b-cause> hopefully I'll have the opportunity soon.
[14:28:59 CDT(-0500)] <b-cause> yes I think we are using the custom sdk but we may have tried the lastest past couple of weeks as well. there is another person in my group who could have tried this.
[14:29:24 CDT(-0500)] <athena> i definitely wouldn't expect it to work w/o the jasig customizations
[14:30:08 CDT(-0500)] <b-cause> ok thanks athena for the info. I'll let the develper working on this know he should still use the jasig customizations.
[14:30:34 CDT(-0500)] <athena> you might try building the latest jasig branch though
[14:30:40 CDT(-0500)] <b-cause> ok
[14:30:47 CDT(-0500)] <athena> think there have been some changes since the last posted version
[14:30:55 CDT(-0500)] <b-cause> great.
[14:31:08 CDT(-0500)] <athena> any idea whether the issue is titanium or the ECP integration?
[14:35:14 CDT(-0500)] <b-cause> I think the issue is in titanium or somewhere in the jasig customizations b/c I can run the emulator in the iphone debugger and see that the ECP authentication took place successfully and the see the authenticated content. but it drops out if I run the emulator in full play mode
[14:35:41 CDT(-0500)] <b-cause> I don't remember off hand if I got that far on android.
[14:36:46 CDT(-0500)] <b-cause> as soon as we get past the start of school year season, I hope to spend some more time debugging with you and your team.
[14:37:58 CDT(-0500)] <athena> gotcha
[14:38:11 CDT(-0500)] <chris_cousquer> athena: jasig titanium_mobile is 1_8_X and appcelerator is now 2_1_X
[14:38:11 CDT(-0500)] <athena> or maybe we could also try testing out the phonegap version
[14:44:39 CDT(-0500)] <chris_cousquer> athena: I'm finishing skinning uP (desktop & mobile) for next 10 days and I will be quite full time on bakbone, phonegap & or titanium at the beginning of september :-D
[14:46:11 CDT(-0500)] <athena> oh terrific!
[14:49:21 CDT(-0500)] <chris_cousquer> if I have understood some university are running mobile app of uMobile for iphone in production ?
[14:49:44 CDT(-0500)] <athena> oakland is now, yes!
[14:49:54 CDT(-0500)] <athena> available in the app store
[14:49:58 CDT(-0500)] <chris_cousquer> cool