If I read correctly Kim, the main difference between #1 and #2 is that
in the latter you just make a copy of the wiki first to preserve for
all prosperity the 2.x state?
#1 seems right approach to me but making a copy first could be prudent.
Kevin
Jin Li wrote:
I vote for #1.
When we (Kim and I) created the
wiki,
it was meant to be a sandbox to put v3.x draft up there for early and
continuous
feedback and solicit more input/contribution from the community. If we
think some of the topics are ready to become official (perhaps we
should
have done this sooner :-), we should promote them to the official place
(namely, http://www.eclipse.org/articles/Article-UI-Guidelines/Index.html).
I would leave the wiki for more draft/input/contribution.
cheers,
Jin Li
IBM Canada Ltd.
Tel: 905-413-2857
Fax: 905-413-4974
Internet: jinli@xxxxxxxxxx
I vote for #1.
Raji Akella
Lotus Expeditor Development
 Tod
Creasey ---11/15/2007 07:17:36 AM---#2 was the ovious choice for me too.
#2 was the ovious choice for me too.
Tod
Hi all,
As some of you know from the UIBP call today, I moved the 3.x content
over
to the 2.1 document at the bottom. The goal being to have one document
to
link the Top Ten (or so) checklist items.
However, I'm running into a snag and would like your votes.
Because the UI Graphic section has essentially been fully updated to
reflect the 3.x style, appending them in full to the bottom makes for
one
very large document. Further, folding in the checklist items means a
checklist of the 2.1 guidelines and a checklist of the 3.x guidelines.
It's
messy. I'd like to propose one of the following (please vote and/or add
suggestions):
1 :: Instead of appending the updates in the current 2.1 document,
just
replace the content sections they apply to and mark them as "new"
or "3.x
update". This keeps the same URL and uncomplicates the merge and
linking.
Note that there is an existing 2.1 article here:
http://www.eclipse.org/articles/Article-UI-Guidelines/Index.html,
so we
needn't preserve the wiki one.
2 :: Take a full copy of the 2.1 and rename that copy with "(old)"
or
something to distinguish and preserve it on the wiki, then continue the
updates in the current 2.1 (with 3.x updates) document. Again, this
preserves the URL as the most current document we update, and puts the
2.1
document into the background.
3 :: Leave the current 2.1 as it is, merge its content with the draft
3.x
document and point instead to the latter from the Top Ten checklist.
I favour #2.
Regards,
Kim
...................................................................
UI Design . Rational Software
IBM Toronto Media Design Studio
From: "Mik Kersten" <beatmik@xxxxxxx>
To: "'User Interface Architecture Working
Group'" <ui-best-practices-working-group@xxxxxxxxxxx>
Date: 11/14/2007 12:20 PM
Subject: RE: [ui-best-practices-working-group] Reminder: Conference
Call: Wednesday, November 14th, 18:00 UTC or 10:00
PST. Call
613.287.8000 or 866.362.7064
passcode 892048#
I could not move a meeting and will unfortunately have to miss this
call.
In other news I finally took my pass through the check list:
205326: Update the checklist for developers
https://bugs.eclipse.org/bugs/show_bug.cgi?id=205326
Mik
> -----Original Message-----
> From: ui-best-practices-working-group-bounces@xxxxxxxxxxx [mailto:ui-
> best-practices-working-group-bounces@xxxxxxxxxxx] On Behalf Of Bob
> Fraser
> Sent: Tuesday, November 13, 2007 3:11 PM
> To: UI Best Practices Working Group
> Subject: [ui-best-practices-working-group] Reminder: Conference
Call:
> Wednesday, November 14th, 18:00 UTC or 10:00 PST. Call
613.287.8000
or
> 866.362.7064 passcode 892048#
>
> Conference Call: Wednesday, November 14th, 18:00 UTC or 10:00 PST.
Call
> 613.287.8000 or 866.362.7064 passcode 892048#
>
> Agenda:
>
> Update from the planning council meeting
>
> Any other topics welcome.
>
> Bob
>
>
> Notice: This email message, together with any attachments, may
contain
> information of BEA Systems, Inc., its subsidiaries
and affiliated
> entities, that may be confidential, proprietary, copyrighted
and/or
> legally privileged, and is intended solely for the use of the
> individual or entity named in this message. If you are not the
intended
> recipient, and have received this message in error, please
immediately
> return this by email and then delete it.
> _______________________________________________
> ui-best-practices-working-group mailing list
> ui-best-practices-working-group@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-
> group
_______________________________________________
ui-best-practices-working-group mailing list
ui-best-practices-working-group@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group
_______________________________________________
ui-best-practices-working-group mailing list
ui-best-practices-working-group@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group
_______________________________________________
ui-best-practices-working-group mailing list
ui-best-practices-working-group@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group
_______________________________________________
ui-best-practices-working-group mailing list
ui-best-practices-working-group@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group
_______________________________________________
ui-best-practices-working-group mailing list
ui-best-practices-working-group@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group
|
