SimpleTicket call added to podcast
The SimpleTicket call held today, April 26, 2006 has been added to the Podcast. If you missed the call check out the recording.
Here is a summary of the topics covered during the call:
- PostgreSQL: To facilitate PostgreSQL support, we request that if you have any code which alters the SQL to cross-commit to the suntel branch or consult with the mailing list. After the May 1 release, we’re going to freeze the code so we can remove SQL from the controllers and views such that simpleticket will be database agnostic.
- Search Functionality: We’ve started to implement search functionality using SimpleSearch. Currently there isn’t a “ticket details” page so the question was where should the search result link to. The answer is to use the search to populate the current ticket view and use pagination (”Today, Yesterday, etc.”)
http://www.chadfowler.com/SimpleSearch
http://wiki.rubyonrails.com/rails/pages/SearchGenerator - User Interface Design: Everyone is satisfied with replacing the popup with a more seamless interface. As mentioned in the search conversation it’s been agreed upon to use pagination and not scroll bars.
- Rich Text Editing: The subject of integrating TinyMCE came up and the only issue was full text search could pose a problem as the contents would contain HTML. At best this could be valuable to many users and at worst we can make the support a system-wide option. In doing so, I’ve confirmed the search mechanism we are using ignores markup. The subject of using markdown was brought up as well. We can use markdown for configurations where the use of tinymce is not preferred.
http://tinymce.moxiecode.com/ - Security: It has been agreed upon to filter user input and to start filtering for javascript. This could be done by only allowing only certain html tags - this would be a better method than filtering out javascript. The global company password methods still require implementation and Kate has indicated she will be able to work on this.
- Wiki: We’ll be setting up a user wiki and developer wiki. Fred will probably be setting up pmwiki (although we may look at a rails-based wiki - to be consistent with the rest of the site [blog? what blog?])