AP framework weakness

Subject: AP framework weakness
From: Hubert Figuiere (hfiguiere@teaser.fr)
Date: Tue Mar 06 2001 - 14:34:43 CST

• sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Next message: Sam TH: "Re: AP framework weakness"
• Previous message: Michael D. Pritchett: "Re: TRANSFORM_TO_DOS_PATH problems"
• Next in thread: Sam TH: "Re: AP framework weakness"
• Reply: Sam TH: "Re: AP framework weakness"
• Reply: Thomas Fletcher: "Re: AP framework weakness"

I'm currently analyzing the ap framework to know what I have to do
for the Mac port.

I mostly compare beOS and UNIX port, and find that there are too much
similarities.

For example, compare
AP_BeOSFrame::loadDocument
and
AP_UnixFrame::loadDocument

and you'll find that they are ALMOST identical: only the frame class
is different, but since they both come from the same incestor, there
should be no problem at all.

I have lot of other examples like this. What about cleaning all this
up ?
Shorter benefits: better design, less work for me
Long term benefits: less bug to fix, less code lines to maintain.

Hub

• Next message: Sam TH: "Re: AP framework weakness"
• Previous message: Michael D. Pritchett: "Re: TRANSFORM_TO_DOS_PATH problems"
• Next in thread: Sam TH: "Re: AP framework weakness"
• Reply: Sam TH: "Re: AP framework weakness"
• Reply: Thomas Fletcher: "Re: AP framework weakness"

This archive was generated by hypermail 2b25 : Tue Mar 06 2001 - 14:31:33 CST