Re: [Harbour] SF.net SVN: harbour-project:[14454] trunk/harbour

2010-05-10 Thread francesco perillo
What if I want to register menu items ? Or create a toolbar ?

Maybe you can keep a list of active plugins... just don't scan the
directory to load all plugins but you must activate them before and
only the enabled plugins will be opened at startup...

    % Changed: plugins are loaded on first call instead of
      loading all plugins at startup. Now the overhead is negligible.
___
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


Re: [Harbour] SF.net SVN: harbour-project:[14454] trunk/harbour

2010-05-10 Thread Viktor Szakáts
 Maybe you can keep a list of active plugins... just don't scan the
 directory to load all plugins but you must activate them before and
 only the enabled plugins will be opened at startup...

IMO it's much better and simpler to use the directory listing.

If a plugin is not needed, it's enough to move it away.

Viktor

___
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


Re: [Harbour] SF.net SVN: harbour-project:[14454] trunk/harbour

2010-05-10 Thread francesco perillo
 IMO it's much better and simpler to use the directory listing.

 If a plugin is not needed, it's enough to move it away.

Me too... but sometimes it's easier to enable/disable from a list...
___
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


Re: [Harbour] SF.net SVN: harbour-project:[14454] trunk/harbour

2010-05-10 Thread Viktor Szakáts
 IMO it's much better and simpler to use the directory listing.
 
 If a plugin is not needed, it's enough to move it away.
 
 Me too... but sometimes it's easier to enable/disable from a list...

Then you have to maintain a list, keep it in sync with 
directory list, handle the error, when list refers to 
non-existing plugin, handle the support problem when 
existing plugin is missing from list, deal with sophisticated 
installation/uninstallation which add/removes plugin 
to/from the list in addition to copying/deleting the file.

It's not worth it.

Viktor

___
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


Re: [Harbour] SF.net SVN: harbour-project:[14454] trunk/harbour

2010-05-10 Thread francesco perillo
 It's not worth it.

Ok, I agree. Just scan the directory
___
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


[Harbour] SF.net SVN: harbour-project:[14454] trunk/harbour

2010-05-09 Thread vouchcac
Revision: 14454
  
http://harbour-project.svn.sourceforge.net/harbour-project/?rev=14454view=rev
Author:   vouchcac
Date: 2010-05-10 03:14:05 + (Mon, 10 May 2010)

Log Message:
---
2010-05-09 20:11 UTC-0800 Pritpal Bedi (prit...@vouchcac.com)
  * contrib/hbide/hbide.prg
  * contrib/hbide/ideplugins.prg
% Changed: plugins are loaded on first call instead of 
  loading all plugins at startup. Now the overhead is negligible.

Modified Paths:
--
trunk/harbour/ChangeLog
trunk/harbour/contrib/hbide/hbide.prg
trunk/harbour/contrib/hbide/ideplugins.prg


This was sent by the SourceForge.net collaborative development platform, the 
world's largest Open Source development site.
___
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour