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: "Donelle Sanders" <donelle_sanders@xxxxxxxxxxx>
  • To: shell-coding@xxxxxxxxxxxxx
  • Date: Thu, 29 Aug 2002 13:54:32 +0000


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 appreciate 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

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.