Robertson-Ravo, Neil (RX) wrote:
After quite an extended play with the system at the weekend, I have a few
questions.   When creating a type it all works fine and dandy (though I am
not sure if the system also creates the folders within
{applicationname}packages\types\   for you?).

Folder creation? no.


The idea of the folder is simply to hold included methods and/or PLPs that you might be using. Why do this? Well it's just a way of making things neater -- you could of course have the entire CFC specified in a single file.

Deleting types... Creating types via creation on a new .cfc is great and
very user friendly BUT when you physically delete the cfc for a new type
after it has been deployed to the schema does nothing - the system will not
even recognise the fact it has been deleted (except on restart of the
services and even then it will leave the schema intact with the new object
types.)

Deleting types? Well without the CFC the type doesn't get defined to the system on application intialisation so it is effectively unavailable. There is no automated methodology for getting rid of the types tables and references -- I think you're right in suggesting this as a worthwhile feature enhancement.


I think we rarely delete whole types from the system so it hasn't become enough of an issue for us to bother building machinery for it just yet.

This is more of an exhancement request : I would love a way to copy system
types such as dmHTML into user types ? and then hide the system types.

Do you mean substitute your own customised dmHTML for the core dmHTML type?? If so, specifically what elements of dmHTML are you changing??


Why was there never a way to create types via the back-end?  not so much of
a problem as the CFC creation is so simple and so great it doesnt really
bother me.

Well this would mean scripting automatic CFC creation. But the primary reason is one of code version control. We like to be able to version all the code changes -- having the system dynamically create a CFC on the server makes it difficult to accommodate changes in version control systems. Oh and of course I guess it's byassed by our own internal preference to script objects :)


The same goes for Containers - was the logic behind containers that they
would be created on the fly much like <cf_page> and Spectra?

Yes similar concept to Spectra. Similar problem too in that there is no efficient garbage collection model just yet for containers -- but we're looking to make some major enhancements to containers before the end of the year.


Thanks - and I must say, I am loving it.  Once we get past all of the little
bugs in the system where we can totally skin the system to our hearts
content I plan to roll out a system with all our events (over 150+ and
growing).

That's great news! All we can ask is spread the word -- the more FarCry developers the better.


Best regards,

-- geoff
http://www.daemon.com.au/



---
You are currently subscribed to farcry-dev as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]

Reply via email to