*Nuke integration into gallery...

MiiJaySung

Joined: 2003-04-30
Posts: 19

Posted: Sun, 2003-05-11 16:44

Is this going to happen ? If so what sort of details can you disclose ?

Also, what about Xaraya, the new PostNuke replacement, In a few weeks time, when I get the time, I plan to have a good dabble with the CMS, and it would be nice to see Gallery be able to run under that.

bharat

Joined: 2002-05-21
Posts: 7994

Posted: Tue, 2003-05-13 03:50

G2 will eventually support PostNuke in the same relatively seamless way that G1 does. My current plan is to provide add-on packs that work with a G2 install and provide a glue layer between the two. I believe I've worked out most of the technical details in my head, but I haven't committed it to media anywhere so I can't tell you more than that.

pawmarks

Joined: 2002-08-19
Posts: 19

Posted: Sun, 2003-05-18 22:37

bharat wrote:

G2 will eventually support PostNuke ....

Any chance there exists some cheat notes or hastily drawn thoughts on bolting G2 on to Xaraya? The built-in image property type is a great step forward but us Gallery fans are totally spoiled! 8)

bharat

Joined: 2002-05-21
Posts: 7994

Posted: Mon, 2003-05-19 06:51

Off the top of my head there are several things that we need to do. We need to create a new entry point into G2 that replaces main.php. This new entry point will be PostNuke/PHP-Nuke/Xaraya/Xoops/Drupal/etc. specific and will give us a way to interoperate between the two. Then we need to extend the database storage layer so that it understands that the user/group information is now stored in a different table/column arrangement so that our queries continue to function. Then we need disable certain functionality and provide some new templates for the administration console so that we can tie the G2 site admin interface into the CMS' admin system.

I'm envisioning shipping a snap-on pack for each CMS that converts your G2 install into one that works for the specific CMS. It'll work by adding new files/modules to the G2 install (but not replacing existing files). I also haven't done any work on it yet so I've got nothing to show .. yet. Don't worry, it's coming.

pawmarks

Joined: 2002-08-19
Posts: 19

Posted: Mon, 2003-05-19 13:46

bharat wrote:

We need to create a new entry point into G2 that replaces main.php. Then we need to extend the database storage layer so that it understands that the user/group information is now stored in a different table/column arrangement so that our queries continue to function. Then we need disable certain functionality and provide some new templates for the administration console so that we can tie the G2 site admin interface into the CMS' admin system.

I'm envisioning shipping a snap-on pack for each CMS

Excellent! Please advise when it's appropriate/logical to scare up some Xaraya developer resources for this effort. As the beta begins to stabilize, tunnel vision on the core should relax a bit.

MiiJaySung Joined: 2003-04-30 Posts: 19	Posted: Sun, 2003-05-11 16:44
	Is this going to happen ? If so what sort of details can you disclose ? Also, what about Xaraya, the new PostNuke replacement, In a few weeks time, when I get the time, I plan to have a good dabble with the CMS, and it would be nice to see Gallery be able to run under that.
	XUser login Username: * Password: * Create new account Request new password
bharat Joined: 2002-05-21 Posts: 7994	Posted: Tue, 2003-05-13 03:50
	G2 will eventually support PostNuke in the same relatively seamless way that G1 does. My current plan is to provide add-on packs that work with a G2 install and provide a glue layer between the two. I believe I've worked out most of the technical details in my head, but I haven't committed it to media anywhere so I can't tell you more than that.

pawmarks Joined: 2002-08-19 Posts: 19	Posted: Sun, 2003-05-18 22:37
	bharat wrote: G2 will eventually support PostNuke .... Any chance there exists some cheat notes or hastily drawn thoughts on bolting G2 on to Xaraya? The built-in image property type is a great step forward but us Gallery fans are totally spoiled! 8)

bharat Joined: 2002-05-21 Posts: 7994	Posted: Mon, 2003-05-19 06:51
	Off the top of my head there are several things that we need to do. We need to create a new entry point into G2 that replaces main.php. This new entry point will be PostNuke/PHP-Nuke/Xaraya/Xoops/Drupal/etc. specific and will give us a way to interoperate between the two. Then we need to extend the database storage layer so that it understands that the user/group information is now stored in a different table/column arrangement so that our queries continue to function. Then we need disable certain functionality and provide some new templates for the administration console so that we can tie the G2 site admin interface into the CMS' admin system. I'm envisioning shipping a snap-on pack for each CMS that converts your G2 install into one that works for the specific CMS. It'll work by adding new files/modules to the G2 install (but not replacing existing files). I also haven't done any work on it yet so I've got nothing to show .. yet. Don't worry, it's coming.

pawmarks Joined: 2002-08-19 Posts: 19	Posted: Mon, 2003-05-19 13:46
	bharat wrote: We need to create a new entry point into G2 that replaces main.php. Then we need to extend the database storage layer so that it understands that the user/group information is now stored in a different table/column arrangement so that our queries continue to function. Then we need disable certain functionality and provide some new templates for the administration console so that we can tie the G2 site admin interface into the CMS' admin system. I'm envisioning shipping a snap-on pack for each CMS Excellent! Please advise when it's appropriate/logical to scare up some Xaraya developer resources for this effort. As the beta begins to stabilize, tunnel vision on the core should relax a bit.

*Nuke integration into gallery...

XUser login