[IxDA Discuss] Returned mail: Data format error

2008-09-06 Thread dave
Your message was undeliverable due to the following reason:

Your message could not be delivered because the destination computer was
unreachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

Your message was not delivered within 8 days:
Mail server 98.150.226.58 is not responding.

The following recipients could not receive this message:
discuss@lists.interactiondesigners.com

Please reply to [EMAIL PROTECTED]
if you feel this message to be in error.


Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help

Re: [IxDA Discuss] Returned mail: Data format error

2008-09-06 Thread Konrad
Hi All,

I'm hoping you could advice me on some prototyping tools for
websites and potentially mobile devices?

I'm wondering about:
- intuitiveness of a tool's interface
- complexity of UI that can be achieved
- the quality of auto-generated code

Perhaps I missed an important factor that should be considered?

Best,
Konrad


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=32712



Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


[IxDA Discuss] [event] 90 Mobiles in 90 Days Celebration

2008-09-06 Thread k lenox
My friend and colleague, Rachel Hinman, started on a personal  
creative challenge about 3 months ago to explore mobile design  
concepts - 1 idea a day! It's been an amazing creative journey for  
her! I have so much respect and admiration for her dedication and the  
amazing ideas she's generated and shared with the world - check out  
her blog: http://90mobilesin90days.com/index/


In honor of her completing the 90th day, we are hosting a party at  
the Adaptive Path San Francisco office on Weds September 17th.


Come celebrate with us!

Please RSVP on upcoming: http://upcoming.yahoo.com/event/1077637

Hope to see you there!

Wednesday September 17, 2008 from 6:30pm - 8:30pm
Adaptive Path
363 Brannan Street
San Francisco, California 94107

Here are some additional links to learn more about the project and  
Rachel:
http://www.adaptivepath.com/blog/2008/06/20/creative-recovery-90- 
mobiles-in-90-days/

http://90mobilesin90days.com/index/?page_id=51

Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] Disability Discrimination Act and AJAX

2008-09-06 Thread Caroline Jarrett
From Mike Zarro
 
 Nicholas makes a great point. The best (and only?) way to ensure
 accessibility is to test with users who make use of assistive
 technologies
 (not just screen readers).

It is essential to take this a step further:

The best (and only?) way to ensure accessibility is to test with users who
have disabilities.

Reason: lots of people with disabilities (the majority, even?) don't have
any assistive technologies. 

Example: the very large numbers of people with age-related eyesight
problems.

Example: the people with cognitive disabilities. There are very few
assistive technologies that will help with text that's too difficult to
understand. Possibly none. 

And it's also important to understand that people with disabilities who use
assistive technologies may use those technologies in a different way to
people without disabilities who use them. Example: many people with
disabilities who use a screen reader 'speed hear' in a way that the casual
user of a screen reader wouldn't be able to emulate. 

Longer article on the topic of working with assistive technologies as a
non-disabled person:
http://www.usabilitynews.com/news/article1773.asp

best
Caroline


Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


[IxDA Discuss] RE : Re: Firefly

2008-09-06 Thread Alain
Don't buy the Firefly DVDs if you like the kind of science fiction
that's based on at least a minimum of science ideas or a minimum of
technology ideas.  Firefly makes no pretense and I mean absolutely no
pretense of having some kind of grounding in the idea-driven SF
classics, the kind written by Asimov, Clarke or Heinlein, or by any
author who got printed by Astounding/Analog or Galaxy.

A friend of mine recommended the series, and there were rave reviews
all over the Web.  I bought all of the DVDs based on those
recomendations.  I watcehd each eapisode, with no distractions, so I
know what I'm talking about.

And yeah, it's also rotten if you're interested in the way SF portrays
interfaces of the future.

Alain

 Me too - I was going to say - definitely purchase it - one of the
 best shows
 of the last 10 years. Well worth the price of the dvds.
 



  Offrez un compte Flickr Pro à vos amis et à votre famille.
http://www.flickr.com/gift/

Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] A New Browser: Google Chrome

2008-09-06 Thread Håkan Reis
Regarding the security issues:

One major difference between Browser resident apps and Air and JavaApps are
 the security parameters. Since it is installed it falls under that part of
 the controlled OS which can be blocked by Administrators, so the sandbox
 that Flash traditionally has for example is not really found (or
 externalized) in AIR apps (basically the same technology).


While you discuss the various securities for the apps in the browser a
colleague and I discovered a quite critical security issue with Chrome as a
windows application:

Chrome do not install itself in the OS application area x:\Program Files it
installs in the users local account area.
On WIndows XP there is not any immediate difference around this, security
wise. But it makes room for a huge security hole in Vista. The user area is
fully writable and any application might write to this area (even
malicious).

If the application would reside in x:\Program Files (as it should) UAC would
kick in an save the user. For more information check:

blog.reis.sehttp://blog.reis.se/2008/09/05/GoogleChromeCriticalSecurityIssues.aspxand
techie
notpadhttp://blog.noop.se/archive/2008/09/05/google-chrome-plays-outside-of-vista-security-zones.aspxaround
this issue and also what Chrome
leaves 
behindhttp://myitforum.com/cs2/blogs/rtrent/archive/2008/09/03/here-s-what-chrome-s-uninstall-leaves-behind.aspx
.

So we have an app that can update what ever it wants without noticing you
and even if you remove it it will leave the updater behind.

---

Håkan Reis
Dotway AB
+46(768)510033

My blog || http://blog.reis.se
My company || http://dotway.se
Our conference || http://oredev.org - See you in 2008

Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


[IxDA Discuss] Interview with Google Chrome Team

2008-09-06 Thread Jared Spool
For anyone interested in trying to revive the IxDA dead horse called  
Google Chrome, Steve Gillmor had an excellent interview with the  
product manager and UI developer. Lots of things we discussed here  
were talked about in the interview, confirming my thinking on where  
they are going.


Gillmor's synopsis: http://tinyurl.com/5bv645
The audio of the interview: http://tinyurl.com/64bcbz

Jared

Jared M. Spool
User Interface Engineering
510 Turnpike St., Suite 102, North Andover, MA 01845
e: [EMAIL PROTECTED] p: +1 978 327 5561
http://uie.com  Blog: http://uie.com/brainsparks


Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] Interview with Google Chrome Team

2008-09-06 Thread Andrei Herasimchuk

On Sep 6, 2008, at 4:59 PM, Jared Spool wrote:

For anyone interested in trying to revive the IxDA dead horse called  
Google Chrome, Steve Gillmor had an excellent interview with the  
product manager and UI developer. Lots of things we discussed here  
were talked about in the interview, confirming my thinking on where  
they are going.


They keep saying they want people to make cool web apps, but that they  
are still going to operate fundamentally as Web Browser #4, they'll be  
OpenSource and they'll follow web standards. I have to believe they  
are being honest. Nothing tells me they are trying to be devious here.


So... The only way I think they can begin to believe that premise is  
that they also believe that an SDI application model is sufficient for  
everything that can be considered a web application. That Google  
Docs, Spreadsheet, Maps, and a whole host of certain kind of apps can  
be sustained in single window interfaces and be completely self- 
contained.


That's where the breakdown occurs for me. Web apps currently work in  
an SDI mode, and a fairly limited SDI mode at that. You can't take  
over the keyboard interaction, you can't make floating palettes or  
slave windows that are aware of each other to pass data via a common  
pipe, and you can't do other things like use OS alerts, OS dialogs,  
etc. And web apps in that SDI model have to worry abut the address  
bar, the back button, and other browsing interactions resident  
inside a web browser that have nothing to do with more tool oriented  
application interactions.


Given all of that, they are basically building Browser #4, and all  
innovation will stop there, or at least innovation done there will be  
done across the browsers, and nothing will be done for Chrome  
specifically. Their route is certainly legit (even Photoshop Lightroom  
works largely in an SDI conceptual model so that type of interface  
approach can certainly do a lot if the task at hand is reasonably  
specific), but in going this route, it will be clear that the RIA+  
route of AIR will be very different, as the RIA+ route will head back  
towards more fully fleshed out little desktop applications.


Who will win? Not sure I care. I don't pick sides in these sorts of  
things. I just design what I have to for whatever I'm asked to do it  
for.


But there is a big difference between Chrome being Browser #4 and  
Chrome being a new application platform that happens to use OpenSource  
web technologies but plans on making a clean break from being a  
browser. As I'm sure you might have guessed... I wish they'd do the  
latter.


If they did, we'd have a lot of choices going forward to make  
software: traditional web browser for more service like applications,  
richer web application platforms for more robust tool-like apps, RIA+  
using proprietary tech for even more complex tool-like apps, and good  
old traditional desktop application built right on the OS itself to do  
whatever the heck you want.


But Chrome in its current trajectory is clearly not going to help me  
with what we design anytime soon, as being Browser #4 will only mean  
for me that things will largely be faster. It won't solve the problems  
of trying to build multi-window, rich interaction based web  
applications that just happen to use a lot of web technologies at its  
base instead of a proprietary technology like Flex, et al. Ah well.


--
Andrei Herasimchuk

Principal, Involution Studios
innovating the digital world

e. [EMAIL PROTECTED]
c. +1 408 306 6422

Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] Why are password fields asterisked on join-up forms?

2008-09-06 Thread dawa riley
On Thu, Sep 4, 2008 at 9:15 AM, Guillermo Ermel 
[EMAIL PROTECTED] wrote:

In Palm OS, when you type a password, each letter you type remains on the
screen for a moment, and THEN becomes an asterisk. That way, you get
feedback on what you just typed, which makes it unnecesary to type it twice
in two different input fields

The same thing happens in password fields on the iphone and I remember
thinking ..what a super useful feature!



  1.  Nick Gassman - Wednesday, 1:07pm

 When you fill in a form to sign up to a website, the password field,
 but not the username, is usually asterisked. Is it to avoid the risk
 of someone peering over your shoulder?


 Yes. But I've come across a better solution to the asterisk+double input
 field pattern.
 It will not work in web browsers, but I think it adds up to this
 discussion. In Palm OS, when you type a password, each letter you type
 remains on the screen for a moment, and THEN becomes an asterisk. That way,
 you get feedback on what you just typed, which makes it unnecesary to type
 it twice in two different input fields.

 Please note that usage context IS different, since it is easier to hide the
 palm device from peeking eyes while entering the password, but it's not that
 easy to do so with a big 17 computer display sitting on your desk.

 And sometimes when they aren't asterisked, you have to type the
 password in twice, but not the username. What's the rationale for
 that?


 That's just a plain mistake :-)
 Users CAN read it, so they don't need it twice.


 Guillermo

 --
 Guillermo Ermel
 Responsable de usabilidad
 MercadoLibre.com
 
 Welcome to the Interaction Design Association (IxDA)!
 To post to this list ... [EMAIL PROTECTED]
 Unsubscribe  http://www.ixda.org/unsubscribe
 List Guidelines  http://www.ixda.org/guidelines
 List Help .. http://www.ixda.org/help


Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] 37 Signals Change Management for IE6 Phase Out

2008-09-06 Thread Andrew Jaswa
Being a web developer I think this is a very good thing. IE6 is old
(~7 years?) and broken in a lot of ways. While it might not be the
best way to go about announcing discontinued support for IE6, it is
progress in the right direction. Think if we still had to support NS4
or IE4 (*ducks* I'm sure someone out there still has to. Sorry.)? I've
been waiting for announcements like this for a while now.

If 37signals has the data to back up their decision I don't see this
as a problem. I'm sure they have been looking at their webstats and
have found that IE6 users have been dropping off left and right. I
figure they found the magic number at which to stop support.

The web is about change. When was the last time you used a piece of
software for 7 years without upgrading?

Andrew Jaswa

On Fri, Sep 5, 2008 at 8:54 AM, Nasir Barday [EMAIL PROTECTED] wrote:
 37 Signals decided to pick August 15th, no wait, October 1st, as the day
 when they would phase out IE6:
 http://37signals.blogs.com/products/2008/07/basecamp-phasin.html

 They must have been barraged with e-mails from angry users (probably already
 angry at Basecamp's extraterrestrial interface ...), because they posted a
 clarification:
 http://37signals.blogs.com/products/2008/09/further-clarifi.html

 Whoops, phase-out? Probably a stronger phrase than they intended. And
 nothing is going to happen on that day-- no features that are compatible
 only with the latest browsers, nothing to break current functionality-- so
 why make an announcement like this? With no concrete incentive to upgrade,
 the decision for the user to upgrade is arbitrary, and most people will put
 it off until it actually matters. This announcement strikes me as premature.

 Maybe I'm just being whiny on a Friday morning ...

 Happy Friday,
 - Nasir
 
 Welcome to the Interaction Design Association (IxDA)!
 To post to this list ... [EMAIL PROTECTED]
 Unsubscribe  http://www.ixda.org/unsubscribe
 List Guidelines  http://www.ixda.org/guidelines
 List Help .. http://www.ixda.org/help




-- 
Andrew Jaswa
andrewjaswa.com
wsuug.org

Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] A New Browser: Google Chrome

2008-09-06 Thread Luiz Ricardo Grzeca
Hi Dave,

Imho is a matter of expectation.
I`m not a big user of AIR apps, but those that I tested delivered a slightly 
different experience than a regular webpage app. Some of the UI elements (note 
that AIR`s default color is black/dark grey, instead of a plain white - empty - 
page), the apps flow, plus their size (in bytes) makes them fill more like an 
installed application that turns to be connected to some web resource. Add the 
possibility to control hardware, local file system access, network detection 
and the other features and you`ll start to feel like using a desktop, but 
connected, app, thus, expecting a desktop behavior, while with prism, and maybe 
chrome (I`m a mac user, so i haven`t tested it yet) you still expects a webapp 
behavior.

wyt?

Ricardo


Date: Fri, 5 Sep 2008 06:59:37 -0400
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [IxDA Discuss] A New Browser: Google Chrome
CC: [EMAIL PROTECTED]; [EMAIL PROTECTED]

Hi Luiz, I see your point and feel similarly.But then why does AIR work? Its 
not a rhetorical question, BTW. I mean from an IxD perspective isn't AIR just 
the same thing, except running HTML it is running Flash, which for all intent 
and purposes really just an web-app?

-- dave




_
Conheça o Windows Live Spaces, a rede de relacionamentos do Messenger!
http://www.amigosdomessenger.com.br/

Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] Chrome Comic Parodies

2008-09-06 Thread Mark Hurd
This is my favorite:
http://www.theregister.co.uk/2008/09/02/google_chrome_comic_funnies/

Buy more blue paint!


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=32666



Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] Hyperbolic Trees

2008-09-06 Thread Larry Buck
InXight (a Xerox Parc spinoff that was later acquired by Business
Objects(BO)) has had a product out there for a long time (I believe
it predates Thinkmap and the sourceforge efforts). 

They called it StarTree. It was very nice but the license was
expensive (more than $15K back in 2002-ish); don't know what BO
charges for it now.


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=32709



Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] Returned mail: Data format error

2008-09-06 Thread Lawrence Agbayani
Konrad,

I think your best bet is Dreamweaver CS3. The interface is good. It
also includes the Adobe's Ajax framework, Spry, so you can acheive
some fairly complex UI prototypes. The ajax and html code also isn't
bad for small to midisize sites and you probably do not want to use
the code for enterprise level sites.

If you never have used the tool, Adobe has some great tutorials on
their site. 

Hope this helps and what you were looking for.




. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=32712



Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


[IxDA Discuss] Fonts and paper prototyping

2008-09-06 Thread Janna
A colleague and I had an interesting discussion yesterday and I was
wondering if anyone on this list has relevant experience to share or has
seen publications on this topic.

We are creating paper prototypes for a change in software. We want to keep
them sketchy looking for obvious reasons.

My colleague felt we should use a font such as chalkboard or comic sans to
keep the loose and sketchy feeling and won't look like a finished interface.
My response is to use something like Arial or Myriad since it no longer has
any particular connotations and people won't have any reaction to it
positively or negatively.

Any experience with this or thoughts on the subject? Thanks!

-- 
Janna C. Kimel, JK Consulting
Career: Design Research/User Experience
Volunteer:  Co Vice-Chair OR-IDSA
Blogging: http://seenheardnoticed.blogspot.com/
Motto: Be the change you want to see in the world. -Gandhi

Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] Hyperbolic Trees

2008-09-06 Thread Itamar Medeiros
If you're just trying to graph data (network in particular) in
different visualization styles, you could try yFILES:
 
http://www.yworks.com/en/index.html

{ Itamar Medeiros } Information Designer
  designing clear, understandable communication by
  caring to structure, context, and presentation
  of data and information

  mobile :::  86 13671503252
  website ::: http://designative.info/
  aim ::: itamarlmedeiros
  skype ::: designative


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=32709



Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] Interview with Google Chrome Team

2008-09-06 Thread Jared Spool


On Sep 6, 2008, at 9:33 PM, Andrei Herasimchuk wrote:

That's where the breakdown occurs for me. Web apps currently work in  
an SDI mode, and a fairly limited SDI mode at that. You can't take  
over the keyboard interaction, you can't make floating palettes or  
slave windows that are aware of each other to pass data via a common  
pipe, and you can't do other things like use OS alerts, OS dialogs,  
etc. And web apps in that SDI model have to worry abut the address  
bar, the back button, and other browsing interactions resident  
inside a web browser that have nothing to do with more tool oriented  
application interactions.


Yah, yah, yah.

However...

First: Gears could do those things and does some of them already. One  
of the things from the interview I found interesting was that Chrome  
is optimized for Gears, but Gears is also a middle-ware package for  
the other browsers. I think that's a fascinating strategy to make  
things work.


Second: I'm betting that somewhere between 65% and 80% of the  
applications that are built today *could* operate in an SDI model.  
Granted, it's nice to have floating windows, but apps with those types  
of interaction modalities are fairly advanced. UPS, for example,  
doesn't need that kind of interaction model for their WorldShip app,  
which is sophisticated in functionality, but straight forward in terms  
of the demand on UI modalities. Even something as sophisticated as  
Salesforce can get away with an SDI model for 90% of what people try  
to do with it. (And Flash/Flex/AIR can provide the rest.)


Not everyone builds a sophisticated tool for manipulating artwork.  
Many just build tools for manipulating customer data.


But there is a big difference between Chrome being Browser #4 and  
Chrome being a new application platform that happens to use  
OpenSource web technologies but plans on making a clean break from  
being a browser. As I'm sure you might have guessed... I wish they'd  
do the latter.


There's a third possibility, which is what I heard in the interview:  
Chrome is a stimulus for a competitive response by the other big  
browser producers. It came out that Sergei Brin/Google would consider  
Chrome a success if MS IE9 adopted the core components from the Chrome  
open source set.


I think that's really where I think this is heading and why I'm  
excited about it.


Jared

Jared M. Spool
User Interface Engineering
510 Turnpike St., Suite 102, North Andover, MA 01845
e: [EMAIL PROTECTED] p: +1 978 327 5561
http://uie.com  Blog: http://uie.com/brainsparks


Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] Interview with Google Chrome Team

2008-09-06 Thread Andrei Herasimchuk

On Sep 6, 2008, at 6:59 PM, Jared Spool wrote:

Not everyone builds a sophisticated tool for manipulating artwork.  
Many just build tools for manipulating customer data.


Agreed. Like I said... Photoshop Lightroom is largely an SDI model  
type of application, and it's pretty intense with the rich interaction  
model it follows inside the confines of SDI. If you haven't used it,  
go grab the 30 day trial download to see what I mean.


But there are plenty of examples that aren't. Some light, some heavy.

Instant Messenger applications are relatively light apps that work a  
ton better outside the SDI confines. The WebSketch product example  
would as well. Many industrial strength enterprise apps would benefit  
immensely from being web technology based but built outside the SDI  
confines.


We also helped design an enterprise application for Agile Software  
(who were acquired by Oracle last year), which is a prime example of  
something that needed a multiple window environment. The application  
was a document management and project workflow product where you had  
to track thousands of parts that go into building physical products.  
We ended up having to do a lot of custom work to make it happen so  
windows could talk to each other).


There a ton of enterprise level applications that are quite simply  
*begging* for such an development environment.


There's a third possibility, which is what I heard in the interview:  
Chrome is a stimulus for a competitive response by the other big  
browser producers. It came out that Sergei Brin/Google would  
consider Chrome a success if MS IE9 adopted the core components from  
the Chrome open source set.


I heard that too... but that doesn't change the browser paradigm, it  
only really makes it more robust at the tech level, which helps it  
somewhat at the interaction level, but not in the core mode it  
operates. In other words, an intense, interaction rich product like  
Lightroom could someday be built in that new platform with that more  
robust engine, but in the end, it's *still* SDI.


--
Andrei Herasimchuk

Principal, Involution Studios
innovating the digital world

e. [EMAIL PROTECTED]
c. +1 408 306 6422


Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] Disability Discrimination Act and AJAX

2008-09-06 Thread Jeff Seager
Great article, Caroline! Thanks for that. I work with a guy who
teaches people with low vision and blindness to use those assistive
technologies, and I lean on him for that kind of insight. But I
don't recall ever reading it anywhere, and I have looked! I
regularly consult resources published by the RNIB, AFB, WebAIM and
others, because accessibility is a high priority for me.

Anyway, I think more people would make an effort to think and code
accessibly if they could gain some small measure of the understanding
you have. Please keep it up!


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=32646



Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help


Re: [IxDA Discuss] Interview with Google Chrome Team

2008-09-06 Thread Jared Spool

On Sep 6, 2008, at 8:41 PM, Daniel Szuc wrote:


What if Chrome was simply a stepping stone towards a Google OS?

What if some of the principles in the Google apps to date suggest not
having to rely on the need for deeper functions?

One trend is to be able to serve up applications that have a few key
simple functions that people use more regularly with the ability to
switch on more features as needed.


What's interesting about the interview is that the product manager  
said that the reason there is no Mac or Linux version yet is that  
they've optimized the existing beta heavily to Windows.


He also said that Android, which *is* a Google OS, isn't using Chrome  
for the same reason. They are using the same rendering engine, WebKit,  
but have different UIs and components because their OS environment is  
very different.


I thought that was very interesting and telling about Google's view.

Jared



Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscribe  http://www.ixda.org/unsubscribe
List Guidelines  http://www.ixda.org/guidelines
List Help .. http://www.ixda.org/help