johnf wrote: > On Tuesday 17 February 2009 05:13:00 am Nate Lowrie wrote: >> On Tue, Feb 17, 2009 at 8:01 AM, Uwe Grauer >> >> <[email protected]> wrote: >>> Is Dabo a framework or is it an IDE? >>> If it is a framework, code dealing with pathing issues shouldn't be >>> included in the framework code. >>> >>> I think it's plain wrong to put such code deep into a database glue >>> module. It just doen't belong there. >> A framework with an IDE to facilitate development. And I fully >> disagree with your statement about pathing code. There are plenty of >> frameworks that define a standard directory structure and pathing >> requirements for their applications. If adding pathing code to the >> framework makes for less applications code and issues, why not. > > Most modern FrameWorks and IDE's do not impose a path requirement for a > project. At least in my experience. For example .Net, VFP, VB, Java > (netbeans, or eclipise), C++, C leave the project structure to the developer. > > I realize there are few that do. Such as Ruby on Rails (but Ruby by it's > self does not) and there are others I'm sure. > > Instead of me answering "why not" explain why we shouldn't just allow the > developer to determine the location of the SQLite DB or the structure he/she > may want (or required to use by a corp office) for the a project. After all > they are developers. > > That said, I believe that is not the issue (to force a path or not to). The > real issue is there is no IDE yet. And that is the cause of new developers > problems with forced paths. If there was a complete IDE (and the developer > was using it) when creating a project the structure would be created and the > problem would be solved. But at the moment Dabo does not provide a complete > IDE. > > Also there is little to nothing in the Doc's (or screencasts) that let's the > users of ClassDesigner know there is a structure they should be following. >
Even the "argument" about that there is no IDE, is a non isssue. Tell the people that all paths have to be relative to the project app directory and there are no issues any more. The notion of the current working directory is important to very cumputer user. You don't have to be a developer to understand it. Putting strange pathing code into a framework is really unnecessary once this little convention has been put into place. Uwe _______________________________________________ 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]
