On Feb 9, 2004, at 5:00 PM, Richard Gaskin wrote:
Rev objects can be atomized down to individual properties and scripts, and
reassembled again in nearly infinite variety.
What specifically is needed, and what are the challenges of building it?
David:
Not sure but I think Chipp last brought up the issue of multi-developer support. I guess as more people write business apps with Runrev, multi-developer support will be requested more.
Brian:
Developers that use CVS, Subversion etc. often use it on solo projects as well! It's very empowering to be able to "turn back the clock" on all or part of your code. IBM Visual Age for Java which has a "repository" where project code could be freeze-dried, versioned, and saved for later use or inspection. Good stuff, even working solo.
Richard:
If there were a version-control plugin for runrevI would surely be a customer! I believe some ideas have been kicked around on-list for mapping Rev stacks into a version control system. Some hurdles one would be looking at are:
- lack of specific hooks in IDE for controlling the script editor, the application browser, and property inspector.
- background groups - are they placed or not placed? How many cards are they placed on? I found trying to envision a stack as a filesystem hierarchy then background groups get confusing.
- proprietary binary stack format - depending on perspective it may be a non-issue because we need to have version control from within the IDE not from the filesystem.
-- Alex Rice | Mindlube Software | http://mindlube.com
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
