You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Justin Mclean <ju...@classsoftware.com> on 2012/04/07 02:25:44 UTC

Workspace files in SVN

Hi,

>> That's exactly the thing, that it doesn't work like that - everyone has
> their source code in a different place, different project settings... if
> you do this in a team you will get infinite war of minor similar changes of
> the same property being set 
You can avoid this if you take a little care with some minor hand edits of the project files (all paths can be made relative to the users workspace). I do this on a couple of large projects ie workspace files are checked into SVN. It also works cross platform window/mac.

 Jeff if you need a hand with this just ask.

Thanks,
Justin

Re: Workspace files in SVN

Posted by Left Right <ol...@gmail.com>.
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<actionScriptProperties analytics="false" mainApplicationPath="
apache-flex.as" projectUUID="e9c1d7ef-02a5-471d-952b-ebcadc844ffa"
version="10">
  <compiler additionalCompilerArguments="" autoRSLOrdering="true"
copyDependentFiles="false" fteInMXComponents="false"
generateAccessible="false" htmlExpressInstall="true" htmlGenerate="false"
htmlHistoryManagement="false" htmlPlayerVersionCheck="true"
includeNetmonSwc="false" outputFolderPath="bin" removeUnusedRSL="true"
sourceFolderPath="../flex/SDK/projects/framework/src" strict="true"
targetPlayerVersion="0.0.0" useApolloConfig="false" useDebugRSLSwfs="false"
verifyDigests="false" warn="true">
    <compilerSourcePath>
      <compilerSourcePathEntry kind="1" linkType="1"
path="/home/wvxvw/flex/SDK/apache/frameworks/projects/mx/src"/>
      <compilerSourcePathEntry kind="1" linkType="1"
path="${PROJECT_FRAMEWORKS}/projects/rpc/src"/>
      <compilerSourcePathEntry kind="1" linkType="1"
path="/home/wvxvw/flex/SDK/apache/frameworks/projects/spark/src"/>
. . .
    </compilerSourcePath>
    <libraryPath defaultLinkType="0">
      <libraryPathEntry kind="4" path="">
        <excludedEntries>
          <libraryPathEntry kind="3" linkType="1"
path="${PROJECT_FRAMEWORKS}/libs/flex.swc" useDefaultLinkType="false"/>
          <libraryPathEntry kind="3" linkType="1"
path="${PROJECT_FRAMEWORKS}/libs/core.swc" useDefaultLinkType="false"/>
        </excludedEntries>
      </libraryPathEntry>
    </libraryPath>
    <sourceAttachmentPath/>
  </compiler>
  <applications>
    <application path="apache-flex.as"/>
  </applications>
  <modules/>
  <buildCSSFiles/>
  <flashCatalyst validateFlashCatalystCompatibility="false"/>
</actionScriptProperties>

But I'm using the project only to edit the code, I don't use FB to compile
anything / it's too slow / inconvenient. I rather use it because of
autocompletion and F4 functionality.

Best.

Oleg

Re: Workspace files in SVN

Posted by Jeffry Houser <je...@dot-com-it.com>.
On 4/7/2012 4:17 AM, Left Right wrote:
> Hi Jeffry,
>
> I replied in another thread, but in a nutshell: I'm used to different 
> project structure,

  What project structure do you use?


-- 
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust

Re: Workspace files in SVN

Posted by Left Right <ol...@gmail.com>.
Hi Jeffry,

I replied in another thread, but in a nutshell: I'm used to different
project structure, so I won't be using the project files you are creating /
they won't fit my setup anyway (sorry if this sounds like a threat, I don't
intend it :). However, it does no harm either, so far any special meaning
isn't assigned to these files. So I don't care.

Best.

Oleg

Re: Workspace files in SVN

Posted by Jeffry Houser <je...@dot-com-it.com>.
On 4/6/2012 8:25 PM, Justin Mclean wrote:
> Hi,
>
>>> That's exactly the thing, that it doesn't work like that - everyone has
>> their source code in a different place, different project settings... if
>> you do this in a team you will get infinite war of minor similar changes of
>> the same property being set
> You can avoid this if you take a little care with some minor hand edits of the project files (all paths can be made relative to the users workspace). I do this on a couple of large projects ie workspace files are checked into SVN. It also works cross platform window/mac.
>
>   Jeff if you need a hand with this just ask.

  Thanks!  I got the stuff checked in (as I'm sure many of you saw the 
50 or so notification emails).  Since all the source directories are 
relative to the workspace root; I would expect it to just work.  I'm 
doing the same thing with another project I'm on and we share the 
workspace / project files between Windows (Me) and Mac (Other 
developer).  It's been incredibly convenient.  My co-consultant on the 
project did the initial commit; but as far as I knew he did no manual 
edits to the eclipse property files.

  Even if you don't use Flash Builder; you can drill down into the 
directories to get the source code.

  IF others have thoughts on this; I would love to hear them.



-- 
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust