Project:Package Builder
Version:5.x-1.0
Component:User interface
Category:feature request
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

Hi,

think maybe you can move the "add project" UI component to the top of the project list? When you're adding lots of modules, it means lots of scrolling down in between updates, which is mildly annoying. I've added only two so far and already I'm compelled to add this issue :)

Comments

#1

Status:active» fixed

Good call. I too was scrolling a lot to add projects and it didn't even occur to me to move some form elements around. It will show up in the 1.1 release.

#2

Haha...

Nice one :)

BTW, do check out the Install Profile API - it provides other stuff and you may be duplicating each others work.

#3

One step ahead of ya, chief. Prior to my work on this module I had been working with both installation profile modules: Profile Generator & Install Profile API. In the original development, I was using Package Builder as an add on to these modules. About halfway through it occurred to me that it much easier to build Drupal packages with installation profiles if I could just request new versions of modules right off of d.o.

I look at this module as a complement to, not replacement of, these modules. Both these modules to a good job of creating a Installation Profile, but the problem is you still have download Drupal & the needed modules to make use of the installation profile. This module was created to eliminate this last step. With the profile generator modules you can generate the PHP code to insert into the Package Builder's Profile PHP field. From there, you have a tool that can take that automate the process of downloading & bundling modules with a Drupal package that contains your installation profile.

#4

Okay... Soooo rather than have to use the interface to select each module, why not make it so that it picks up install profile module lists and automatically inserts them, once you've selected a version...?

Is that feasible and clever, or just nonsense?

#5

The list of modules that the installation profiles output are just the module names, not project names. Without knowing the project short name, there's no way to retrieve release information (or the project tarballs) from drupal.org. If you're already going to have to manually add the short name to retrieve each project, you might as well just specify which modules to enable on the same form. Or so my thinking goes about this matter.

Since each module name is stored in Package Builder, it's very likely you could do something like this. I'm not going to do it since Package Builder already accomplishes what I set out to do. However, if anyone was willing to create a patch that would implement such interoperability between Package Builder & these profile builders, I wouldn't be opposed to adding it to the project.

#6

Status:fixed» closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

nobody click here