From: Mentalspice <clu...@ya...> - 2000-08-03 23:16:48
|
Paragraphs are always a nice thing to use. I belive that windowmaker is the best window manager out there. Sure, it doesn't look a nice as E, but can E run on my box? NO! Why not? E needs to much RAM. I only have 16MB. WindowMaker uses a few hundred K or RAM. I can comfortably be running XMMS, abiword, Emacs, Netscape, and xpdf. Plus, windowmaker is semi GNOME compliant. IMHO KDE is ok, but not the best desktop enviroment. It has lots of features, a nice windowmanager(kwin is really, really sweet), but it is too slow. The KOM is a very nice thing, and KOffice is much more intergrated than GNOME workshop too. But to me, GNOME with windowmaker just seems mroe robust. I donm't like sawfish either. It looks nice, but it eats more RAM than it should(Besides, I don't want ot have to rewrite my windowmaker theme i made). GNOME should be the default enviroment(using kdm as the login manager). php would require loading Apache during hte install, and is that even remotley feasible? I liek the indea of defining hte interface in XML, but using javascripts(well, a special version of javascript) would be better. Just customize gecko. Add a few commands(file system stuff), and allow people to use regular old binary programs in their modules too. The back-end I was talking about would be the graphics backend--the main program would essentially just be a module loader(like inDesign...little to no features, but great module support). The display backend would be loaded alongside the installer binary(maybe as a library?). The back-end would use display modules. You simply wrote your module using XML and javascript/C, using the back-end API to draw stuff. Imagine this: <xml header stuff> <interface><!--The interface definition--> <remote src="interface.xml\> </interface> That would allwo the interface to be defined in a seperate file(for bigger modules). here is a locat interface: <xml header stuff> <interface> <local><!--tells the parser to look in this section for hte formatting--> <item type="button"><!--lets make a button--> <look="shadow" \><!--what kind of button? shadow? 3d? flat? etc--> <text>Testing</text><!--The button text--> <position x="64" y="64" \><!--the button position--> <action><!--what to do when pressed--> <exec type="program" desc="null" loc="null.app" \> <exec type="script desc="hmmm" loc="local" kind="javascript" \> </action> </local> </interface> I hope the action section was self explanitory. if not, exec executes somthing. type is what(program, script, etc), desc is hte description(Possibly to be read by the help module?), loc is the location, and kind is only usable by scripts(to tell what kind of script it is, since type has been used). Make sense? Well, the evil message board script is going to yell at me if it's any longer so... --------------------------------------------- DO NOT REPLY TO THIS MESSAGE BY EMAIL! --------------------------------------------- You have chosen to receive messages from "mentalunix" by email. Reply to this message: http://clubs.yahoo.com/clubs/mentalunix/bbsfrp?action=r&tid=mentalunix&sid=1600006580&mid=287 Unsubscribe from the Club mailing list: http://clubs.yahoo.com/clubs/mentalunix/config/change_mb_list Return to "mentalunix": http://clubs.yahoo.com/clubs/mentalunix ---------------------------------------------- Not a member? Remove yourself from this list: http://edit.clubs.yahoo.com/config/unsubscribe_mb_list?.userID=munix_devr&.groupID=mentalunix&.groupType=&.code=IVyJGMuRxG |