On 15 Jun., 14:25, Yuval Levy wrote:
> What I still would like to see (don't know if it is possible/feasible in short
> time as the release is more important) is a pop up window like the one of
> hugin-stitch_project that displays the console output in the GUI.
see
http://groups.google.com/gr
On 18 Jun., 04:55, Yuval Levy wrote:
> > The problem was just that python's print statements seem to go
> > directly to the underlying stdio handles (stdin, stdout and stderr)
> > instead of C++'s cin, cout, cerr - so redirecting the output worked
> > only for any operator<< calls within C++. M
On 18 Jun., 05:23, Yuval Levy wrote:
> On June 15, 2011 10:36:45 AM kfj wrote:
> > > Short term I would display a message asking the user to start Hugin from
> > > the CLI and report the message on the bug tracker
>
> > This does not work on Windows. Or does it now?
>
> no clue. Even on Kubuntu
On June 15, 2011 10:36:45 AM kfj wrote:
> hpi.py currently has no other way of telling hugin what's wrong than to
> 'return -10'. We do really need a better protocol.
where do we start?
>
> > Short term I would display a message asking the user to start Hugin from
> > the CLI and report the messa
On June 17, 2011 06:06:20 AM kfj wrote:
> On 15 Jun., 14:25, Yuval Levy wrote:
> > What I still would like to see (don't know if it is possible/feasible in
> > short time as the release is more important) is a pop up window like the
> > one of hugin-stitch_project that displays the console output
Hi Kay,
On June 17, 2011 12:07:12 PM kfj wrote:
> On 17 Jun., 14:50, Yuval Levy wrote:
> > Moreover, "system requirements" are more complex for scripted Python than
> > for compiled C++ code. Kay says that his five plugins all work and are
> > useful on his Kubuntu system. I have the "same" Kub
On 17 Jun., 14:50, Yuval Levy wrote:
> Moreover, "system requirements" are more complex for scripted Python than for
> compiled C++ code. Kay says that his five plugins all work and are useful on
> his Kubuntu system. I have the "same" Kubuntu system and yet my success
> running them is more li
On June 15, 2011 02:23:59 AM Gnome Nomad wrote:
> I think in some applications, a SCRIPT is something written in a script
> language and interpreted at run time, while a plugin is compiled binary
> code that uses the parent application as an API.
There are many different definitions, and personall
On June 17, 2011 05:15:08 AM David Haberthür wrote:
> On 17.06.2011, at 10:29, kfj wrote:
> > This google groups
> > interface sucks. It sometimes takes to load forever! Can't we move to
> > somehwere better?
>
> I follow this (and other) google groups in my Email application using a
> tiny bit of
On June 15, 2011 05:22:07 PM T. Modes wrote:
> On 15 Jun., 01:55, Yuval Levy wrote:
> > > What's the difference between a script and a plugin?
> >
> > A plugin runs within Hugin. A script runs as a standalone. And there is
> > also a hybrid category that can do both.
>
> That's not fully corre
On 15 Jun., 14:25, Yuval Levy wrote:
> What I still would like to see (don't know if it is possible/feasible in short
> time as the release is more important) is a pop up window like the one of
> hugin-stitch_project that displays the console output in the GUI.
I looked into the matter a bit ye
On 17 Jun., 11:15, David Haberthür wrote:
> On 17.06.2011, at 10:29, kfj wrote:
>
> > This google groups
> > interface sucks. It sometimes takes to load forever! Can't we move to
> > somehwere better?
>
> I follow this (and other) google groups in my Email application using a tiny
> bit of filt
On 17.06.2011, at 10:29, kfj wrote:
> This google groups
> interface sucks. It sometimes takes to load forever! Can't we move to
> somehwere better?
I follow this (and other) google groups in my Email application using a tiny
bit of filtering-fu. Makes it also easy to follow and interact while
On 16 Jun., 12:06, Gnome Nomad wrote:
> > Yuval Levy wrote:
> > I prefer to call plugins *actions*, because the user is triggering an action
> > by running this code/functionality that just happens to use plugin
> > technology
> > rather than native code.
>
> But how is an "action" different fro
Yuval Levy wrote:
On June 15, 2011 02:23:59 AM Gnome Nomad wrote:
I think in some applications, a SCRIPT is something written in a script
language and interpreted at run time, while a plugin is compiled binary
code that uses the parent application as an API.
There are many different definition
On 15 Jun., 01:55, Yuval Levy wrote:
> > What's the difference between a script and a plugin?
>
> A plugin runs within Hugin. A script runs as a standalone. And there is also
> a hybrid category that can do both.
That's not fully correct. Each plugin can also run "standalone" (if
you consider
On 15 Jun., 14:25, Yuval Levy wrote:
> Kay's mail are as usually, full of very important details, and take more than
> just a few minutes to follow up. So I-ll make myself some pointers which I
> hope to find again when I will have the time to continue on this...
same back, but I'll pick out a
On June 15, 2011 05:34:13 AM kfj wrote:
> On 15 Jun., 08:23, Gnome Nomad wrote:
> > I think in some applications, a SCRIPT is something written in a script
> > language and interpreted at run time, while a plugin is compiled binary
> > code that uses the parent application as an API.
>
> and in h
Kay's mail are as usually, full of very important details, and take more than
just a few minutes to follow up. So I-ll make myself some pointers which I
hope to find again when I will have the time to continue on this...
On June 15, 2011 05:28:37 AM kfj wrote:
> -10 is an import error. Either
On June 15, 2011 02:23:59 AM Gnome Nomad wrote:
> I think in some applications, a SCRIPT is something written in a script
> language and interpreted at run time, while a plugin is compiled binary
> code that uses the parent application as an API.
There are many different definitions, and personall
On 15 Jun., 08:23, Gnome Nomad wrote:
> I think in some applications, a SCRIPT is something written in a script
> language and interpreted at run time, while a plugin is compiled binary
> code that uses the parent application as an API.
and in hugin, a plugin is interpreted code that uses the
On 14 Jun., 21:35, "T. Modes" wrote:
> One point more: With the exposing of the scripts in its own menu there
> needs some more quality management for the plugin.
>
> Currently there are 4 scripts installed and have it own entry in the
> menu. But not all work.
> On windows only two scripts work,
T. Modes wrote:
I have just committed the first part of significant changes related to the new
plugin and scripting interfaces.
PLUGINS
SCRIPTS
Do we really need a distinction into these 2 categories? What's the
difference between a script and a plugin?
I think in some applications, a
On June 14, 2011 03:35:57 pm T. Modes wrote:
> Do we really need a distinction into these 2 categories?
YES
> What's the difference between a script and a plugin?
A plugin runs within Hugin. A script runs as a standalone. And there is also
a hybrid category that can do both.
> One point mo
>
> I have just committed the first part of significant changes related to the new
> plugin and scripting interfaces.
>
> PLUGINS
>
>
> SCRIPTS
>
Do we really need a distinction into these 2 categories? What's the
difference between a script and a plugin?
One point more: With the exposing of th
On 13 Jun., 09:47, Yuval Levy wrote:
> Hi all,
>
> I have just committed the first part of significant changes related to the new
> plugin and scripting interfaces.
Well done!
I noticed that on my system, the installation directory for hsi.py and
hpi.py has moved from
/usr/local/lib/python2.7/
26 matches
Mail list logo
