11 replies to this topic

[Cris D.]

So since trying to break the API "getIntTableRows"...
I'm wondering if there is a software development platform that is particularly compatible with Etomite?

Edited by Cris D., 14 June 2007 - 12:41 AM.

[Ralph]

So since trying to break the API "getIntTableRows"...
I'm wondering if there is a software development platform that is particularly compatible with Etomite?

Do you mean like a PHP IDE, which is already being discussed in at least one other forum thread...???

[Randy]

Perhaps he means building future versions of Etomite with a base of code that more clearly represents a framework. So Etomite continues to thrive as a CMS while developers have a full blown framework to work from underneath (technically, academically, Eto is a mini-framework...but I'll defer). There are some wonderful PHP development frameworks out there that would be very cool to have available underneath Eto. I suppose you could think of this as adding the power of the framework API along side the content management capability of Eto. When I say framework I don't mean the likes of Drupal or Horde...I mean like Qcodo or CakePHP. There is a difference.

--------------( I'm not suggesting you turn Eto into a full blown framework..you know I concur with you on that point. )

Edited to include ^^^ the word not above....clearly a different meaning without that word

Edited by Randy, 13 June 2007 - 07:19 PM.

[Dean]

Or do you mean a framework like CodeIgniter?

[Cris D.]

I'm talking framework that allows you to write functional code without relying on Etomite's API's but works with them and will work with the codebase. Was that why you were talking about AJAX in previous threads? Perhaps I am talking about COCOON? I don't really know what I'm talking about, framework sound right, I'm not talking about an IDE.

EDITED LATER: Yes, CakePHP Qcodo and CodeIgniter look right on the money. Has anyone else used / is using these frameworks successfully with Etomite?

Edited by Cris D., 14 June 2007 - 12:30 AM.

[Ralph]

Etomite is far more than a simple "framework"... But it's not a full-blown IDE, either... But I don't consider Etomite to be a CMS either - nor a portal... Just exactly where it lies in the realm of buzz-words is kinda tough to pin down... Which is why I have always referred to it as more of a web-app platform, when you stop wrapping your head around the notion that a platform has to be an operating system and/or hardware architecture... While people are big on fitting everything into a category, does Etomite really need to fit into a category...???

I'd rather see Etomite break the perceived notion of having to conform and fit into a little box... Etomite is more than that which is why we have so many people who have stuck with the code base these past several years... They've tried the rest and decided that Etomite was just enough different to be the <your definition here> to do the job...

So, what is Etomite...??? Good question... Might be a good time to start a poll to see what the community thinks...

[Ralph]

EDITED LATER: Yes, CakePHP Qcodo and CodeIgniter look right on the money. Has anyone else used / is using these frameworks successfully with Etomite?

I have played with all three... I like some ideas from each, yet each one also has some concepts that I don't like... Some are lacking the full scope of what I envision in a package... Others make me feel like my hands are always tied... It's checking out the other packages that reaffirms my vision for Etomite...

[Randy]

So, what is Etomite...??? Good question...

I don't think it's so much what you call it. Stepping away from the semantics of this thread and looking squarely at what folks have done with Eto should indicate where it needs to grow. I care less about semantics then I do about having to rewrite trivial code over and over. That is the basic tenant of any library of code (software reuse) regardless of its incarnation.

If Etomite doesn't provide the foundational code required to avoid rewriting trivial code (over and over again) perhaps there is a need for an external library of code to fill the gaps for snippet writers. Since Dean mentioned CodeIgniter I've listed the library of capabilities it provides. Scouring the forums and snippets, it is undeniable that nearly all of these capabilities have been requested or discussed...

Class Reference

* Benchmarking Class
* Calendaring Class
* Config Class
* Database Class
* Email Class
* Encryption Class
* File Uploading Class
* FTP Class
* HTML Table Class
* Image Manipulation Class
* Input and Security Class
* Loader Class
* Language Class
* Output Class
* Pagination Class
* Session Class
* Trackback Class
* Template Parser Class
* Unit Testing Class
* URI Class
* User Agent Class
* Validation Class
* XML-RPC Class
* Zip Encoding Class


Helper Reference

* Array Helper
* Cookie Helper
* Date Helper
* Directory Helper
* Download Helper
* File Helper
* Form Helper
* HTML Helper
* Inflector Helper
* Security Helper
* Smiley Helper
* String Helper
* Text Helper
* Typography Helper
* URL Helper
* XML Helper

I'll look at this further as I have time to see if there is an integration path, but with Cocoon on the distant horizon I fear I'll be spinning my wheels.

[Cris D.]

If Etomite doesn't provide the foundational code required to avoid rewriting trivial code (over and over again) perhaps there is a need for an external library of code to fill the gaps for snippet writers.

Now thats what I'm talking about!

[Cris D.]

I've been playing with CodeIgniter (CI), and it seems pretty simple to use.

What is the most efficient method to include it as a mod? The more I look into this, the larger and more complex the task seems...

What would be the best path to evaluate a snippet from within Etomite but also make use of CI's inbuilt functions?

Should this be added to the index.php file as an include? a class? as part of the evaluateSnippet() function? Another option I've not mentioned?

Will CI snippets need to be saved in the site_content_snippet table? Or should they stay separate in a CI folder?

I don't expect it to be integrated any time soon, I'm just trying to get an appreciation of what is actually involved in this process and get a feel for the way I should be using CI which will allow for integration later.

[Ralph]

I've been playing with CodeIgniter (CI), and it seems pretty simple to use.

What is the most efficient method to include it as a mod? The more I look into this, the larger and more complex the task seems...
<<< SNIP >>>

While CodeIgniter does have some nice features I think you'll find it difficult to try to get it to integrate with Etomite... I'd probably be more inclined to attempt to replicate the functionality rather than attempting to integrate... This is especially true given the fact that the current code base in in a maintenance mode - at least for now...

[Randy]

Hi Cris,

If you want to pursue the integration, perhaps the most direct way would be to make the Etomite class into a CI front controller (that is essentially what it does now). Secondly, you'll have to create a controller in the same fashion to deal with the functionality in the /manager/index.php file. That would get things started. You should work on moving all the presentation into view files, and all the database capabilities into models. You don't have to do either of these last two for things to work. This all sounds easy...but it isn't.

The problem, as with all 'integrations', is that both environments must be 'in control' to some extent to work properly. 'Integrating' as you describe would require some amount of duplication in functionality and configuration. This always ends up being a mess. You've been working with a mini version of this type of thing with EtoGal. It is a wonderful capability (that I use), but it has grown too big to be a 'snippet' any longer.


Frankly, it would be ideal to build Eto on top of something like CI. Eto could be essentially identical to the user, while providing a great foundation to build upon. I would love to see something like this too. There are many obstacles....

Don't hold your breath.