Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 6769] sorcery show-held requires root privilegues

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT metalab.unc.edu
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 6769] sorcery show-held requires root privilegues
  • Date: Thu, 3 Jun 2004 00:48:35 -0400

http://bugs.sourcemage.org/show_bug.cgi?id=6769

acedit AT armory.com changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED



------- Additional Comments From acedit AT armory.com 2004-06-03 00:48 -------
show-held is now in gaze, please verify.

As a matter of preference its difficult to decide where to put
functionality. Given any script we can point out several places
where we break our conceptual model. If we define gaze as the
one true resource for peering into the system on a read-only level
one could point at "prune" (which is going to move out of gaze btw).
Simlarly one could point out that summon now and gaze both have access
to source and source_url dumping. So other opinions on where stuff ought
to go is good, we may not use them, but hey, its better than nothing.

As for a general guideline for _user_ interfaces.
if it has to do with read-only looking at the system its in gaze
(hence the move)
if its a codex manipulation thing its scribe
if its for removing spells its dispel
if its for installing stuff its cast
if its for spiffy high level menu or "big" stuff its sorcery
if its for cleaning anything, or restoring order its cleanse
if its for downloading spells its summon

Granted a lots of crossing over will occur, both scribe and sorcery
do downloading, (and they'll be made to use the same interface as summon)
summon does some of the same things as gaze (and more), so we'll just have
to feel our way through.

it may be worth considering to have a seperate tool for "state manipulation"
which could change spells to held or not held, muck around with depends
and run the appropriate cast commands. But thats down the road.

Anyways, ideas and different ways of thinking are beneficial, and its not
your fault martin.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




Archive powered by MHonArc 2.6.24.

Top of Page