On Tue, Aug 7, 2012 at 5:10 PM, Victor Olaya wrote:
>>
>> I don't know the SEXTANTE architecture well enough but surely we could
>> keep the vector menu in place and just delegate the work to some
>> SEXTANTE tool?
>>
>
> Sure, you can keep the menu, and even the custom dialog, and then call
> the
>
> I don't know the SEXTANTE architecture well enough but surely we could
> keep the vector menu in place and just delegate the work to some
> SEXTANTE tool?
>
Sure, you can keep the menu, and even the custom dialog, and then call
the SEXTANTE algorithm from there. No difference for users, but a
2012/8/7 Nathan Woodrow
> Personally I am not a fan (not yet anyway) of removing the plugins in
> favour of an interface though only Sextante. I would be happy if
> fTools could be interfaced and scripted though Sextante but removing
> from the Vector menu at this current time would be very bad
Hi
On Tue, Aug 7, 2012 at 3:34 PM, Nathan Woodrow wrote:
> Personally I am not a fan (not yet anyway) of removing the plugins in
> favour of an interface though only Sextante. I would be happy if
> fTools could be interfaced and scripted though Sextante but removing
> from the Vector menu at thi
Il 07/08/2012 15:36, Alexander Bruy ha scritto:
> I'm already working on moving fTools to SEXTANTE and also
> fix some existing bugs. As work is not complete I don't commit
> it to the SEXTANTE main repo.
>
> If anyone interested, I can upload existing code somewhere.
> But don't expect much, curre
I'm already working on moving fTools to SEXTANTE and also
fix some existing bugs. As work is not complete I don't commit
it to the SEXTANTE main repo.
If anyone interested, I can upload existing code somewhere.
But don't expect much, currently only 15 algorithms reviewed
and I even didn't test the
Personally I am not a fan (not yet anyway) of removing the plugins in
favour of an interface though only Sextante. I would be happy if
fTools could be interfaced and scripted though Sextante but removing
from the Vector menu at this current time would be very bad IMO.
- Nathan
On Tue, Aug 7, 201
Hi Victor,
I understand the idea of including all plugins in Sextante, even if only as a
wrap for the first times. I just wonder if it will raise some confusion for
users who are not aware of this, when they realize that there are algorithms
that can not be used in modeler and in batch. They ma
Il 06/08/2012 19:08, Victor Olaya ha scritto:
> a menu item to an entry in the SEXTANTE toolbox. That adds some
> homogeneity and is probably less confusing, IMHO
IMHO we should first reach complete parity between a particular backend
and its Sextante equivalent, having it fully tested, and then re
Hi
On Mon, Aug 6, 2012 at 7:08 PM, Victor Olaya wrote:
> Interesting topic. I think we should try to replicate those
> functionalities and when they are fully supported in SEXTANTE, maybe
> remove them in their original form.
>
+1 - lets get rid of any duplicated stuff, consolidate things and
ge
Interesting topic. I think we should try to replicate those
functionalities and when they are fully supported in SEXTANTE, maybe
remove them in their original form.
Something that can be done while that happens is to wrap those
algorithms that are a bit harder to adapt to SEXTANTE, wrapping them
a
Hi all,
since SEXTANTE will be a part of QGIS core soon (see [0] and [1]) so I want to
raise a new discussion related to it.
As all you know, currently SEXTANTE contains many providers. Some of them
partially duplicates existing core functionality of QGIS. First of all
I mean fTools
and GDALTools
12 matches
Mail list logo
