dynapyide-developer — Developers list concerning issues with developing the DynAPI IDE

RE: [Dynapyide-developer] Large file bug fixed.

[Creighton K. <cki...@ho...>]

Henrik ,
I meant the JavaScriptTokenMarker, sorry.  I also do not agree with =
that
highlighting scheme.  We need to go with something standard and easy to
read.  Most people who have used IDE's note that they highlight special =
code
in color or bold.  They do tend to put all the code in one color and =
only
bold keywords (except black with some IDEs).  We can change the colors =
of
the JavaScript keywords to some other colors than what we used in the =
HTML.
But I think in general the normal code and text needs to stay in black =
on
white for ergonomic and consistency reasons (We may be able to have a
bgcolor of light gray though for the JS area I not sure right now).  I =
spent
some time using many different IDE's and find that they handle thing =
pretty
much the same way.  I do not think we want to go and change this =
because it
may cause problems with users not being comfortable in the environment. =
  In
fact I know of only one that highlights code differently and that is VS =
on
ASP pages.  The ASP background is highlighted in yellow.
=20
Creighton =20
=20
-----Original Message-----
From: Henrik V=E5glin [mailto:hv...@ya...]=20
Sent: Tuesday, February 19, 2002 12:27 PM
To: dyn...@li...
Subject: RE: [Dynapyide-developer] Large file bug fixed.
=20

Now I'm confused... what does javaTokenMarker have to do with this...
shouldn't that be JavaScriptTokenMarker?
=20
Anyways my point is not so much on what is highlighted as the color the =
text
get.
I think we should use different colors for HTML and Javascript keywords
markup. I would like to see everything in javascript getting one color,
javascript keywords in bold in that color and HTML-tags being one other
color. Maybe values no matter where they're at can have one unified =
color...
=20
As said before, my intension is purely to be helpful to the =
development, not
to dicourage - and not to confuse.
=20
Thanks so much for your feedback on the docs. I'll put efforts more =
with the
into then - I considerd it to be of a minor importance actually, so it =
was
good i got your point. Second priority I'll put on developing and =
outlining
the package description.
=20
Henrik
=20
-------Original Message-------
=20
From: Creighton Kirkendall <mailto:cki...@ho...>=20
Date: den 19 februari 2002 13:47:11
To: dyn...@li...
<mailto:dyn...@li...>=20
Subject: RE: [Dynapyide-developer] Large file bug fixed.
=20
Henrik, the java code is highlighted.  However I only highlighted =
keywords
like new, function, this, var, for, while, any literal (string in =
quotes),
and comments (complete list in the JavaTokenMarker.java).  I have =
different
colors for each type of keyword.  This is kind of a standard way of
highlighting code, so I am little confused.  Do you have another way =
you are
suggesting, if so please outline it and I will try to accommodate it.  =
I
have included a screen shot demonstrating all the keywords and their
highlighting.  We can highlight DynAPI key words in our own =
highlighting.
Also about the specs, hold off on them for a little while.  We worked =
on
some of the HTML wysiwyg part this weekend and I need to figure out how =
this
all works into the overall design.   I have looked over the =
documentation
and I like the package description and some of the design stuff.  =
However I
think that for right now the intro is the driving force of development
because it out lines the goals.  As the application grows we will have =
to
grow the implementation documentation, because right now it bares no
resemblance to the architecture describe in the documents.  Don't get =
me
wrong it will in the long run but right now we are concentrating on =
getting
pieces working so we have something to work with.
P.S I may be mistaken but isn't new a javascript keyword???
Creighton Kirkendall
-----Original Message-----
From: Henrik V=E5glin [mailto:hv...@ya...]=20
Sent: Monday, February 18, 2002 3:01 PM
To: dyn...@li...
Subject: Re: [Dynapyide-developer] Large file bug fixed.

I fired up the second bug-fixed version (after compiling it - BTW I'm =
using
the newest Java SDK 1.4 for all my compiling and the same version to =
run)
I like the improvements I see. I like the progress a lot. hehe, you've =
even
come as far as to create at least one new class. However, I'd still =
like to
see the javascript code colored. And why is the word 'new' in the =
inline
javascript the same blue color as the main HTML code. It's good its =
colored,
just not ass if it was as javascript key word. Is it possible to get an =
own
color highlightning for DynAPI reserved words, like 'DynAPI' and =
'dynlayer'
and maybe even theit methods?
Hope I'm not dicouraging your efforts by pointing out these things. My
intensions is the total opposite - to encourage the development.
Yes, if I only knew how I could get CVS set up I would try, but its =
really a
chore for me to understand what I need to do as admin to set it up. I =
think
Jitu (Jitendra) knew how to work it, I hope he's still around so he can
instruct me...=20
BTW can you guys give me a clue as to how you find the new specs. Am I
keeping up with you? What specs would you need me to work on next? =
Please
let me know...
Henrik=20
-------Original Message-------
From: Creighton Kirkendall <mailto:cki...@ho...>=20
Date: den 18 februari 2002 17:32:10
To: 'dyn...@li...'
<mailto:dyn...@li...>=20
Subject: [Dynapyide-developer] Large file bug fixed.
I have fixed the problem with large files. It was a very simple and =
stupid
mistake on my part. But non the less here is the new version. Henrik we
need to get the cvs thing worked out. I think I may try to post =
something
to it tomorrow. Until we have code out there it is going to be hard to =
get
other developers.

Update:
Jason and I got a HTML preview pane working but have yet to intergrate =
it
with the editor.=20

Crighton Kirkendall





=20
=20
=20
 <http://www.incredimail.com/redir.asp?ad_id=3D309&lang=3D9>   =
IncrediMail -
Email has finally evolved -
<http://www.incredimail.com/redir.asp?ad_id=3D309&lang=3D9> Click Here=20
=20


=20
=20
=20
____________________________________________________
 <http://www.incredimail.com/redir.asp?ad_id=3D309&lang=3D9>   =
IncrediMail -
Email has finally evolved -
<http://www.incredimail.com/redir.asp?ad_id=3D309&lang=3D9> Click Here=20

[Dynapyide-developer] Starting a Structure

[DeWeese, J. <jde...@ba...>]

I think we need to set up cvs soon.  Creighton and I have proved that the
general concept of what we want is possible, now I think we need to start
restructuring the code we have so that we can code indepenently without
stepping on each others code.  He is a basic plan.

1.)  We put the jedit_syntax in a jar file called jedit_syntax.jar,  that
way we can swap in thier updated code into our project easily.
2.)  We put all of our code into a package called dynHTML.jar
3.)  We restructure the classes...
	WrapperApp becomes  dynHTML
	WrapperAppFrame becomes dynHTMLFrame with some changes ...
		All the editor code is put into a class called dynTextEditor
		All the browser code is put into a class called dynGuiEditor
	WrapperAppFrame_AboutBoxPanel1 becomes dynHTMLFrame_AboutBox

I know there is design docs with a layout, but we need to grow into it, this
would be something simple that we could continue the learning phase of our
development with.  I is going to get hard to continue to e-mail code back
and forth, we will start to confuse versions of code.

[Dynapyide-developer] Editor with Browser

[DeWeese, J. <jde...@ba...>]

All -

	Here is Creighton's newest editor with my browser added in.  There
is lots of problems with it right now, but the purpose is to show it can be
done.  Two problems that I am aware of are when you change from browser to
editor the updates do not get made unless you manually save and that if you
try to CANCEL a view change you get stuck in a loop.  Easily fixed I just
didn't have the time and I'm trying to get Creighton the consolidated code
before he makes another update.

[Dynapyide-developer] More Bugs Fixed

[Creighton K. <cki...@ho...>]

I have fixed some more bugs. Henrik, I fixed the problem with </a> and I
fixed a problem with multi line tags.  

Creighton

[Dynapyide-developer] Large file bug fixed.

[Creighton K. <cki...@ho...>]

I have fixed the problem with large files. It was a very simple and stupid
mistake on my part.  But non the less here is the new version.  Henrik we
need to get the cvs thing worked out.  I think I may try to post something
to it tomorrow.  Until we have code out there it is going to be hard to get
other developers.

Update:
Jason and I got a HTML preview pane working but have yet to intergrate it
with the editor.  

Crighton Kirkendall

RE: [Dynapyide-developer] Splash Screen

[DeWeese, J. <jde...@ba...>]

I agree with name #5 and screen #5

Jason

-----Original Message-----
From: Creighton Kirkendall [mailto:cki...@ho...]
Sent: Wednesday, February 13, 2002 1:40 PM
To: dynapi ide
Subject: RE: [Dynapyide-developer] Splash Screen


So Javi does not have to implement all of the names in splash screens I
propose a vote.  Below are the entries. Feel free to add more.  The one that
wins will be our working name.  This does not mean that we will not change
it at a later date.  But it will make it a lot easier to build cvs tree and
splash screen for if we have a name.

1. Dynapy <!--IDE-->
2. Dynapi <!--IDE-->
3. DynEditor
4. DynHTML Editor
5. <!--DynHtml-->

I vote for <!--DynHtml--> (5) and splash screen 5.
 

Creighton Kirkendall


-----Original Message-----
From: DeWeese, Jason [mailto:jde...@ba...] 
Sent: Wednesday, February 13, 2002 1:17 PM
To: 'Javi Nievas'; dynapi ide
Subject: RE: [Dynapyide-developer] Splash Screen

And I like the name <!-- dynHTML --> .

-----Original Message-----
From: Javi Nievas [mailto:jav...@ya...]
Sent: Tuesday, February 12, 2002 2:02 PM
To: dynapi ide
Subject: [Dynapyide-developer] Splash Screen


To Creighton
 
I did those Splash screens long time ago... so you have not seen them yet
 
There are a problem with the name, I still don't know the name that the
application is going to have. 
 
 
 
 

_______________________________________________
Dynapyide-developer mailing list
Dyn...@li...
https://lists.sourceforge.net/lists/listinfo/dynapyide-developer

_______________________________________________
Dynapyide-developer mailing list
Dyn...@li...
https://lists.sourceforge.net/lists/listinfo/dynapyide-developer

RE: [Dynapyide-developer] Splash Screen

[Creighton K. <cki...@ho...>]

So Javi does not have to implement all of the names in splash screens I
propose a vote.  Below are the entries. Feel free to add more.  The one that
wins will be our working name.  This does not mean that we will not change
it at a later date.  But it will make it a lot easier to build cvs tree and
splash screen for if we have a name.

1. Dynapy <!--IDE-->
2. Dynapi <!--IDE-->
3. DynEditor
4. DynHTML Editor
5. <!--DynHtml-->

I vote for <!--DynHtml--> (5) and splash screen 5.
 

Creighton Kirkendall


-----Original Message-----
From: DeWeese, Jason [mailto:jde...@ba...] 
Sent: Wednesday, February 13, 2002 1:17 PM
To: 'Javi Nievas'; dynapi ide
Subject: RE: [Dynapyide-developer] Splash Screen

And I like the name <!-- dynHTML --> .

-----Original Message-----
From: Javi Nievas [mailto:jav...@ya...]
Sent: Tuesday, February 12, 2002 2:02 PM
To: dynapi ide
Subject: [Dynapyide-developer] Splash Screen


To Creighton
 
I did those Splash screens long time ago... so you have not seen them yet
 
There are a problem with the name, I still don't know the name that the
application is going to have. 
 
 
 
 

_______________________________________________
Dynapyide-developer mailing list
Dyn...@li...
https://lists.sourceforge.net/lists/listinfo/dynapyide-developer

RE: [Dynapyide-developer] Splash Screen

[DeWeese, J. <jde...@ba...>]

And I like the name <!-- dynHTML --> .

-----Original Message-----
From: Javi Nievas [mailto:jav...@ya...]
Sent: Tuesday, February 12, 2002 2:02 PM
To: dynapi ide
Subject: [Dynapyide-developer] Splash Screen


To Creighton
 
I did those Splash screens long time ago... so you have not seen them yet
 
There are a problem with the name, I still don't know the name that the
application is going to have. 
 
 
 
 

[Dynapyide-developer] Basic Components

[DeWeese, J. <jde...@ba...>]

    I didn't explain the whole object model very well.  Lets take a step
back and look at what are the basic components we need to complete this
project.  We might want to take time to make a "Requirements Document" so
that we won't lose sight of what is in the scope of our project.
     Here are the basic parts to our project in my opinion ...
 
1.)  Object Model
    - Java classes that represent the web page
2.)  Graphical Design View
    - GUI designer that allows drag and drop design
3.)  Compiler
    - Converts the Object Model to HTML
4.)  Text Design View
    - Text editor that edits the HTML with add dynAPI support
5.)  Decompiler
    - Converts the HTML into the Object Model 
 
  The justification for the object model is so we can have a Graphical
Design view.  Browsers do the same thing, the HTML is just a way of
communicating how the browser should setup its object model.  In a way for
the graphical design we are building a highly specialized browser.

RE: [Dynapyide-developer] Fw: Screenshot

[Creighton K. <cki...@ho...>]

I also like just "DynEditor"

RE: [Dynapyide-developer] Fw: Splash Screen

[Creighton K. <cki...@ho...>]

Spash5 gets my vote.
 
About the name, I think we need to have something that describes it as a
Dynamic Html editor.  I know we are using the DynAPI, but what we are
building is something much more.  Possibly   "DynHTML <!-- IDE -->" I do
like tag representation.
 
-----Original Message-----
From: Javi Nievas [mailto:jav...@ya...] 
Sent: Wednesday, February 13, 2002 8:32 AM
To: dynapi ide
Subject: [Dynapyide-developer] Fw: Splash Screen
 
 
----- Original Message ----- 
From: Javi Nievas <mailto:jav...@ya...>  
To: dynapi ide <mailto:dyn...@li...>  
Sent: Tuesday, February 12, 2002 8:01 PM
Subject: Splash Screen
 
To Creighton
 
I did those Splash screens long time ago... so you have not seen them yet
 
There are a problem with the name, I still don't know the name that the
application is going to have. 
 
 
 
 

RE: [Dynapyide-developer] Just an update.

[Creighton K. <cki...@ho...>]

>>  OK, I commented out the package my testrun failed on - which only was
used for the aboutbox
>>  - and at least got it working. 
 
I sent the fix out in my last zip file.  Let me know if it worked.
 
>> The application opened up OK, and open, save, copy and paste commands
>> seemed to function as expected. Save command however opened a dialoge
>> that said open on the button, but the command worked as it should anyway
>> (or it just didn't clear the buffer).
 
Seems to be a problem with JFileChoser.  We will probably have to write our
own file manager program (Jason you want to take this one).
 
>> The syntax highlightning didn't seem very proof. In a file that mixed
javascript in a
>> HTML-document - something our application must be able to handle for sure
- it
>> mistook an inline javascript syntax for the begining of an HTML-tag and
the
>> highlightning was totally mixed up. Got me wondering if this Jedit
syntax-handeling
>> package will work for our purpous...
 
I know about this problem.  It has to do with their default HTMLTokenMarker
it does not do a very good job.  I already have in the work a replacement
for it.
 
 
>> All-in-all I'm not complaining. It's good for a start to have an
application that actually
>> fires up, and this update was vwery much appriweated, but I suggest we
look into utilizing
>>  the part of Jedit that resides in the 'org' directory in their
distribution. Under that dir we
>> find most of what we are interested in for our application and that's
also the Jedit
>> contribution to the GJT which aim is to distribute code bits for reuse.
What do you
>> think? Please object if you feel I'm all off-side...
 
I think at first we need to use the syntax highlighter so we don't spend all
of our time working on the editor.  I think I can fix all of the problems
with syntax highlighting.  In the long run I think we will integrate the
main editor of Jedit into it, but right now I think that work is better used
else where.
 
Thank you very much for the feed back and I will work on the problems as
soon as I get a chance to.  
 
P.S. You just submitted our first bug report.
 
Creighton Kirkendall
 
 
 

RE: [Dynapyide-developer] Creating a foundation

[Creighton K. <cki...@ho...>]

Okay I think we are getting a head of our selves.  Jason and I are going to
get together this weekend and hash some of the architecture out for the
major components.  What Jason is trying to describe is a method for
representing graphical components on the screen and then translating them to
real text format in this case HTML.  Below is the basic functions a browser
has to do to display a page (our gui will have to do similar).

1.  Reads in the HTML/JavaScript

2.  Parse it into an object tree (in java this is an object the implements
the Document interface)

3.  It then figures out how big the display area is. (Window size or size of
largest non-wrappable item i.e. a table or image)  

4.  Traverses the tree deciding where line returns need to go for word
wrapping. (Realize that during this it is essentially breaking the document
into display lines)

4a. Each line must know its height (this is the height of the tallest
element in the line) 

6.  Then the document is drawn line by line moving down the line height
before it draws the next one.  Each element renders its self and then its
children.  A table is in a line however it may have the same steps mentioned
above playing out in each cell.

This is a very simplistic view.  In reality there is a lot of optimization
that goes into this to do what I suggest in as few passes of the data as
needed.  I have been looking at code of different browsers and graphical
editors.

P.S. In my last message I included a file with the fix to the about box
problem.  Simply take that file and replace the bad one with it.

Creighton Kirkendall 




-----Original Message-----
From: Javier Nievas [mailto:jav...@ya...] 
Sent: Tuesday, February 12, 2002 3:24 PM
To: DynAPI IDE
Subject: Re: [Dynapyide-developer] Creating a foundation


> * Array of Objects  -  images, tables, text, ...;  this will be objects
> compiled into HTML
> * Array of ObjectPositions  -  matching array that give relative
positioning
> of objects above;
> * Array of Events  -  responses to events on the layer level (mouse
clicks,
> mouse over, ...)
> * Position  -  Absolute position of layer on base layer
> * Size - height and width of layer
> * Background Color  -  color of layer (may be clear, i think)

I don't understand the first and second array, What are you thinking about?
What's an image or a table? (I know what are them... but, Why are you
considering them as objects "inside" a layer?)

And, I don't understand why are you putting an array for object positions,
that "objects" you mention don't have an absolute position...

I think, we should have an array of child layers and add a HTML_Content
property

Well, I'm not a great programmer... but I just don't understand that, maybe
it is an stupid question...





----- Original Message -----
From: "DeWeese, Jason" <jde...@ba...>
To: "DynAPI IDE Developers (E-mail)"
<dyn...@li...>
Sent: Tuesday, February 12, 2002 8:51 PM
Subject: [Dynapyide-developer] Creating a foundation


> All -
>
> To start we need to create an abstract java interface that
> encapsulates what a layer contains on the most basic level.
>
>
> Layer  -  abstract interface representation of a dynAPI layer
> -----------
> * Array of Objects  -  images, tables, text, ...;  this will be objects
> compiled into HTML
> * Array of ObjectPositions  -  matching array that give relative
positioning
> of objects above;
> * Array of Events  -  responses to events on the layer level (mouse
clicks,
> mouse over, ...)
> * Position  -  Absolute position of layer on base layer
> * Size - height and width of layer
> * Background Color  -  color of layer (may be clear, i think)
>
>
> These are the properties handled by the dynAPI we are using as our
> core.  There might be more, but I think these are the bare minimums.  If
we
> come to an agreement early on the basics, we will have a good start.
>
> Unrelated to the previous here is some code for a basic system file
> viewer I created.  It is far from finished, it has some resizing issue and
> no real funtionality.  We could eventually use it as a part of a project
> viewer.
>
>  <<JFileTree.java>>  <<FileTree.java>>
>
>
>
>


----------------------------------------------------------------------------
----


>
> _______________________________________________
> Dynapyide-developer mailing list
> Dyn...@li...
> https://lists.sourceforge.net/lists/listinfo/dynapyide-developer


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


_______________________________________________
Dynapyide-developer mailing list
Dyn...@li...
https://lists.sourceforge.net/lists/listinfo/dynapyide-developer

Re: [Dynapyide-developer] Creating a foundation

[Javier N. <jav...@ya...>]

> * Array of Objects  -  images, tables, text, ...;  this will be objects
> compiled into HTML
> * Array of ObjectPositions  -  matching array that give relative
positioning
> of objects above;
> * Array of Events  -  responses to events on the layer level (mouse
clicks,
> mouse over, ...)
> * Position  -  Absolute position of layer on base layer
> * Size - height and width of layer
> * Background Color  -  color of layer (may be clear, i think)

I don't understand the first and second array, What are you thinking about?
What's an image or a table? (I know what are them... but, Why are you
considering them as objects "inside" a layer?)

And, I don't understand why are you putting an array for object positions,
that "objects" you mention don't have an absolute position...

I think, we should have an array of child layers and add a HTML_Content
property

Well, I'm not a great programmer... but I just don't understand that, maybe
it is an stupid question...





----- Original Message -----
From: "DeWeese, Jason" <jde...@ba...>
To: "DynAPI IDE Developers (E-mail)"
<dyn...@li...>
Sent: Tuesday, February 12, 2002 8:51 PM
Subject: [Dynapyide-developer] Creating a foundation


> All -
>
> To start we need to create an abstract java interface that
> encapsulates what a layer contains on the most basic level.
>
>
> Layer  -  abstract interface representation of a dynAPI layer
> -----------
> * Array of Objects  -  images, tables, text, ...;  this will be objects
> compiled into HTML
> * Array of ObjectPositions  -  matching array that give relative
positioning
> of objects above;
> * Array of Events  -  responses to events on the layer level (mouse
clicks,
> mouse over, ...)
> * Position  -  Absolute position of layer on base layer
> * Size - height and width of layer
> * Background Color  -  color of layer (may be clear, i think)
>
>
> These are the properties handled by the dynAPI we are using as our
> core.  There might be more, but I think these are the bare minimums.  If
we
> come to an agreement early on the basics, we will have a good start.
>
> Unrelated to the previous here is some code for a basic system file
> viewer I created.  It is far from finished, it has some resizing issue and
> no real funtionality.  We could eventually use it as a part of a project
> viewer.
>
>  <<JFileTree.java>>  <<FileTree.java>>
>
>
>
>


----------------------------------------------------------------------------
----


>
> _______________________________________________
> Dynapyide-developer mailing list
> Dyn...@li...
> https://lists.sourceforge.net/lists/listinfo/dynapyide-developer


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

[Dynapyide-developer] Creating a foundation

[DeWeese, J. <jde...@ba...>]

All - 

	To start we need to create an abstract java interface that
encapsulates what a layer contains on the most basic level.


Layer  -  abstract interface representation of a dynAPI layer
-----------
* Array of Objects  -  images, tables, text, ...;  this will be objects
compiled into HTML
* Array of ObjectPositions  -  matching array that give relative positioning
of objects above;
* Array of Events  -  responses to events on the layer level (mouse clicks,
mouse over, ...)
* Position  -  Absolute position of layer on base layer
* Size - height and width of layer
* Background Color  -  color of layer (may be clear, i think)


	These are the properties handled by the dynAPI we are using as our
core.  There might be more, but I think these are the bare minimums.  If we
come to an agreement early on the basics, we will have a good start.

	Unrelated to the previous here is some code for a basic system file
viewer I created.  It is far from finished, it has some resizing issue and
no real funtionality.  We could eventually use it as a part of a project
viewer.

 <<JFileTree.java>>  <<FileTree.java>> 



begin 600 JFileTree.java
M:6UP;W)T(&IA=F$N=71I;"XJ.PT*:6UP;W)T(&IA=F$N:6\N*CL-"FEM<&]R
M="!J879A>"YS=VEN9RXJ.PT*:6UP;W)T(&IA=F%X+G-W:6YG+F5V96YT+BH[
M#0II;7!O<G0@:F%V87@N<W=I;F<N=')E92XJ.PT*:6UP;W)T(&IA=F$N87=T
M+BH[#0H-"G!U8FQI8R!C;&%S<R!*1FEL951R964@97AT96YD<R!*4&%N96P@
M:6UP;&5M96YT<R!4<F5E5VEL;$5X<&%N9$QI<W1E;F5R('L-"@T*("!P<FEV
M871E($1E9F%U;'1-=71A8FQE5')E94YO9&4@=&]P.PT*("!P<FEV871E($I4
M<F5E('1R964[#0H-"@T*("!P=6)L:6,@2D9I;&54<F5E*"D@>PT*("`@('1H
M:7,H(DUY($-O;7!U=&5R(BD[#0H@('T-"@T*#0H@('!U8FQI8R!*1FEL951R
M964H4W1R:6YG(')O;W1?;F%M92D@>PT*("`@('1O<"`](&YE=R!$969A=6QT
M375T86)L951R965.;V1E*')O;W1?;F%M92D[#0H@("`@=')E92`](&YE=R!*
M5')E92AT;W`I.PT*("`@($I38W)O;&Q086YE('-C<F]L;"`](&YE=R!*4V-R
M;VQL4&%N92AT<F5E*3L-"B`@("!T:&ES+F%D9"AS8W)O;&PI.PT*("`@('1R
M964N861D5')E95=I;&Q%>'!A;F1,:7-T96YE<BAT:&ES*3L-"B`@("!T:&ES
M+F%D9%)O;W1S*"D[#0H@('T-"@T*#0H@('!R:79A=&4@=F]I9"!A9&12;V]T
M<R@I('L-"B`@("!&:6QE6UT@<F]O=',@/2!&:6QE+FQI<W12;V]T<R@I.PT*
M("`@($I4<F5E+D1Y;F%M:6-5=&EL5')E94YO9&4N8W)E871E0VAI;&1R96XH
M*$1E9F%U;'1-=71A8FQE5')E94YO9&4I=&]P+"!T:&ES+G=R87!&:6QE07)R
M87DH<F]O=',I*3L-"B`@("!T:&ES+F%L;&]W<T-H:6QD<F5N*'1O<"D[#0H@
M('T-"@T*#0H@('!R:79A=&4@=F]I9"!A9&1&:6QE<RA$969A=6QT375T86)L
M951R965.;V1E(&YO9&4I('L-"B`@("!N;V1E+G)E;6]V94%L;$-H:6QD<F5N
M*"D[#0H@("`@1FEL95M=(&9I;&5S(#T@*"A&:6QE3F]D92EN;V1E+F=E=%5S
M97)/8FIE8W0H*2DN9V5T1FEL92@I+FQI<W1&:6QE<R@I.PT*("`@($I4<F5E
M+D1Y;F%M:6-5=&EL5')E94YO9&4N8W)E871E0VAI;&1R96XH;F]D92QT:&ES
M+G=R87!&:6QE07)R87DH9FEL97,I*3L-"B`@("!T:&ES+F%L;&]W<T-H:6QD
M<F5N*&YO9&4I.PT*("!]#0H-"@T*("!P<FEV871E('9O:60@<F5M;W9E1FEL
M97,H1&5F875L=$UU=&%B;&54<F5E3F]D92!N;V1E*2![#0H@("`@:6YT(&-O
M=6YT(#T@;F]D92YG971#:&EL9$-O=6YT*"D[#0H@("`@;F]D92YR96UO=F5!
M;&Q#:&EL9')E;B@I.PT*("`@(&EF*&-O=6YT(#X@,"D-"B`@("`@(&YO9&4N
M861D*&YE=R!$969A=6QT375T86)L951R965.;V1E*"DI.PT*("!]#0H-"@T*
M("!P<FEV871E('9O:60@86QL;W=S0VAI;&1R96XH1&5F875L=$UU=&%B;&54
M<F5E3F]D92!N;V1E*2![#0H@("`@16YU;65R871I;VX@8VAI;&1R96X@/2!N
M;V1E+F-H:6QD<F5N*"D[#0H@("`@=VAI;&4H8VAI;&1R96XN:&%S36]R945L
M96UE;G1S*"D@*2![#0H@("`@("!$969A=6QT375T86)L951R965.;V1E(&-H
M:6QD(#T@*$1E9F%U;'1-=71A8FQE5')E94YO9&4I8VAI;&1R96XN;F5X=$5L
M96UE;G0H*3L-"B`@("`@(&EF*&YO9&4@/3T@=&]P('Q\("@H1FEL94YO9&4I
M8VAI;&0N9V5T57-E<D]B:F5C="@I*2YG971&:6QE*"DN:7-$:7)E8W1O<GDH
M*2`I#0H@("`@("`@(&-H:6QD+G-E=$%L;&]W<T-H:6QD<F5N*'1R=64I.PT*
M("`@('T-"B`@?0T*#0H-"B`@<')I=F%T92!&:6QE3F]D95M=('=R87!&:6QE
M07)R87DH1FEL95M=(&9I;&5S*7L-"B`@("!I9BAF:6QE<R`A/2!N=6QL*7L-
M"B`@("`@($9I;&5.;V1E6UT@9FEL96YO9&5S(#T@;F5W($9I;&5.;V1E6V9I
M;&5S+FQE;F=T:%T[#0H@("`@("!F;W(H:6YT(&D@/2`P.R!I(#P@9FEL97,N
M;&5N9W1H.R!I*RLI#0H@("`@("`@(&9I;&5N;V1E<UMI72`](&YE=R!&:6QE
M3F]D92AF:6QE<UMI72D[#0H@("`@("!R971U<FX@9FEL96YO9&5S.PT*("`@
M('T-"B`@("!R971U<FX@;G5L;#L-"B`@?0T*#0H-"B`@<'5B;&EC('9O:60@
M=')E95=I;&Q%>'!A;F0H5')E945X<&%N<VEO;D5V96YT(&5V96YT*7L-"B`@
M("!$969A=6QT375T86)L951R965.;V1E(&YO9&4@/2`H1&5F875L=$UU=&%B
M;&54<F5E3F]D92EE=F5N="YG9710871H*"DN9V5T3&%S=%!A=&A#;VUP;VYE
M;G0H*3L-"B`@("!I9BAN;V1E("$]('1O<"E[#0H@("`@("!T:&ES+F%D9$9I
M;&5S*&YO9&4I.PT*("`@('T-"B`@?0T*#0H-"B`@<'5B;&EC('9O:60@=')E
M95=I;&Q#;VQL87!S92A4<F5E17AP86YS:6]N179E;G0@979E;G0I>PT*("`@
M($1E9F%U;'1-=71A8FQE5')E94YO9&4@;F]D92`]("A$969A=6QT375T86)L
M951R965.;V1E*65V96YT+F=E=%!A=&@H*2YG971,87-T4&%T:$-O;7!O;F5N
M="@I.PT*("`@(&EF*&YO9&4@(3T@=&]P*0T*("`@("`@=&AI<RYR96UO=F5&
M:6QE<RAN;V1E*3L-"B`@?0T*#0H-"B`@<'5B;&EC(&-L87-S($9I;&5.;V1E
M('L-"@T*("`@('!R:79A=&4@1FEL92!F:6QE.PT*#0H@("`@<'5B;&EC($9I
M;&5.;V1E*$9I;&4@849I;&4I>PT*("`@("`@9FEL92`](&%&:6QE.PT*("`@
M('T-"@T*("`@('!U8FQI8R!&:6QE(&=E=$9I;&4H*2![#0H@("`@("!R971U
M<FX@9FEL93L-"B`@("!]#0H-"B`@("!P=6)L:6,@4W1R:6YG('1O4W1R:6YG
M*"E[#0H@("`@("!I9B@A(&9I;&4N9V5T3F%M92@I+G1R:6TH*2YE<75A;',H
M(B(I("D-"B`@("`@("`@<F5T=7)N(&9I;&4N9V5T3F%M92@I.PT*("`@("`@
M96QS90T*("`@("`@("!R971U<FX@9FEL92YT;U-T<FEN9R@I.PT*("`@('T-
+"@T*("!]#0H-"GT=
`
end

begin 600 FileTree.java
M:6UP;W)T(&IA=F%X+G-W:6YG+BH[#0II;7!O<G0@:F%V82YA=W0N*CL-"@T*
M<'5B;&EC(&-L87-S($9I;&54<F5E>PT*("!S=&%T:6,@=F]I9"!M86EN*"!3
M=')I;F=;72!A<F=S("E[#0H@("`@2D9R86UE('=I;F1O=R`](&YE=R!*1G)A
M;64H(D9I;&54<F5E(%1E<W0B*3L-"B`@("!W:6YD;W<N<V5T1&5F875L=$-L
M;W-E3W!E<F%T:6]N*$I&<F%M92Y%6$E47T].7T-,3U-%*3L-"B`@("!";W)D
M97),87EO=70@8F]R9&5R(#T@;F5W($)O<F1E<DQA>6]U="@I.PT*("`@($-O
M;G1A:6YE<B!C;VYT96YT(#T@=VEN9&]W+F=E=$-O;G1E;G1086YE*"D[#0H@
M("`@8V]N=&5N="YS971,87EO=70H8F]R9&5R*3L-"B`@("!*4W!L:71086YE
M('-P;&ET(#T@;F5W($I3<&QI=%!A;F4H($I3<&QI=%!A;F4N2$]225I/3E1!
M3%]34$Q)5"P-"B`@("`@("`@("`@("`@("`@("`@("`@("`@("`@("`@("`@
M("`@(&YE=R!*1FEL951R964H*2P-"B`@("`@("`@("`@("`@("`@("`@("`@
M("`@("`@("`@("`@("`@(&YE=R!*5&5X=$%R96$H*2`I.PT*("`@(&-O;G1E
M;G0N861D*'-P;&ET+$)O<F1E<DQA>6]U="Y#14Y415(I.PT*#0H@("`@=VEN
M9&]W+G!A8VLH*3L-"B`@("!W:6YD;W<N<V5T5FES:6)L92AT<G5E*3L-"B`@
*#0H-"B`@?0T*?0==
`
end

RE: [Dynapyide-developer] Just an update.

[Creighton K. <cki...@ho...>]

>> I've already been looking into Jedit a lot, and also
>> looking into Jext and other Open Source editors to use
>> as a base for our development. Jedit has probably been
>> the strongest candidate, although, like you noticed
>> Jext have implemented Rhino, and would therefore also
>> have its advantages.=20

If you look at Jext it has Jedit's syntax highlighter as it core and =
also
uses the same plug-in architecture of older versions of Jedit.  Jext =
did add
a nice Rhino implementation that I have the code for. =20


>> I'm not sure we could do it just as a plugin, I think
>> we would need to do it as a own distribution with a
>> lot of the original Jedit core as our base (maybe so
>> much, it can be fully-compable with Jedit original
>> distribution and upgraded along-side the Jedit
>> development). But for a start we could aim to do
>> plugins, but eventually I think we'd have so many
>> special plugins it should be considered a new
>> distribution. We'll see...

I agree that this needs to be a full distribution with just some of =
Jedit at
its core.  What I was referring to when I said that we need to build =
the
system as a set of plug-ins on a common bus was just use Jedits base =
syntax
highlighter and bus system to handle the major architecture decisions.  =
Long
term we can look at merging it into the main Jedit but right now it is =
not
really possible for the graphical editor to exist in Jedit because this
represents a different view of the document and Jedit does not support =
this.


>> Dan Steinman, the originator of DynAPI have been
>> contributing his begun WYSIWYG dynlayer editor code to
>> this project.=20
>> If your still monitoring this list Dan: Do you have an
>> update or could you please submit your code pieces
>> again?

Does anyone know his email? I suggest we just email him directly.

Attached is the code for the basic editor.  It is extremely simplistic =
and I
have tried to comment what I did.  The only addition I did was to add a
WrapperApp, and WrapperAppFrame to hold the text area.  Most of the =
code I
did is in the WrapperAppFrame.  I did not modify any of the original =
Jedit
Syntax code (We will in the long run).


Creighton=20

-----Original Message-----
From: Henrik V=E5glin [mailto:hv...@ya...]=20
Sent: Tuesday, February 12, 2002 7:54 AM
To: Creighton Kirkendall
Subject: Re: [Dynapyide-developer] Just an update.

I've already been looking into Jedit a lot, and also
looking into Jext and other Open Source editors to use
as a base for our development. Jedit has probably been
the strongest candidate, although, like you noticed
Jext have implemented Rhino, and would therefor also
have its advantages.=20

However, I've found the documentation and support for
Jedit to be stronger and wider spread. And if you feel
its a good base, I'm all with you to go ahead and use
it as sugested.

I'm not sure we could do it just as a plugin, I think
we would need to do it as a own distribution with a
lot of the original Jedit core as our base (maybe so
much, it can be fully-compable with Jedit original
distribution and upgraded along-side the Jedit
development). But for a start we could aim to do
plugins, but eventually I think we'd have so many
special plugins it should be considered a new
distribution. We'll see...

I've found this independent guide/essay on doing a
plugin for jedit, that might be of some help:

http://www.generationjava.com/projects/JEdit.shtml

Jedit is a part of the Giant Java Tree project, so you
might also want to check out http://www.gjt.org

Dan Steinman, the originator of DynAPI have been
contributing his begun WYSIWYG dynlayer editor code to
this project.=20
If your still monitoring this list Dan: Do you have an
update or could you please submit your code pieces
again?=20

Henrik

 --- Creighton Kirkendall <cki...@ho...>
skrev: > I have spent this weekend going over the code
for
> Jedit and some other open
> source editors.  By the way, most of the other
> editors that are written in
> java have Jedit as their core engine
> (Interesting???).  It seems we are the
> very first to attempt an open source DHTML wysiwyg
> editor in java.  I think
> we can borrow a lot of the architecture from Jedit
> as far as event bus,
> plug-ins and class-loading are concerned.  Where we
> need to concentrate our
> efforts now is design.  What can we use from jedit
> and what does not suit
> graphical editor.  I spend a lot of time poring over
> code I have some very
> good ideas of what the architecture of the main
> components are going to have
> to be.  The largest and most difficult is going to
> be the layout manager
> used in the design view.  All of the other pieces
> can be written or borrowed
> from Jedit or others relatively easily.  Jason, I
> want to talk some things
> over with you about the main design view element.  I
> think I am going to
> email the creator of Jedit and see if he knows of
> anyone who has tried to
> use their architecture for a graphical editor.  If
> anyone wants to
> understand where I am looking to take us next, spend
> some time looking at
> Jedit's code.  Pay special attention to the way
> plug-ins are written and how
> they are actually implemented in Jedit (note:
> description of writing a
> plug-in is in Jedits user manual  & you can check
> out the EditPlugin and
> EBPlugin code in the source tree.  Also look at the
> EditBus source.)  I
> think we should plan to implement the whole system
> as a bunch of plug-ins
> that add and remove messages from a bus.   This will
> allow us to work
> separately on different sections with out having
> duplication of work.
> =20
> -- Javier I looked over the graphics and I think we
> are, for the beginning,
> going to have to use the System buttons (Mainly due
> to differences with mac,
> unix, and windows).  However icons for the buttons
> look good and I will see
> if I can implement those into the test browser,
> okay.  If you have a splash
> screen I'd like to see it. =20
> =20
> P.S. I also found an interesting embedded
> implementation of Rhino in a text
> editor called Jext.
> P.S.S. I have the editor working with file save and
> file load.  I also got
> copy and past working. =20
> =20
> =20
> Creighton=20
> =20

=3D=3D=3D=3D=3D
// Henrik Vaglin

**************************************************
Visit my comics artpage at=20
http://photos.yahoo.com/bc/hvaglin?d&.flabel=3Dfld5&.src=3Dbc
**************************************************

_____________________________________________________
Hitta sn=F6rapporter...=20
fr=E5n 500 olika skidorter i Europa
p=E5 http://se.snow.yahoo.com

Re: [Dynapyide-developer] Just an update.

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

I've already been looking into Jedit a lot, and also
looking into Jext and other Open Source editors to use
as a base for our development. Jedit has probably been
the strongest candidate, although, like you noticed
Jext have implemented Rhino, and would therefor also
have its advantages. 

However, I've found the documentation and support for
Jedit to be stronger and wider spread. And if you feel
its a good base, I'm all with you to go ahead and use
it as sugested.

I'm not sure we could do it just as a plugin, I think
we would need to do it as a own distribution with a
lot of the original Jedit core as our base (maybe so
much, it can be fully-compable with Jedit original
distribution and upgraded along-side the Jedit
development). But for a start we could aim to do
plugins, but eventually I think we'd have so many
special plugins it should be considered a new
distribution. We'll see...

I've found this independent guide/essay on doing a
plugin for jedit, that might be of some help:

http://www.generationjava.com/projects/JEdit.shtml

Jedit is a part of the Giant Java Tree project, so you
might also want to check out http://www.gjt.org

Dan Steinman, the originator of DynAPI have been
contributing his begun WYSIWYG dynlayer editor code to
this project. 
If your still monitoring this list Dan: Do you have an
update or could you please submit your code pieces
again? 

Henrik

 --- Creighton Kirkendall <cki...@ho...>
skrev: > I have spent this weekend going over the code
for
> Jedit and some other open
> source editors.  By the way, most of the other
> editors that are written in
> java have Jedit as their core engine
> (Interesting???).  It seems we are the
> very first to attempt an open source DHTML wysiwyg
> editor in java.  I think
> we can borrow a lot of the architecture from Jedit
> as far as event bus,
> plug-ins and class-loading are concerned.  Where we
> need to concentrate our
> efforts now is design.  What can we use from jedit
> and what does not suit
> graphical editor.  I spend a lot of time poring over
> code I have some very
> good ideas of what the architecture of the main
> components are going to have
> to be.  The largest and most difficult is going to
> be the layout manager
> used in the design view.  All of the other pieces
> can be written or borrowed
> from Jedit or others relatively easily.  Jason, I
> want to talk some things
> over with you about the main design view element.  I
> think I am going to
> email the creator of Jedit and see if he knows of
> anyone who has tried to
> use their architecture for a graphical editor.  If
> anyone wants to
> understand where I am looking to take us next, spend
> some time looking at
> Jedit's code.  Pay special attention to the way
> plug-ins are written and how
> they are actually implemented in Jedit (note:
> description of writing a
> plug-in is in Jedits user manual  & you can check
> out the EditPlugin and
> EBPlugin code in the source tree.  Also look at the
> EditBus source.)  I
> think we should plan to implement the whole system
> as a bunch of plug-ins
> that add and remove messages from a bus.   This will
> allow us to work
> separately on different sections with out having
> duplication of work.
>  
> -- Javier I looked over the graphics and I think we
> are, for the beginning,
> going to have to use the System buttons (Mainly due
> to differences with mac,
> unix, and windows).  However icons for the buttons
> look good and I will see
> if I can implement those into the test browser,
> okay.  If you have a splash
> screen I'd like to see it.  
>  
> P.S. I also found an interesting embedded
> implementation of Rhino in a text
> editor called Jext.
> P.S.S. I have the editor working with file save and
> file load.  I also got
> copy and past working.  
>  
>  
> Creighton 
>  

=====
// Henrik Vaglin

**************************************************
Visit my comics artpage at 
http://photos.yahoo.com/bc/hvaglin?d&.flabel=fld5&.src=bc
**************************************************

_____________________________________________________
Hitta snörapporter... 
från 500 olika skidorter i Europa
på http://se.snow.yahoo.com

[Dynapyide-developer] Just an update.

[Creighton K. <cki...@ho...>]

I have spent this weekend going over the code for Jedit and some other open
source editors.  By the way, most of the other editors that are written in
java have Jedit as their core engine (Interesting???).  It seems we are the
very first to attempt an open source DHTML wysiwyg editor in java.  I think
we can borrow a lot of the architecture from Jedit as far as event bus,
plug-ins and class-loading are concerned.  Where we need to concentrate our
efforts now is design.  What can we use from jedit and what does not suit
graphical editor.  I spend a lot of time poring over code I have some very
good ideas of what the architecture of the main components are going to have
to be.  The largest and most difficult is going to be the layout manager
used in the design view.  All of the other pieces can be written or borrowed
from Jedit or others relatively easily.  Jason, I want to talk some things
over with you about the main design view element.  I think I am going to
email the creator of Jedit and see if he knows of anyone who has tried to
use their architecture for a graphical editor.  If anyone wants to
understand where I am looking to take us next, spend some time looking at
Jedit's code.  Pay special attention to the way plug-ins are written and how
they are actually implemented in Jedit (note: description of writing a
plug-in is in Jedits user manual  & you can check out the EditPlugin and
EBPlugin code in the source tree.  Also look at the EditBus source.)  I
think we should plan to implement the whole system as a bunch of plug-ins
that add and remove messages from a bus.   This will allow us to work
separately on different sections with out having duplication of work.
 
-- Javier I looked over the graphics and I think we are, for the beginning,
going to have to use the System buttons (Mainly due to differences with mac,
unix, and windows).  However icons for the buttons look good and I will see
if I can implement those into the test browser, okay.  If you have a splash
screen I'd like to see it.  
 
P.S. I also found an interesting embedded implementation of Rhino in a text
editor called Jext.
P.S.S. I have the editor working with file save and file load.  I also got
copy and past working.  
 
 
Creighton 

[Dynapyide-developer] The Other New Guy

[DeWeese, J. <jde...@ba...>]

Hello,

	My name is Jason, I'm a java web based application developer for a
goverment contracter.  Crieghton and I were interested in doing a project on
the side for the sake of the challenge.
	Currently Creighton is working on an editor and I am building some
components that we can use in the project.  I am currently working on a
"Project Viewer", it is basicly a expandable tree that allows you to view
files.  I will post send a screen shot when I have it finished.

Jason

RE: [Dynapyide-developer] New developers joined in

[Michael P. <pem...@ho...>]

>From: Creighton Kirkendall <cki...@ho...>
>To: dyn...@li...
>Subject: RE: [Dynapyide-developer] New developers joined in
>Date: Thu, 7 Feb 2002 13:56:11 -0500
>
>I just want to get an Idea of the skill set of the other developers so we
>can coordinate our activities better:  number of years working with java,
>expertise in Swing, past development of IDE or editor, and writing ability
>(help text and or technical documentation) other open source project you're
>involved in.
>

As far as programming skills, I have had about 6 month actualy training in 
Java / Swing in which time we didn't get much further than simple gui and a 
few text-based programs.

I do have an extensive range of skills coming from a number of years working 
with VB / VBA.

I currently do most of my coding in PHP.  This is due to me using it as a 
method to perform scheduled tasks on my server at home and as part of my web 
development work.

My only other open-source work is with DynAPI (+my own AfroAPI).  I spend 
more time breaking code than writing it and as a result sometimes get lost 
for a day or two.

Other than that, I am actually a techie more than a coder.  I send my days 
installing and maintaining PCs here for a national TV station.  I am still 
more than willing to spend a few hours playing with code to automate a task 
rather than sit there and repeat the same simple task repeatedly.

_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com

RE: [Dynapyide-developer] New developers joined in

[Creighton K. <cki...@ho...>]

I just want to get an Idea of the skill set of the other developers so =
we
can coordinate our activities better:  number of years working with =
java,
expertise in Swing, past development of IDE or editor, and writing =
ability
(help text and or technical documentation) other open source project =
you're
involved in.  =20
=20
Here's my Info
Creighton Kirkendall
=20
Senior Software Engineer / Project Manager
Java --- Expert (> 5 years)
Swing --- Intermediate (Spent most of my time on the server side.)
Architecture --- Good (worked a lot with J2EE and Formal Design =
Patterns)
Documentation --- (Good with class layout and design documentation bad =
with
user side documentation)
Open Source --- Limited with Jakarta
=20
=20
-----Original Message-----
From: Henrik V=E5glin [mailto:hv...@ya...]=20
Sent: Thursday, February 07, 2002 1:13 PM
To: dyn...@li...
Subject: [Dynapyide-developer] New developers joined in
=20

Well, just the other day I got this nice and intriguing message from
Creighton Kirkendall:
=20
***
I email your Source Forge account but I am not sure you received it.  A
friend and I where discussing creating an IDE for this sort of project, =
that
is when I discovered you guys.  I am a little bit confused on where =
this
project stands now.  It does not seem to even be in the coding phase =
yet.  I
am a Senior Software Engineer and Project Manager for a company out of
Cincinnati, Ohio.  My friend is a Software Engineer out of Ball =
Aerospace in
Dayton, Ohio.  I would like to know who is on the team and how many =
years of
experience with Java and Architecture in general they have.  I had a =
hard
time figuring out what plan of attack what for this project.  What are =
we
going to try to do first?
Creighton Kirkendall
Senior Software Engineer
Hobsons
cki...@ho... <mailto:cki...@ho...>=20
***
=20
Well, since we haven't gotten vwry far, and I'm giuessing everybody =
else is
buzy elsewhere I added the guys without further ado and hope we all can =
see
this as new start.
=20
So I'm very glad that Creighton and Jason are willing to jump on for a =
new
take at getting this project out of planning and into development =
phase. A
big welecome to you guys from me and I hope everybody still planning to =
get
in with the develoment will join me in that - let know of yourselves =
now so
we can wrap this up and get going! :)
=20
First things first: aiming for version 0.1 right ahead! A simple =
texteditor
to be the base of the code of our application. Probably be looking far =
from
our vision of the full product, but its a go, that we're going to let =
the
development take off from.
=20
Creighton with assistance of  Jason takes care of that. I will put out =
the
code for download on the project's homesite when ready, since I haven't
really got the hang of setting up CVS properly yet.
=20
Henrik V=E5glin [ hv...@ya... <mailto:hv...@ya...>  ]


=20
=20
=20
____________________________________________________
 <http://www.incredimail.com/redir.asp?ad_id=3D309&lang=3D9>   =
IncrediMail -
Email has finally evolved -
<http://www.incredimail.com/redir.asp?ad_id=3D309&lang=3D9> Click Here=20

Re: [Dynapyide-developer] New plan & class diagram

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

Well, Javi, you can still work on the buttons- and other grphics. I like =
the grphics in thatvision-preview you did. Do you think you can put =
together a graphic set like that. What I'd like to see is both regulars =
like

cut
copy
paste

as well as for objects (in the GUI workspace)

add
remove
duplicate (clone)
refresh

and something to represent the main panel modules in different colors

tools
widgets
browsers
document(main workspace)
inspectors
debuggers
trashcan

and we also need a final and original splashpanel grahics for the =
loading process. And preferably a couple of more and smaller versions =
with the logo, If you can attach the originals (photoshop or =
paintshoppro-format) in the graphic package, would be great.

besides that, if you could do pre-screenshots of the pre-versions as =
outlined, so everyone can get the idea of what we're working towards =
with every pre-version would be nice.

Do it as you find time. Its no rush for you, but the sooner the better.

Henrik V=E5glin [ hv...@ya... ]

PS. I got called up on my cellular by a fellow swede that belived me to =
be a DynAPI guru of sorts, because of my involvement with the project. I =
didn't tell him, but actually I'm pretty lame - I only know what I use, =
and don't have much more than a hunch  of an insight to the =
inner-workings of the DynAPI. BTW I only belive the real DynAPI =
developers does. And that's why I rather work on this project than to =
ruin it for everybody by trying to code and improve the API. ;) DS

----- Original Message -----=20
From: "Pepe Gutierrez" <jav...@ya...>
To: "Henrik_V=E5glin" <hv...@ya...>
Sent: Thursday, January 03, 2002 11:37 PM
Subject: Re: [Dynapyide-developer] New plan & class diagram


> Just... I have no words.=20
>=20
> Good job
>=20
> It seems a good beggining design.
>=20
> As a graphic designer... I suppose that I have no work
> by now, when the project needs me, just say it to me.
> =BFok?
>=20
>=20
>=20
>  --- Henrik_V=E5glin <hv...@ya...> escribi=F3: >
> Hello,
> >=20
> > As I belive the reasonwe have failed to get going is
> > that the application aims was probably to high and
> > the initial docs to start out too complex (mostly my
> > fault).
> >=20
> > I'm giving it a new try now, hoping that more
> > reachable milestones in form of builds up to the 1.0
> > version will make it easier to see how we should be
> > progressing. Also I've wrote in how the vapplication
> > could be begun to come to use with each pre-version.
> >=20
> > I also set a working name for each version, mainly
> > to have something to call it by while developing,
> > but also trying to invoke what the version will
> > bring new in the application. My english is bad, and
> > I tried to keep the theme of calling them all
> > something ending with Ed, hope you can excuse it,
> > cause its only temporary.
> >=20
> > Please, please, please read through these very much
> > shortened down text files. dynAPIideVersions.txt is
> > very briefly outlining my plan as to how we will
> > proceed with pre-versioning up til the full 1.0
> > version release. and dynAPIdeClasses is the classes
> > diagram as I figure it, for having a functioning=20
> > version 0.1 build according to plan outlined.
> >=20
> > As always this isn't set in stone. I'd be glad to
> > get any comments or sugestions - even flamings (as
> > long as reasonable). ;)
> >=20
> > Just a few brief notes of what my vision of this
> > application is, so you'll understand my thinking as
> > outlined in these textfiles:
> > =20
> > * The application is divided into 3
> > cross-interacting layers of classtypes: Handlers
> > (core operations and data), Managers (UI operations)
> > and Modules (GUI)
> >=20
> > * All classes and instances thereof (IDE objects) is
> > loaded via an internal (class-)loading engine which
> > works on load and reload events
> >=20
> > * Loading is configured in javasscript in an DynAPI
> > syntax-like manner (promoting the learning of DynAPI
> > which is much forward JAVA)
> >=20
> > * As much as possible of the in-application
> > communication between IDE objects is done by
> > invoking and answering to event calls. This way one
> > object can independatly reacting upon another
> > objects actions.
> >=20
> > * Plugability and customization should be done to
> > the highest possible extent. Any part of the
> > application should work as independently as possible
> > within the application, but also define which other
> > parts it depend upon and not load unless it's there.
> >=20
> > This is what I've figured makes a application that
> > can be customed for any induviduals prefered likings
> > and uses. From my thinking this class-structure
> > achieves that to highest possible and reasonable.
> > You're very welecome to disagree as long as you can
> > define why :)
> >=20
> > Hope to get some kinda response from everybody that
> > still wanna be in on this endeavour.=20
> >=20
> > I know the demand for this application is still high
> > cause every now and then someone emails me to try
> > and give an idea as to what we could aim at to get
> > going. of course you would wish for some of them to
> > actually be willing to spend some time to help
> > developing it, but an interest in it is still better
> > than no response at all...
> >=20
> > Henrik V=E5glin [ hv...@ya... ]
> >=20
> >=20
> > > version 0.1: TextEd
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > The aim in this version is to have the IDE loading
> > up a working Texteditor. The focus is more that we
> > have classes that can work simple file- and
> > text-commands and that we have an initial build of
> > the class-loading engine. At this point though, we
> > need not yet implement the listener handling - we
> > can hardcode event listening for this build. Now we
> > should be able to use our own application for the
> > rest of the development ;)
> >=20
> > version 0.2: JSTextEd
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > For this build we should have Javascript
> > implemented, possibly using Mozilla project's Rhino
> > (Javascript engine in Java). Also, now we modify the
> > class-loading engine to run a javascript file
> > (bin/configuration.js) in which is defined in a way
> > that through Rhino load up the application. Now we
> > sshould be able to simply try out our new modules
> > without recompiling the whole package :)
> >=20
> > version 0.3: JSEd
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > This is the first relase to support an Development
> > API syntax, which should be javascript. Now
> > developers can begin using the IDE for widget
> > development :D
> >=20
> > version 0.4: HTMLEd
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > In this release we try out and perfect the syntax
> > handeling to use 2 API's, adding HTML support. Now
> > hand-coding freaks can start using the the IDE for
> > webpage development :P
> >=20
> > Version 0.5: EventEd
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > For this release all eventhandeling should be moved
> > to using the independent listening throughout the
> > application.
> >=20
> > Version 0.6: InputEd
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > With this build eventManagment should be added, so
> > that mouse- and keyboard-events is no longer static
> > and/or hardcoded. Keyboard event bindings should be
> > configured in an an scriptfile (bin/keybindings.js).
> > Now users can custom their enviroment for faster
> > keyboard-coding. :D
> >=20
> > Version 0.7: GUIEd
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > With this build layoutManagment should be added, so
> > that modules can be added and the layout is no
> > longer static and/or hardcoded.
> >=20
> > Version 0.8: PluginEd
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > A full pluginmanagment with plugindevelopers docs
> > should be ready. Add a helpsystem with doc-display.
> > Now anyone should be able to begin making their own
> > custom handlers, managers and modules.
> >=20
> > Version 0.9: WysiwygEd
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > WYSIWYG document view is added. Now regular users
> > can begin using the IDE as a wysiwyg enviroment :D
> >=20
> > Version 1.0: DynAPI Editor
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
> >=20
> > Refinements and full documentation added.
> >=20
> >=20
> >=20
> > > DynAPIide
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > This is the top class of any object that is part of
> > the IDE.
> >=20
> > properties
> > **********
> > name - String - what is the screenname of this
> > object (a more descriptive name than the class
> > name).
> > version - Int - a number so that comparing versions
> > will be an as quick task as possible.
> > compIDEversion -  Int - this is the version of the
> > IDE core and any dependent objects needed that are
> > compatible with that version or below should be
> > checked to be working with this before set to
> > compatible
> > dependantObjects - Array of DynAPIide Objects - this
> > is so that it can be checked that all dependant
> > DynAPIide Objects needed for this object to work is
> > loaded
> > listeners - Array of Listeners - DynAPIlisteners
> > active for this Object
> >=20
> >=20
> >=20
> > DynAPIideHandler
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > Is mostly data handling objects and inherits
> > DynAPIide.
> >=20
> > properties
> > **********
> >=20
> >=20
> > DynAPIideTextFileHandler=20
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > Is handeling textfiles and inherits
> > DynAPIideHandler
> >=20
> > methods
> > *******
> > writeTo - In: String of text to save; Out: Int of
> > file operation
> > readFrom - In: String of filepath; Out: String of
> > text
> >=20
> > DynAPIideClassLoader=20
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > Is loading up the classes into use in the
> > application
> >=20
> > methods
> > *******
> > loadClass - In: String of filepath
> >=20
> >=20
> >=20
> > DynAPIideManager
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > Is mostly module managing objects and inherits
> > DynAPIide.
> >=20
> > properties
> > **********=20
> >=20
> >=20
> > DynAPIideFileManager=20
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > Managing all files loaded into the application for
> > edit.
> >=20
> > properties
> > **********=20
> > files - Array of DynAPIideFile objects - name of
> > the LayoutManager class in use for the GUI.
> >=20
> >=20
> >=20
> > DynAPIideModule
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > Is mostly GUI real-time rendering objects and
> > inherits DynAPIide.
> >=20
> > properties
> > **********
> > caption - String - screenname for use in title bars
> > and such (in case it is a multiple-loadable module
> > it should add a number or something as additional
> > reference to separate them)
> > allowMultiple - Boolean - if this module can be
> > loaded more than once in the same parent object or
> > not
> > parentClassType - String - if this module is
> > restricted to be a child of an object that is
> > instance of a certain other DynAPIideModule Class.
> > Default is of course the IDE main window
> > (DynAPIideWindow) which means it can be invoked into
> > any underlying module.=20
> >=20
> >=20
> > DynAPIideWindow=20
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > The main window of the application
> >=20
> > properties
> > **********=20
> >=20
> >=20
> > DynAPIidePopUp=20
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > An independent popup window, for error- or
> > information messaging.
> >=20
> > properties
> > **********=20
> >=20
> >=20
> >=20
> > DynAPIideFile
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > Is a file supported in the IDE.
> >=20
> > properties
> > **********
> > name - String - what it's called in the filesystem
> > path - String - the filesystem directory path
> > saved - Bolean - True if file is unchanged since
> > last saved
> >=20
> > methods
> > *******
> > getName - out: String of name
> > setName - in: String of new name
> > getPath - out: String of path
> > setPath - in: String of new path
> > getSaved - out: Bolean of saved
> > setSaved - in: Bolean value to set for saved=20
> >=20
> >=20
> > DynAPIideDocument=20
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > Is a document which is the root-node of any
> > development inside the IDE.
> >=20
> > properties
> > **********=20
> > documentTtype - String - documenttype which is
> > what its used as regardless of the extension.=20
>=20
> _______________________________________________________________
> Do You Yahoo!?
> Yahoo! Messenger
> Comunicaci=F3n instant=E1nea gratis con tu gente.
> http://messenger.yahoo.es
>=20



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

[Dynapyide-developer] New plan & class diagram

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

Hello,

As I belive the reasonwe have failed to get going is that the =
application aims was probably to high and the initial docs to start out =
too complex (mostly my fault).

I'm giving it a new try now, hoping that more reachable milestones in =
form of builds up to the 1.0 version will make it easier to see how we =
should be progressing. Also I've wrote in how the vapplication could be =
begun to come to use with each pre-version.

I also set a working name for each version, mainly to have something to =
call it by while developing, but also trying to invoke what the version =
will bring new in the application. My english is bad, and I tried to =
keep the theme of calling them all something ending with Ed, hope you =
can excuse it, cause its only temporary.

Please, please, please read through these very much shortened down text =
files. dynAPIideVersions.txt is very briefly outlining my plan as to how =
we will proceed with pre-versioning up til the full 1.0 version release. =
and dynAPIdeClasses is the classes diagram as I figure it, for having a =
functioning  version 0.1 build according to plan outlined.

As always this isn't set in stone. I'd be glad to get any comments or =
sugestions - even flamings (as long as reasonable). ;)

Just a few brief notes of what my vision of this application is, so =
you'll understand my thinking as outlined in these textfiles:
=20
* The application is divided into 3 cross-interacting layers of =
classtypes: Handlers (core operations and data), Managers (UI =
operations) and Modules (GUI)

* All classes and instances thereof (IDE objects) is loaded via an =
internal (class-)loading engine which works on load and reload events

* Loading is configured in javasscript in an DynAPI syntax-like manner =
(promoting the learning of DynAPI which is much forward JAVA)

* As much as possible of the in-application communication between IDE =
objects is done by invoking and answering to event calls. This way one =
object can independatly reacting upon another objects actions.

* Plugability and customization should be done to the highest possible =
extent. Any part of the application should work as independently as =
possible within the application, but also define which other parts it =
depend upon and not load unless it's there.

This is what I've figured makes a application that can be customed for =
any induviduals prefered likings and uses. From my thinking this =
class-structure achieves that to highest possible and reasonable. You're =
very welecome to disagree as long as you can define why :)

Hope to get some kinda response from everybody that still wanna be in on =
this endeavour.=20

I know the demand for this application is still high cause every now and =
then someone emails me to try and give an idea as to what we could aim =
at to get going. of course you would wish for some of them to actually =
be willing to spend some time to help developing it, but an interest in =
it is still better than no response at all...

Henrik V=E5glin [ hv...@ya... ]

Re: [Dynapyide-developer] Re: Possible Logos / Splash Screen

[Michael P. <mp...@ph...>]

I love the third logo in Logos.gif.

I put my vote in for "DynEditor" as the title for the project.  I think that "visual" sounds too much like an M$ application :)
--
Michael Pemberton
mp...@ph...
ICQ: 12107010

[Dynapyide-developer] Fw: DynAPI IDE Splash Screen 2

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

As Javi writes, more files here...

Henrik V=E5glin [ hv...@ya... ]

----- Original Message -----=20
From: "Pepe Gutierrez" <jav...@ya...>
To: "Henrik_V=E5glin" <hv...@ya...>
Sent: Wednesday, October 10, 2001 4:52 PM
Subject: Re: DynAPI IDE Splash Screen 2


> More files...
>=20
>=20
>=20

-------------------------------------------------------------------------=
-------






-------------------------------------------------------------------------=
-------






-------------------------------------------------------------------------=
-------