First of all, if you don't distribute the source code with your SWC file most people won't see it. You probably saw it because you have the library linked ( even if it was closed ) or the source files linked to the SWC build path.
Secondly, SWC and SWF files can be easily decompiled using a tool like Buraks Actionscript Viewer. This however does not limit your rights as the creator of the code, it just means people can get to it. Most people won't though as they have better things to do and projects to get done. Some will though and it may or may not be worth the extra effort( think ROI ) to attempt to stop them. I think this is the reason that some companies offer to send the source as well ( but limit your priveleges with the source in the license ) for a premium over the price of just the component alone. This might be smarter. It gives people a legal way to get the source for your components so they can push your components past their initial design constraints while giving you more cash for your work. Ultimately the decision is up to you. --- In [email protected], "ahmad_eldardiry" <[EMAIL PROTECTED]> wrote: > > I forgot to mention that when I pressed the debug button, a dialogue > box showed with a "This file is not inside a project, many Flex > builder features will be disabled" message. > > Thank you. > > > > --- In [email protected], "ahmad_eldardiry" > <ahmad_eldardiry@> wrote: > > > > I'm a flex beginner, and I'm making a flex component (.swc) and I want > > to sell it. While I was testing it within an AIR application on Flex > > Builder 3, an error ocurred, so I thought I can use the debugger (It > > works well on Flex compiler). > > > > When I did try to debug the application, the debugger actualy > > decompressed the output swf and opened one of the classes contained > > inside my .swc to point to the line having the error!!! > > > > So, now I can see my source code (not to mention the variables and > > objects listing inside the variables tab) inside the so thought > > 'protected' .swc, without any external decompiler, but within the Flex > > builder 3 itself! > > > > When I googled about it, I found only this similar note: > > > > > http://clintm.esria.com/2007/05/11/linking-source-code-to-a-swc-in- flexbuilder/ > > > > If I was to sell this .swc, anybody can see my source code that way, > > so is there any solution for this issue? Has anybody faced something > > similar? Or is it even a known fact? > > > > How can someone protect his flex components from flex builder debugger? > > > > Thank you. > > >
