[Dynapyide-developer] Re: [Dynapyide-developer]

[<hv...@ya...>]

Hey!!!

A very big welecome to new guy (uhm err did I miss the
name - sorry I'm so distracted) - I'll get that
straight once we see what you can do :)

AND Kevin!!! nice to see you back!!! Your re-enntrance
made my mind get rolling a bit... :)

Actually we've decided to adapt an componentbased
architectural approch and to differ out GUI from the
core system. I have 3 specs done that outline this,
but I think the best thing is if you get the whole
pre-alpha package from David, which include these.

I've mainly learnt about CBD (Component Based Design)
and COP (Compoinent oriented Programming) from the
Apache Jakarta/Avalon project (
http://jakarta.apache.org/avalon/index.html ), but has
also taken up a contact with the Bebop - which is a
framework for transparently integrate Javabeans and
EJB technology as components - project developer. The
thing is Avalon is basicly a framework for servers and
Bebop ( http://sourceforge.net/projects/bebop ) is
transisational between desktop and server, while the
previous is way more documented and in use than the
latter one that didn't even was published till we
notified the author. Please research which one best
serves our purpous once you've read the specs if you
would...

concerning the DTD's I'm a bit curious why you think
we would need DTD'd for the scripting languages? I'm
not so well-researched on these yet, so maybe I missed
something, but isn't DTD's only for Markup languages?
Or maybe you have an brilliant idea that I haven't
figured, please explain further...

BTW I'm, a purist and I say we simply download every
DTD on W3C from the HTML 3.2 and later. Keep as close
as possible to the most de facto standard source
unless they're way to much overdue or lacks something
in particular.

concerning what is the core of the application I'd
rather say a Javascript Parser AKA Mozilla Rhino
wrapped up as a component. I'd say the XML parser is
of course the natural second. My view is this way:

- ECMA/Javascript is the glue between the components
and everything with the application is initiated by a
loading script. For the application to even start the
Javascript parser is crucial.

- XML is used for static settings and for making the
the core functionality of the documents DOM handling.
(You see I'm all with you on using XML for the DOM
techniques outliners)

I admit this is nowhere in the specs yet, but belive
me: I have the thoughts clear on this - its all in the
target audiance best interest.

I can't look much at the source right now. I'm having
big diffuculties with getting JRE to run on my current
installation or even to reinstall it - I'm working as
fast as I can to make sure my upcomming clean boot
installation will be as simple as possible in advance.

But anyways, I'm not much of a advanced code guy, so
maybe your lucky that I can't mess with it :P. I'll
continue the specs wrtiting meantime and leave the
coding solely to you others. (currently reading my
eyes out on XML, DTD's and parsers - I'm living and
breathing it soon ;)

Please take a look at http://xml.apache.org if you
will. I went through W3C looking for their official
Java implementations of DOM parsers, and via
Sourceforge actually come to the conclution that any
such source has been moved to Apache. ECS and Xerxes-J
looks like well worth for reuse I think (but I'm still
not the coding expert here)

I hopefully will havre more on this by the end of the
weekend. it all depends on the swedish teams
advancements in the FIFA WC :P

Henrik 

_____________________________________________________
Följ VM på nära håll på Yahoo!s officielle VM-sajt www.yahoo.se/vm2002
Håll dig ajour med nyheter och resultat, med vinnare och förlorare...