If there is anything we can start documenting (i.e. how to get your
tool to work without iframes) in the cafe docs or changes we need to
make in the framework (seems unlikely, this should mostly be
tools/portals) then let me know and I will help where I can.

I really want to see the iframe become optional.
 :-)
-AZ


On 9/25/07, May, Megan M <mmmay@indiana.edu> wrote:
> > Mike,
> > Sounds like a great idea and if Chuck gets the resources, seems like a
> > good way to be proactive rather than reactive. It's been very
> > frustrating "chasing" the tools.
> >
> > Megan
> >
> > -----Original Message-----
> > From: antranig@caret.cam.ac.uk [mailto:antranig@caret.cam.ac.uk]
> > Sent: Monday, September 24, 2007 11:31 AM
> > To: Charles Severance
> > Cc: Michael S Elledge; May, Megan M; Londergan, M D; Colin Clark;
> > aaronz@vt.edu
> > Subject: Re: New Portal-based, iFrameless Sakai Opportunity
> >
> > Yes, this sounds like a great initiative. My earlier point was simply
> > that Chuck's work, as well as being directly useful for the PDA portal
> > itself, is also an excellent opportunity to "shake the wheels off"
> > tools throughout Sakai to see what might fall off in such a "rebased"
> > dispatching environment. Whatever tools cannot run correctly and
> > usably in Chuck's portal certainly will not survive transition to a
> > "full" frameless portal - and this is a great opportunity to get
> > a graduated QA done across the board using this environment as a
> > readily accessible "stepping stone". As I understand it the PDA
> > dispatcher is enabled by default in 2.5.
> > After the 2.5 release would seem to me a great time to devote cycles
> > to this.
> >
> > Cheers,
> > A.
> >
> >
> > Quoting Charles Severance <csev@umich.edu>:
> >
>> > > This sounds great. I have a smaller, simpler suggestion - I would
>> > > like to make the PDA portal *sparkle* w.r.t screen readers.
>> > >
>> > > The PDA portal markup is REALLY simple and is easily modified. I am
>> > > guessing that 1-2 days with a programmer, a CSS expert, and an
>> > > accessiblity experrt - we cold have a stellar UI for assistive folks.
>> > >
>> > > After that the imperfections of tools will become even more obvious
>> > > and then we can move down. This way our first impression is
>> > > outstanding. We could embed a link on Charon to point folks to /
>> > > portal/pda - to make it really work smoothly.
>> > >
>> > > I cannot do this alone - I am only 10% of the talent needed to do
> > this.
>> > >
>> > > Charles Severance
>> > > csev@umich.edu www.dr-chuck.com
>> > >
>> > >
>> > >
>> > > On Sep 24, 2007, at 11:11 AM, Michael S Elledge wrote:
>> > >
>>> > > > Hi Megan--
>>> > > >
>>> > > > I wanted to float an idea for the post 2.5 release period when we
>>> > > > have traditionally (well, since 2.4 :-) ) reviewed Sakai
>>> > > > accessibility. As part of that effort (perhaps the focus of it, now
>>> > > > that we've reviewed essentially all the tools, samigo and gradebook
>>> > > > notwithstanding) I wonder if we shouldn't take a thorough review of
>>> > > > how the core tools behave in Chuck's new environment.
>>> > > >
>>> > > > This is a great opportunity for moving beyond frames in Sakai,
>>> > > > which would be a big usability and accessibility win.
>>> > > >
>>> > > > Antranig and Chuck, you may want to add your thoughts about what is
>>> > > > necessary for the transition to take place from a technical
>>> > > > viewpoint; my understanding is that it's not that great a leap,
>>> > > > which would make this a reasonable thing to consider.
>>> > > >
>>> > > > Thoughts?
>>> > > >
>>> > > > Mike

I updated this to a task as this is planned work for the next release