Standalone, it's a packaged eclipse. Two builders == two eclipses I just
went with builder because I prefer the way some menus are layed out and I
don't do any java + flex (at the same time) development. My responsibilities
at work end at the WSDL these days.

-Josh

On Thu, Aug 7, 2008 at 10:10 PM, Johannes Nel <[EMAIL PROTECTED]>wrote:

>  just kick of another eclipse and select the second workspace. it works
> fine.no i am serious, why two flexbuilders, i am trying to think of a
> scenario where 1 is not enough. a java and flex eclipse instance i get, but
> two flex builder instances?
>
> also, did you install the plugin version of flexbuilder or stand alone,
> this might be a problem with standalone.
>
>
> On Thu, Aug 7, 2008 at 2:02 PM, Josh McDonald <[EMAIL PROTECTED]> wrote:
>
>>   Ew, is that a joke? Besides I already said that it was two different
>> workspaces. Switching between them takes way too long, and I wanted to be
>> able to work in one while the other is building (which also takes way too
>> long)
>>
>> On Thu, Aug 7, 2008 at 9:34 PM, Johannes Nel <[EMAIL PROTECTED]>wrote:
>>
>>>  yeah, thats the way, why would you however want two instances of flex
>>> builder (i get two eclipses).if its more than one project just open both
>>> at once, or have both in one project and mod your build script.
>>>
>>>
>>>
>>>
>>
>>
>> --
>> "Therefore, send not to know For whom the bell tolls. It tolls for thee."
>>
>> :: Josh 'G-Funk' McDonald
>> :: 0437 221 380 :: [EMAIL PROTECTED]
>>
>>
>
>
> --
> j:pn
> \\no comment
> 
>



-- 
"Therefore, send not to know For whom the bell tolls. It tolls for thee."

:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: [EMAIL PROTECTED]

Reply via email to