×

Discussion Board

Results 1 to 2 of 2
  1. #1
    Registered User
    Join Date
    Mar 2003
    Posts
    148

    Some comments on the Eseries plugin

    I would like to make some comments on the Eseries plugin that has been released a couple of days ago, and in particular on the printing API.

    1) The decision to provide an ECom plugin to hide the availability or not of the printing subsystem is in itself a good one. What's not good is the decision to only do this for FP1 and higher. At this moment the number of 3rd ed FP1 Eseries devices is dwarfed by the number of 3rd ed Eseries. So making the plugin available as a sis file would have been an obvious idea, Iw ould say. Even though S60 3rd ed doesn't handle handle embedded sis file sproperly at deinstallation, we could always have told the user to install the printer ecom plugin separately.

    2) So what does a developer do in such a case: he creates his own plugin. I mean, a couple of million E61(i) users are not the kind of people I want to abandon.
    Creating a wrapper around CPrintingAPI on the FP1 hand, and around CPrintJob/CPrintUi on the other hand isn't exactly very taxing. What was taxing though was the behaviour of my CPrintJob object after the print was done. As far as I can see, it gets deleted before MPrintJobObserver::NotifyPrintEnded() is called. I have a CPrintJob member var in the Observer, and deleting the CPrintJob panics with a kern-exec, and the implementation pointer in CPrintJob has the dead-pointer bit pattern at that point.

    Problem is, I am using CPrintUi::PrintDialogLD(CPrintJob& aPrintJob), where the print job is passed by reference. This should mean that ownership of the print job isn't transferred.

    I would like some explanation on this as the docs do not say anything at all about it.

    3) Testing for Eseries devices like is done in the plugin user manual seems a bit strange. What happens when other manufacturers also starts to make Eseries-like devices? I would say that testing the availability of the printer subsystem would be more future proof. Either by testing on a given file (like the plugin resource file) or by adding a PRINTER attribute.

    But apart from that, well done releasing this plugin

    Sander van der Wal
    www.mBrainSoftware.com

  2. #2
    Nokia Developer Moderator
    Join Date
    Sep 2004
    Location
    Tampere, Finland
    Posts
    11,359

    Re: Some comments on the Eseries plugin

    Thank you for your feedback Sander, I will forward it on to the ES guys.

    Best regards,

Similar Threads

  1. MMF Controller plugin
    By cherem in forum Symbian Media (Closed)
    Replies: 24
    Last Post: 2007-12-06, 00:36
  2. Eseries SDK plugin problem with 800*352 screen mode
    By svdwal in forum Tools and SDK Feedback (Closed)
    Replies: 1
    Last Post: 2007-11-13, 16:43
  3. [defect report] perforce plugin not working in carbide.c++ project explorer
    By simo.salminen in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 2
    Last Post: 2007-08-28, 12:29
  4. Problem with SIP Resolver Ecom Plugin
    By ecio83 in forum Symbian Networking & Messaging (Closed)
    Replies: 8
    Last Post: 2007-07-30, 09:04
  5. SIP ECOM plugin not working on Nokia 6600?
    By marcel_kok555 in forum Symbian Networking & Messaging (Closed)
    Replies: 0
    Last Post: 2006-01-25, 10:58

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×