Galleon has been updated today, and it finally has a project page. So what was changed?
- A bug was reported when you deleted content that people were subscribed too.
- The page templates forgot to turn off enablecfoutputonly.
- Search terms needed to be limited to 100 characters. This was done in various places.
- Message titles can be 100 characters long. DB scripts updated to reflect that.
- Etc.
So not a huge update - but an update nonetheless. Oh, I also changed the footer to stop saying copyright Raymond Camden. Sure I still have the copyright, but I think it may make people think they can't use it. I've changed it to link to the project page and my blog.
What are the future plans for Galleon? Even though I think it is silly as hell, people seem to want that silly (stupid) smiley language. So I guess I'll add that. What is much more useful is file attachments to messages.
Archived Comments
Noooooo not the smiley language.
I'm going threw your apps now and doing a pretty intense integration. I'll send you my thoughts in a week or so, but I already have quite a few suggestions.
The biggest change I had to do (I'm actually converting them to a fusebox type approach with a single file handler so that I can include them in another application) is that you use the base of the application scope for storing all your application vars.
I'm including your apps in a larger application so I have had to put them in thier own scope in application (application.blogcfc, application.galleon).
Could be a very transparent change for you to do in your code base that would really help in future integrations.
thanks.
At my job we wouldn't dare deploy a forum without smileys! Attachments are nothing compared to the smileys!
Anyway, we plan to review your Galleon to include in several planned applications, doing some sort of conenction with the Model-Glue framework that we plan to adapt everywhere.
Ray: I felt the same way about emoticons for a long time, but I've since surrendered. I'm not sure why I softened on them... after a while, it just seemed like fighting folks' expectations just wasn't worth it.
Bug using MySQL < 5.01?
The database booleans are defined as TINYINT(1) but in the queries the CF_SQL_BIT parameter is used. Does not work, have to be the CF_SQL_TINYINT parameter.
It should work fine w/ MySQL 4.1 using the drive from MySQL, NOT the built-in driver.