Description: KWebWatch is a small utility designed to monitor urls, checking for changes. It docks into the KDE 3.0 panel and can also be used as a launching pad for viewing urls in your favorite browser.Last changelog:
KDE3 port, gcc3 compile, drag and drop url from browser
When I hit the X button to close it, it kills the app even though I set it to run the system tray. Other apps just hide the window, and continue to run from the system try.
Not that big a deal, but I have the habit of hitting X since that is easier then going down to the tray and clicking the icon again.
It would also be nice to be able to move items from 1 group to another.
Overall I like it so far, I have only been running it 20 minutes, but I have been needing something like this to monitor sites that don't change that much.
Thanks.
Thanks for the feedback. I think you are referring to these lines in kwebwatch/makefile.am:
$(mkinstalldirs) $(kde_htmldir)/en/kwebwatch
rm -f $(kde_htmldir)/en/kwebwatch/common
ln -s $(kde_htmldir)/en/common/ $(kde_htmldir)/en/kwebwatch/
$(INSTALL_DATA) $(srcdir)/index.docbook $(kde_htmldir)/en/kwebwatch/index.docbook
[...]
The Makefile.am was based off a template from the KDE2 days so it wouldn't surprise me if it could use some work. Any pointers to the correct and modern way to install kde documentation are welcome :-)
Doesn't kdevelop automatically take care of that sort of thing? Here's (imho) what looks like a good, simple example of how docs should be installed:
***./doc/en/Makefile.in***
$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail
echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/; \
$(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/; \
echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/; \
$(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/; \
-rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/common
$(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/common
$(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail
echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/$$base ;\
$(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/$$base ;\
rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/$$base ;\
***End***./doc/en/Makefile.in***
This was found by:
for i in `find`; do echo "***$i***"; grep DESTDIR $i; echo "***End***$i***"; done
AFAIK, kdevelop was designed so that one can code more, and worry less about these sort of things. I would imagine that the easiest way to get things up to KDE3 standards, would be to import your current workbase, deal with the kdevelop warnings, then export the modern GNU-tools source-package.
Ratings & Comments
4 Comments
When I hit the X button to close it, it kills the app even though I set it to run the system tray. Other apps just hide the window, and continue to run from the system try. Not that big a deal, but I have the habit of hitting X since that is easier then going down to the tray and clicking the icon again. It would also be nice to be able to move items from 1 group to another. Overall I like it so far, I have only been running it 20 minutes, but I have been needing something like this to monitor sites that don't change that much. Thanks.
make install shouldn't touch anything outside of DESTDIR. I'm specifically referring to the ln -s /usr/share/doc/HTML/en/common to somewhere else.
Thanks for the feedback. I think you are referring to these lines in kwebwatch/makefile.am: $(mkinstalldirs) $(kde_htmldir)/en/kwebwatch rm -f $(kde_htmldir)/en/kwebwatch/common ln -s $(kde_htmldir)/en/common/ $(kde_htmldir)/en/kwebwatch/ $(INSTALL_DATA) $(srcdir)/index.docbook $(kde_htmldir)/en/kwebwatch/index.docbook [...] The Makefile.am was based off a template from the KDE2 days so it wouldn't surprise me if it could use some work. Any pointers to the correct and modern way to install kde documentation are welcome :-)
Doesn't kdevelop automatically take care of that sort of thing? Here's (imho) what looks like a good, simple example of how docs should be installed: ***./doc/en/Makefile.in*** $(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/; \ $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/; \ echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/; \ $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/; \ -rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/common $(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/common $(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/$$base ;\ $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/$$base ;\ rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/kcheckgmail/$$base ;\ ***End***./doc/en/Makefile.in*** This was found by: for i in `find`; do echo "***$i***"; grep DESTDIR $i; echo "***End***$i***"; done AFAIK, kdevelop was designed so that one can code more, and worry less about these sort of things. I would imagine that the easiest way to get things up to KDE3 standards, would be to import your current workbase, deal with the kdevelop warnings, then export the modern GNU-tools source-package.