Re: [Atomos-discuss] New Update

[Weirdbro <wie...@gm...>]

Which executable commands don't work? I was sure I had fixed most of them,
the only one I don't have is `cd`, since it isn't an executable, but a real
WASH command.
If you've noticed, I've implemented a environment variable system where
processes, if they use the this.exec command, copy their env variable sinto
their child.

I didn't really think about a root process. How do you think it should work,
why is it necessary to be able to access it, and what would other processes
use that for?

Processes, because of the inability in our current system to safely remove
events, need to have a function that is called when it is killed. It needs
to kill its own process when it finishes running, since we have no way of
knowing whether it still has events attached, keeping it from being garbage
collected by javascript.

The build system, when it moves rom into files, it doesn't escape their
contents, leaving '<' and '>' to be interpreted by Firefox as elements,
which absolutely messes up their innerHTML, because the stuff between < and
> is interpreted by firefox as element attributes, and has ="" added after
every space. That was incredibly hard to figure out, and I just added about
2 lines of code to the ROM builder to make sure it escapes stuff before it
writes the file.
Also, I had to write some DOMFS functions to handle the same things for
reading and writing DOMFS files from Javascript.

Have you thought about reimplementing hte build system in Javascript? It
fits with Atomic OSs philosophy, is much more cross-platform than a Perl and
BASH setup, and it just cleaner, at least if we reimplement it cleaner.

We really need to write the IO objects and add tons of functions to DOMFS,
so that even if it is based off of widgets, they should never have to use
widget functions ever outside of writing kernel code.

-Weirdbro

On 9/26/06, Scott Elcomb <ps...@gm...> wrote:
>
> On 9/25/06, Weirdbro <wie...@gm...> wrote:
> > Here's my latest version:
> > http://www.weirdbro.com/src2.tar.gz
> >
> > I didn't finish adding objects to the kernel, but I added a Process
> class,
> > moved Wash out of the kernel, fixed a glitch in the build system,
> > and started moving the commands from wash out to binaries. `cd` needs to
> be
> > readded to Wash.
>
> Processes are a huge step forward.  *Thank you*
>
> Most of the executable commands no longer work, but that's the way it
> is.  We also need garbage collection in the process object.  When
> child processes complete their code, they need to be "killed" so we
> don't end up using unnecessary resources in the client browser.
>
> Based on your code and style of programming, I think a Kernel object
> is in order...  Given that, I'd also suggest renaming the current
> global Process object to Kernel.processZero or some other name
> indicative of the Root Process found on *nix type systems.
>
> Uhmm, what glitch did you find in the build system?  lol.  I'm still
> tied up looking at your code and trying to figure out the
> implications...  Thanks again!
>
> --
> Scott Elcomb
> http://atomos.sourceforge.net/
> http://search.cpan.org/~selcomb/SAL-3.03/
> http://psema4.googlepages.com/
>
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
>
>   - Benjamin Franklin
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Atomos-discuss mailing list
> Ato...@li...
> https://lists.sourceforge.net/lists/listinfo/atomos-discuss
>