|
From: <hv...@ya...> - 2002-06-06 13:09:20
|
OK, first my biggest and most gentle excuses for my very long absence -
in presence but not in mind though. My stay at the hospital, the lovely
summer heat we've had here the last couple of WEEKS (sweat!) and of
course the Soccer WC (probably shouldn't go further into that one
considering our split loyalties - but there is still hopes for us both
:P ) got to me and I just have to admit I had to get my priorities
sorted.=20
Now I'm trying to get enough grip of how Bebop works to know what to ask
Tim about it. I'm far from sure Bebop is the right framework. I do like
the idea of reusing Sun's JavaBeans and EJB's (although EJB still seem
like overkill yet), on the other hand they're not Open Source and I'm a
bit of a purist - not for the sake itself but rather for any future
issues. Any thoughts on that?
Anyways, David, did you get the 3 RTF-files AMBITION.RTF, ARCITECT.RTF &
DEFINIT.RTF and did you mean you have them spellchecked?
Purist I said. Well, as long as possible I think we should stick to
existing and defacto standards - especially W3C's.=20
For example I propose we aim to use XML as grounding for all Documents
and then DTD's to format them for the various HTML, XHTML and XML
variants - XML is after all specified to be general and edxtensible to
cover all these markup languages(going as far back as to SGML seems
oldish and overkill too).
By that the only DOM we need to have inbuilt support for is the latest
XML DOM I figure (and having a good DTD-compatible validating parser).
And any thinkering I've done leads that the most genral common thing for
thequniques we want to cover with DynAPI <!-- IDE --> is the DOM. My
research leaveas that any middleware done in Java that were initiated by
W3C on a DOM parser ended up within the Apache Java/Jakarta projects.
By that, what would you feel is the most urging specification to get
down in writing? Being a bit distracted away from what I was at, I kind
of lost the track on what's next.
OK, mainly just wanted to give a lifesign and that I'm still onto
working further with the project. I don't expect myself to have much to
do with the coding of the inner workings of the IDE("the core" system),
but rather to get working on the a bit with a default GUI if any coding.
Henrik
> -----Ursprungligt meddelande-----
> Fr=E5n: Mo...@sp... [mailto:Mo...@sp...]=20
> Skickat: den 19 maj 2002 12:37
> Till: henrik v=E5glin
> =C4mne: RE: Beebop
>=20
>=20
> Henrik,
>=20
> I can read rtf alright, don't worry.
>=20
> For the time being I have been doing a quick splashscreen for=20
> the IDE. I decided to start checking out all this javaBeans=20
> stuff, so I'm turning it into one at the moment.
>=20
> Hows your trip going? hope you have a good time.
>=20
> BTW, I have the bebop source now... at work (yeah, right very=20
> useful...) and been looking at it. It certainly looks=20
> impressive, but i could do with a bit more documentation than=20
> the javadocs i produced...
>=20
> probably for the proper release tim will have done some.
>=20
> take care,
>=20
> david.
>=20
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.1
> GCS/CC/IT/L/MU/P/S/AT d? s++: a-- C+++ U--- P+ L E-- W+++ N++=20
> o+ K? w+++=20
> O? M V? PS+++ PE-- Y+ PGP- t+ 5 X+ R tv+ b+++ DI+++ D G e++=20
> h! r y+ ------END GEEK CODE BLOCK------
>=20
>=20
>=20
> --
> Personalised email by http://another.com
>=20
|
|
From: Kevin D. <one...@ho...> - 2002-06-13 04:08:21
Attachments:
xp.zip
|
Sorry for the long absence but was in a tornado of work and projects since
September. Been in the dark working my ass off for backend web systems.
Once again I can spare some time for this project.
I've kept up on all the messages but am not sure where everything stands -
where we are and where this project has started heading towards since I hear
alot about EJB and Bebop?
Since I don't know exactly where everyone is I'll start at where I left off
which was the beginning.
Let's keep the Class specs but let's now focus what should be the heart
of this app. I think an XML parser should be the center of this program
since it will provide us with the ability to parse the HTML - XML - and get
into the nitty gritty of parsing the Javascript code. The XML parser also
fits in nicely with the ability of this program to be easily updated and
actually personalized. I mean by this is that we can create XML Docs that
spell out the HTML 4.+ specifications so they can be easily altered if the
specification changes - an XML Doc to spec the DynAPI so it can be easily
altered when it changes - Javascript Specs in XML format - and even an XML
doc so the users can create there own Code Libraries. All of this will be
done by XML DTD's that will be parsed by the XML parser. The program will
of course autogenerate the XML code and a GUI will be used to alter specs.
This way we don't have to hard code the specs of any of these things and the
program will run off of the DTD's and we can change the XML docs easily
whenever the specs or versions change.
Here's the XML parser written in java - open source. (files attached)
Kevin D.
ks...@ho...
|
|
From: <hv...@ya...> - 2002-06-13 09:23:40
|
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... |