× Warning! This forum is in archival status. New contributions may not work.
[livesupport-dev] style guide document
  • hello everyone,

    sangita and i are anxious to hear comments on our style guide. midterms
    just ended here, and we'd love to hear what the developers have to say
    about the usefulness of the document in it's current format. we're
    hoping that this is what you're looking for and that it will be
    helpful for you in the implementation of the graphical user interface.

    if it is lacking, let us know how we can improve it to suit your needs.
    Once we have a good idea about what its ideal state should be, we will
    revise it, complete descriptions for the other modules, and optimize
    the graphics for use in the application.

    this document should be used as a guide to creating modules that adhere
    to the style we decided upon last summer. As for application user
    experience, the style guide should be modified to accommodate whatever
    we agree is best. The descriptions of user experience can be modified
    as we go and "finalized" when the application is ready for release. But
    what this document should be doing at every step of the way is making
    it clear how to deal with things like palette construction, button
    usage, table display, basic elements like that. The first job of the
    doc is to describe "how" to use these elements. The discussion of
    "when" to use them or "if" we should use them is an evolving one, and
    we will incorporate revisions to these kinds of decisions as we go.


    how is it going anyway? are you guys almost done? ; )


    thanks so much, hope all is well on your side of the planet,



    charles

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • 5 Comments sorted by
  • This is a multi-part message in MIME format.
    --------------080304040902000604020303
    Content-Type: text/plain; charset=ISO-8859-1; format=flowed
    Content-Transfer-Encoding: 7bit

    Hi Sangita, hi Charles,

    Thanx for your good wishes.
    Seems to me that we have problem with mails again.
    I sent you several times my comments about Guide User Interface,
    but I didn't get any reply from you guys.

    Do you have some special filter for my mails? Please tell me you don't. Smile

    So, I will send to you again my suggestions in attachment.
    Please respond to me if you get this mail and its attachment, so that we
    don't have any more misunderstandings.


    Lots of greetings and good wishes from this side of the planet and
    lots of luck during your elections. Smile


    Robert











    charles truett wrote:

    > hello everyone,
    >
    > sangita and i are anxious to hear comments on our style guide.
    > midterms just ended here, and we'd love to hear what the developers
    > have to say about the usefulness of the document in it's current
    > format. we're hoping that this is what you're looking for and that it
    > will be helpful for you in the implementation of the graphical user
    > interface.
    >
    > if it is lacking, let us know how we can improve it to suit your
    > needs. Once we have a good idea about what its ideal state should be,
    > we will revise it, complete descriptions for the other modules, and
    > optimize the graphics for use in the application.
    >
    > this document should be used as a guide to creating modules that
    > adhere to the style we decided upon last summer. As for application
    > user experience, the style guide should be modified to accommodate
    > whatever we agree is best. The descriptions of user experience can be
    > modified as we go and "finalized" when the application is ready for
    > release. But what this document should be doing at every step of the
    > way is making it clear how to deal with things like palette
    > construction, button usage, table display, basic elements like that.
    > The first job of the doc is to describe "how" to use these elements.
    > The discussion of "when" to use them or "if" we should use them is an
    > evolving one, and we will incorporate revisions to these kinds of
    > decisions as we go.
    >
    >
    > how is it going anyway? are you guys almost done? ; )
    >
    >
    > thanks so much, hope all is well on your side of the planet,
    >
    >
    >
    > charles
    >
    >
    >
    > __________ NOD32 1.906 (20041025) Information __________
    >
    > This message was checked by NOD32 antivirus system.
    > http://www.nod32.com
    >
    >
    >


    --------------080304040902000604020303
    Content-type: message/external-body; access-type=URL; URL=http://sympa.mdlf.org/sympa-bin/wwsympa.fcgi/attach/livesupport-dev/417FE9C3.2060705@b92.net/Robert comment about style guide_doc; name="Robert comment about style guide_doc"; size="76834"

    Content-type: application/msword;
    name="Robert comment about style guide.doc"
    Content-Transfer-Encoding: base64

    --------------080304040902000604020303--

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • Robert,

    yes, we did get your comments, and we've reviewed them, and would like to implement them in the next revision of the style guide.

    what we'd like first is to get some feedback from the developers as to their impressions of the document, so Sangita and I know whether or not the format is useful for their purposes.

    Once we hear from them, we'll know a little bit better how to treat this document so that its as useful as possible in building the application.

    Then we'll go back and include your comments, and complete the descriptions of the remaining modules.

    Does that sound OK?


    Charles

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • livesupport-dev@campware.org schrieb am 28.10.04 00:55:00:
    >
    > Robert,
    >
    > yes, we did get your comments, and we've reviewed them, and would like to implement them in the next revision of the style guide.
    >
    > what we'd like first is to get some feedback from the developers as to their impressions of the document, so Sangita and I know whether or not the format is useful for their purposes.

    sorry for my absence. i will look at the document over the weekend and comment thoroughly. for now i just want to press robert's concerns to the front of the gui considerations (for the live assist mode at least Wink after all, he is the only person in the team who has a practical radio background and a good knowledge of radio software.

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • Dear Charles,

    I looked at the document, and it seemed very thorough to me. I think
    this level of detail is sufficient to create GUIs. What I find missing
    is the specific bitmaps that would need to be used to create the GUIs
    described in the document, but I guess that would come as some sort of
    attachments.


    Akos

    ------------------------------------------
    Posted to Phorum via PhorumMail
  • Hi Charles,

    That sounds good ... The scenario is ok for me .

    Looking forward for the developers impressions.

    See you and hear from you soon !

    Robert





    charles truett wrote:

    >Robert,
    >
    >yes, we did get your comments, and we've reviewed them, and would like to implement them in the next revision of the style guide.
    >
    >what we'd like first is to get some feedback from the developers as to their impressions of the document, so Sangita and I know whether or not the format is useful for their purposes.
    >
    >Once we hear from them, we'll know a little bit better how to treat this document so that its as useful as possible in building the application.
    >
    >Then we'll go back and include your comments, and complete the descriptions of the remaining modules.
    >
    >Does that sound OK?
    >
    >
    >Charles
    >
    >
    >__________ NOD32 1.908 (20041027) Information __________
    >
    >This message was checked by NOD32 antivirus system.
    >http://www.nod32.com
    >
    >
    >
    >
    >

    ------------------------------------------
    Posted to Phorum via PhorumMail