On 08/25/2011 11:06 PM, Carsten Haitzler (The Rasterman) wrote:
> On Thu, 25 Aug 2011 21:49:12 -0300 Wido<wido...@gmail.com>  said:
>
> you dont merge them. you simply add features to the one u like from the other.
> e's shot module is simple. i didn't intend to make it complicated. you could 
> add
> features if u wanted. it's not hard. emprint is a stand alone tool though. 
> shot
> is just a feature added to e17 via a module
>
I had actually wanted to do just that...add to E's screenshot tool some 
missing features from emprint, just have not had the time yet. Patches 
welcome ;)

dh

>> What about merge them?
>>
>> Sure, emprint has a lot of goodstuff and the newer screenshot too......why
>> waste effort in maitaining two good tools that practically do the same
>> thing?
>>
>> wouldn't be smarter to merge both projects, both perspectives into one much
>> more rich application/module?
>>
>> 2011/8/25 Christopher Michael<cpmicha...@comcast.net>
>>
>>> On 08/25/2011 07:02 AM, Carsten Haitzler (The Rasterman) wrote:
>>>> On Wed, 24 Aug 2011 11:49:21 -0400 "J(tWdy)P"<jtw...@ttlc.net>   said:
>>>>
>>>>> Has emprint been depreciated or something???
>>>>>
>>>>> I ask about emprint because I'm used to using it in a few personal
>>> scripts.
>>>>> Some of which I've assigned keyboard shortcuts too. And I've got a new
>>>>> installation of Sabayon Linux on my laptop. And Sabayon's "own" package
>>>>> management system "entropy" doesn't seem to offer emprint.
>>>>>
>>>>> I would have just thought it was a Sabayon thing but when I googled
>>> around
>>>>> about it I came across something about a new E17 built-in "simple"
>>> screenshot
>>>>> utility coming down the pipe. (Which hasn't yet trickled down to any of
>>> my
>>>>> installed Linux distros yet) And it wouldn't be available when I'm using
>>> E16
>>>>> or xfce like emprint is, in any case.
>>>>>
>>>>> And I'd really like to know if I need to take measures with the various
>>>>> Linux installations where I still have it to prevent their package
>>> managers
>>>>> from automatically uninstalling it on me. At least until I find an
>>>>> acceptable scriptable command line substitute that can be used
>>>>> independently of which desktop I'm currently using.
>>>>>
>>>>> If emprint really is going away, can somebody recommend another desktop
>>>>> independent CLI tool that I could modify my scripts to use?
>>>>
>>> No, emprint is not going anywhere. I plan to support it and keep it
>>> alive ;) as it is much lighter than things like scrot, etc (because it's
>>> efl based). Yes, e17 itself now comes with a simple screenshot tool, but
>>> it is not as powerful as emprint (can't do regions, or grab specific
>>> windows, etc). So no, emprint will be staying around for quite some time...
>>>
>>>
>>> dh
>>>
>>>> import (imagemagick)
>>>>
>>>>> TIA
>>>>>
>>>>> --
>>>>> |  ~^~   ~^~
>>>>> |<?>     <?>         Joe (theWordy) Philbrook
>>>>> |      ^                J(tWdy)P
>>>>> |    \___/<<jtw...@ttlc.net>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> EMC VNX: the world's simplest storage, starting under $10K
>>> The only unified storage solution that offers unified management
>>> Up to 160% more powerful than alternatives and 25% more efficient.
>>> Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
>>> _______________________________________________
>>> enlightenment-users mailing list
>>> enlightenment-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
>>>
>>
>>
>>
>> --
>> Wido
>
>


------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management 
Up to 160% more powerful than alternatives and 25% more efficient. 
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to