Member Controls

Goto page 1 2 3 4 5 6      Next
Developers > SVN structure changes - finished
pljonesLink to postposted: Tue Jan 01, 2008 1:03 am

Member since:
 2005-04-02
Posts:
 616

I'm currently in the early stages of moving PJSE into the SimPE SVN.

 

As part of this, I've split the "Non-core" components of SimPE off into a subfolder, called __NonCore, updated Everything.sln, added a new "Build" project and moved everything that a plugin developer can't rely on into __NonCore.  (Okay, Theo already relies on one of the components and PJSE will probably end up in __NonCore, too -- the idea is to discourage cyclic dependency: cross-dependency within __NonCore isn't great but the Core mustn't depend on __NonCore.)

 

rev 400: is the next part.  Each non-core project will have two project files and its own solution file.  One project file will be for building as part of Everything.sln.  The other will be for building "stand alone".  I've committed the Career Editor version.

 

Other than updates to the other __NonCore projects to provide the new project and solution files, there's nothing outstanding and Everything.sln builds.  There's a new Core.sln (rev 397) that builds all but __NonCore.  And I updated SimPE.sln to be in line with Everything.sln (i.e. add in the widgets).

 

 

Provisionally, after this stage, I'll add PJSE.

 

Then I'll "do something" so that there isn't a dependency on an already-installed version of SimPe (should become trivial once PJSE has a project as part of Everything.sln).

pljonesLink to postposted: Tue Jan 01, 2008 3:06 pm

Member since:
 2005-04-02
Posts:
 616

In the SimPE SVN repository, I've committed the new projects and solutions for the remaining __NonCore components.

 

In the PJSE CVS repository, I've committed new projects which can be added to Everything.sln to incorporate PJSE.  Locally, I've made these changes and also amended the dependencies of the Career Editor and SimPe BHAV projects to use the PJSE projects rather than the DLLs.  As part of that, the new PJSE post-build script fakes up the "version.txt" file required by the pjse update checker and creates a PJSE_help\Contents.htm that redirects to the simlogical site.

 

(All with no code changes :).)

 

I don't want to lose the CVS history of PJSE, really.  However, the cross-folder dependencies in the project files are a bit ugly (you have to check out PJSE to pjseCoderPlugin-cvs at the same level as where fullsimpe lives).  So my next step may be to work out how to get the CVS imported into the SimPe SVN with its history.

Inge JonesLink to postposted: Tue Jan 01, 2008 3:21 pm

Member since:
 2005-03-06
Posts:
 1900
If you're not moving the PJSE sources, then you should give Quaxi and perhaps one other person some powers in there.  We don't want you going missing (doing a Quaxi lol) and no one able to continue work on the plugins.
NumenorLink to postposted: Wed Jan 02, 2008 11:23 am

Member since:
 2005-03-07
Posts:
 380

So, all the stuff moved to the "_NonCore" section is something that SimPE can run without (though missing some relevant functions)? This is interesting, because I was thinking to make the installer more flexible, allowing people to install (and run) a personalized "light version" of SimPE.

 

EDIT: Is the tool that Quaxi refers to in this thread somewhat related to (or influenced by) these SVN changes? Peter, will you please take a look there and reply, if needed?

pljonesLink to postposted: Wed Jan 02, 2008 11:07 pm

Member since:
 2005-04-02
Posts:
 616

Numenor wrote:
So, all the stuff moved to the "_NonCore" section is something that SimPE can run without (though missing some relevant functions)? This is interesting, because I was thinking to make the installer more flexible, allowing people to install (and run) a personalized "light version" of SimPE.

You could look at it that way -- although there are things not in __NonCore that SimPE can run without - but they are needed to build __NonCore.  The bare minimum is probably defined by the "SimPe.sln" solution file.

 

Numenor wrote:
EDIT: Is the tool that Quaxi refers to in this thread somewhat related to (or influenced by) these SVN changes? Peter, will you please take a look there and reply, if needed?
I've still not look at the new tool at all, so I can say that it's not influenced things :).
quaxiLink to postposted: Thu Jan 03, 2008 4:53 pm
Avator for quaxi

Member since:
 2006-04-28
Posts:
 3154
Nope that Release Tool should not matter at all. It just needs a Folder where all the Data that needs to be packed is located in.
quaxiLink to postposted: Sun Jan 06, 2008 12:15 pm
Avator for quaxi

Member since:
 2006-04-28
Posts:
 3154
Inge told me you were working in a new branch. Did you merge it back, or will we develop in that branch?
Inge JonesLink to postposted: Sun Jan 06, 2008 12:39 pm

Member since:
 2005-03-06
Posts:
 1900

As I understand it, the branch contained the 0.64 release.  This was in case there were small bugs in the release that needed fixing with an immediate new public release.   That means development of new and maybe risky features can be continued in the main trunk (from 0.65), without fear that they will get into and spoil any emergency bugfix release of 0.64.

 

Peter hasn't continued with the SVN changes for a few days as he's still bogged down with the career editor!

quaxiLink to postposted: Sun Jan 06, 2008 2:09 pm
Avator for quaxi

Member since:
 2006-04-28
Posts:
 3154

I am a noob again...

 

I just tried to compile the DockBox from the __Solutions/NonCore Folder and it gives me errors, since it was unabe to locate the referenced packages. Are you still working on this, aor am I doing something wrong? 

Inge JonesLink to postposted: Sun Jan 06, 2008 2:17 pm

Member since:
 2005-03-06
Posts:
 1900

He's still working on it.  We'd expected you to not be back on SimPE work till March so we didn't realise there was a hurry to get the reorganisation finished.  He has to finish the career editor first because that being missing has the largest impact on the community.

Goto page 1 2 3 4 5 6      Next


viewthread, 0, 0, Changes-currently-in-progress