dynapyide-developer

[<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