Normally I would just use working set to segment differenct sets of projects.

It's easier then setting up multiple workspaces (IMO).

Jeremy.

On 6/27/06, Michael Schmalle <[EMAIL PROTECTED]> wrote:

> Go into

I didn't even realize that. Until I prove myself wrong, a new workspace for a component set seems to work pretty good for me.

I need someone form Adobe to tell me this is wrong and the reasons. Specifically component sets seem to fit good in this ... repeat, I have no idea.

I'm sure there are choices and consequences to everything I do.

I see what using a new workspace does, it creates the .metadata folder in the root folder that you use.

Peace, Mike



On 6/27/06, ben.clinkinbeard < [EMAIL PROTECTED]> wrote:

Michael, you can also use the "Go into" link on the context menu when
you right click on a project name. That will effectively hide
everything outside that project from view.

While we're on the subject though, can anyone point me to a decent
"Eclipse basics" reference? Book, web site, whatever, I would just
like to feel a little more comfortable in the app. I plan on using it
for Flex, non-Flex Flash dev and have even begun using it for HTML/CSS
work, but I still feel like I am kinda fumbling around in it.

Thanks,
Ben




--
What goes up, does come down.


__._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com





SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to