How the projects are created right now in Eclipse you could drop SWC
files into your C:\Program Files\Adobe\Flex Builder 2\Flex SDK
2\frameworks\locale\en_US folder and they will work.
This is because in Project -> Properties -> Flex Build Path -> Library
Path there is an entry of ${FRAMEWORKS}\locale\{locale}
The downfall is this is gear for localization not component
deployment. But you can add a SWC folder to your projects, it would
be nice for the default Flex Projects to come with a "Components" SWC
Folder already defined in the project settings and make that the
default place to install 3rd party SWC. Something like in Flex 1.5
where we would put SWC's in the user_clases folder under the
\WEB-INF\flex\user_classes.
Then a plugin like Jesse is referring to could be made to make it easy
to use the manage all the SWC's for the Flex Builder. Now if people
are using the SDK, it could be stated that all 3rd party SWC's that
you want access to in compiling your applications could go in this
folder and have the default compile parameters pick it up just like it
would be defaulted in teh Flex Build Path for each project.
This would require some change by Adobe but I believe its a pretty
good idea. If we have to tell people to configure their projects each
time they add new compoenents it could get a feeling like its not
supposed to be that way. But if by default there was a standard place
to put user_classes then it would make process go much smoother.
Renaun
--- In [email protected], "JesterXL" <[EMAIL PROTECTED]> wrote:
>
> Make Andy's Flexbuilder group can build us an "install Component
into project", or perhaps a window to keep track of your installed
components like the Component Panel in Flash; I Ioved that thing.
I'll be frank when I say I really frikin' miss Extension Manager.
That guy was so damn useful, for Flash at least. It'd be nice to have
some sort of hook to how SVN and other plugins work in the Eclipse
plugin manager where our SWC's could dropped right in, installed,
uninstalled, queried for data, etc.
>
> ----- Original Message -----
> From: Ted Patrick
> To: [email protected]
> Sent: Saturday, July 15, 2006 4:26 PM
> Subject: RE: [flexcomponents] Component Packaging, Delivery, and
Installation
>
>
> Ralf,
>
>
>
> Nothing is technically wrong with SWC for the component itself but
95% of the time more is needed.
>
>
>
> Here are a few:
>
>
>
> 1.. SWC lacks documentation HTML.
> 2.. SWC lacks code examples of component use.
> 3.. SWC lacks instructions of how to install it.
> 4.. If you want to distribute source as/mxml, SWC doesn't cover this.
>
>
> The discussion here is intended to answer this question?
>
>
>
> "When a component is delivered, what does the developer receive and
how is it organized?"
>
>
>
> SWC is just one piece of the puzzle.
>
>
>
> Regards,
>
>
>
> Ted J
>
>
>
>
>
--------------------------------------------------------------------------------
>
> From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Ralf Bokelberg
> Sent: Saturday, July 15, 2006 11:45 AM
> To: [email protected]
> Subject: Re: [flexcomponents] Component Packaging, Delivery, and
Installation
>
>
>
> What's wrong with swc?
> Cheers,
> Ralf.
>
> On 7/15/06, Ted Patrick <[EMAIL PROTECTED]> wrote:
> > >Cool... so... how do we do it?
> >
> > We just do it and move forward.
> >
> > The goal is to make sure 100% sure that any Flex developers can
install
> > components. We make the file system consistent and simple so that
> > everyone understands a component ZIP file or file system. We do
this as
> > a group and define a standard for any component developer to
aspire to.
> >
> > a. Reference Example Component FileSystem/ZIP.
> > b. Page on Flex.org to denote standard.
> > c. FlexComponents endorses it as a 'standards body'.
> > d. KISS - Keep It Simple Stupid.
> > e. Get an Adobe WhitePaper written.
> > f. Get Adobe ASDocs released or use Mike's toolset!
> > g. We automate compilation/packaging for component developers. Make a
> > file system this way, edit an XML Build document, run this script, out
> > pops a perfect ZIP with SOURCE, SWC, DOCS, LICENSE, INSTALLATION,
ready
> > to roll! Repeatable, consistent, simple. ( I can hear Anatole
typing out
> > an ANT script to do this right now... :) )
> >
> > The standard is a goal, something that developers should aspire to. If
> > you want to write poorly formatted code without comments you are
free to
> > do so. I think eventually people will realize the quality of the
> > components is based on these details. If docs are sharp, licensing,
> > installation spot on perfect, it says that this developer took the
time
> > to do things right. It also makes a much stronger case for developers
> > licensing components. Developers do not license crap, they license
code
> > that saves them time and money.
> >
> > We just need to take dead aim on a really great format to allow
> > components to be distributed. If the format is easy for any
developer to
> > use, then we have succeeded.
> >
> > If we pruned things back to cover just a component distribution format
> > then that would be perfect with me.
> >
> > IMHO,
> >
> > Ted :)
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
>
> --
> Ralf Bokelberg <[EMAIL PROTECTED]>
> Flex & Flash Consultant based in Cologne/Germany
>
------------------------ Yahoo! Groups Sponsor --------------------~-->
Great things are happening at Yahoo! Groups. See the new email design.
http://us.click.yahoo.com/TISQkA/hOaOAA/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/
