Hi all,

Over the last couple weeks I've been rushing commits on a personal
project, Atomic OS.  It's an in-browser linux-like metaphor that I
hope to one day offer other developers as a SPA (Single Page
Application) building library / platform.

A student recently approached me, offering to work on an old version
(the one with a screenshot on the Google Code link in my signature)
for his CompSci project.  That code is old and awful.  After speaking
with the student, he's agreed to help work on a new version.

Due to the workload I'm responsible for in my day job - and my desire
to get something usable to the student as quickly as possible - I've
been committing updates without thoroughly checking for code quality.
The plan being to first get things working, then to make the code
clean and efficient after.

I'd like to think my JS skills have improved since my first attempts
on Atomic OS, but I'm fairly certain I'm still making some basic
mistakes.  At this point I'm not looking for a full code review; I'm
planning to do one this weekend.  In the meantime though, I wonder if
anyone here might point out any jaw-dropping (or face-scrunching)
errors they may notice.

Please ignore the eval calls - IIRC there are 4 and two of them will
be removed in short order.  I know they're evil and fully intend to
replace the others if I can. (If I can't figure out how, I'll start a
new thread ;-)

The prototype's sources can be found at:

  <https://github.com/psema4/Atomic-OS/tree/master/prototype/scripts>

The relevant files are main.js and the those files in the hx/ (core
classes) and bin/ (shell commands) folders.

To get an idea of how things fit together, or to read the docs (such
as they are), please see the "reference implementation" at
<http://psema4.github.com/Atomic-OS/>

[There's plenty left to be implemented; the lack of unit tests and
universal path parsing are my two biggest gripes right now.  If you
run into any trouble using the demo, please feel free to email me
off-list.  For several commands, using a full, absolute path will
solve the problem]

With thanks,
- Scott.


-- 
  Scott Elcomb
  @psema4 on Twitter / Identi.ca

  Atomic OS: Self Contained Microsystems
  http://code.google.com/p/atomos/

  Member of the Pirate Party of Canada
  http://www.pirateparty.ca/

-- 
To view archived discussions from the original JSMentors Mailman list: 
http://www.mail-archive.com/[email protected]/

To search via a non-Google archive, visit here: 
http://www.mail-archive.com/[email protected]/

To unsubscribe from this group, send email to
[email protected]

Reply via email to