On 3/22/10 12:50 PM, Ed Leafe wrote:

> On Mar 22, 2010, at 3:38 PM, Paul McNett wrote:

>

>>> As it stands now, I agree: it isn't portable. What I was thinking of

>>> doing is finding a way to make it portable, so that it can work x-

>>> platform. I have a few ideas, but nothing I've tested at all

>>

>> The missing piece, as you pointed out in our discussion at pycon, is

>> the project manager. One of the key things (the only thing?) in a

>> project file is the home directory for the project. If when opening a

>> project file the directory doesn't exist the appdev could be prompted

>> for it.

>

> That's one of the solutions I was considering.

>

>> For the time being couldn't we just implement this in

>> dabopreferences.db?

>

> I think that that would be a) rather clumsy to implement and b) totally non-portable.

Definitely clumsy, but it would get us rolling until we get the project manager. The

status-quo is already non-portable.

My point is that the information in question (where the root of the project is) only

really makes sense to keep on a per-system basis. I could be working on the exact

same code base from any number of locations on any number of systems.

>> Or at the app level with a ProjectHomeDir (means a different thing and

>> only relevant at design time) property?

>

> Design time is not all that different than run time. I find it best not to think about things that way.

And usually we can get away with that. But at design-time you have two application

objects to work with: 1) the Class Designer and 2) the application the developer is

producing. So I think in this case at least you are forced to separate design-time

and run-time.

>> Portability aside, it makes no sense for an app property set at design

>> time to determine the home directory at run time. Unless you are going

>> to require the end user to put the application in a proscribed

>> location...

>

>

> Not at all. The ability to either prompt for (ugly) or discover (elegant) the HomeDirectory should make it easier, not harder, to move apps around without the pathing issues we had when assuming that the main script being run was always in the HomeDirectory.

If you are planning to prompt for or discover the HomeDirectory at run-time anyway,

why save the HomeDirectory to the cdxml at all? If the answer is, "so the class

designer maintains a consistent reference to it", then this really points to the need

to maintain a separate property somewhere. I believe otherwise we have one too many

purposes for HomeDirectory.

> I don't have time to work on this now, but I'll see about looking into this next weekend when I might have more free time.

I have no time, either. Hopefully this discussion has been constructive!

Paul

_______________________________________________

Post Messages to: Dabo-dev@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev

Searchable Archives: http://leafe.com/archives/search/dabo-dev

This message: http://leafe.com/archives/byMID/4BA7DA6D.6040904@ulmcnett.com