RE: [Aspinfinity-developer] (no subject)

[David S. F. <ds...@cr...>]

Hi,
=20
In my opinion the next steps is to really discuss the class subsystems
that will support the core functionality for each module.
=20
But before we get into that, I was hoping to get a handle on the
background/strengths weaknesses of the other developers working on this
project.
=20
I am an application developer who has been working full time as a
programmer for about 5 years. I live in New York City, am looking to
work on projects like this in my spare time, when my wife isn't around.
I am a Microsoft certified Application Developer (MCAD). My strengths
are in VB, VB.NET, classic asp, ASP.NET, C#, SQL, TSQL, etc   =20
=20
Anyway, I also wanted to add some preface to the proof of concept. As
Matt indicated, there are no "dancing elephants." This is proving that
page rendering can be accomplished by dynamically initiating objects
based on database settings. It's really rough, but by extending this
concept we can create a fully functionally object management system in
asp. The end result is to package one base vbscript class with asp html
like forms to create a module. We can have the framework auto wire to
the class methods based on form settings. This provides a consistent
method for extending the core functionality any which way we want.
=20
These are the kind of class subsystems that we will need to work on,
just off the top of my head.
=20
A Data Access layer.
An authentication/Security layer.
An Object Persistence Layer
A Module Rendering Object
A Page Rendering Object
A Skin Object for Skinning Pages
A Metadata Object
A Configuration Layer (For Global Variables as demonstrated in the POC)
A Debug Object (As demonstrated in the POC)
A File IO Object
A XML IO Object
A File Upload Object

I haven't fully explored these ideas, I'm just throwing them out there.
=20
Please let me know what you think.
=20
-Dave
=20
  _____ =20

From: asp...@li...
[mailto:asp...@li...] On Behalf Of
Adullam
Sent: Monday, February 21, 2005 7:26 AM
To: asp...@li...
Subject: [Aspinfinity-developer] (no subject)


Hi all,
=20
I have added the proof of concept to the releases on sourceforge.
=20
I would like to consider the PoC as a starting point to build our
framework from.  However there are a number of issues to address which I
will outline below for feedback.
=20
Theme and UI: The core will need to allow for a seperate set of files
that in some way handle the look and feel seperate from the data and
logic layers.  The technique in the early trails centered arround a
module of functions and rendering subs.  This has some limits but has
the advantage of being tested and reasonably easy to document.  However
there are other options and these include a templating system of which
there exists one for ASP under the GNU.
=20
Data Systems and Boot Strapping: In an ideal world the set up of the
system should be "upload files, naviagte to xyz.asp, follow on screen
promts." so the ideal of creating the connection to the database from a
file that the config creates is best.  This would mean that we would be
working DSN-less connection which has the advantage of slightly lower
server strain and given the nature of our object oriented design I can
see no benifit to using DSN. =20
=20
Where next: This is the key issue that we must address.  Although the
above issues will have a bering on this issue it is vital that we
address it directly at least in terms of planning and general direction.
=20
I have drafted a short list but am open to alternatives.
=20
Discussion of Proof of concept and surrounding ideas
Documentation of best practice and options for UI-Layer and the
advantages and disadvantages of each technique
Drafting of a list of requirements for the core functions (and
eventually creation thereof).  This would also include the use of the
authentication class with the core.
Development of PoC into a core system
First testing and feedback
=20
-Matt