Re: GM - more questions

Bob Friesenhahn <[email protected]> Fri, 21 Feb 2020 15:46:53 -0600 (CST)
Newsgroups gmane.comp.video.graphicsmagick.apis
Message-ID <[email protected]>
  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3735943886-341603450-1582321613=:17288
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Fri, 21 Feb 2020, 10bxjfhf wrote:
>> 
>> As mentioned, the log is likely being sent to the Windows Application Event 
>> log.  This requires using an application to look at.  I hate the Windows 
>> Application Event log but it is the equivalent of textual log files on 
>> Unix-like systems.
>
> It seems the log.mgk my app was using had <log output="stderr" />.
>
> After I modified this line to <log output="win32debug" /> I was able to see 
> some output in my IDE

If there is a reliable (and quick) way to determine if the running app 
is a console app or something else, then this could be used to assign 
the most useful default.

> The main problem with the GM naming conventions under Win is the fact that 
> the string bits which differentiate between debug & release version are 
> placed in the middle of the project name. This makes it very difficult to 
> both stay consistent with the GM naming conventions and at the same time keep 
> the IDE happy enough

If you can propose a better naming convention which will work for both 
old and new Visual Studio, then we could consider changing to the 
better convention.

>> I sense your frustration.  If you are comfortable with C++, Magick++ is 
>> definitely easier to pick up than the C API.  Magick++ does require using 
>> STL containers to read multiple frames from an image file though.  The C 
>> linked lists and STL containers did not seem like a good match, so I made 
>> it so that the C linked lists were converted into STL vectors, lists, or 
>> similar containers.
>
> In some ways, and especially for this app, I would prefer C, though I am 
> reasonably comfortable with either, though I am by no means a guru either.

C obviously works fine once you get the hang of the conventions.

> Right now, it is not C vs C++ but simply old MSVC vs new MSVC vs the Linux 
> way :-)

Speaking of the Linux way, I am super impressed by MSYS2 (a way to use 
Linux-style tools/compiler to target native Windows).  I had a 
fully-fledged GraphicsMagick building under Windows with MSYS2 in no 
more than half an hour even though I had never used its package 
manager before.  See 
http://www.graphicsmagick.org/INSTALL-unix.html#building-under-mingw-msys2 
for a small bit of information.

> As I am getting more familiar with the GM/IM way of doing things, especially 
> in the Win world, I am making some slow progress, though I may have to defer 
> pushing ahead for some time.
>
> For one  TIFF files play a very small part of my interests because I have 
> just a few and my main interest is in the metadata my images carry and TIFF 
> carries very little information which might be important for my needs. Hence 
> I will have to convert all of these tiffs to scaled PNGs in most cases.
>
> The main reason I got started with GM was because all the other libraries 
> gave sufficient access to what I needed, except for TIFFs
>
> Now having found out more about GM's libraries, I see potentially useful 
> features and functionality, so I will have to get back to check those out.
>
> I very much appreciate your patience and help along this bumpy road.

Not a problem.  Useful feedback helps.  I am not a "native" Windows 
user and primarily use it to make sure that GraphicsMagick is 
reasonably supported under Windows.  Since I am not a "native" Windows 
user I may not be doing things or describing things in ideal ways.

Bob
-- 
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
Public Key,     http://www.simplesystems.org/users/bfriesen/public-key.txt
--3735943886-341603450-1582321613=:17288
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--3735943886-341603450-1582321613=:17288
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Graphicsmagick-apis mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/graphicsmagick-apis

--3735943886-341603450-1582321613=:17288--