Some PackMan Questions

@BobRay:

Until today, I've only seen the old one. (This is my fault, though as you mentioned this is my post on RO.IDEs.)

Can I substitute chocolate for the beer?

I suppose... it's your loss though. I'd rather have chocolate AND beer. But I'm diabetic, so chocolate is out.

They make some pretty good sugar-free chocolate. Diabetics aren't supposed to drink beer, either. Enough cheese and chocolate and I'm flying for the rest of the day! Casein and caffeine!

Diabetics aren't supposed to drink beer, either.

Depends on the beer and quantity.

They make some pretty good sugar-free chocolate.

Yes, but it always makes me sick for a day. I have that intolerance thing.

@Fuzzical Logic & @BobRay:

Hi guys, I'm using PackMan at the moment to quickly create and continuously update packages containing chunks, templates and TVs so I can roll out websites to my clients with efficiency. There's still some stuff to desire from PackMan just like you guys have said though, so what you're up to sounds awesome – I'll put my faith in you two to improve PackMan or create a GUI for myComponents and subscribe to this thread whilst holding my breath (although it makes "step 1" a bit trycky)

@Sketchi
I personally think best of both worlds would be awesome. Of course, I always have my own take on things. I certainly don't want to step on anyone's toes, but I also want an easy way to build transport packages. I would also like some expanded features, though not many.

@BobRay:
The new MyComponent is pretty awesome, so far! I can't wait for a GUI!

I'll probably develop independently of BobRay (hopefully with some of his awesome guidance) and then compare and contrast. This is a purely selfish endeavor as my little packages won't be a problem, but RO.IDEs is kind of another matter and will require a lot of work.

The new MyComponent really has only one config file that you have to edit for each project (and one line in another file that specifies which project you are working on). Including the file returns a PHP array with all the settings, but it's premature to be building a GUI for it now, because there are a number of changes yet to come.

If you have all the code written for an extra, I think you could easily create a transport file for it in less than an hour and update it in about 5 minutes. That said, I have yet to test it on a real project (though it's passing all the unit tests at present).


@fuzzicallogic: I would hate to have us both end up with competing extras that do the same thing, especially since I've already spent several hundred hours on MyComponent. I love it when people contribute to my extras by sending me bug reports or fixes and new features to integrate, but I'm not crazy about them doing major refactoring. I don't have the spare time to evaluate their work.



------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html



------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

@BobRay:

When I code alongside a project, I don't release my own independently if the other already fits the communities needs. (I don't like to compete if there's not a need) I also don't make adjustments to the primary codebase. I will add seperate modules instead. I find this makes my work more collaborative and gives the original coder the option to include or not include specific features, reduces the need for refactoring and evaluation, etc.

This is because, the way I do things in my own code often results in confusion. So, if I write my code as if it were an "addon" to the original code, its easier to just accept or deny. Even my own tutorials use techniques that make each compatible with each other, but not necessary. Ideally, if more than one extra needed to be released (which I strongly doubt), it would be to extend functionality, not dependency. In other words, I hate to "rewrite" code. I only do it when I feel that it is necessary. This is particularly true when I am fairly new to a community. [ed. note: fuzzicallogic last edited this post 14 years, 1 month ago.]

Quote from: BobRay at Aug 26, 2012, 07:23 PM

4. In the _build directory, edit the build.config.php file. Change line 10 to
$configFileName = 'myproject.config.php

@BobRay: I thought I'd give MyComponent a try but I got stuck at step 4 – I can't find build.config.php...?

(The build I downloaded from GitHub is called BobRay-MyComponent-ee8918c)