atomos-discuss

[Atomos-discuss] Fun@#!!

[Bryan E. <for...@gm...>]

> Naturally we need JS hackers, but there's also some other critical
> items to be looked at.  You have some history with SLAX and were the
> author of MyDSL Maker (Personally my single-most-admired web-based
> tool).

Danks ^_^.  I have some ideas for a mimimalist environment within which
AtomOS could work.  S'why I was asking about the backend stuff before.

> Would you be interested in taking on an AOS-specific
> customized live CD?  Would you like to hack on the AOS code?

Sure, on both counts.  I have a bit of experience hacking on things like the
backend bash daemons in Slax and Ubuntu that handle disk recognition,
process throttling, etc (could be better done in Perl or C, but hey; not
everyone does perl, and writing it in a compiled lingo means distributing
the source).

Also, I'm almost as browser quirks fluent as this
guy<http://www.quirksmode.org/>(though I'm not a very good writer, so
no book to my credit), with one
exception: I'm better at XMLHttpRequest / iFrame / Script include wrangling
(ie: I found out good ways to fall back to other techniques if XMLHttp isn't
working and we're using JSON).  So, I'd really like to have a stab at
debugging cross-browser compatibility issues.

I'd also like to have a hand in separation of design / presentation /
structure / content / behavior of the OS (I've become pretty practiced in
it, so far).

Oh, if anyone wants to see some stuff I've done recently:
http://wwwdev.wharton.upenn.edu/alumni (what I do at my real job - on the
development server 'cos it won't be live 'till monday.  Take a look at the
JS for the navmenu and the tabbed boxes; they're great examples of how I do
JS OOP).

http://www.fordi.org/comics (the neat little dock at the bottom is my work;
the pages are stuff I like to look at.  For some reason, I'm not fond of
bookmarks.  I'm actually working on it; a '+' symbol to add a link, and a
nice interface for choosing the image)
-- 
Bryan Elliott
for...@gm...
http://www.fordi.org

Re: [Atomos-discuss] Fun@#!!

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

Bryan, thats some nice JS code. I can't do anything nearly that useful. I
did do some metaprogramming to get the Process system working, and thats
probably the best JS code you can find for me.

On 1/7/07, Bryan Elliott <for...@gm...> wrote:
>
> > Naturally we need JS hackers, but there's also some other critical
> > items to be looked at.  You have some history with SLAX and were the
> > author of MyDSL Maker (Personally my single-most-admired web-based
> > tool).
>
> Danks ^_^.  I have some ideas for a mimimalist environment within which
> AtomOS could work.  S'why I was asking about the backend stuff before.
>
> > Would you be interested in taking on an AOS-specific
> > customized live CD?  Would you like to hack on the AOS code?
>
> Sure, on both counts.  I have a bit of experience hacking on things like
> the backend bash daemons in Slax and Ubuntu that handle disk recognition,
> process throttling, etc (could be better done in Perl or C, but hey; not
> everyone does perl, and writing it in a compiled lingo means distributing
> the source).
>
> Also, I'm almost as browser quirks fluent as this guy<http://www.quirksmode.org/>(though I'm not a very good writer, so no book to my credit), with one
> exception: I'm better at XMLHttpRequest / iFrame / Script include wrangling
> (ie: I found out good ways to fall back to other techniques if XMLHttp isn't
> working and we're using JSON).  So, I'd really like to have a stab at
> debugging cross-browser compatibility issues.
>
> I'd also like to have a hand in separation of design / presentation /
> structure / content / behavior of the OS (I've become pretty practiced in
> it, so far).
>
> Oh, if anyone wants to see some stuff I've done recently:
> http://wwwdev.wharton.upenn.edu/alumni (what I do at my real job - on the
> development server 'cos it won't be live 'till monday.  Take a look at the
> JS for the navmenu and the tabbed boxes; they're great examples of how I do
> JS OOP).
>
> http://www.fordi.org/comics (the neat little dock at the bottom is my
> work; the pages are stuff I like to look at.  For some reason, I'm not fond
> of bookmarks.  I'm actually working on it; a '+' symbol to add a link, and a
> nice interface for choosing the image)
> --
> Bryan Elliott
> for...@gm...
> http://www.fordi.org
> -------------------------------------------------------------------------
> 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
>
>
>

Re: [Atomos-discuss] Fun@#!!

[Scott E. <ps...@gm...>]

On 1/8/07, Weirdbro <wie...@gm...> wrote:
> Bryan, thats some nice JS code. I can't do anything nearly that useful. I
> did do some metaprogramming to get the Process system working, and thats
> probably the best JS code you can find for me.

I'd suprised if that remains true for long - you took me off gaurd a
few times with your JavaScript.  I'm not that great at JS coding yet,
but your solution for creating processes was elegant and done
extremely quickly.  Quite literally no-small-feat.  =)

I'm still torn as to whether or not to include that code.  I'd really,
really like to since it'd be in keeping *nix style system/software
design.  As you pointed out it though, it might not be the best thing
for AOS to have.  Particularly since we don't really need it atm.

(Incidentally, the same is true of the combined I/O terminal you and
your friend came up with.  Very cool stuff that I'd love to see AOS
using eventually.)

Your Pure-JS build system and OOP kernel changes will be integrated
with the 0.1.0 release I'm planning to get out this month.

There's no need to be modest.  ;-)

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

'"A lie can travel halfway around the world while the truth is putting
on its shoes."

  - Mark Twain

Re: [Atomos-discuss] Fun@#!!

[Scott E. <ps...@gm...>]

On 1/7/07, Bryan Elliott <for...@gm...> wrote:
> Danks ^_^.  I have some ideas for a mimimalist environment within which
> AtomOS could work.  S'why I was asking about the backend stuff before.

Glad to hear that.  I've played with creating customized distros, and
while it truly is fun and very educational, it's also quite time
consuming.

Love to hear what you think such an environment should look like.
I've been thinking lately to use the LFS project
(http://www.linuxfromscratch.org/) as a base for the image though I'm
not sure it'd be worth the effort just yet.

> > Would you be interested in taking on an AOS-specific
> > customized live CD?  Would you like to hack on the AOS code?
>
> Sure, on both counts.  I have a bit of experience hacking on things like the
> backend bash daemons in Slax and Ubuntu that handle disk recognition,
> process throttling, etc (could be better done in Perl or C, but hey; not
> everyone does perl, and writing it in a compiled lingo means distributing
> the source).
>
> Also, I'm almost as browser quirks fluent as this guy (though I'm not a very
> good writer, so no book to my credit), with one exception: I'm better at
> XMLHttpRequest / iFrame / Script include wrangling (ie: I found out good
> ways to fall back to other techniques if XMLHttp isn't working and we're
> using JSON).  So, I'd really like to have a stab at debugging cross-browser
> compatibility issues.

Absolutely wonderful.  =)

I'm familiar with the quirksmode site.  Lol.  'Been visiting it
on-and-off for years.  Definately good to have a x-browser developer
on board who's familar with some (of the seemingly zillions of)
browser quirks.

> I'd also like to have a hand in separation of design / presentation /
> structure / content / behavior of the OS (I've become pretty practiced in
> it, so far).

How do you see the seperation of the project components?  I'd like to
delve into this topic deeper - it could have a serious impact on the
way the project is developed.  I've had some difficulty organizing and
documenting; suggestions would be more than welcome.

> Oh, if anyone wants to see some stuff I've done recently:
> http://wwwdev.wharton.upenn.edu/alumni (what I do at my
> real job - on the development server 'cos it won't be live 'till monday.
> Take a look at the JS for the navmenu and the tabbed boxes; they're great
> examples of how I do JS OOP).
>
> http://www.fordi.org/comics (the neat little dock at the bottom is my work;
> the pages are stuff I like to look at.  For some reason, I'm not fond of
> bookmarks.  I'm actually working on it; a '+' symbol to add a link, and a
> nice interface for choosing the image)

Nice clean code.  I love it, and the dock in particular.  Has me
wondering if a version could be implemented for the AOS desktop.
Along the lines of an applet maybe?

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

'"A lie can travel halfway around the world while the truth is putting
on its shoes."

  - Mark Twain