I would start hacking on the wiki, but given that I haven't installed on Win in quite a while I think I'll just post half baked comments. and I need to figure out what my user/pass is. it is around here somewhere.
I am in the process of setting up an XP box to test running XP on XP (I need to simulate 16 cpu's which qemu docs say it can do.) in a day or so I'll be able to run though the InstallationOnWindows steps. Correct me if I'm wrong: there are 4 categories of install: dabo runtime - what is needed for a user to run an app. stable Dabo package - least bugs (for now, also out of date quickly) svn trunk for use svn trunk for editing The last 2 are the same initially, but the 2nd one gets modified. The reason I broke them out is they have different backup requirements. >> Coming back to Dabo itself, the standard package download uses the >> distutils tools and includes eggs information. I haven't yet sorted >> out the eggs in my mind. > > Eggs are supposed to "just work". You package up your module, and > users can install it with a single command. I agree that they are not > the most intuitive approach, but at least people are working on > improving how they work even more. > >> Should one use SVN to place the Dabo files in site-packages directly >> or under the C:\Python25\Lib\site-packages\Dabo-0.7.2s-py2.5.egg >> directory? The eggs info is not updated, thus that the former is >> likely the more appropriate. The eggs directory can be discarded. Is >> that right? > > I would recommend deleting the eggs, and installing the Subversion > folders in site-packages. The two methods don't work together; use > one or the other. Given that installing the 'stable Dabo package' (or whatever it is called) is a reasonable first step, and then switching to the 'unstable development version' is the likely next step - I think there should be some instructions about A) why there are 2, and B) how to switch. Add link to A) at the begging of all install pages. > > I've been trying to keep the Wiki (http://dabodev.com/wiki/ > updated with the latest information for people > installing Dabo; have you looked at it at all? Was it helpful? > Anything you found that was incorrect or out-of-date? InstallationOnWindows is a lot of page. (and this is a lot of post :) It needs 2 levels of introduction. 1 something about why so many steps. (I know why, but it is a bit of a shift from the "everything in the box" world of VFP.) 2nd a summary of the steps, maybe in some sort of pseudo code. Then the details of each step. It can also have quite a bit split off. I am tempted to say make each package it's own page - maybe leave a line or 2 on the main page. These options should be on another page: "Under Linux, Mac [OS X]?, or cygwin you can simply make a symbolic link" typo: "since I we already added that to the path in the first step." As much as we hate spaces in field names and all that, I think the 'recomended' (so what is used as examples) place should be c:/Documents and Settings/carl/Application Data/Dabo Where does Visual Studio put this stuff? I also think we should assume the developer does not normally run with administrator rights - 1 or 2 of the 5 or 6 I have asked actually do that. (I tried, and gave up after a week) so something that gets updated often should not require admin. I think it is safe to assume this will be a "current user" install, not shared. The 'stable Dabo package' install should probably go somewhere else. And then there is the Dabo runtime that is needed to run Dabo apps - no clue where that should go, but not needed for this page. ok, this is enough post. I'll go back to building my XP box. Carl K _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
