Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

Browser CRM 5.002 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Browser CRM 5.002 (Default branch)
# 1  
Old 02-11-2008
Browser CRM 5.002 (Default branch)
Image Browser CRM is a Web-based suite combining integrated email functionality with flexible and powerful CRM (customer relationship management) and collaboration tools. Browser CRM is a single, comprehensive application that is accessible from anywhere. Browser CRM logs incoming and outgoing email against the customer record to build a complete customer history along with other Browser CRM events including Opportunities, Tasks, Appointments, Memos, Documents, and custom events. License: Free To Use But Restricted Changes:
The 5.x branch is very stable and 5.002 packages a number of key changes, including user interface fixes for Internet Explorer 7 and Safari on Mac, general user interface enhancements, significant improvements to People & Company module configurations, and improvements for foreign fields, sorting, and menu based filters. The default character set is now UTF-8 and there are configuration changes to the default home page to avoid memory limit issues in some configurations. There is also an improved import script, with fixes for merging and improved memory handling for large imports.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

padre::browser

Padre::Browser(3pm)					User Contributed Perl Documentation				       Padre::Browser(3pm)

NAME

       Padre::Browser -- documentation browser for Padre

DESCRIPTION

       Provide an interface for retrieving / generating documentation, resolving terms to documentation (search?) and formatting documentation.

       Allow new packages to be loaded and interrogated for the MIME types they can generate documentation for. Provide similar mechanism for
       registering new documentation viewers and URI schemes accepted for resolving.

       NOTE: I think all the method names are wrong. Blast it.

SYNOPSIS

	 # Does perlish things by default via 'Padre::Browser::POD'
	 my $browser = Padre::Browser->new;
	 my $source = Padre::Document->new( filename=>'source/Package.pm' );

	 my $docs = $browser->docs( $source );
	 # $docs provided by Browser::POD->generate
	 #  should be Padre::Browser::Document , application/x-pod

	 my $output = $browser->browse( $docs );
	 # $output provided by Browser::POD->render
	 #  should be Padre::Document , text/x-html

	 $browser->load_viewer( 'Padre::Browser::PodAdvanced' );
	 # PodAdvanced->render might add an html TOC in addition to
	 #  just pod2html

	 my $new_output = $browser->browse( $docs );
	 # $new_output now with a table of contents

METHODS

   new
       Boring constructor, pass nothing. Yet.

   load_provider
       Accepts a single class name, will attempt to auto-use the class and interrogate its "provider_for" method. Any MIME types returned will be
       associated with the class for dispatch to "generate".

       Additionally, interrogate class for "accept_schemes" and associate the class with URI schemes for dispatch to "resolve".

   load_viewer
       Accepts a single class name, will attempt to auto-use the class and interrogate its "viewer_for" method. Any MIME types returned will be
       associated with the class for dispatch to "render".

   resolve
       Accepts a URI or scalar

   browse
   accept
EXTENDING

	 package My::Browser::Doxygen;

	 # URI of doxygen:$string or doxygen://path?query
	 sub accept_schemes {
	     'doxygen',
	 }

	 sub provider_for {
	     'text/x-c++src'
	 }

	 sub viewer_for {
	     'text/x-doxygen',
	 }

	 sub generate {
	     my ($self,$doc) = @_;
	     # $doc will be Padre::Document of any type specified
	     # by ->provider_for

	     # push $doc through doxygen
	     # ...
	     # that was easy :)

	     # You know your own output type, be explicit
	     my $response = Padre::Document->new;
	     $response->{original_content} = $doxygen->output;
	     $response->set_mimetype( 'text/x-doxygen' );
	     return $response;
	 }

	 sub render {
	     my ($self,$docs) = @_;
	     # $docs will be of any type specified
	     # by ->viewer_for;

	     ## turn $docs into doxygen(y) html document
	     #	...
	     #

	     my $response = Padre::Document->new;
	     $response->{original_content} = $doxy2html->output;
	     $response->set_mimetype( 'text/x-html' );
	     return $response;

	 }

perl v5.14.2							    2012-06-27						       Padre::Browser(3pm)