Jump to content











Photo
- - - - -

PEFactory Documentation


  • Please log in to reply
7 replies to this topic

#1 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 22 August 2010 - 10:59 AM

I'm working on documentation for the PEFactory package.

The latest version is available at http://nativeex.exec...y/PEF_index.htm
It will be completed / updated day by day.

Comments are welcome.
It maybe also necessary to translate some parts into "Real English" :)

Peter

#2 Rui Paz

Rui Paz

    Frequent Member

  • Advanced user
  • 201 posts
  •  
    Portugal

Posted 22 August 2010 - 11:25 AM

Hi Peter,

Tanks for documenting PEFactory and make all this "components" more clear for new users like me.
By the way can you start for explaining what is PEFactory and what is does? What is the main difference on the final result when using PEFactory or not.

Tanks.

___
Rui Paz

#3 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 22 August 2010 - 11:45 AM

Obrigado!

Done.
I hope that is what you wanted.

Peter

#4 Rui Paz

Rui Paz

    Frequent Member

  • Advanced user
  • 201 posts
  •  
    Portugal

Posted 22 August 2010 - 12:13 PM

Obrigado!

Done.
I hope that is what you wanted.

Peter


Something like that i probably don't have the needed knowledge to understand all that you write.

Obrigado.

___
Rui Paz

#5 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15546 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 22 August 2010 - 02:01 PM

Done.
I hope that is what you wanted.


With all due respect :) this:

PEFactory is a package that can be added to different WinBuilder projects which create bootable PEs.
The package is OOP similar and therefore
The package does not need to know about project internal values.
The project does not need to know about package internal values.


says NOTHING at all. :)

I'll use one of my carpenter's comparisons :):

A hammer is a tool that can be added to any toolbox.
The tool is mainly made of iron or steel, therefore:
It is heavy and floats not
Can be used equally by left handers and right handers


You may notice how the above carefully avoids to :):
  • DESCRIBE the hammer (it is composed by a wooden or plastic handle and a steel or iron head)
  • TELL WHAT it is useful for (driving nails into wood or senseless hitting things really hard)
  • TELL HOW to use it (grip it by the handle and use it in a swinging motion from top to bottom to hit nail head with the hammer head)

I know you can do better. :)

:)
Wonko

#6 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 22 August 2010 - 02:27 PM

You can read both definitions in wiki:
OOP
Hammer

And in my OOP tab of the docu:

Do not worry, I don't intend to write a new 'OOP' wiki here.

BTW: I added the wiki link to the documentation.

TELL HOW to use it (grip it by the handle and use it in a swinging motion from top to bottom to hit nail head with the hammer head)

Will be one of the tabs next days.

It will be completed / updated day by day.


Peter

#7 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 22 August 2010 - 02:40 PM

Maybe you should take the (Finalize) and (Virtual Tests) away from all projects and include your PEFactory in Winbuilder.

Hey why have CAPI included in each project when you could include that in Winbuilder too....

How about Main Configuration? Or PreConfig?????

Sorry Off Topic

#8 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 22 August 2010 - 03:59 PM

Maybe you should take the (Finalize) and (Virtual Tests) away from all projects and include your PEFactory in Winbuilder.

Hey why have CAPI included in each project when you could include that in Winbuilder too....

That is a bit OFFTOPIC in a discussion about documentation, but nevertheless:

WinBuilder has a lot of single commands, getting parameters with the command. Having ONE PEFactory command containing all the necessary parameters for different projects, would need multi-page wizard for this command. Seriously: It is not wise to replace the simple command functionality by some built in complex functionality.

Many of the CAPI functions could be replaced by WinBuilder commands, like _calculate.
But the CAPI functions are historic, and from a time where the current WB commands did not exist yet.
To replace the runnging CAPI use by intrinsic WB commands, can bring a bit speed increase, but can also cause a lot of troubles.

How about Main Configuration? Or PreConfig?????

Some Main Configuration definitions about the final PE build, e.g. grub4dos use, multiboot creation, etc., are currently simply ignored, and redefined in the PEFactory.
Other definitions about "Run from RAM" are passed as properties and used, but can be overwritten in the PEFactory.
PostConfig is replaced by PEFactory functionality ("Delete Finalize Folder")

Peter




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users