Noonan.m.e
That's a great question. I know a lot of other members are asking me
for direction as well. And I need to post a project plan. Right now
my main concern is consensus. I know that I want to do, and I know
that there are a lot more technologies out there that I haven't been
exposed to. So, I'm trying to give the group a lot of room to
discuss, "What services should a Collaborative website that brings
Freelancers and Entrepreneurs together have?"
Beyond just providing this space there are several goals:
- Build a space that patrons come to and say, "WOW!!! They thought
of everything needed to make collaboration easy."
- Build a space that supports Freelancers and Entrepreneurs.
- Build a space that can grow and adapt as new techniques are
discovered to make collaboration easier.
- Provide a space where Freelancers can gain and demonstrate their
experience in developing web applications. (mind you I"m not
limiting freelancers to web developers)
These are goals are obtainable, the questions for me are:
- What does the underlying structure of the site look like?
- What are the core services we want to offer?
- Is 2 to 3 programmers enough to build the initial site?
(considering previous goal)
- how much do we want to bring in from other sites, vs create new?
(more in a minute)
To the last question, I have been working on building web based
applications in a new methodology called Ladder. It's technically
not new. It's an object oriented data management tool that looks
like a File Management System. The PHP concept version presently
layers over top of mySQL. However, I'm working to make Ladder a
completely independent database engine. Why??? Because I feel it
organizes data better. It's easier to import and export
(synchronize) branches of the object tree (OODMS) via XML, than it
is to do this with a Flat File Database Management System (FFDMS).
The next level above that is FORM processing or WorkFlow. This is
the middle ware which accepts an ID that points to a specific spot
in Ladder, similar to a File Systems Shortcut. The Form Processing
engine then takes, for example, an invoice and populates all the
areas of the tree that need the data. Now initially that might be
just the accounting system, but as the system grows, or as users
find specific needs for different metrics, it would also populate
data into sales representatives account for a percentage of the
sale, or another folder that tracks the number of sales made, or
that updates all the inventory data, if inventory management is
needed.
From a work flow perspective the form passes from one user to the
next to the next based on the rules of the form processing
algorithms. Each time the form moves, new fields are added, data is
collected and modified, things are updated, .blah blah blah ...
because a processing the background that manages the form is saying
what should happen. The form is no longer migrating through email,
but maybe users are being prompted via email to check the form and
do something with it.
Which bring us to a new IDE environment where Forms and Form
Processing need to be built and managed.
So we have a database architecture that sits on separate servers.
We have forms processing that sit on middleware servers and we have
web servers that simply present the forms, collect the information
and tell the middleware servers where to find the new data. We can
create other middle ware services that link email, or RSS feeds, or
other services.
So, what does this have to do with Collaboration Alley? What if
after we've identified all the services we want, we could build them
using this methodology, and allow users to create specific instances
for themselves and tweak it as they needed. So someone builds out a
full workflow process for managing a tradeshow using our system.
We've provided most of the framework, they state, this is what my
forms look like, this is where the data needs to go, this is who
needs to be updated, this is what they need to see when they see my
forms, and so on... they go as light or as deep as needed.
Is this all doable, yes.
Is it the right path to take .. I don't know. It's the path I keep
seeing to take, and I haven't seen anyone else come up with a better
path yet.
Has anyone else attempted to build this type of system before, not
to my knowledge. No one has thought about how to separate form
processing from the form. They've thought about how the object
model can be separated from the data, but never the form from the
processing.
And am I accurately describing the vision to you? I don't know
about that either.
So, I've been holding off saying what I want because it's a very
drastic change from what most people are used to. And I've been
focusing the group on thinking about services because once you
identify the base services needed, then we can think about how to
tie them together at the database, object model, form processing
level and presentation level.
Ok, very scared now ...
Mike,
--
