adobe-source-devel — ASL development topic discussion

Re: [Adobe-source-devel] Finding resources

[Foster B. <fbr...@ad...>]

On 30/05/09 12:34 PM, "Robert Dailey" <rcd...@gm...> wrote:

> So I found out that adobe::find_resource() is being used to try to find
> glossary.xstr. However, it only uses the root_path() for searching, which
> isn't very flexible at all. How about making this function check a few more
> places, in particular the working directory. Also, it would be a nice feature
> to be able to specify a list of resource directories at the command line for
> the begin app and have those be used for searching for resources, amongst
> other obvious paths.

The resource system in APL definitely lacks a more robust design; that being
said, it is not used outside of Adobe Begin, so it's limited use has
prevented further development of it. If you would like to improve it to
better suit your needs, please feel free. How would you specify additional
resource directories at the command line for Adobe Begin? The idea is that
it's a double-clickable app, so I'm missing something here.

> Doing this will prevent me from having to copy files around via CMake to
> ensure that resources can be found. I can make these changes myself, if you
> guys think it would be a good idea. I'm leaning more towards the command-line
> parameter approach for specifying resource directories.

If the resource directories you are interested in finding (e.g., the working
directory or a common a preferences directory) can be derived from the OS
(even if it's an OS-specific routine) then I'd think it would be better for
the app to discover those directories automatically. There are
platform-specific source directories for both Mac and Windows that the
resource system would be able to tap into to solve this problem.

> Another comment: The root_path() is basically a singleton, and not thread safe
> at all. It would be ideal to make
> resource "hints" a concept, possibly create a new class called ResourceReposit
> ory, which can be given directory hints (where to find resources) and can be u
> sed to obtain resources.

Can you describe a use case where one thread would want a different set of
resource directories than another? As for the thread safety issue, it
shouldn't be too hard to turn root_path into a threadsafe type.

As I said before, there's no concerted effort going on inside Adobe to
improve APL. Occasionally bug fixes will be made and utility code shuffled
around to make it more accessible to external sources, but most of it is
unused. You're welcome to work out ways of improving it.

Blessings,
Foster


> On Fri, May 29, 2009 at 7:56 PM, Robert Dailey <rcd...@gm...> wrote:
>> Hello,
>> 
>> So I've got the Begin app compiling and linking under CMake, however it
>> cannot 
>> find resources during the loading process. I pointed the working directory in
>> Visual Studio to the begin/resources directory, but this does not seem to
>> help. I tried referencing the bjam scripts as well, but since I am not
>> familiar with bjam I had trouble finding anything helpful.
>> 
>> Can anyone give me some pointers? It is trying to find glossary.xstr.
> 

-- 
Foster T. Brereton                <ἰχθύς><                Ro 3:21-26
  Computer Scientist 2 --- Photoshop Engineering --- Adobe Systems
"What 99 percent of programmers need to know is not how to build
components but how to use them." -- Alexander Stepanov

[Adobe-source-devel] CMake: Time to talk about requirements

[Robert D. <rcd...@gm...>]

Hey guys,
I've got a basic and functional first pass on my CMake implementation. I can
successfully build, link, and run the Begin app, as well as ASL/APL. There's
2 major steps we need to take from here.

First, I need some of you guys to review my work so far. If this requires me
moving my work to the review branch, I will do so. Please give me some
detailed instruction on this if this is the path I am to take. I need you
guys to try using CMake to generate the projects. None of you will need to
become familiar with the CMake language at this point, you'll be working
directly with the command-line client or the GUI interface (on windows). I
want to gather opinions on the process, as well as potential suggestions for
improvement.

Secondly, we need to figure out requirements. Improving the work I've
already done is of course part of this, but we need to figure out long-term
requirements, such as unit testing support and extensibility level of the
scripts for future projects. There is also a particular topic we need to
discuss. A typical approach to creating CMake scripts is to have a "root"
CMakeLists.txt file that contains all of the inheritable, reusable code and
other entities. For example, the root of the Perforce repository would look
like this in a typical case:

//CMakeLists.txt
//cmake/find_modules/FindTBB.cmake//adobe_source_libraries/CMakeLists.txt
//adobe_platform_libraries/CMakeLists.txt

Here, we define all of the reusable cmake functions, macros, and variables
in CMakeLists.txt, and both ASL and APL CMakeLists.txt simply inherit those,
and no explicit include() needs to be performed. However, the current
structure I have is as follows:

//cmake/common.cmake
//cmake/find_modules/FindTBB.cmake
//adobe_source_libraries/CMakeLists.txt
//adobe_platform_libraries/CMakeLists.txt

In this case, the root cmake directory still must exist. This cannot be
removed. There is reusable CMake code that needs to be centralized in a
location that both ASL and APL can get to, and one level above each of them
is the best place for it that I know of. However, I've been told that no
files can exist in the root (//), so I had to create //cmake/common.cmake
that each of ASL and APL's CMakeLists.txt file must include, which increases
the amount of boiler plate CMake code in each project-specific cmake script
file.

This is one of the major issues we have to tackle. We, as a group, need to
figure out what the best long-term hierarchical structure is for CMake. I
also want to let you guys know that I do have a full time job. What that
means to you is that I am most active on the weekends. However, this mailing
list is extremely low traffic and my biggest bottle neck right now is
getting feedback from the rest of the team. Not to rush, but if you guys
could respond more often (especially on weekends), I would be able to get a
little bit more done. I can only do so much work without thorough
requirements.

Thanks to everyone for reading.

Re: [Adobe-source-devel] Finding resources

[Robert D. <rcd...@gm...>]

So I found out that adobe::find_resource() is being used to try to find
glossary.xstr. However, it only uses the root_path() for searching, which
isn't very flexible at all. How about making this function check a few more
places, in particular the working directory. Also, it would be a nice
feature to be able to specify a list of resource directories at the command
line for the begin app and have those be used for searching for resources,
amongst other obvious paths.
Doing this will prevent me from having to copy files around via CMake to
ensure that resources can be found. I can make these changes myself, if you
guys think it would be a good idea. I'm leaning more towards the
command-line parameter approach for specifying resource directories.

Another comment: The root_path() is basically a singleton, and not thread
safe at all. It would be ideal to make
resource "hints" a concept, possibly create a new class called
ResourceRepository, which can be given directory hints (where to find
resources) and can be used to obtain resources.

On Fri, May 29, 2009 at 7:56 PM, Robert Dailey <rcd...@gm...> wrote:

> Hello,
> So I've got the Begin app compiling and linking under CMake, however it
> cannot find resources during the loading process. I pointed the working
> directory in Visual Studio to the begin/resources directory, but this does
> not seem to help. I tried referencing the bjam scripts as well, but since I
> am not familiar with bjam I had trouble finding anything helpful.
>
> Can anyone give me some pointers? It is trying to find *glossary.xstr*.
>

[Adobe-source-devel] Finding resources

[Robert D. <rcd...@gm...>]

Hello,
So I've got the Begin app compiling and linking under CMake, however it
cannot find resources during the loading process. I pointed the working
directory in Visual Studio to the begin/resources directory, but this does
not seem to help. I tried referencing the bjam scripts as well, but since I
am not familiar with bjam I had trouble finding anything helpful.

Can anyone give me some pointers? It is trying to find *glossary.xstr*.

Re: [Adobe-source-devel] Need to make a backlog

[Robert D. <rcd...@gm...>]

It is MrDoomMaster I believe. Thanks Sean.

On Fri, May 29, 2009 at 12:01 AM, Sean Parent <sea...@ma...> wrote:

> If you let me know what your sourceforge user name is then I can add you to
> the project and you can use the task list. I added a cmake category.
>
> Sean
>
>
> On May 28, 2009, at 9:25 PM, Robert Dailey wrote:
>
>  Hey guys,
>>
>> I'm currently in the process of working on CMake stuff in my submission
>> branch, and I have a heap of things I need to add to a backlog somewhere. I
>> was hoping you guys had a Mantis website, or something similar setup. Is
>> there any place I can create tickets or backlog items? I'm hoping I don't
>> have to jot these down in notepad :)
>>
>> Thanks!
>>
>> ------------------------------------------------------------------------------
>> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
>> is a gathering of tech-side developers & brand creativity professionals.
>> Meet
>> the minds behind Google Creative Lab, Visual Complexity, Processing, &
>> iPhoneDevCamp as they present alongside digital heavyweights like
>> Barbarian
>> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com_______________________________________________
>> Adobe-source-devel mailing list
>> Ado...@li...
>> https://lists.sourceforge.net/lists/listinfo/adobe-source-devel
>>
>
>

Re: [Adobe-source-devel] Need to make a backlog

[Sean P. <sea...@ma...>]

If you let me know what your sourceforge user name is then I can add  
you to the project and you can use the task list. I added a cmake  
category.

Sean

On May 28, 2009, at 9:25 PM, Robert Dailey wrote:

> Hey guys,
>
> I'm currently in the process of working on CMake stuff in my  
> submission branch, and I have a heap of things I need to add to a  
> backlog somewhere. I was hoping you guys had a Mantis website, or  
> something similar setup. Is there any place I can create tickets or  
> backlog items? I'm hoping I don't have to jot these down in notepad :)
>
> Thanks!
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity  
> professionals. Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp as they present alongside digital heavyweights like  
> Barbarian
> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com  
> _______________________________________________
> Adobe-source-devel mailing list
> Ado...@li...
> https://lists.sourceforge.net/lists/listinfo/adobe-source-devel

[Adobe-source-devel] Need to make a backlog

[Robert D. <rcd...@gm...>]

Hey guys,
I'm currently in the process of working on CMake stuff in my submission
branch, and I have a heap of things I need to add to a backlog somewhere. I
was hoping you guys had a Mantis website, or something similar setup. Is
there any place I can create tickets or backlog items? I'm hoping I don't
have to jot these down in notepad :)

Thanks!

Re: [Adobe-source-devel] ASL 1.0.42 Released

[Foster B. <fbr...@ad...>]

On 21/05/09 2:52 PM, "Robert Dailey" <rcd...@gm...> wrote:

> On Thu, May 21, 2009 at 1:49 PM, Sean Parent <sea...@ma...> wrote:
>> ASL 1.0.42 is now released. The windows built distributions have not
>> been posted yet but Mat or I will get to them soon. There is a
>> critical bug fix in this release for property model initializers. So
>> if you are using property models and input cells, make sure you grab
>> this release.
>> 
>> This will be my last ASL release as an Adobe employee. The Adobe
>> Software Technology Lab is now a virtual organization. I will likely
>> still keep a hand in guiding the progress of ASL and I'm certain it
>> will continue to grow and improve. STLab was able to accomplish some
>> amazing things. ASL being one externally visible artifact and the book
>> <http://www.elementsofprogramming.com/book.html> being another. I want
>> to thank the members of STLab, Foster Brereton, Mat Marcus, Paul
>> McJones, and Alex Stepanov along with everyone who supported the lab
>> over the years. We had a great run.
>> 
>> My personal e-mail is sean_parent <at> mac <dot> com. Messages to the
>> forums and mailing lists will continue to reach me.
> 
> Wait... is ASL dying or something? If you leave, what does that mean for the
> libraries? I'm a bit confused as to what is happening. What do you mean by "it
> is now a virtual organization"? 

ASL is not dying. Sean was the primary owner of ASL within Adobe, and now
that he's leaving those roles and responsibilities are shifting somewhat. It
is still an open source project and there will still be contributions to it
from inside and outside Adobe (including yours). There's a lot that's up in
the air at this point, but rest assured when things settle down ASL will
have as much of a pulse as it's ever had.

Blessings,
Foster

-- 
Foster T. Brereton                <ἰχθύς><                Ro 3:21-26
  Computer Scientist 2 --- Photoshop Engineering --- Adobe Systems
"What 99 percent of programmers need to know is not how to build
components but how to use them." -- Alexander Stepanov

Re: [Adobe-source-devel] ASL 1.0.42 Released

[Robert D. <rcd...@gm...>]

On Thu, May 21, 2009 at 1:49 PM, Sean Parent <sea...@ma...> wrote:

> ASL 1.0.42 is now released. The windows built distributions have not
> been posted yet but Mat or I will get to them soon. There is a
> critical bug fix in this release for property model initializers. So
> if you are using property models and input cells, make sure you grab
> this release.
>
> This will be my last ASL release as an Adobe employee. The Adobe
> Software Technology Lab is now a virtual organization. I will likely
> still keep a hand in guiding the progress of ASL and I'm certain it
> will continue to grow and improve. STLab was able to accomplish some
> amazing things. ASL being one externally visible artifact and the book
> <http://www.elementsofprogramming.com/book.html> being another. I want
> to thank the members of STLab, Foster Brereton, Mat Marcus, Paul
> McJones, and Alex Stepanov along with everyone who supported the lab
> over the years. We had a great run.
>
> My personal e-mail is sean_parent <at> mac <dot> com. Messages to the
> forums and mailing lists will continue to reach me.


Wait... is ASL dying or something? If you leave, what does that mean for the
libraries? I'm a bit confused as to what is happening. What do you mean by
"it is now a virtual organization"?

[Adobe-source-devel] ASL 1.0.42 Released

[Sean P. <sea...@ma...>]

ASL 1.0.42 is now released. The windows built distributions have not  
been posted yet but Mat or I will get to them soon. There is a  
critical bug fix in this release for property model initializers. So  
if you are using property models and input cells, make sure you grab  
this release.

This will be my last ASL release as an Adobe employee. The Adobe  
Software Technology Lab is now a virtual organization. I will likely  
still keep a hand in guiding the progress of ASL and I'm certain it  
will continue to grow and improve. STLab was able to accomplish some  
amazing things. ASL being one externally visible artifact and the book  
<http://www.elementsofprogramming.com/book.html> being another. I want  
to thank the members of STLab, Foster Brereton, Mat Marcus, Paul  
McJones, and Alex Stepanov along with everyone who supported the lab  
over the years. We had a great run.

My personal e-mail is sean_parent <at> mac <dot> com. Messages to the  
forums and mailing lists will continue to reach me.

Sean

----

2009/05/13 : 1.0.42
   ASL:

       - Property model library (Adam)

           Changed calculation logic so that when an interface cell is  
defined
           by a direct expression and by a relate clause, both  
expression are
           applied. Prior it was one or the other. For example:
           ---
           interface:
               x;
               y <== round(y);
           logic:
               relate {
                   x <== y;
                   y <== x;
               }
           ---
           When x is of higher priority, y will be evaluated as:
           ---
           y'  = x;
           y'' = round(y')
           ---
           This avoids having to replicate filters (self referential
           expression on an interface cell) in relate clauses.
           Note that if the expression defining y was not self  
referential,
           then the relate clause would be ignored. For example, if y  
were
           defined as:
           ---
           y <== 10;
           ---
           Then y would have the value of 10 regardless of the value  
of x.

       	- Fixed issue introduced in 1.0.41 with incorrect poison set  
being
       	    calculated for invariants.
	        - Reworked invariant cells they now behave more like output  
cells
	          and can be refered to in expressions.
	        - Updated the image_size example to demonstrate an ignored/ 
disabled
	          control (resample method when not resampling).
       - Some 64 bit fixes and cleanup.
       - Minor cleanup, performance improvements and bug fixes.

Re: [Adobe-source-devel] asl-users: Problems with place and outsets

[Sean P. <sea...@ma...>]

[Foster - can you forward to asl-users? I'm not VPNed in].

The layout engine doesn't deal in view systems, it deals in coordinates.

If you have a button that 80x20 then specify that as your size with 4  
pixel outsets (don't include the outsets in the size calculation)
The baseline is specified as an offset within the 80 pixels. The  
position specified for placement is where the top/left of the 80x20 box

Top Outset
         ^
         |
* <--+---------> Width
         |
         |
         V
    Height

(*) Left Outset

What the outsets do, is "flow" into the outsets of a container so the  
container will be created large enough to hold the children.

For example, say you have a button in a panel, when you hide the panel  
you don't want it to leave the drop shadow of the button behind. If  
the outset of the button overhangs the panel, then the panel will gain  
an outset large enough to account for the button outset.

Outsets do not effect layout and do not effect placement. The only  
thing outsets effect are other outsets.

If an outset collides with a visible entity then an error is reported  
to std::cerr in debug builds. You must provide enough spacing /  
margins to account for outsets. This is done because a local change is  
not what you want in this case, you most likely want to adjust the  
spacing globally to readjust the view.

Sean


On May 20, 2009, at 4:32 PM, Foster Brereton wrote:

> The problem is that I'm in a widget implementation that needs the  
> widget to
> own the entire rect pertaining to its widget's pixels on the screen-
> including the outsets- otherwise those regions outside the widget's  
> rect
> won't be drawn properly. For example when I have a button that is  
> 80x20, I
> need the widget to be 88x28 to account for the 4-pixel-per-size  
> focus ring.
> This means I need to take into account the total extents of the  
> widget, but
> only for measurement; at layout time I need to inset the actual  
> widget to
> account for outsets, which is throwing off my baselines.
>
> Blessings,
> Foster
>
>
> On 20/05/09 1:42 PM, "Sean Parent" <sp...@ad...> wrote:
>
>> outsets don't affect layout or placement. They play two roles:
>>
>> For a creating container which lacks a frame, the outset of a child
>> may become part of the outset of the container. This is to make sure
>> that the container is large enough to hold the child.
>>
>> If outsets collide with a visible element, the engine will assert.
>>
>> If your container is creating, it may not be handling it's own outset
>> correctly.
>>
>> Sean
>>
>> On May 20, 2009, at 1:36 PM, Foster Brereton wrote:
>>
>>> I'm trying to place two widgets in a row. One has no vertical  
>>> outsets,
>>> another does. Both have baselines. When I place them I set their top
>>> value
>>> to be top(placement) - top_outset, which lines them up correctly  
>>> with
>>> respect to each other and their containers, but messes up the  
>>> baseline
>>> alignment. When I set their top value to be simply top(placement),
>>> their
>>> baselines match up but they aren't placed properly vertically (e.g.,
>>> the
>>> distance from their top outset to their neighbor's bottom is the
>>> container's
>>> spacing, which is too much.) What am I missing?
>>>
>>> Blessings,
>>> Foster
>>>
>>>
>>> --
>>> Foster T. Brereton                <ἰχθύς><                Ro
>>> 3:21-26
>>> Computer Scientist 2 --- Photoshop Engineering --- Adobe Systems
>>> "What 99 percent of programmers need to know is not how to build
>>> components but how to use them." -- Alexander Stepanov
>>>
>>>
>>
>
> -- 
> Foster T. Brereton                <ἰχθύς><                Ro  
> 3:21-26
>  Computer Scientist 2 --- Photoshop Engineering --- Adobe Systems
> "What 99 percent of programmers need to know is not how to build
> components but how to use them." -- Alexander Stepanov
>
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity  
> professionals. Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp asthey present alongside digital heavyweights like  
> Barbarian
> Group, R/GA, & Big Spaceship. http://www.creativitycat.com
> _______________________________________________
> Adobe-source-devel mailing list
> Ado...@li...
> https://lists.sourceforge.net/lists/listinfo/adobe-source-devel

Re: [Adobe-source-devel] CMake support: Work in Progress

[Robert D. <rcd...@gm...>]

Just a status update:
I have the Begin test app successfully compiling, linking, running, and then
crashing :)

I have to setup the resource directory, since it is having trouble finding
resources. But I think I've gotten through the biggest hurdles.

With your permission, I would like to have a perforce account so I can start
checking in these script files either directly to the root or in some
prototypical directory structure. If you are interested in my work I would
be honored to contribute it. However, if you do not feel comfortable with it
or perhaps have no need for it, I can keep it to myself. I'm also a bit
interested to get some of you other guys taking a look at it so you can see
how you like it.

It's up to you! Let me know soon so I can know where I can mainline my work.

On Wed, May 20, 2009 at 3:34 PM, Peter Kümmel <syn...@gm...> wrote:

> Hi Sean,
>
> boost now also ships with cmake files. At the moment it is not
> officially supported, but it is nearly a complete bjam replacement.
> And it is in discussion if cmake will replace bjam.
>
> cmake is not a build system it generates native build files,
> and it includes the configure step.
>
> Under Windows it supports:
> (output when cmake is called without any argument:)
>
>  Borland Makefiles           = Generates Borland makefiles.
>  MSYS Makefiles              = Generates MSYS makefiles.
>  MinGW Makefiles             = Generates a make file for use with
>                               mingw32-make.
>  NMake Makefiles             = Generates NMake makefiles.
>  Unix Makefiles              = Generates standard UNIX makefiles.
>  Visual Studio 6             = Generates Visual Studio 6 project files.
>  Visual Studio 7             = Generates Visual Studio .NET 2002 project
>                               files.
>  Visual Studio 7 .NET 2003   = Generates Visual Studio .NET 2003 project
>                               files.
>  Visual Studio 8 2005        = Generates Visual Studio .NET 2005 project
>                               files.
>  Visual Studio 8 2005 Win64  = Generates Visual Studio .NET 2005 Win64
>                               project files.
>  Visual Studio 9 2008        = Generates Visual Studio 9 2008 project
> files.
>  Visual Studio 9 2008 Win64  = Generates Visual Studio 9 2008 Win64 project
>                               files.
>  Watcom WMake                = Generates Watcom WMake makefiles.
>  CodeBlocks - MinGW Makefiles= Generates CodeBlocks project files.
>  CodeBlocks - Unix Makefiles = Generates CodeBlocks project files.
>  Eclipse CDT4 - MinGW Makefiles
>                             = Generates Eclipse CDT 4.0 project files.
>  Eclipse CDT4 - NMake Makefiles
>                             = Generates Eclipse CDT 4.0 project files.
>  Eclipse CDT4 - Unix Makefiles
>                             = Generates Eclipse CDT 4.0 project files.
>
>
>
> On Linux cmake could generate build files for:
>
>  Unix Makefiles              = Generates standard UNIX makefiles.
>  CodeBlocks - Unix Makefiles = Generates CodeBlocks project files.
>  Eclipse CDT4 - Unix Makefiles
>                              = Generates Eclipse CDT 4.0 project files.
>  KDevelop3                   = Generates KDevelop 3 project files.
>  KDevelop3 - Unix Makefiles  = Generates KDevelop 3 project files.
>
>
> Under OSX cmake supports at least Xcode and plain makefiles.
>
> And on all systems QtCreator could use the cmake files.
>
> Peter
>
>
> Sean Parent wrote:
> > Hi Robert,
> >
> > I'd be happy to set you up with a developer account on our perforce
> > server. Before accepting a CMake system I'd want to know what
> > complexity it adds and what benefits it provides.
> >
> > Currently we use bjam because it works with boost, and allows us to
> > construct and execute unit tests with a fairly simply, unit tests can
> > be specified to compile or fail to compile, or run or fail to run. The
> > ability to do both positive and negative test cases are important. We
> > minimally maintain the IDE projects largely because I prefer to
> > develop in an IDE.
> >
> > If you're willing to maintain a CMake environment and it provides some
> > benefit to the community without too much complexity then we can roll
> > it in.
> >
> > Thanks,
> > Sean
> >
> > On May 17, 2009, at 8:47 PM, Robert Dailey wrote:
> >
> >> Hey guys,
> >>
> >> Just letting you know that I have a first pass complete on my CMake
> >> build system for Adobe's ASL/APL libraries. Currently, I can
> >> successfully generate a visual studio 2008 project using CMake. This
> >> project will build a static library of ASL only. I'm currently in
> >> the process of writing the logic for APL, which is going to be
> >> nearly identical. After that, I need to support the begin app. My
> >> goal is to keep the "look and feel" the same as with the checked in
> >> visual studio project in msvc_ide.
> >>
> >> I'm flying though this pretty quickly, as there really hasn't been
> >> much work to do so far. I can compile the library successfully so
> >> far with an unpatched version of Boost 1.39 and TBB.
> >>
> >> I would like to be able to commit my work to Perforce, but from the
> >> little reading I did, contributions are a rather complex process at
> >> Adobe. I would rather one of the developers let me know how to
> >> contribute my work, if you even want it.
> >>
> ------------------------------------------------------------------------------
> >> Crystal Reports - New Free Runtime and 30 Day Trial
> >> Check out the new simplified licensing option that enables
> >> unlimited royalty-free distribution of the report engine
> >> for externally facing server and web deployment.
> >>
> http://p.sf.net/sfu/businessobjects_______________________________________________
> >> Adobe-source-devel mailing list
> >> Ado...@li...
> >> https://lists.sourceforge.net/lists/listinfo/adobe-source-devel
> >
> >
> >
> ------------------------------------------------------------------------------
> > Crystal Reports - New Free Runtime and 30 Day Trial
> > Check out the new simplified licensing option that enables
> > unlimited royalty-free distribution of the report engine
> > for externally facing server and web deployment.
> > http://p.sf.net/sfu/businessobjects
> > _______________________________________________
> > Adobe-source-devel mailing list
> > Ado...@li...
> > https://lists.sourceforge.net/lists/listinfo/adobe-source-devel
> >
>

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Robert D. <rcd...@gm...>]

With everyone's help here, along with a little bit of peeking into bjam
script files, I managed to generate the following list of preprocessor
defines that I am specifying for both ASL and APL on Windows when I build
them:
   _UNICODE
   UNICODE
   _SCL_SECURE_NO_DEPRECATE
   _CRT_SECURE_NO_DEPRECATE
   USE_WINTHREAD
   _WIN32_WINNT=0x0501
   ADOBE_TEST_MICROSOFT_NO_DEPRECATE
   ADOBE_SERIALIZATION
   ADOBE_STD_SERIALIZATION
   BOOST_SIGNALS_STATIC_LINK
   BOOST_THREAD_USE_LIB
   BOOST_ALL_NO_LIB
   __TBB_NO_IMPLICIT_LINKAGE
   NOMINMAX

Everything seems to be working fine now! So far, I've been able to compile
APL and ASL into static libraries on Windows using CMake. However, the real
test will be getting the Begin test app to work! Thanks for the support
everyone.


On Wed, May 20, 2009 at 1:51 PM, Sean Parent <sea...@ma...> wrote:

> The issue may be that ADOBE_STD_SERIALIZATION=1 is not defined (this should
> be an optional flag but we may not fully be testing without it). Also note
> that boost and TBB have configuration options (well documented) that need to
> be set appropriately.
>
> Looking at my GCC build I see the following:
>
> ADOBE_STD_SERIALIZATION=1
> BOOST_SIGNALS_STATIC_LINK=1 BOOST_THREAD_USE_LIB=1 BOOST_ALL_NO_LIB=1
> __TBB_NO_IMPLICIT_LINKAGE=1
>
>
> Sean
>
> On May 19, 2009, at 6:49 PM, Robert Dailey wrote:
>
>  Hey guys,
>>
>> I'm compiling the HEAD in Perforce, and I'm running into a few compiler
>> errors on MSVC9:
>>
>> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(32)
>> : error C2504: 'basic_omanipulator' : base class undefined
>> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(32)
>> : error C2143: syntax error : missing ',' before '<'
>> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
>> : error C2143: syntax error : missing ';' before '<'
>> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
>> : error C4430: missing type specifier - int assumed. Note: C++ does not
>> support default-int
>> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
>> : error C2238: unexpected token(s) preceding ';'
>>
>> These errors occurred while compiling property_model_formatter.cpp in APL.
>> Any reason for this failure? Are there certain files in APL that I should
>> NOT be compiling?
>>
>> ------------------------------------------------------------------------------
>> Crystal Reports - New Free Runtime and 30 Day Trial
>> Check out the new simplified licensing option that enables
>> unlimited royalty-free distribution of the report engine
>> for externally facing server and web deployment.
>>
>> http://p.sf.net/sfu/businessobjects_______________________________________________
>> Adobe-source-devel mailing list
>> Ado...@li...
>> https://lists.sourceforge.net/lists/listinfo/adobe-source-devel
>>
>
>

Re: [Adobe-source-devel] asl-users: Problems with place and outsets

[Foster B. <fbr...@ad...>]

The problem is that I'm in a widget implementation that needs the widget to
own the entire rect pertaining to its widget's pixels on the screen-
including the outsets- otherwise those regions outside the widget's rect
won't be drawn properly. For example when I have a button that is 80x20, I
need the widget to be 88x28 to account for the 4-pixel-per-size focus ring.
This means I need to take into account the total extents of the widget, but
only for measurement; at layout time I need to inset the actual widget to
account for outsets, which is throwing off my baselines.

Blessings,
Foster


On 20/05/09 1:42 PM, "Sean Parent" <sp...@ad...> wrote:

> outsets don't affect layout or placement. They play two roles:
> 
> For a creating container which lacks a frame, the outset of a child
> may become part of the outset of the container. This is to make sure
> that the container is large enough to hold the child.
> 
> If outsets collide with a visible element, the engine will assert.
> 
> If your container is creating, it may not be handling it's own outset
> correctly.
> 
> Sean
> 
> On May 20, 2009, at 1:36 PM, Foster Brereton wrote:
> 
>> I'm trying to place two widgets in a row. One has no vertical outsets,
>> another does. Both have baselines. When I place them I set their top
>> value
>> to be top(placement) - top_outset, which lines them up correctly with
>> respect to each other and their containers, but messes up the baseline
>> alignment. When I set their top value to be simply top(placement),
>> their
>> baselines match up but they aren't placed properly vertically (e.g.,
>> the
>> distance from their top outset to their neighbor's bottom is the
>> container's
>> spacing, which is too much.) What am I missing?
>> 
>> Blessings,
>> Foster
>> 
>> 
>> --
>> Foster T. Brereton                <ἰχθύς><                Ro
>> 3:21-26
>>  Computer Scientist 2 --- Photoshop Engineering --- Adobe Systems
>> "What 99 percent of programmers need to know is not how to build
>> components but how to use them." -- Alexander Stepanov
>> 
>> 
> 

-- 
Foster T. Brereton                <ἰχθύς><                Ro 3:21-26
  Computer Scientist 2 --- Photoshop Engineering --- Adobe Systems
"What 99 percent of programmers need to know is not how to build
components but how to use them." -- Alexander Stepanov

[Adobe-source-devel] Problems with place and outsets

[Foster B. <fbr...@ad...>]

I'm trying to place two widgets in a row. One has no vertical outsets,
another does. Both have baselines. When I place them I set their top value
to be top(placement) - top_outset, which lines them up correctly with
respect to each other and their containers, but messes up the baseline
alignment. When I set their top value to be simply top(placement), their
baselines match up but they aren't placed properly vertically (e.g., the
distance from their top outset to their neighbor's bottom is the container's
spacing, which is too much.) What am I missing?

Blessings,
Foster


-- 
Foster T. Brereton                <ἰχθύς><                Ro 3:21-26
  Computer Scientist 2 --- Photoshop Engineering --- Adobe Systems
"What 99 percent of programmers need to know is not how to build
components but how to use them." -- Alexander Stepanov

Re: [Adobe-source-devel] CMake support: Work in Progress

[Peter K. <syn...@gm...>]

Hi Sean,

boost now also ships with cmake files. At the moment it is not
officially supported, but it is nearly a complete bjam replacement.
And it is in discussion if cmake will replace bjam.

cmake is not a build system it generates native build files,
and it includes the configure step.

Under Windows it supports:
(output when cmake is called without any argument:)

 Borland Makefiles           = Generates Borland makefiles.
 MSYS Makefiles              = Generates MSYS makefiles.
 MinGW Makefiles             = Generates a make file for use with
                               mingw32-make.
 NMake Makefiles             = Generates NMake makefiles.
 Unix Makefiles              = Generates standard UNIX makefiles.
 Visual Studio 6             = Generates Visual Studio 6 project files.
 Visual Studio 7             = Generates Visual Studio .NET 2002 project
                               files.
 Visual Studio 7 .NET 2003   = Generates Visual Studio .NET 2003 project
                               files.
 Visual Studio 8 2005        = Generates Visual Studio .NET 2005 project
                               files.
 Visual Studio 8 2005 Win64  = Generates Visual Studio .NET 2005 Win64
                               project files.
 Visual Studio 9 2008        = Generates Visual Studio 9 2008 project files.
 Visual Studio 9 2008 Win64  = Generates Visual Studio 9 2008 Win64 project
                               files.
 Watcom WMake                = Generates Watcom WMake makefiles.
 CodeBlocks - MinGW Makefiles= Generates CodeBlocks project files.
 CodeBlocks - Unix Makefiles = Generates CodeBlocks project files.
 Eclipse CDT4 - MinGW Makefiles
                             = Generates Eclipse CDT 4.0 project files.
 Eclipse CDT4 - NMake Makefiles
                             = Generates Eclipse CDT 4.0 project files.
 Eclipse CDT4 - Unix Makefiles
                             = Generates Eclipse CDT 4.0 project files.



On Linux cmake could generate build files for:

  Unix Makefiles              = Generates standard UNIX makefiles.
  CodeBlocks - Unix Makefiles = Generates CodeBlocks project files.
  Eclipse CDT4 - Unix Makefiles
                              = Generates Eclipse CDT 4.0 project files.
  KDevelop3                   = Generates KDevelop 3 project files.
  KDevelop3 - Unix Makefiles  = Generates KDevelop 3 project files.


Under OSX cmake supports at least Xcode and plain makefiles.

And on all systems QtCreator could use the cmake files.

Peter


Sean Parent wrote:
> Hi Robert,
> 
> I'd be happy to set you up with a developer account on our perforce  
> server. Before accepting a CMake system I'd want to know what  
> complexity it adds and what benefits it provides.
> 
> Currently we use bjam because it works with boost, and allows us to  
> construct and execute unit tests with a fairly simply, unit tests can  
> be specified to compile or fail to compile, or run or fail to run. The  
> ability to do both positive and negative test cases are important. We  
> minimally maintain the IDE projects largely because I prefer to  
> develop in an IDE.
> 
> If you're willing to maintain a CMake environment and it provides some  
> benefit to the community without too much complexity then we can roll  
> it in.
> 
> Thanks,
> Sean
> 
> On May 17, 2009, at 8:47 PM, Robert Dailey wrote:
> 
>> Hey guys,
>>
>> Just letting you know that I have a first pass complete on my CMake  
>> build system for Adobe's ASL/APL libraries. Currently, I can  
>> successfully generate a visual studio 2008 project using CMake. This  
>> project will build a static library of ASL only. I'm currently in  
>> the process of writing the logic for APL, which is going to be  
>> nearly identical. After that, I need to support the begin app. My  
>> goal is to keep the "look and feel" the same as with the checked in  
>> visual studio project in msvc_ide.
>>
>> I'm flying though this pretty quickly, as there really hasn't been  
>> much work to do so far. I can compile the library successfully so  
>> far with an unpatched version of Boost 1.39 and TBB.
>>
>> I would like to be able to commit my work to Perforce, but from the  
>> little reading I did, contributions are a rather complex process at  
>> Adobe. I would rather one of the developers let me know how to  
>> contribute my work, if you even want it.
>> ------------------------------------------------------------------------------
>> Crystal Reports - New Free Runtime and 30 Day Trial
>> Check out the new simplified licensing option that enables
>> unlimited royalty-free distribution of the report engine
>> for externally facing server and web deployment.
>> http://p.sf.net/sfu/businessobjects_______________________________________________
>> Adobe-source-devel mailing list
>> Ado...@li...
>> https://lists.sourceforge.net/lists/listinfo/adobe-source-devel
> 
> 
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables 
> unlimited royalty-free distribution of the report engine 
> for externally facing server and web deployment. 
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Adobe-source-devel mailing list
> Ado...@li...
> https://lists.sourceforge.net/lists/listinfo/adobe-source-devel
> 

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Sean P. <sea...@ma...>]

The issue may be that ADOBE_STD_SERIALIZATION=1 is not defined (this  
should be an optional flag but we may not fully be testing without  
it). Also note that boost and TBB have configuration options (well  
documented) that need to be set appropriately.

Looking at my GCC build I see the following:

ADOBE_STD_SERIALIZATION=1
BOOST_SIGNALS_STATIC_LINK=1 BOOST_THREAD_USE_LIB=1 BOOST_ALL_NO_LIB=1
__TBB_NO_IMPLICIT_LINKAGE=1


Sean

On May 19, 2009, at 6:49 PM, Robert Dailey wrote:

> Hey guys,
>
> I'm compiling the HEAD in Perforce, and I'm running into a few  
> compiler errors on MSVC9:
>
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(32) : error C2504: 'basic_omanipulator' :  
> base class undefined
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(32) : error C2143: syntax error : missing  
> ',' before '<'
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(34) : error C2143: syntax error : missing  
> ';' before '<'
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(34) : error C4430: missing type specifier -  
> int assumed. Note: C++ does not support default-int
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(34) : error C2238: unexpected token(s)  
> preceding ';'
>
> These errors occurred while compiling property_model_formatter.cpp  
> in APL. Any reason for this failure? Are there certain files in APL  
> that I should NOT be compiling?
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> unlimited royalty-free distribution of the report engine
> for externally facing server and web deployment.
> http://p.sf.net/sfu/businessobjects_______________________________________________
> Adobe-source-devel mailing list
> Ado...@li...
> https://lists.sourceforge.net/lists/listinfo/adobe-source-devel

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Sean P. <sea...@ma...>]

What cpp file was being compiled?

Sean

On May 19, 2009, at 6:49 PM, Robert Dailey wrote:

> Hey guys,
>
> I'm compiling the HEAD in Perforce, and I'm running into a few  
> compiler errors on MSVC9:
>
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(32) : error C2504: 'basic_omanipulator' :  
> base class undefined
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(32) : error C2143: syntax error : missing  
> ',' before '<'
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(34) : error C2143: syntax error : missing  
> ';' before '<'
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(34) : error C4430: missing type specifier -  
> int assumed. Note: C++ does not support default-int
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/ 
> expression_formatter.hpp(34) : error C2238: unexpected token(s)  
> preceding ';'
>
> These errors occurred while compiling property_model_formatter.cpp  
> in APL. Any reason for this failure? Are there certain files in APL  
> that I should NOT be compiling?
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> unlimited royalty-free distribution of the report engine
> for externally facing server and web deployment.
> http://p.sf.net/sfu/businessobjects_______________________________________________
> Adobe-source-devel mailing list
> Ado...@li...
> https://lists.sourceforge.net/lists/listinfo/adobe-source-devel

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Robert D. <rcd...@gm...>]

On Tue, May 19, 2009 at 11:44 PM, Mat Marcus <mat...@em...> wrote:

> I'd need a bit more info before I can answer usefully. Are you
> compiling the Adobe Begin visual studio solution, or is this your own
> project, or are you using CMake? If you are not using one of the
> provided bjam files or visual studio solutions then you may not have
> the necessary flags, options and macros set. The reasons that I
> encouraged you to begin with bjam included:
>  1) Once things were configured you'd have a baseline build that you
> could compare to/test against.
>  2) You could use the build system as an oracle to determine the
> options to pass the compiler if you're going your own way


I'm compiling every single source file under:
adobe_platform_libraries/adobe/.....
adobe_platform_libraries/windows/adobe/....

These are being compiled as a single library.

I looked at <adobe/iomanip.hpp>, <adobe/manip.hpp>, and
expression_formatter.hpp. I did not see any preprocessor conditions, nor
anything else that made it immediately obvious that a certain command line
configuration must be present in order for this to successfully compile.

When I get home, I will reference the bjam scripts to see if I can't hunt
down the problem and I'll also try to compile it using bjam. Please note,
however, that I do not know
bjam nor do I have a desire to learn it. I was hoping I could resolve
this issue without depending on bjam too much. For example, if there
were documentation somewhere that adequately explained
how to build APL and ASL. For example, I would expect such documentation to
inform me of:

   - All of the command line options required to successfully build both APL
   and ASL.
   - All of the files that are compiled per-platform. Currently, for ASL, I
   am compiling every single CPP file I can find in that directory tree
   (adobe_source_libraries). For APL, it's a bit trickier, since there are
   platform specific files in there.
   - Any preprocessor definitions that are required by both APL and ASL.
   - Anything else out of the ordinary.

I have yet to read the URL you linked me to earlier, so some of these may be
addressed there. However, from what you've told me so far, there seems to be
a high dependency on bjam to figure out how to properly build the project.

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Mat M. <mat...@em...>]

On Tue, May 19, 2009 at 9:15 PM, Robert Dailey <rcd...@gm...> wrote:
> Thanks for the help.
> I must be going crazy and seeing things, because this error:
> expression_formatter.hpp(32) : error C2504: 'basic_omanipulator' : base
> class undefined
> shouldn't be happening.
> expression_formatter.hpp includes <adobe/iomanip.hpp>, which in turn
> includes
> <adobe/manip.hpp>, which contains the definition of basic_omanipulator. I checked my include paths, and I have adobe_source_libraries and adobe_platform_libraries set in my include path. And it obviously has no problem finding the files it is including.
> Any explanation for this, other than the fact that I'm not using bjam? I think that regardless of what build system I'm using, this error should not be occurring.


I'd need a bit more info before I can answer usefully. Are you
compiling the Adobe Begin visual studio solution, or is this your own
project, or are you using CMake? If you are not using one of the
provided bjam files or visual studio solutions then you may not have
the necessary flags, options and macros set. The reasons that I
encouraged you to begin with bjam included:
  1) Once things were configured you'd have a baseline build that you
could compare to/test against.
  2) You could use the build system as an oracle to determine the
options to pass the compiler if you're going your own way

 - Mat

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Robert D. <rcd...@gm...>]

Thanks for the help.
I must be going crazy and seeing things, because this error:

expression_formatter.hpp(32) : error C2504: 'basic_omanipulator' : base
class undefined

shouldn't be happening.

expression_formatter.hpp includes <adobe/iomanip.hpp>, which in turn
includes
<adobe/manip.hpp>, which contains the definition of
basic_omanipulator. I checked my include paths, and I have
adobe_source_libraries and adobe_platform_libraries set in my include
path. And it obviously has no problem finding the files it is
including.

Any explanation for this, other than the fact that I'm not using bjam?
I think that regardless of what build system I'm using, this error
should not be occurring.

On Tue, May 19, 2009 at 11:07 PM, Mat Marcus <mat...@em...> wrote:

> On Tue, May 19, 2009 at 7:05 PM, Robert Dailey <rcd...@gm...> wrote:
> > I have a feeling that I can't simply start blindly compiling APL. I
> presume
> > there are some prerequisites (Preprocessor definitions, etc) that I need
> to
> > obtain/setup. Is there a developer readme somewhere that I can reference?
>
> One approach is to use bjam, the only fully supported build option at
> present, for your first attempts. There is a somewhat dated
> description of the build process here:
>
> http://stlab.adobe.com/asl_readme.html#Building_Under_Win32
>
> There is also an "ASL command window", resembling the "Visual Studio
> Command Window", that can be of some assistance here. After initial
> setup, building involves a matter of cd-ing to the appropriate
> directory and invoking the command as:
>
>  bjam
>
> This builds the basic static debug version of all libraries (including
> the relevant parts of boost), the apps, and runs the unit tests.
> Variations are possible, given more interesting command lines (debug,
> release, compiler, processor architecture, dll, etc.)
>
> The command:
>
>  bjam -n
>
> won't actually build, but will show the commands that would be used,
> together with all defined macros, etc.
>
> I believe that IDE projects also offer a GUI for examining the full
> set of build flags, but I recommend the bjam to begin with.
>
>  - Mat
>

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Mat M. <mat...@em...>]

On Tue, May 19, 2009 at 7:05 PM, Robert Dailey <rcd...@gm...> wrote:
> I have a feeling that I can't simply start blindly compiling APL. I presume
> there are some prerequisites (Preprocessor definitions, etc) that I need to
> obtain/setup. Is there a developer readme somewhere that I can reference?

One approach is to use bjam, the only fully supported build option at
present, for your first attempts. There is a somewhat dated
description of the build process here:

http://stlab.adobe.com/asl_readme.html#Building_Under_Win32

There is also an "ASL command window", resembling the "Visual Studio
Command Window", that can be of some assistance here. After initial
setup, building involves a matter of cd-ing to the appropriate
directory and invoking the command as:

  bjam

This builds the basic static debug version of all libraries (including
the relevant parts of boost), the apps, and runs the unit tests.
Variations are possible, given more interesting command lines (debug,
release, compiler, processor architecture, dll, etc.)

The command:

  bjam -n

won't actually build, but will show the commands that would be used,
together with all defined macros, etc.

I believe that IDE projects also offer a GUI for examining the full
set of build flags, but I recommend the bjam to begin with.

 - Mat

[Adobe-source-devel] expression_formatter.hpp failing to compile

[Robert D. <rcd...@gm...>]

Hey guys,
I'm compiling the HEAD in Perforce, and I'm running into a few compiler
errors on MSVC9:

D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(32)
: error C2504: 'basic_omanipulator' : base class undefined
D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(32)
: error C2143: syntax error : missing ',' before '<'
D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
: error C2143: syntax error : missing ';' before '<'
D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
: error C4430: missing type specifier - int assumed. Note: C++ does not
support default-int
D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
: error C2238: unexpected token(s) preceding ';'

These errors occurred while compiling property_model_formatter.cpp in APL.
Any reason for this failure? Are there certain files in APL that I should
NOT be compiling?

Re: [Adobe-source-devel] expression_formatter.hpp failing to compile

[Robert D. <rcd...@gm...>]

I have a feeling that I can't simply start blindly compiling APL. I presume
there are some prerequisites (Preprocessor definitions, etc) that I need to
obtain/setup. Is there a developer readme somewhere that I can reference?

On Tue, May 19, 2009 at 8:49 PM, Robert Dailey <rcd...@gm...> wrote:

> Hey guys,
> I'm compiling the HEAD in Perforce, and I'm running into a few compiler
> errors on MSVC9:
>
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(32)
> : error C2504: 'basic_omanipulator' : base class undefined
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(32)
> : error C2143: syntax error : missing ',' before '<'
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
> : error C2143: syntax error : missing ';' before '<'
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
> : error C4430: missing type specifier - int assumed. Note: C++ does not
> support default-int
> D:\IT\perforce\asl\adobe_platform_libraries\adobe/implementation/expression_formatter.hpp(34)
> : error C2238: unexpected token(s) preceding ';'
>
> These errors occurred while compiling property_model_formatter.cpp in APL.
> Any reason for this failure? Are there certain files in APL that I should
> NOT be compiling?
>

Re: [Adobe-source-devel] CMake support: Work in Progress

[Robert D. <rcd...@gm...>]

Sean,
Thanks for getting back with me about this. First of all I just want to
mention that while this is a work in progress, its existence does not
interfere with anything else currently in the repository. You will see a
couple of CMakeLists.txt files lying around, but you are under no obligation
whatsoever to use it. I'm letting you know this because even though CMake is
not entirely usable yet, having it checked in for "backup purposes" does not
hurt anything.

The benefits CMake provides are quite substantial, but to mention a few:

   1. It provides a portable way of generating projects. For example:
      - On Windows, you can generate Visual Studio projects (there are of
      course other choices as well)
      - On Linux, you can generate Makefile scripts (There are also other
      options)
      - On Mac, you can generate XCode projects (There are, again, also
      other options)
   2. There are multiple IDE's and build systems support *per platform*
   3. CMake can easily handle unit tests, and also supports the use of
   CTest. Benefits include:
      - CMake allows you to define a project as a unit test, which allows
      CMake to know which executables to run when testing is executed. It will
      neatly report to you the results of all of the unit tests.
      - Compile pass/fail unit tests are outside of the scope of CMake.
      These can be automated using Boost. Since a unit test that fails
to compile
      will be treated as any normal project, this should work fine. While CMake
      only facilitates runtime unit testing, it does not prohibit compile time
      unit testing in any way that I am aware of.
      - Optionally, unit test results can be posted to a server where unit
      test results can be reviewed remotely in a nicely formatted, color-coded
      HTML web page. I have not worked with CTest much for this, but
it isn't hard
      to learn. I know that the system itself exists and can be very useful for
      continuous integration.
   4. With some extra work, cross-compilation is also supported by CMake.
   For example, if you ever wanted to port ASL to a mobile platform, like the
   IPhone or Symbian, this would be a useful feature.
   5. CMake provides all of the idioms of a typical language, such as
   functions, macros, and other things. This allows you to generalize your
   CMake scripts so the process of defining a project or unit test is just a
   few lines of code.
   6. CMake scripts are arguably less tedious to configure than Visual
   Studio directly, or other IDEs and build systems

I could list more, but those are the biggest benefits that come to mind.

I feel that CMake will be a far better alternative to bjam because it will
allow the developers to choose a visual IDE for development if they wish. I
personally can't stand compiling things from command line when I work with
them on a daily basis (Like my personal projects and ASL). There's nothing
better than giving the developer the option as to how they want to compile
the code instead of saying "Here's bjam. Learn to use it. Learn to love it".

Starting out, the CMake scripts will be relatively simple, and inevitably
restrictive. Providing a unique and generic unit testing system and complex
project creation will take several continuous iterations. For someone not
really maintaining CMake, they don't have to care about the "heavy" logic,
since it will be modularized and placed in a location outside of your
typical work environment.

Getting CMake to behave exactly as your team requires will require some
collaboration and (obviously) requirements. Right now, I'm doing the basics
and making a few assumptions as well. For a functional and satisfactory
long-term solution, you and I (and maybe others) will need to discuss
requirements. CMake is even flexible enough that we may have to even do a
bit of analysis/design as well.

One of the most important requirements is getting an idea of how developers
would like to interface with CMake for tasks such as creating projects and
unit tests. Some programmers like the idea of unit tests not being something
explicitly defined. In this case, the directory structure would be set up in
such a way that each "project" has a "tests" directory under it (or
something similar). This makes unit tests predictable, which in turn allows
you to automate their construction.

Via phone conference or mailing list discussion, in the future, I would be
happy to discuss the long-term goals for a build system. However, for now, I
consider anything I contribute as far as CMake is concerned prototypical. I
want to get something up and running that functions in a minimal way
(Perhaps just simple projects are created with or without unit tests). When
I'm done, I would expect a full review to evaluate CMake's eligibility as a
build system and perhaps discuss any further requirements.

Depending on how complex the CMake system gets (and it will get complex if
your requirements are vast), it could become a full-time job. I will most
definitely be able to always help with its maintenance, but I would expect
other people on the project (That includes you, Sean) to become as familiar
with it as they can/want to. It always helps to have other people pitch in.
I'm going to be working on my open source Layout Editor for ASL in parallel
with my contributions to ASL (Through CMake and perhaps C++ later on).

I definitely love adobe, and I really love what you guys have done with ASL.
It's an extremely promising concept that I've never seen before. I really
look forward to contributing in whatever ways that I can.

Please let me know if I can answer any more of your questions. I am far from
the expert at CMake, but I have used it quite a lot and I'm familiar with
most of its general functionality.

On Tue, May 19, 2009 at 6:39 PM, Sean Parent <sea...@ma...> wrote:

> Hi Robert,
>
> I'd be happy to set you up with a developer account on our perforce server.
> Before accepting a CMake system I'd want to know what complexity it adds and
> what benefits it provides.
>
> Currently we use bjam because it works with boost, and allows us to
> construct and execute unit tests with a fairly simply, unit tests can be
> specified to compile or fail to compile, or run or fail to run. The ability
> to do both positive and negative test cases are important. We minimally
> maintain the IDE projects largely because I prefer to develop in an IDE.
>
> If you're willing to maintain a CMake environment and it provides some
> benefit to the community without too much complexity then we can roll it in.
>
> Thanks,
> Sean
>
>
> On May 17, 2009, at 8:47 PM, Robert Dailey wrote:
>
>  Hey guys,
>>
>> Just letting you know that I have a first pass complete on my CMake build
>> system for Adobe's ASL/APL libraries. Currently, I can successfully generate
>> a visual studio 2008 project using CMake. This project will build a static
>> library of ASL only. I'm currently in the process of writing the logic for
>> APL, which is going to be nearly identical. After that, I need to support
>> the begin app. My goal is to keep the "look and feel" the same as with the
>> checked in visual studio project in msvc_ide.
>>
>> I'm flying though this pretty quickly, as there really hasn't been much
>> work to do so far. I can compile the library successfully so far with an
>> unpatched version of Boost 1.39 and TBB.
>>
>> I would like to be able to commit my work to Perforce, but from the little
>> reading I did, contributions are a rather complex process at Adobe. I would
>> rather one of the developers let me know how to contribute my work, if you
>> even want it.
>>
>> ------------------------------------------------------------------------------
>> Crystal Reports - New Free Runtime and 30 Day Trial
>> Check out the new simplified licensing option that enables
>> unlimited royalty-free distribution of the report engine
>> for externally facing server and web deployment.
>>
>> http://p.sf.net/sfu/businessobjects_______________________________________________
>> Adobe-source-devel mailing list
>> Ado...@li...
>> https://lists.sourceforge.net/lists/listinfo/adobe-source-devel
>>
>
>