Go to the FreeLists Home Page Home Signup Help Login
 



Browse shell-coding: This Month's ArchiveMain Archive PageRelated postsPrevious by DateNext by Date

[shell-coding] Re: [Common Elements] Just a thought

  • From: "Brandon Sneed" <bsneed@xxxxxxxxx>
  • To: <shell-coding@xxxxxxxxxxxxx>
  • Date: Thu, 29 Aug 2002 12:35:55 -0500
you get it that time?  hehe. slooooow down.
  ----- Original Message ----- 
  From: Donelle Sanders 
  To: shell-coding@xxxxxxxxxxxxx 
  Sent: Thursday, August 29, 2002 10:48 AM
  Subject: [shell-coding] Re: [Common Elements] Just a thought


  <Quote

  frankly, i'd love to see something from the ground up start, the bare 
essentials for a shell. common items such as a plugin interfaces, like windows 
shell extensions (maybe without the miserable com crap), a common 
taskbar/system tray implementation, or set of api's to create one, and some 
basic desktop/skinning api's. 

  /Quote>



  Mark:

  Raptor is  that very idea, it encapsulates all the so called "redundant" code 
that is common to all shells and provides addition incenitatives along with it. 
I'm in the process of extending it even further (*matrice64 mutters something 
about finishing up his code at work to get some extra free time) but I've been 
very busy at work on a big project -application- for the government. I have 
some code written for various things you suggested I just haven't found enough 
time to stress test the code before I upload it to sourceforge. I have alot 
going on in trying to get things all together like getting my site for example. 
I have couple of people now helping me with this, I could if your interested, 
send you the software map or plan if you will on about where raptor is going 
and all those "documented" things. 


  -Matrice(64)


  >From: "Mark Belles" 
  >Reply-To: shell-coding@xxxxxxxxxxxxx 
  >To: 
  >Subject: [shell-coding] Re: [Common Elements] Just a thought 
  >Date: Thu, 29 Aug 2002 09:59:03 -0500 
  > 
  >i've been working on a shell for work, unfortunately it's not open source 
due to the fact it's for my company... yada yada, but i digress. i've been 
following litestep and it's build for quite some time, just to learn how most 
of the stuff is done. hooks, and such. it's been my guiding lite so to speak. 
frankly, i'd love to see something from the ground up start, the bare 
essentials for a shell. common items such as a plugin interfaces, like windows 
shell extensions (maybe without the miserable com crap), a common 
taskbar/system tray implementation, or set of api's to create one, and some 
basic desktop/skinning api's. it's one thing to have these really kick ass open 
source shells floating about to look at, and it's another to have a really 
solid code base to look at/learn from. i know i've seen stuff done about 20 
shades of different on pretty much every idea involved with shells, from timers 
to threads searching for active windows. lol. i think with the knowl edge 
that's out there, and most of you guys know what you'd want in this stuff to, 
something really effective could be assembled in no time. and i mean nothing 
based on current implementations. just brainstorm and start fresh just to see 
what comes of it! it could be really fun. if it bombs, no biggie, we've still 
got the current builds to play with, but if not maybe others will see the new 
code and wanna run with it. ya just gotta start somewhere ya know? i keep 
hearing ppl that would like to see something common started, but i'm really 
curious who would be down with helping on something like that. if anyone is 
interested holla back and maybe we can start toying with some ideas. 
  >laterz 
  >-goose 
  > ----- Original Message ----- 
  > From: Donelle Sanders 
  > To: shell-coding@xxxxxxxxxxxxx 
  > Sent: Thursday, August 29, 2002 8:54 AM 
  > Subject: [shell-coding] Re: [Common Elements] Just a thought 
  > 
  > 
  > 
  > I don't think raptor is a solution, Im using raptor because I liked the 
idea and I want to continue on with it. Yes rewrites would have to be made to 
support this idea but with any change like this, rewrites are going to happen 
regardless. I don't expect people to jump on the bandwagon with me Im just 
doing what I love to do and those that are interested can follow. While we are 
on the subject I invented a sort of "patch" for certain shells to interact with 
raptor with having to change "much" of there current implementations. This 
service is I call "Connectors" are more less proxies or a gateway that knows 
how to talk to say "Shell A" and raptor. I thought is would be facinating to 
see "Shell A" get information seemlessly as if it implemented the require 
interfaces for raptor. It was just an experiment that I was trying out for 
geoshell r4.9 , I had gotten the idea from ximian gnome's connector for ms 
exchange server. But anyhoo, I do appr eciate your opinion ;-) . (I'm glad 
somebody is thinking in the same direction as I), and I know this is hobby for 
most people but to me doing this is like the greatest gift God has given me and 
thats to code. 
  > 
  > 
  > -Matrice(64) 
  > 
  > >From: Kevin Schaffer 
  > >Reply-To: shell-coding@xxxxxxxxxxxxx 
  > >To: shell-coding@xxxxxxxxxxxxx 
  > >Subject: [shell-coding] Re: [Common Elements] Just a thought 
  > >Date: Wed, 28 Aug 2002 17:33:38 -0400 
  > > 
  > >I agree completely. It is my hope that this mailing list will help 
  > >to bring 
  > >about better cooperation between shell developers and better 
  > >integration 
  > >between shells. Although you didn't mention it specifically, based 
  > >on your 
  > >last post I assume your solution would be Raptor, or something 
  > >similar; 
  > >however, Raptor is not the solution. Raptor went about it the wrong 
  > >way. 
  > >Shells have to be completely redesigned to work with Raptor and that 
  > >is 
  > >why it failed. I feel the best way to achieve better shell unity is 
  > >to do it 
  > >incrementally and in a way that won't require major rewrites of 
  > >existing 
  > >code. 
  > > 
  > >-- 
  > >Kevin Schaffer 
  > > 
  > > 
  > > 
  > >__________________________________________________ 
  > >Subscription options and archive: 
  > >http://www.freelists.org/list/shell-coding 
  > 
  > 
  
>------------------------------------------------------------------------------ 
  > Chat with friends online, try MSN Messenger: Click Here 
  > __________________________________________________ Subscription options and 
archive: http://www.freelists.org/list/shell-coding 


------------------------------------------------------------------------------
  Chat with friends online, try MSN Messenger: Click Here
  __________________________________________________ Subscription options and 
archive: http://www.freelists.org/list/shell-coding

Other related posts:

  • [shell-coding] [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought
  • [shell-coding] Re: [Common Elements] Just a thought




  • [ Home | Signup | Help | Login | Archives | Lists ]

    All trademarks and copyrights within the FreeLists archives are owned by their respective owners.
    Everything else ©2008 Avenir Technologies, LLC.