Thanks for the heads up. I had missed Robs post. Im not sure exactly
how it would fit with COAL? What part of it though do you think would
work well in COAL? The components that could drive a custom system
could definately fit if they were purposed the right way, but im not
sure if that is what you are meaning.
Thanks!
--
Ryan Guill
BlueEyesDevelopment
ryan...@gmail.com
www.ryanguill.com
(270) 217.2399
got google talk? Chat me at ryan...@gmail.com
The Coldfusion Open Application Library - COAL - http://coal.ryanguill.com
Use CF and SQL? Try qBrowser - http://www.ryanguill.com/docs/
www.ryanguill.com/
The Roman Empire: www.ryanguill.com/blog/
anyways, this list has been silent for some time so if anything, just
throwin something out there that struck me as seeming appropriate for
this project
sean
COAL has been quiet lately, and I am trying to do something about
that. My main problem is the lack of developers getting involved and
writing components to go in COAL. The framework is pretty much done,
as its fairly lightweight by design. The only changes I forsee in the
near future is bug fixes, but until developers start using it it is
sort of hard to find those.
Would you want to write the components to do this? Even if adobe was
to add the features into the next release (which I somehow doubt
personally as its not really high profile) I would image it would
still be useful, especially since COAL is designed to work on 6.1 +.
Thanks again!
I was going to be on for a while and though we could chat a little
easier that way.
If not thats fine too.
I do, however, have an idea for you on how COAL might fit with another
initiative I'm involved with called Grid7. The idea of rolling common
functionality into a reusable service and distributing via COAL is
great in theory as it provides real value to the community (and moreso
to the language). It seems the real key though is going to be in
finding early adopters that derive enough value from expending that
extra effort to make their services using your framework rather than
just writing it for themselves. If it's useful enough to an
organization internally to have this means for packaging commonly-used
services in this way, then they will build out your COAL services in
pursuit of their own self interests and yield value to the community
as a byproduct. Grid7 would actually be a good match for the type of
group that would derive benefit for this and yield services - we can
talk more offline if you wish. We're launching the pilot in 2wks but
our initial group is limited to Ruby developers so it might be a few
months before we incorporate CF people that woudl take advantage of
this.
sean