headers
Craig Duncan | 1 Aug 2003 01:12
Picon
Favicon

[Sigia-l] Craig Duncan is out of the office.

I will be out of the office starting  23/07/2003 and will not return until
04/08/2003.

Please send any urgent Email to vigneau <at> un.org

------------
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable list archive:   http://www.info-arch.org/lists/sigia-l/
________________________________________
Sigia-l mailing list -- post to: Sigia-l <at> asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
Permalink | Reply | 0 comments |
headers
Listera | 1 Aug 2003 02:28
Favicon

Re: [Sigia-l] Going from Windows GUI to Browser-Based GUI

"David Heller" wrote:

> if you can do all IE, then I suggest looking at convea.com

I'm trying to stay out of this topic, but...

This makes me wonder, if you are willing to restrict yourself to IE5/6 then
why bother converting from a Windows-only desktop app to Windows-only web
app in the first place?

Given one's ability with a standalone or a C/S app to a) embed an HTML
rendering engine, b) emulate a browser UI, if one needs/has to, c)
communicate with web servers via HTTP and d) do very light-weight
integration via web services, why bother with the web browser at all?

For those who have missed the "let's port to the web" bandwagon during the
dotcom era, that, in fact, is precisely what Microsoft wants you to do now:
it won't upgrade IE6 as a standalone browser any longer and any significant
enhancements will require people to buy the next Windows version, Longhorn.

This is partly to get everyone to buy another Windows upgrade, you'll have
no other choice, and partly to buy into the .NET/web services paradigm where
platform-specific desktop apps (where Microsoft is strong) reign supreme
once again.

So, unless the objective is to convert Windows-only apps to more ecumenical
ones, people ought to (re)consider why they need to port their standalone,
C/S apps to browser-based ones. Even then, the issue is far deeper than the
UI, if the atrocious record of Windows-only development shops in creating
web apps that work anywhere but IE/Win is any indication.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Dr. Marios Pittas | 1 Aug 2003 03:47

RE: [Sigia-l] List order

Joe I understand more of the problem now.. A couple more questions though:

1. What environment are you using? (i.e. need to understand if there are any
technological constraints, and "imagine some" user expectations i.e. app vs
web)
2. How is the current list sorted (is it the case that due to NDA you cannot
let us know)?
3. How many items are there and how many items do you expect to place in the
near future?
4. I understand that the list includes divisions, cities, countries, company
names.. is that correct, is there anything else? Is there any expecific
numbers/ratios?
5. What are the most commonly selected items by the users (e.g. users most
frequently select countries)?

Marios

-----Original Message-----
From: sigia-l-admin <at> asis.org [mailto:sigia-l-admin <at> asis.org]On Behalf Of
joe
Sent: Friday, August 01, 2003 1:08 AM
To: Stewart Dean; sigia-l <at> asis.org
Subject: Re: [Sigia-l] List order

A few things:
* The list is a list that users use to indicate what group THEY belong to.
It's not a search interface.
* I'm not allowed to ask the users. A political thing. Just the way it is.
* The list will include something like this (can't do the real list due to
NDA-like paranoia):
(Continue reading)

Permalink | Reply | 0 comments |
headers
Victor Lombardi | 1 Aug 2003 04:13
Picon
Favicon

[Sigia-l] RE: Beyond Chargeback: Accountable Consulting

Alex wrote:
A better model may be "internal taxation." ...In
this model, core functions are funded by an annual
levy exacted on each
business unit, based on a formula involving revenue,
utilization of
services, etc.
===
I've also seen the "internal taxation" model work
fairly well. But in general I've found the funding
model doesn't matter as much as 1)skills and
2)personal relationships/politics when deciding
whether to utilize internal design groups.

Victor

=====
Victor Lombardi
http://www.noisebetweenstations.com

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
------------
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable list archive:   http://www.info-arch.org/lists/sigia-l/
________________________________________
(Continue reading)

Permalink | Reply | 0 comments |
headers
Eric Scheid | 1 Aug 2003 04:50
Picon

Re: [Sigia-l] Going from Windows GUI to Browser-Based GUI

On 1/8/03 10:28 AM, "Listera" <listera <at> rcn.com> wrote:

> This makes me wonder, if you are willing to restrict yourself to IE5/6 then
> why bother converting from a Windows-only desktop app to Windows-only web
> app in the first place?

Gets rid of the "distributing and installing software" problem, a major
hassle in corporates, as is "supporting multiple versions of clients
concurrently". It's not all about the users.

e.

------------
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable list archive:   http://www.info-arch.org/lists/sigia-l/
________________________________________
Sigia-l mailing list -- post to: Sigia-l <at> asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
Permalink | Reply | 3 comments |
headers
Listera | 1 Aug 2003 05:22
Favicon

Re: [Sigia-l] Going from Windows GUI to Browser-Based GUI

"Eric Scheid" wrote:

>> This makes me wonder, if you are willing to restrict yourself to IE5/6 then
>> why bother converting from a Windows-only desktop app to Windows-only web
>> app in the first place?
> 
> Gets rid of the "distributing and installing software" problem, a major
> hassle in corporates, as is "supporting multiple versions of clients
> concurrently". It's not all about the users.

Not really. Whether via HTML/HTTP or FTP, the Internet remains the best
medium for distribution. You could make your app extremely easy to install,
practically drag&drop. "Multiple versions" is a red herring, as virtually
any app you use these days has a Prefs setting for auto-checking for
updates; smart client/server or Java software can detect and update
themselves automatically every time they launch. We *are* in the 21st
century, but I don't know about down under. :-)

Look, I'd love to have the web browser as the ultimate runtime client with a
rich GUI that you didn't have to distribute/install, but it ain't the case
*and* the vendor that has the monopoly says it's abandoning the notion of a
standalone browser altogether. I just can't imagine IE, as an embedded part
of Longhorn, becoming more independent, universal, accessible, standards
compliant, etc. I think the opposite is in store. So you do the math.

For web apps, I'm hoping that Macromedia's Royale will materialize soon and
someone will publish an independent study indicating that corporations are
open to the idea of using the Flash client (which apparently has higher
universal penetration rate than even IE) for sizeable web apps.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Eric Scheid | 1 Aug 2003 05:54
Picon

Re: [Sigia-l] Going from Windows GUI to Browser-Based GUI

On 1/8/03 1:22 PM, "Listera" <listera <at> rcn.com> wrote:

> You could make your app extremely easy to install, practically drag&drop.
> "Multiple versions" is a red herring, as virtually any app you use these days
> has a Prefs setting for auto-checking for updates;
> 

Multiple versions may still be required if there is no consistent OS version
in place, or if other apps installed by some departments have installed
different versions of DLLs and other screw-ups occur. Multiply the factors
together, and the resulting exponentiating combinations makes "extremely
easy to install" not so true.

> the Flash client (which apparently has higher universal penetration rate than
> even IE)
> 
not the most recent version though ... maybe macromedia also hasn't heard of
"auto version checking" ;-)

e.

------------
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable list archive:   http://www.info-arch.org/lists/sigia-l/
________________________________________
Sigia-l mailing list -- post to: Sigia-l <at> asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
(Continue reading)

Permalink | Reply | 1 comment |
headers
Listera | 1 Aug 2003 06:13
Favicon

Re: [Sigia-l] Going from Windows GUI to Browser-Based GUI

"Eric Scheid" wrote:

> Multiple versions may still be required if there is no consistent OS version
> in place... 

Yes, but corporations usually synchronize OS upgrades. In any case, this
problem is not substantially different from having different versions of the
same web browser. Like I said, smart client/server apps can detect version
diffs and automatically download and configure at launch time, before the
user even sees the splash screen, a process that can be easier to handle for
an average user than a browser upgrade on the spot.

> Multiply the factors together, and the resulting exponentiating combinations
> makes "extremely easy to install" not so true.

OK, I'm scared. :-)

Ziya
Nullius in Verba 

------------
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable list archive:   http://www.info-arch.org/lists/sigia-l/
________________________________________
Sigia-l mailing list -- post to: Sigia-l <at> asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
(Continue reading)

Permalink | Reply | 0 comments |
headers
Vanessa Wolfe-Coote | 1 Aug 2003 12:07
Picon

RE: [Sigia-l] Going from Windows GUI to Browser-Based GUI

I was faced with this challenge last year at a client who had moments of
conservatism balanced with moments of technophilia, the result of which
was splitting an integrated enterprise application into two modules: one
fronted by a Windows-GUI and another browser-based.

I worked with a core group of 15 users and another 25 users on an ad hoc
basis. I used low and high-fidelity prototypes, did much card-sorting,
interviews, thinking aloud, etc. 

With these particular users, the solution was to:
* Minimise the amount of overlap in use of the 2 interfaces (i.e. for
the user to complete a task, they should not have to use both systems)
* Not try to create a smooth transition in look and feel between the two
interfaces - this did not improve user satisfaction or effectiveness 
* Enure consistency in labelling - this was critical to ensure a high
degree of learnability

Cheers
Vanessa

Vanessa Wolfe-Coote
Information Architect
National Patient Safety Agency (NPSA)
4-8 Maple Street, London, W1T 5HD
Direct Line: +44 20 7927 9880
Fax: +44 20 7927 9501 
Mobile: +44 7968 781 340 
Email: vanessa.wolfecoote <at> npsa.nhs.uk 

------------
(Continue reading)

Permalink | Reply | 1 comment |
headers
David Heller | 1 Aug 2003 20:12
Picon
Favicon

[Sigia-l] Lead UI Designer (Documentum: Oakland/E. Bay, CA)

(please respond to the contact information below; replies to me will be
ignored. If you have applied for this or similar position in the last 2
months there is no reason to resend your resume again.)

JOB ANNOUNCEMENT:
Position: Lead User Interface Designer
Location: Pleasanton, CA (The East Bay area of the San Francisco Bay Area)

Documentum: The leader in enterprise content management is searching for a
lead user interface designer. Documentum develops software and solutions for
the Global 2000.

We are looking for someone to join our User Experience Group as a lead user
interface designer. The position's role is to produce innovative, visually
appealing human interface designs; develop design prototypes; planning and
conducting usability testing; work with engineers to make designs a reality.
We are looking for someone who can work independently, engage team members,
communicate ideas to gain team understanding, and finally work with team
members through release of product. In addition to the role of hands on
designer, your responsibilities will include managing the small but growing
User Experience Group. You will be responsible for personnel, resource, and
mentorship management.

The successful candidate will have experience in both web-based and GUI
based user interfaces, ability to create clear and clean prototypes in Visio
&/or HTML, have good communication skills, work well with customers, have
experience with usability testing and field research. They will also have
experience in managing internal teams as well as working with 3rd party
contract relationships which the position will be expected to coordinate and
manage.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane