I think this thread has gone down the path of using a relaxed attitude.
Packaging, Delivery, and Installation.
Delivery and installation for clients has been discussed thoroughly.
I think the more deligence taken towards delivery makes an good
impression on the client.
Not much has been discussed in terms of management of components
within an internal organisation.
Component development helps provide a much more modular approach to
GUI dev departments. The flex markup language provides an easier way
to make use of flash components.
In terms of packaging a library of components for internal use, i
think developers can benefit from the same perspective as delivering
components to clients.
Are there any particular naming conventions, package structure that
would promote common practice. So far i have been picking up most of
my standards, ('naming', 'commenting', 'coding') from the flex 2
framework.
Regards,
Bjorn
--- In [email protected], "adobeted" <[EMAIL PROTECTED]> wrote:
>
> We have a unique opportunity to define a standard for component
> packaging, delivery, and installation. We need to make sure that end
> users have a reliable, consistant way to get a component installed and
> working. I would like to define this standard here as a group.
>
> Here are some thoughts:
>
> 1. KISS - This needs to be simple and consistant. End users should not
> struggle to get a component installed and working. If we all ship
> components in the same structure/pattern, it will minimize confusion.
>
> 2. Consistant directory structure across components. When a component
> is received it should be easy to find documentation, installation
> instructions, license, and source if included.
>
> Filesystem or ZIP Archive like so:
>
> /ComponentName/
> /ComponentName/source/
> /ComponentName/swc/
> /ComponentName/examples/
> /ComponentName/docs/
> /ComponentName/install.html
> /ComponentName/documentation.html
> /ComponentName/license.html
>
> 3. Consistant instructions in install.html, documentation.html,
> license.html and consistant professional generated documentation.
>
> 4. Code standards for component source. Define simple guidelines for
> formatting source code. Indentation and comments to improve
> readability of code within source.
>
> ------------------
>
> Thoughts, comments, additions?
>
> Ted :)
>
------------------------ Yahoo! Groups Sponsor --------------------~-->
See what's inside the new Yahoo! Groups email.
http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcomponents/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
