Lighthouse Pro 2.5 (Beta)
Tonight I'm happy to release the beta of Lighthouse 2.5. There are a lot of major changes here, so I thought I'd release it as a beta and let folks play with it a bit first. So what's different?
- New design by Justin Johnson, designer of the new CFLib.
- Milestones can be created for projects, along with an optional due date. You can then assign issues to milestones.
- There was a major change to the Ajax code behind the project view. In the previous versions, all the data was loaded on the first load. This made sorting/filtering super quick, but when projects got a bit large, it made that first hit really slow. I had a client with 400+ bugs, and it got to be pretty unusable. I switched to using Ajax to load a page of data at a time. So when you sort, or filter, it does a new HTTP request, but since it's just passing JSON around, it should still be pretty zippy. My feeling here was - keep the funcitonality the same - but ensure that larger clients wouldn't be 'punished' speed wise. Hopefully this works out well for folks.
- As part of the above change, I switched from Spry to jQuery. This was not done because Spry couldn't handle the functionality. It was done so I could play more with jQuery.
- The application includes some basic documentation in itself now. So for less-technical users who are new to the idea of issue trackers in general, we can provide them with a bit of direction.
- ColdSpring. More on that in a sec.
- When you edit an issue, the email was always pretty good about detailing the changes (status changed from X to Y), now the history field will do the same thing as well.
Ok, some quick screen shots:
Login Screen
Home Screen
Issue Screen
You can find the download below. Please note that this is beta, and should be handled with care. The readme tells you what to do on the database side. I'll blog a bit later today about the ColdSpring integration. I may also blog a bit more detail about the Ajax change if folks are interested.
Comments
Excellent, I must try out this beta. Looks pretty. :-) Well done for using JQuery. (I'm actually using JQuery to fetch, parse and display RSS feeds instead of cffeed)
I've often needed to add lists to bug reports. Using an asterisk as a bullet point is not ideal. How easy is it to add fckeditor with just a few basic formatting buttons?
I've often needed to add lists to bug reports. Using an asterisk as a bullet point is not ideal. How easy is it to add fckeditor with just a few basic formatting buttons?
# Posted By Gary Fenton
| 9/29/08 8:15 AM
In theory as easy as replacing the textarea tag. I leave that to others though, as I'm anti-RTE. ;)
# Posted By Raymond Camden
| 9/29/08 8:27 AM
Scott, didn't you tell me you had a _large_ dataset? (Heh, that's what she said.) Is the new ajax system working ok for you?
# Posted By Raymond Camden
| 9/29/08 8:39 AM
Looks awesome. In the process of trying it out. However is there a 'lh_milestones' table that's supposed to be there? It's not in the setup scripts. Unless I'm overlooking something.
# Posted By Ryan
| 9/29/08 8:47 AM
Ahem:
"The readme tells you what to do on the database side."
;)
"The readme tells you what to do on the database side."
;)
# Posted By Raymond Camden
| 9/29/08 8:51 AM
Very Nice ... I'm Installing It ...
# Posted By Edward Beckett
| 9/29/08 10:27 AM
"Getting Started" link gives me this:
Element VERSION is undefined in APPLICATION.
Maybe I missed something else to do in the readme file. Really not understanding this sort of scattered approach, with an installation file, then a readme file that initially looks like just a changelog & credits & licensing but then also has necessary information in it...
Element VERSION is undefined in APPLICATION.
Maybe I missed something else to do in the readme file. Really not understanding this sort of scattered approach, with an installation file, then a readme file that initially looks like just a changelog & credits & licensing but then also has necessary information in it...
@JC: Bug confirmed, and fixed, and I replaced the download.
I respectfully want to disagree with your 'scattered' approach. All of my apps have used this system for years now: An install folder with full installation instructions, and a readme.txt file that explains changes from one version to another. Because this is the beta, I used the readme to explain what to do for the update. There will be a full 'upgrade' doc when I release the final version. Although the readme will still be there for folks who are curious.
I respectfully want to disagree with your 'scattered' approach. All of my apps have used this system for years now: An install folder with full installation instructions, and a readme.txt file that explains changes from one version to another. Because this is the beta, I used the readme to explain what to do for the update. There will be a full 'upgrade' doc when I release the final version. Although the readme will still be there for folks who are curious.
# Posted By Raymond Camden
| 9/29/08 12:42 PM
if only there was an installation package for coldfusion apps.....
Thanks Ray. Yeah, on your other apps I've tried, the info that's needed is in the install.doc. That's sort of what I was getting at. Since it's beta you're doing it differently, which confused me. :)
Additional issues exist on user_edit.cfm (Element PLAINTEXTPASSWORD is undefined in APPLICATION) and milestone.cfm (Element PROJECT is undefined in URL.)
I assume milestone.cfm would probably work if I had a project, though.
Additional issues exist on user_edit.cfm (Element PLAINTEXTPASSWORD is undefined in APPLICATION) and milestone.cfm (Element PROJECT is undefined in URL.)
I assume milestone.cfm would probably work if I had a project, though.
JC, I confirmed the first report. For the second, did you mean to say milestones.cfm was broken? You should not be able to go to milestone.cfm until you add/edit.
# Posted By Raymond Camden
| 9/29/08 1:24 PM
Or did you manually enter milestone.cfm in the URL? If so, that's your fault. ;) But I can look for it and send back to milestones.cfm.
# Posted By Raymond Camden
| 9/29/08 1:24 PM
Good catches! All fixed.
# Posted By Raymond Camden
| 9/29/08 1:35 PM
Hey Ray! Not sure if this would be a bug or not, but if a user updates an issue without modifying anything or adding a note, it still generates an email.
I sent it to my boss to play with and just got a bunch of emails from him looking at the issues I posted and saving them to get back to the issue list screen.
I sent it to my boss to play with and just got a bunch of emails from him looking at the issues I posted and saving them to get back to the issue list screen.
That's normal. I _could_ add code to see if nothing changed, but on the flip side, a person could use this feature to help push certain issues to the top.
# Posted By Raymond Camden
| 9/29/08 8:18 PM
You could always add a *bump* button to throw some text in if they want to do that. Or javascript to grey out the submit button if there's no text in the box. heh.
Not a big deal I guess, but I know from our existing Altiris system, which we all loathe, we have a few users who always open the darned thing in edit mode to read it and then save it, with no changes, which then emails at minimum half dozen people, some of them twice depending on the settings for the incident. But I wouldn't use this for most of those users I guess, just for our web dev group, possibly even just for myself to help keep my 8 #1 top priority drop everything else projects organized. :)
Not a big deal I guess, but I know from our existing Altiris system, which we all loathe, we have a few users who always open the darned thing in edit mode to read it and then save it, with no changes, which then emails at minimum half dozen people, some of them twice depending on the settings for the incident. But I wouldn't use this for most of those users I guess, just for our web dev group, possibly even just for myself to help keep my 8 #1 top priority drop everything else projects organized. :)
You know, that's a good point. Would you mind bringing it up to me after the release, or filing it as a bug report on RIAForge?
# Posted By Raymond Camden
| 10/1/08 12:55 PM
Hi, I noticed a bug with e-mail send as issues, this bug is in the view.cfm where different items are "changed" to there new values. A e-mail issues has empty values and you get errors about the value not being a uuid. I changed view.cfm to check if the value is empty and everything works. The check was already done with milestones but not with the other fields.
if you like I could send you the file.
Also, i changed the status table with a "show" column to let me choose to show the status in my overview of issues or not. We have a status "closed" and I don't want to see those status in my overview.
If you like I could also send you this change.
One project dropped from 600+ issues to 80+ that actually mattered :-)
if you like I could send you the file.
Also, i changed the status table with a "show" column to let me choose to show the status in my overview of issues or not. We have a status "closed" and I don't want to see those status in my overview.
If you like I could also send you this change.
One project dropped from 600+ issues to 80+ that actually mattered :-)
# Posted By Tjarko Rikkerink
| 10/2/08 4:36 AM
Another note: I changed the mailprocess.cfm in this way that e-mail in the mailbox that is not assigned to ANY of the projects in your setup is deleted from the mailbox as well. After checking the debug mode I found out that one mailbox was filled with about 200+ spam mail.
Oh.. and thanks for this great app!! I almost forgot to mention this :-)
Oh.. and thanks for this great app!! I almost forgot to mention this :-)
# Posted By Tjarko Rikkerink
| 10/2/08 5:28 AM
I'd like to get your mods Tjarko. But now the one for show. That one I don't want to integrate. Please and thank you.
Folks, I fixed a bug with pagination, but I haven't pushed the fix up here. I'll push it aftr I get these other mods from Tjarko.
Folks, I fixed a bug with pagination, but I haven't pushed the fix up here. I'll push it aftr I get these other mods from Tjarko.
# Posted By Raymond Camden
| 10/2/08 5:45 AM
Zip updated again. Fixes pagination bug. Fixes a mail server setting issue in App.cfc.
# Posted By Raymond Camden
| 10/2/08 11:43 AM
Hi Raymond, I have tried 3 possible e-mail addresses now but the keep on bouncing for me :-( Could you send me an e-mail at tjarko at carlosgallupa.com?? That way I can send you the 2 small changes. Txns!!
Long-time LHP user here; I've got the beta up and running. A couple of items for consideration:
1) The SQL at line 453 in components/issuemanager.cfc won't run against MS Access without modification. I've used LHP on a couple of small projects with Access for several years w/o problem but had to tweak the SQL to get the beta to work. I'll follow up off-line with updated SQL that should continue to work on other DB platforms but also works on SQL.
2) RE the new layout, please consider going back to an elastic page layout that expands and contracts based on the browser window width.
1) The SQL at line 453 in components/issuemanager.cfc won't run against MS Access without modification. I've used LHP on a couple of small projects with Access for several years w/o problem but had to tweak the SQL to get the beta to work. I'll follow up off-line with updated SQL that should continue to work on other DB platforms but also works on SQL.
2) RE the new layout, please consider going back to an elastic page layout that expands and contracts based on the browser window width.
# Posted By Ron Stewart
| 10/3/08 4:29 PM
I updated the zip again. It fixes Ron's Access issue, but as I can't test, someone else will have to. I tested on MySQL of course.
I fixed an issue from riaforge where sql server complained on the search. It didn't throw an error on mysql, but my fix should be good.
I fixed _another_ bug I can't reproduce, involving MilestoneDAO as well.
@Ron - as to your 'make it wide' rule, I'd like that as well. If someone can share the CSS fix, I'll gladly include it.
I want to wrap this up by Monday I think.
I fixed an issue from riaforge where sql server complained on the search. It didn't throw an error on mysql, but my fix should be good.
I fixed _another_ bug I can't reproduce, involving MilestoneDAO as well.
@Ron - as to your 'make it wide' rule, I'd like that as well. If someone can share the CSS fix, I'll gladly include it.
I want to wrap this up by Monday I think.
# Posted By Raymond Camden
| 10/4/08 8:14 AM
Hi Raymond,
We have been using the previous version of Lighthose for the past year. Is there any way to maintain the data in the old DB after migrating to version 2.5? Thanks so much for creating such a useful progrm!
Regards,
Mike Flach
We have been using the previous version of Lighthose for the past year. Is there any way to maintain the data in the old DB after migrating to version 2.5? Thanks so much for creating such a useful progrm!
Regards,
Mike Flach
# Posted By Michael Flach
| 10/23/08 11:38 AM
I don't know how old your LHP is - but I don't see why you would not be able to migrate the data. Most of my changes have been additive.
# Posted By Raymond Camden
| 10/23/08 11:40 AM
How, where, or do you need to add the coldspring intergration for version 2.5 of lighthouse?
After I installed the code I get the folowing message
Could not find the ColdFusion Component or Interface coldspring.beans.DefaultXmlBeanFactory.
The readme tells you what to do on the database side. I'll blog a bit later today about the ColdSpring.
After I installed the code I get the folowing message
Could not find the ColdFusion Component or Interface coldspring.beans.DefaultXmlBeanFactory.
The readme tells you what to do on the database side. I'll blog a bit later today about the ColdSpring.
# Posted By Geoffrey Barth
| 11/12/08 1:06 PM
Just go to to coldspringframework.org. You should NOT be using the download here. You should be using the download from riaforge: http://lighthousepro.riaforge.org.
# Posted By Raymond Camden
| 11/12/08 1:10 PM
There was a couple of things I wound up tinkering. I disabled emails because my group was in lighthouse almost everyday and the quantity of emails was too great. I flipped the ordering of notes so the most recent was on top, and made the issue text area a giant fckeditor window so we could do things like past email content with lists and links.