Over the past few months we've run into people who time and time again
get frustrated by the errors that happen when the directory that they run a
tool or wizard from is not the same as the one from which they are running the
app. I remember when I wrote the current pathing stuff that I was thinking that
a full IDE was only a couple of months away, and that once that was in place,
the IDE would handle the pathing by providing a project file that would fix the
HomeDirectory location.
Since the IDE thing isn't happening any time soon, I am considering
rewriting the path resolution routines to always work from the app's
HomeDirectory. To make this easier, I've modified the StatusBar of the
CxnEditor to always show the current HomeDirectory, and to make it easy to
change. Here's a screenshot just after starting up:
http://tinypic.com/r/2w4fvuw/6
Note that the HomeDirectory is my Dabo IDE directory. Clicking on the
link opens a getDirectory() dialog, and after I select my project location, it
now looks like this:
http://tinypic.com/r/sawcjr/6
What I also need to do is revisit all the code that references the path
resolution code, and make sure that they don't break if I switch to a
HomeDirectory-based pathing system. Right now I see this as affecting SQLite
connections, .cdxml-based forms, and image resources.
Does anyone see a problem with switching to this approach?
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
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/[email protected]
