Wedge
Public area => The Pub => Off-topic => Topic started by: becometa on May 8th, 2012, 09:11 PM
-
Hi there,
I've been following the progress of wedge till very beginning, but as an inactive on forums..
I am pleasantly surprised at Wedge!
But however, now I would like to know whether there are any plans of releasing a bunch of bridges between other softwares - like CMSes, i mean Drupal, Joomla!, Mambo, Wordpress or even MediaWiki - when the wedge is going to be given into the hands of the community.
I'm asking as a person without programming experience, as a someone disappointed with the attitude of the SMF developers(http://custom.simplemachines.org/bridge_request.php)..as far as I know, SMF does not currently have any developers working on bridges....
-
It's unlikely. Part of the problem is the licenses of the other systems, they don't work all that well with the current (and likely future) licence of Wedge.
I should also add that it's incredibly unlikely that we'll ever write bridges for Drupal or Joomla, having actually tried to USE those, they confuse me, which should give you some idea of how complicated I find them to use, and if that's how the user-experience is, imagine how complicated the code is going to be. Wedge is not designed for bridging, especially when in all honesty you could do a much better job not bridging but building a CMS on top of Wedge.
-
Damn, my nightmares came true.
you could do a much better job not bridging but building a CMS on top of Wedge.
This requires skill in programming.
Fyi, drupal's really not as that bad how it is drawn, really - I say this as newb in it.
I think that the Drupal in conjuction with a real forum software like SMF or even better like Wedge would be a great foundation for most communities - but, that's my personal point of view.
I though that building software bridges could be easier because of hooks(API and SSI) that powers SMF and Wedge(?).
Concluding - I understand that there's a need to look for someone familiar in drupal to build this - likely within a cash contract.
-
And it would require FAR FAR more skill to write a bridge than it would to write a CMS on top of Wedge. Seriously. (Bear in mind that some folks I work with have been discussing building their own CMS because they find their customers can't use Drupal)
Fyi, drupal's really not as that bad how it is drawn, really - I say this as newb in it.
And I've been developing websites for over a decade and I find it incredibly complicated to set up even a simple site - and that's before I even think about trying to code for it (which I assure you is enough to make you cry in frustration)I though that building software bridges could be easier because of hooks(API and SSI) that powers SMF and Wedge(?).
Except that bridges don't work that way when you're trying to bridge a CMS and a forum, because you invariably want to contain the forum inside the CMS layout, which means running all of Wedge's code - except the little tiny bits you don't want it to.
Why do you think the bridges for CMSes haven't been updated in years? It's not merely a lack of interest.
-
I think a plugin for static pages and hierarchy for these static pages would do just fine in turning Wedge into something more CMS-like.
-
Here I thought it was just me being dumber then a box of rocks when I couldn't figure out Drupal and Joomla.
-
becometa, I would recommend when wedge is released approach your CMS flavor about writing an Authentication module for Wedge for there CMS. Most CMS's authentication is modular now so it would be the easiest way to connect the systems.
-
Authentication is only really a tiny part of the process. What's really useful is interconnection at a deeper level.
Also to answer the point earlier about hooks, the hooks are for Wedge to call things, not for things to call Wedge. Same is true for SMF and isn't going to change any time soon.
-
Authentication is only really a tiny part of the process. What's really useful is interconnection at a deeper level.
Also to answer the point earlier about hooks, the hooks are for Wedge to call things, not for things to call Wedge. Same is true for SMF and isn't going to change any time soon.
I don't disagree, though smart use of Authentication + SSI + simlar themes/skins/whatever the design element is called will provide most of the functionality most sites want from bridges.
Anyway my main point is it doesn't have to be Wedge doing the heavy lifting to provide the basic functionality. Little ingenuity and imagination cal solve most basic needs.
-
Can we have a bridge for SMF? :eheh: :whistle:
-
Authentication is only really a tiny part of the process. What's really useful is interconnection at a deeper level.
Also to answer the point earlier about hooks, the hooks are for Wedge to call things, not for things to call Wedge. Same is true for SMF and isn't going to change any time soon.
I don't disagree, though smart use of Authentication + SSI + simlar themes/skins/whatever the design element is called will provide most of the functionality most sites want from bridges.
Anyway my main point is it doesn't have to be Wedge doing the heavy lifting to provide the basic functionality. Little ingenuity and imagination cal solve most basic needs.
exactly!
-
Can we have a bridge for SMF? :eheh: :whistle:
lmao