Hello Sean,
I haven't spent much time learning about Bazaar or HelenOS yet, and I
think I'll delay that until later when I start working with them. I have
some more existing projects to investigate, but after that I'll spend
the next week or two working on the basic design of my project. I want
to consider both an ambitious design that might be difficult to
implement and a more basic design I know is feasible.
Ideas? Questions? Complaints?
Thanks for your email. Your proposal seems to be quite ambitious and it
is good that you are doing your research and looking into different ways
people have already tried to solve similar tasks.
Just make sure that you don't end up with an overly ambitious plan and
don't over-engineer it. In that case you might have hard time to
actually implement and debug it in time.
My suggestion would be to look specifically into the use cases of the
binary data editor in HelenOS. They are primarily:
* A back-end for the debugger.
* A tool for analysing on-disk file system layout.
Fitness for other uses will be great, but has a lower priority that
these goals. Just keep that on your mind when deciding on what is
important and what is less important for finishing your GSoC project.
Also, as Vojta already noted, make sure that the implementation is
designed _for_HelenOS_, not only _with_HelenOS_in_mind_. This certainly
does not mean that the code should not be portable to other systems as well.
Just my 2 cents :) Good luck!
M.D.
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
