[shell-coding] SV: Re: Show of hands

Sounds good to me.

Neil Santos <nsantos16@xxxxxxxxx> skrev:  On 8/14/07, Mike Novia wrote:

> After re-reading that memo, sounds like a really good plan to build
> an SDK/Engine for shell coding? Im not the greatest coder, so
> handling all the hard parts are hard for me. I have more fun working
> on themeing engines, and the fun details. If anyone is interesting
> in building a project, I would love to help!

Honestly, I didn't have any specific plans when I sent that in. All I
knew at the time is that it seemed like a good idea to bring together
all the active dev teams (there being so few) and poll our resources
together to work on new stuff, and make it easier to share code for
old stuff.

For example, Chris is trying to get emerge and Vista to play nicely
with each other. I'm sure it's pretty likely that sharpE and LiteStep
are running into the same problems emerge is on Vista. That's a lot
of duplicated effort.

It's alleviated somewhat by everyone stealing code from everyone else.
But that makes the cycle a bit too long, and design decisions that
could make the code cleaner/more efficient/faster/whatever, had there
been a bigger pool of talents working together, take much longer to
get into other shells.

I've heard tell that Jaykul is working on a Vista-only shell. I'm
sure all shell dev teams can benefit from anything Jaykul comes across
in trying to do that, and vice versa. I've no interest in Vista
myself, but from what I read in emerge's forums, there're some pretty
nice problems to be dealt with on that platform (hooks and DDE support
being broken, among others).

Traditionally, here's how the whole I-steal-your-code-you-steal-mine
scenario works: dev team for shell A gets some problem on platform X
fixed. Dev team for shell B, having been working on the same problem
for some time now, sees the fix in shell A and steals it. In the
process, they incorporate changes that make that particular piece of
code cleaner/faster/more efficient. Shell A's dev team, having been
continuously working on said code snippet since the last commit, comes
up with something almost the same as what shell B's dev team has come
up with.

Duplicated effort.

What's the turnaround on a scenario like this? A couple of weeks?
Maybe a month?

I guess what I have in mind is sort of a supercharged amalgam of
shell-coding and WinShellEx. WinShellEx is a pretty good idea, but it
failed to take off. Part of it may be the fact that there are so few
shell reps available today (I remember when I routinely developed
headaches just trying to figure out which shell to try out in a
particular week). Maybe it's the NIH syndrome at work.

Personally, I haven't touched (or even looked at) WinShellEx (even
supposing its code is available) because it's a separate application.
One of my intended selling points for siaynoq is the fact that it's
small (needs about a megabyte to run) and light; having an old PC with
less RAM than most of the newer video cards, that characteristic is
important for me to preserve.

I guess I'm aiming for a sort of common repository for code used in
all the extant shells. Notification area, startup items, DDE, maybe a
VWM. It should be in the form of a library, with anyone able to join
in its development. So, the scenario becomes: shell A's dev team
fixes a problem with the notification area under platform X; they then
commit it to the common repo. Shell B's dev team takes the code,
makes it better, and commits. Shell A will have it the next time its
dev team integrates the changes.

I'm sure it won't be as easy as that the first time around. It'll
require possibly extensive changes on the each shell's development
cycle. That's why I've opened this discussion first, to flesh out
details, instead of starting work on it and then expect others to use
it immediately.

But I think it'll be worth it. If it'll cut the time we each spend on
worrying out mundane details, enabling us to work more on actually
interesting stuff (like, maybe, Mike's idea of a common theming engine
for skinnable shells), then it'll prove to be worth the effort.

We each steal code from each other (well, maybe not from me; I'm a
leech. :D) and then integrating it into our respective shells, anyway.
Why not make it easier to collaborate and get better quality code?

What do you guys think?

(I've got to stop writing stuff like this on my first cup of coffee,
and right after I wake up, at that.)
-- 
Reclaim your digital rights, eliminate DRM, learn more at
http://www.defectivebydesign.org/what_is_drm

__________________________________________________
Subscription options and archive:
http://www.freelists.org/list/shell-coding



       
---------------------------------
Sök efter kärleken! 
Hitta din tvillingsjäl på Yahoo! Dejting: http://se.meetic.yahoo.net

Other related posts: